Fuel Tank Confusion on Descent
Improper fuel selector management and a power loss on approach — the decision window is measured in seconds
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, on a personal cross-country flight to a field 120 nm northeast. Elevation 76 ft MSL. It is a clear, calm morning; OAT 18°C, altimeter 30.02. Visibility 10+ SM. Winds calm to light.
You are a Private pilot with roughly 250 hours total time, about 80 hours in the Piper Archer. You have flown this airplane before, but not recently — your last flight was 6 weeks ago. The airplane has been in the school's fleet and was last flown by another instructor yesterday. You did a standard preflight: visually checked both fuel tanks (they appeared full to the filler neck), confirmed the fuel selector was on LEFT, and ran the engine on the ground. Everything looked normal.
You depart Runway 09 at 0845 local, climb to 3,500 ft MSL (well below the overlying Tampa Class B floor of 6,000 MSL), and cruise northeast at 100 KIAS. The flight is uneventful. At 1045 local, you are 2.5 hours into the flight, 85 nm from KBKV, and beginning descent to the destination field. You have not switched fuel tanks during the flight — you have been on the LEFT tank the entire time.
Aircraft: Piper PA-28-181 Archer, solo, full fuel at departure (both tanks appeared full). Carbureted Lycoming O-360-A, 180 hp, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Steam panel. The fuel selector has been on LEFT since before takeoff.
Pilot: you — a Private pilot, current, roughly 250 hours total, 80 hours in the Archer. You have not flown this specific airplane in 6 weeks. You did not establish a fuel tank switching plan before departure. You have not monitored fuel quantity closely during the cruise — the panel has analog fuel gauges, and you glanced at them occasionally but did not log the readings.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about fuel management in the Piper Archer? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC08FA020 (2007, FATAL): A Piper PA-28-181 on an instructional flight experienced a total loss of engine power during cruise near Boynton Beach, Florida. The probable cause was fuel starvation caused by improper in-flight fuel management by the pilots. The pilots did not establish a fuel tank switching plan before departure and did not actively manage which tank was feeding the engine. The airplane impacted trees and terrain. The accident was fatal.
NTSB CEN24LA050 (2023): A Piper PA-28-181 on a personal cross-country flight lost engine power on final approach near Minneapolis after 3.5 hours of flight. The probable cause was fuel starvation caused by a leaking left fuel tank drain with a deformed o-ring seal, compounded by pilot confusion about which tank was selected. The pilot did not know which tank was feeding the engine and did not switch tanks before the critical approach phase.
NTSB WPR23LA203 (2023): A Piper PA-28-181 lost engine power during initial climb after takeoff and made a forced landing to a soccer field, resulting in landing gear collapse and tree strike. The probable cause was fuel starvation caused by improper gascolator installation by maintenance personnel. The mechanic failed to properly secure the fuel system gascolator strainer bowl, allowing fuel to bypass the engine.
NTSB CEN21LA383 (2021): A Piper PA-28-181 during local flight with touch-and-go landings experienced engine roughness during a soft-field takeoff attempt, lost power, and the pilot made a forced landing. The probable cause was loss of engine power due to fuel starvation and the pilot's mismanagement of available fuel. The pilot did not switch tanks and ran one tank dry while the other tank had usable fuel.
The regional precedents (WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205) all show the same pattern: pilots failed to establish a fuel tank switching plan, did not actively manage which tank was feeding the engine, and either ran one tank dry or switched tanks too late in the approach. The common thread is complacency and inadequate fuel management discipline.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history (see field dominant patterns), but these specific fuel starvation 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 consistent lesson across all these events: the Piper Archer has a LEFT / RIGHT fuel selector with NO BOTH position. You must actively manage which tank is feeding the engine. Establish a fuel tank switching plan before departure (e.g., switch every 30–45 minutes). Switch tanks before descent to ensure you have usable fuel for the approach and a known tank selection for landing. Do not rely on analog fuel gauges — they are notoriously unreliable. Verify fuel quantity by visual inspection of the filler neck before departure. If the engine quits due to suspected fuel starvation, immediately switch to the other tank — it may have usable fuel.
Key lesson — The Piper Archer's LEFT / RIGHT fuel selector requires active pilot management. Establish a fuel tank switching plan before departure. Switch tanks before descent to ensure usable fuel for the approach. Do not rely on analog fuel gauges. If the engine quits, immediately switch to the other tank — it may restore power. At 600 ft AGL on short final, the decision window is measured in seconds.
Debrief — teaching points
The Archer has LEFT / RIGHT fuel selector — there is NO BOTH position.
Unlike some other aircraft (e.g., Cessna 172 with BOTH), the Piper Archer requires you to actively select which tank is feeding the engine. There is no BOTH position. This is a critical systems difference. If you forget to switch tanks or select the wrong tank, the engine will quit when that tank is empty or starved, even if the other tank has usable fuel. This is the dominant failure mode in Archer fuel starvation accidents.
Establish a fuel tank switching plan BEFORE departure.
Before you line up on the runway, plan when you will switch tanks during the flight. A common plan is to switch every 30–45 minutes, or at specific waypoints. Write it down on your flight plan or kneeboard. During the flight, follow the plan. Switching tanks at regular intervals ensures balanced fuel burn and prevents running one tank dry. It also ensures you know which tank is feeding the engine at any given time — critical information if the engine quits.
Switch tanks BEFORE descent, not during approach.
The correct time to switch tanks is before you begin descent — when workload is low and you have time to verify the switch is correct. Switching tanks during approach or on final is poor airmanship and introduces unnecessary risk during the critical landing phase. If the engine stumbles after a tank switch on final, you will not have time to diagnose and correct the problem. Establish a known tank selection before descent and maintain it through landing.
Analog fuel gauges in the Archer are notoriously unreliable.
The Archer's analog fuel quantity gauges can read full when a tank is nearly empty, or vice versa. Do not trust them. The most reliable method to determine fuel quantity is visual inspection of the filler neck before departure. If you cannot see fuel at the filler neck, the tank is not full. During flight, monitor fuel consumption by time and distance, not by gauge reading. If the gauge reading does not match your expected fuel consumption, trust the time/distance calculation, not the gauge.
If the engine quits due to suspected fuel starvation, immediately switch to the other tank.
If the engine quits and you suspect fuel starvation (not carburetor ice, not electrical failure), your first action is to switch the fuel selector to the other tank. The other tank may have usable fuel. If it does, the engine will restart within 5–10 seconds. If it does not, you have confirmed that both tanks are empty or starved, and you must execute a forced landing. But if the other tank has fuel, switching immediately may restore power and give you a chance to reach the runway.
At low altitude on approach, best glide speed is 76 KIAS — know this number.
If the engine quits at 600 ft AGL on short final, you must immediately establish best glide speed of 76 KIAS. This speed maximizes glide distance and gives you the best chance of reaching the runway or a safe landing spot. Slower speeds reduce glide distance; faster speeds reduce glide distance and increase impact energy. 76 KIAS is the number. Know it, and fly it if the engine quits.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28-181 fuel starvation / improper in-flight fuel management), CEN24LA050 (2023 PA-28-181 fuel starvation / leaking tank drain), WPR23LA203 (2023 PA-28-181 fuel starvation / gascolator installation failure), CEN21LA383 (2021 PA-28-181 fuel starvation / pilot mismanagement), and regional precedents WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205. Anonymized and localized to KBKV.
NTSB reports: NYC08FA020 · CEN24LA050 · WPR23LA203 · CEN21LA383 · WPR24LA167 · GAA19CA534 · WPR12LA023 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight · PA.II.C — Fuel System and Management
Relevant FARs: §91.3 · §91.13 · §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 Archer scenarios · More scenarios at KBKV