Fuel Tank Confusion on Descent
A Piper Warrior's LEFT/RIGHT selector, inadequate preflight planning, and a power loss during approach — the decision window is measured in minutes
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 2-hour local flight to a nearby airport and back. Elevation 76 ft MSL. The field is towered part-time (0700–2200 local); it is currently 1400 local and the tower is active. You are in Class D airspace with overlying Tampa Class B above 6,000 ft MSL.
It is a clear, calm Florida afternoon: OAT 26°C, winds light and variable, altimeter 29.95. Visibility 10 SM. A textbook VFR day. You filed no flight plan — this is a local flight, and you are familiar with the area.
Preflight: You visually inspected both fuel tanks and noted what appeared to be 'about three-quarters full' in each. You did not dip the tanks or record a specific fuel quantity. The Warrior's fuel system has two 24-gallon tanks (LEFT and RIGHT), with 48 gallons total usable fuel. At a cruise burn of roughly 8 gallons per hour, you calculated you had 'plenty of fuel' for a 2-hour round trip. You did not account for taxi, climb, or reserve.
Flight: You departed Runway 09 at 1400 local, climbed to 2,500 ft MSL (roughly 2,425 ft AGL), and cruised for 1 hour 45 minutes to the destination airport. You did not switch fuel tanks during the flight — you left the fuel selector on LEFT for the entire cruise. You did not monitor fuel consumption against a planned burn rate. You did not check the fuel quantity gauges during cruise.
Now, at 1545 local, you are 15 minutes out from KBKV on descent. You are at 1,500 ft MSL (roughly 1,425 ft AGL), configured for approach, when you notice the fuel quantity gauges are lower than you expected. The LEFT tank gauge reads roughly 1/8 tank. The RIGHT tank gauge reads roughly 1/4 tank. You have been on the LEFT tank for the entire flight.
Pilot: You — a Private pilot, current, roughly 180 hours total. You have flown the Warrior before, but fuel management has never been a focus of your training. You are not in a hurry, but you are committed to landing at KBKV. You have not declared an emergency. You have not advised the tower of any fuel concern.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you know about fuel management in the Piper Warrior PA-28-161? (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 — a compounding factor, but the root cause was fuel mismanagement.
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. The pilot did not account for headwind burn or plan fuel tank switching.
NTSB ERA09LA456 (2009): A Piper PA-28-161 on a local sightseeing flight experienced engine power loss during approach. The probable cause was the pilot's inadequate preflight inspection and failure to ensure an adequate quantity of fuel was available for the flight. A visual 'looks full' inspection was not adequate.
NTSB LAX06CA026 (2005): A Piper PA-28-161 on a personal cross-country flight 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 inadequate preflight and in-flight planning, miscalculation of fuel consumption, and failure to divert to an alternate airport before the fuel situation became critical.
NTSB GAA19CA534 (2019): A Piper PA-28 lost engine power during descent to land after the pilot switched to the left fuel tank and failed to follow the emergency power loss checklist. The pilot did not switch to the right tank containing usable fuel, leading to fuel starvation and a forced landing on a road.
NTSB WPR24LA167 (2024): A Harvard MK IV lost all engine power due to fuel starvation when the pilot improperly selected the left fuel tank at low fuel levels. The accident resulted from improper fuel tank selection and a malfunctioning fuel selector.
The consistent thread across all these events: the Piper Warrior's LEFT/RIGHT fuel selector demands active management. There is no BOTH position. Pilots who do not switch tanks at planned intervals, who do not dip tanks during preflight, and who do not monitor fuel consumption against a planned burn rate run one tank dry while the other has fuel. The engine quits. The forced landing follows. The real accidents cited above occurred at other airports and in other aircraft — NOT at KBKV. KBKV has its own accident history (see field dominant patterns), but these specific fuel-exhaustion events happened elsewhere. The scenario is localized to KBKV to make the fuel management decision real and consequential for you as a student here.
The off-field environment off Runway 09 at KBKV (heading 90°) is open developed areas, pasture, and medium development — a forced landing there is survivable but not guaranteed. Runway 09 is your best option if the engine fails on descent or approach. But the entire accident is preventable: switch fuel tanks at planned intervals (every 30–45 minutes), dip the tanks during preflight, and monitor fuel consumption against a planned burn rate. Do not rely on fuel quantity gauges — they are notoriously inaccurate in older aircraft like the Warrior.
Key lesson — The Piper Warrior's LEFT/RIGHT fuel selector has no BOTH position. The pilot must actively manage which tank is feeding the engine. Fuel exhaustion in the Warrior is always a result of inadequate preflight planning, failure to switch tanks at planned intervals, and failure to monitor fuel consumption. At KBKV, an engine failure on descent or approach is a forced landing in the off-field environment or on Runway 09. The accident is entirely preventable: dip the tanks during preflight, plan fuel tank switching intervals, and monitor fuel consumption against a planned burn rate. Switch tanks every 30–45 minutes. If the engine quits due to fuel starvation (one tank empty, the other full), switch the fuel selector to the full tank immediately — but only if you have altitude to recover.
Debrief — teaching points
The Warrior's fuel selector is LEFT / RIGHT — there is no BOTH position.
Unlike Cessnas, which have a BOTH position, the Piper Warrior requires the pilot to actively select which tank is feeding the engine. There is no automatic fuel balancing. If you leave the selector on LEFT for the entire flight, the LEFT tank will empty while the RIGHT tank remains full. At that point, if you do not switch to the RIGHT tank, the engine will quit. This is not a system failure — it is a design feature that demands pilot discipline. Fuel tank switching is not optional; it is mandatory.
Preflight fuel inspection must be accurate — visual 'looks full' is not adequate.
The Warrior has two 24-gallon tanks. A visual inspection cannot distinguish between 20 gallons and 24 gallons, or between 15 gallons and 20 gallons. Fuel tanks must be dipped with a calibrated stick to know the exact quantity before flight. Record the dip stick reading on your preflight checklist. If you do not know the exact fuel quantity, you cannot plan the flight accurately. A visual inspection is the first step; the dip stick is the verification.
Plan fuel tank switching intervals — typically every 30–45 minutes.
Establish a habit of switching fuel tanks at planned intervals during cruise. Set a timer if necessary. Alternate between LEFT and RIGHT every 30–45 minutes to balance consumption. This ensures that neither tank is depleted while the other has fuel. If you forget to switch, you run the risk of running one tank dry. At 8 gallons per hour burn, a 24-gallon tank will last 3 hours. On a 2-hour flight, you should switch at least once.
Monitor fuel consumption against a planned burn rate — do not rely on fuel gauges.
Fuel quantity gauges in the Warrior are notoriously inaccurate. They are an aid, not a reliable measure. Instead, plan your fuel consumption based on the POH burn rate (typically 8 gal/hr at cruise power) and monitor time elapsed. Calculate how much fuel you should have remaining at each checkpoint. If the actual fuel quantity is significantly different from the calculated amount, investigate the discrepancy. Headwinds increase burn rate; tailwinds decrease it. Account for taxi, climb, and reserve in your preflight planning.
Reserve fuel is not optional — plan for it in your preflight calculations.
The FAA requires 30 minutes of reserve fuel for day VFR flights (45 minutes for night VFR). This means that when you land, you should have at least 30 minutes of fuel remaining in the tanks. For the Warrior at 8 gal/hr, 30 minutes of reserve is 4 gallons. If you plan a 2-hour flight, you need 16 gallons for the flight plus 4 gallons for reserve — 20 gallons total. With 48 gallons usable, you have 28 gallons available for the flight. This is adequate, but it leaves little margin for headwinds or diversions. Always account for reserve in your preflight planning.
Declare low-fuel early — do not wait until the situation is critical.
If you realize during flight that your fuel situation is tighter than planned, declare low-fuel to ATC immediately. Do not wait until the engine is rough or the gauges are reading empty. ATC will give you priority handling and vector you to the nearest airport if necessary. A low-fuel declaration is not an emergency declaration — it is a precautionary communication that alerts ATC to your situation and allows them to help you manage the approach.
If the engine quits due to fuel starvation, switch the fuel selector to the full tank immediately.
If the engine quits and you suspect fuel starvation (one tank empty, the other full), switch the fuel selector to the full tank immediately. The engine may restart if you have altitude to recover. But this is a last resort — the correct approach is to prevent fuel starvation by switching tanks at planned intervals and monitoring fuel consumption. If you are at low altitude (below 1,000 ft AGL) when the engine quits, switching fuel tanks may not give you enough time to restart the engine and recover. The forced landing is the likely outcome.
Built from the real accident record
Scenario built from NTSB CEN22LA324 (2022 PA-28-161 fuel exhaustion), ERA11CA423 (2011 PA-28-161 fuel exhaustion during missed approach), ERA09LA456 (2009 PA-28-161 inadequate preflight fuel inspection), LAX06CA026 (2005 PA-28-161 fuel exhaustion cross-country), and regional precedents WPR24LA167 (fuel tank selection error), GAA19CA534 (PA-28 fuel starvation on descent), WPR12LA023 (fuel selector mismanagement), ERA17LA205 (post-maintenance fuel starvation). Localized to KBKV.
NTSB reports: CEN22LA324 · ERA11CA423 · ERA09LA456 · LAX06CA026 · WPR24LA167 · GAA19CA534 · WPR12LA023 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · 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.151 · §91.185
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 KBKV