FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

Fuel Gauge Ambiguity on Approach

A Piper Warrior's fuel selector and quantity uncertainty — the decision window closes fast

Piper Warrior · Sarasota Bradenton International Airport (KSRQ) · Private · Approach / Landing

The scenario

Departing Sarasota Bradenton International Airport (KSRQ), Sarasota/Bradenton, FL — Runway 14, a 2.5-hour local flight in the Piper Warrior (PA-28-161). Elevation 30 ft MSL. The field is towered, Class C airspace, ceiling 4,000 ft MSL. Runway 14 is 9,500 ft of asphalt; off-field environment on the climb-out (heading 134°) is dense development, low-density development, and medium development — not ideal for a forced landing, but not water.

It is a clear, calm Florida morning: OAT 22°C, winds calm to light, altimeter 30.02. Visibility 10+ SM. You are a Private pilot, roughly 180 hours total, current and proficient. You have flown this Warrior before; it is the school's workhorse trainer.

Preflight: You visually checked the fuel tanks — both appeared full to the filler neck. You did not use a fuel sampler or dipstick; the visual check looked good. The fuel quantity gauges in the Warrior are steam-driven mechanical indicators, notoriously unreliable. You know this. You did not dip the tanks. You noted the flight time would be 2.5 hours; the Warrior burns roughly 8 GPH at cruise. That is 20 gallons for the flight, well within the 48-gallon usable capacity. You filed no flight plan; this is a local VFR flight.

Cruise: You climbed to 2,500 ft MSL, set cruise power, and flew a local tour — over the Keys, along the coast, inland to some familiar landmarks. The flight was smooth and uneventful. You did not switch fuel tanks during the flight; you left the fuel selector on LEFT. The Warrior's fuel selector is LEFT / RIGHT (no BOTH position) — tank management is your job, and you did not manage it.

Now: You are on a 10-mile straight-in approach to Runway 14, descending through 1,500 ft MSL. ATC has cleared you to land. The left fuel tank gauge reads roughly 1/4 tank. The right tank gauge reads empty. You have been flying for 2 hours 35 minutes. You have not switched tanks. You are 8 minutes from touchdown.

The decision

Before we get into the decision tree — what do you know about the Piper Warrior's fuel system and fuel management? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB CEN22LA324 (2022): A Piper PA-28-161 on a personal flight experienced total engine power loss due to fuel exhaustion and made a forced landing on an interstate roadway. The probable cause was fuel exhaustion; the student pilot was operating the aircraft while intoxicated. The accident resulted in injury.

NTSB ERA11CA423 (2011): A Piper PA-28-161 experienced total engine failure due to fuel exhaustion during a missed approach after a 4-hour 43-minute flight. The probable cause was the pilot's inadequate preflight planning and fuel management, with contributing factors including headwinds and lack of wheel fairings (which reduced cruise speed and increased flight time). The pilot did not account for headwind or reserve fuel.

NTSB ERA09LA456 (2009): A Piper PA-28-161 on a local sightseeing flight experienced engine power loss during approach and the pilot executed a forced landing short of the runway. The probable cause was the pilot's inadequate preflight inspection and failure to ensure an adequate quantity of fuel was available for the flight. The pilot did not dip the tanks; the visual check was insufficient.

NTSB LAX06CA026 (2005): A Piper PA-28-161 on a personal cross-country flight from Odessa to Prescott exhausted its usable fuel after 5.7 hours of flight at a burn rate exceeding the aircraft's 48-gallon capacity. The probable cause was the pilot's inadequate preflight and in-flight planning, his inadequate fuel consumption calculations, and his failure to divert to an alternate airport before the fuel situation became critical. The pilot did not account for headwind or reserve fuel.

NTSB ERA12FA002 (2011, FATAL): A Temco GC-1B Swift experienced total loss of engine power over the Chesapeake Bay and ditched in the water after a controlled glide. The probable cause was the pilot's improper fuel management in that he did not verify the fuel selector position before flight or after the power loss, resulting in fuel starvation. The pilot had fuel in the other tank but did not switch.

NTSB ANC17LA043 (2017): A Cessna T207 on a Part 135 scheduled commuter flight lost all engine power during approach due to fuel starvation and made a controlled ditching near Coghlan Island. The probable cause was total loss of engine power due to fuel starvation, with contributing factors including unreliable fuel quantity indicators and a company history of fuel management issues. The crew relied on gauges instead of dipstick checks.

NTSB LAX97LA278 (1997): A Cessna 150G on a banner towing operation lost engine power and ditched in the Pacific Ocean off California. The probable cause was fuel starvation caused by the pilot's mismanagement of the aircraft's fuel supply, specifically forgetting to switch to the auxiliary tank as required by operating procedures. The pilot had fuel available but did not switch tanks.

NTSB LAX98LA168 (1998): A Cessna T210M ditched in the Pacific Ocean 2 miles south of Santa Barbara after engine failure on final approach. The probable cause was the pilot's mismanagement of fuel through improper fuel tank selector positioning. The pilot did not verify fuel quantity before departure or maintain proper selector positioning.

The consistent thread: fuel exhaustion and starvation in light aircraft are almost always pilot errors. The Piper Warrior's LEFT / RIGHT selector with no BOTH position makes tank management the pilot's explicit responsibility. Fuel gauges are unreliable — dipstick checks are the standard. Switching tanks every 30–45 minutes during flight is mandatory. Verifying fuel selector position before takeoff and immediately after any power loss is non-negotiable. The real accidents cited above occurred at other airports and in other aircraft — NOT at KSRQ. But the off-field environment at KSRQ (dense development off Runway 14, open water off Runway 22) makes fuel mismanagement particularly consequential here.

The scenario is localized to KSRQ to make the approach environment real and consequential for you as a student here. Runway 14's climb-out environment (heading 134°) is dense development — not ideal for a forced landing. Runway 22's climb-out environment (heading 218°) is open water — a forced landing there is a ditching. Know your off-field options before you depart.

Key lesson — In the Piper Warrior, fuel management is not optional. The LEFT / RIGHT selector requires active switching every 30–45 minutes during flight. Fuel gauges are mechanical and unreliable — dipstick checks before every flight are the standard. Verify fuel selector position before takeoff and immediately after any power loss. At KSRQ, an engine failure on approach due to fuel mismanagement means a forced landing in dense development (Runway 14) or a ditching in open water (Runway 22). The decision window is measured in minutes — not hours.

Debrief — teaching points

The Piper Warrior's fuel selector is LEFT / RIGHT with no BOTH position — tank management is your job.

Unlike Cessnas with a BOTH position, the Warrior requires you to actively select LEFT or RIGHT throughout the flight. Standard practice is to switch tanks every 30–45 minutes to balance fuel consumption and ensure you don't run one tank dry while the other has fuel. Forgetting to switch, or switching to an empty tank, is a classic Warrior fuel starvation accident. The NTSB LAX97LA278 (banner tow) and ERA12FA002 (Chesapeake Bay ditching) cases both involved pilots who had fuel in the other tank but did not switch.

Fuel quantity gauges in the Warrior are mechanical and notoriously unreliable — dipstick checks are the standard.

The Warrior's steam-driven fuel quantity indicators can read optimistically, pessimistically, or anywhere in between. A visual check at the filler neck (looking at the fuel level) is better than nothing, but a dipstick check — actually measuring the fuel depth in each tank with a calibrated stick — is the only reliable method. NTSB ERA09LA456 (sightseeing flight) and ANC17LA043 (T207 commuter) both involved pilots who relied on gauges instead of dipsticks and ran out of fuel. Dip both tanks before every flight. Write down the numbers. Plan your flight based on dipstick readings, not gauge readings.

Verify fuel selector position before takeoff and immediately after any power loss.

Before you line up on the runway, visually confirm the fuel selector is in the position you intend (LEFT or RIGHT). If the engine quits or runs rough in flight, your first action after checking the engine instruments is to verify the fuel selector position — it may have been bumped or you may have forgotten to switch. NTSB ERA12FA002 (Swift ditching) involved a pilot who did not verify selector position before flight or after the power loss; he had fuel in the other tank but did not switch. This is a simple, life-saving check.

Plan your flight with a fuel reserve and account for headwind.

The Warrior has 48 gallons usable fuel and burns roughly 8 GPH at cruise. That is 6 hours of endurance in still air. But headwind reduces your ground speed and increases flight time. A 2.5-hour local flight with a 10-knot headwind becomes 2.9 hours — 23 gallons of fuel, leaving only 25 gallons as a reserve. NTSB ERA11CA423 (4-hour 43-minute flight) and LAX06CA026 (5.7-hour cross-country) both involved pilots who did not account for headwind or reserve fuel. Always plan with a 30-minute reserve minimum (4 gallons in the Warrior). If the flight is going to consume more than 44 gallons, divert to an alternate airport before the fuel situation becomes critical.

At KSRQ, an engine failure on approach due to fuel mismanagement is a forced landing in dense development or a ditching in open water.

Runway 14's climb-out environment (heading 134°) is dense development, low-density development, and medium development — not ideal for a forced landing, but survivable. Runway 22's climb-out environment (heading 218°) is open water and low-density development — a forced landing there is a ditching. Runway 04's climb-out environment (heading 38°) is marginal — medium development, wooded wetland, low-density development. Runway 32's climb-out environment (heading 314°) is poor — medium development, dense development, marsh. Know your off-field options before you depart. Fuel mismanagement that leads to an engine failure on approach at KSRQ is not a minor mistake — it is a forced landing or ditching.

Built from the real accident record

Scenario built from NTSB CEN22LA324, ERA11CA423, ERA09LA456, LAX06CA026 (PA-28-161 fuel exhaustion events), and regional precedents ERA12FA002, ANC17LA043, LAX97LA278, LAX98LA168 (fuel starvation in light aircraft). Anonymized and localized to KSRQ.

NTSB reports: CEN22LA324 · ERA11CA423 · ERA09LA456 · LAX06CA026 · ERA12FA002 · ANC17LA043 · LAX97LA278 · LAX98LA168

ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Inspection · PA.II.B — Engine Starting / Systems Preflight · PA.III.A — Normal Takeoff and Climb · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.103 · §91.151

Run this scenario yourself

Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.

Open the interactive scenario →

All sample scenarios · More Piper Warrior scenarios · More scenarios at KSRQ