Fuel Tank Confusion on the Approach
A Piper Archer's LEFT/RIGHT fuel selector, a low-fuel descent, and the cost of inattention to tank management
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, a 3.5-hour cross-country flight to a nearby airport. Elevation 71 ft MSL. KCLW is non-towered (CTAF 122.8); you are in Class G airspace, overlaid by Tampa Class B above 3,000 ft MSL.
You filed a VFR flight plan, checked weather (clear skies, light winds from the east, visibility 10+ SM), and completed a thorough preflight. Fuel: both tanks full at departure, 39 gallons usable total (left tank 19.5 gal, right tank 19.5 gal). You planned a 3.5-hour flight with a 30-minute reserve — well within limits.
The flight has been uneventful. You are now 3 hours 15 minutes into the flight, descending toward the destination airport. Fuel gauges show: left tank approximately 2 gallons remaining, right tank approximately 3 gallons remaining. You have been flying on the left tank for the past 1.5 hours without switching. The fuel selector is currently in the LEFT position.
You are at 2,500 ft MSL, 8 nm from the destination, beginning a descent to pattern altitude. The weather remains clear. You have not yet contacted the destination airport on CTAF. You are focused on the descent and approach setup.
Aircraft: Piper PA-28-181 Archer, solo, within weight and balance limits. Lycoming O-360-A carbureted engine, fixed-pitch prop, fixed gear, LEFT/RIGHT fuel selector (no BOTH position). Steam/vacuum panel. Nothing was written up; the airplane was airworthy at departure.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown the Archer before but are not type-current. You did not establish a formal fuel-tank switching schedule before departure; you simply flew on the left tank and did not monitor tank status closely during cruise.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you 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 aircraft impacted trees and terrain. The probable cause was fuel starvation caused by improper in-flight fuel management by the pilots. The PA-28-181 has a LEFT/RIGHT fuel selector with no BOTH position — one tank feeds the engine at a time. Improper switching or failure to switch tanks led to starvation.
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 switch tanks during the approach, and the leak drained the selected tank.
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 fuel system was compromised by maintenance error, not pilot error — but the outcome was the same: total power loss at low altitude.
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 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 appropriately during the flight.
The regional precedents (WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205) show a consistent pattern: fuel starvation in single-engine aircraft with LEFT/RIGHT selectors (or in aircraft where one tank is selected) is often caused by pilot failure to switch tanks, failure to monitor tank status, or failure to switch to the fullest tank during descent and approach. The engine quits with no warning — there is no gradual roughness or power loss. It is a total power loss.
At KCLW, the off-field environment off Runway 34 (heading 335°) is low-density and medium development — scattered houses, small roads, some open areas. A forced landing off-field is survivable if you find an open area, but it is not ideal. The runway is the preferred landing surface. The real accidents cited above occurred at other airports — NOT at KCLW. The scenario is localized to KCLW to make the fuel-management decision real and consequential for you as a student here.
The consistent thread across all these events: fuel starvation in the PA-28-181 is a total power loss with no warning. The fix is simple: establish a fuel-switching schedule BEFORE departure (e.g., switch every 1 hour, or every 1.5 hours), monitor tank status continuously during cruise, and switch to the fullest tank during descent to ensure adequate fuel pressure and flow for the approach and landing. Complacency and inattention are the killers.
Key lesson — The Piper Archer has a LEFT/RIGHT fuel selector with no BOTH position. One tank feeds the engine at a time. Fuel starvation is a total power loss with no warning. Establish a fuel-switching schedule BEFORE departure, monitor tank status continuously, and switch to the fullest tank during descent. At KCLW, an engine failure at low altitude during approach leaves you with a forced landing — either on the runway (if you have enough altitude) or off-field in low-density development. The decision window is measured in seconds.
Debrief — teaching points
The Archer has LEFT/RIGHT fuel selector — there is NO BOTH position.
Unlike the Cessna 172 (which has a BOTH position), the Piper Archer's fuel selector is LEFT or RIGHT. One tank feeds the engine at a time. If you fly on one tank for too long without switching, that tank will run dry and you will experience fuel starvation — a total power loss with no warning. The engine does not sputter or run rough; it quits. Establish a fuel-switching schedule BEFORE departure (e.g., switch every 1 hour, or every 1.5 hours) and stick to it.
Fuel starvation is a total power loss — there is no gradual warning.
Unlike carburetor ice (which shows as engine roughness and a dropping tachometer), fuel starvation in the Archer is sudden and complete. The engine quits. There is no time to troubleshoot or recover. At low altitude during approach, a total power loss means a forced landing — either on the runway (if you have enough altitude) or off-field. The only defense is prevention: monitor tank status continuously and switch tanks appropriately.
During descent and approach, switch to the FULLEST tank.
As you begin descent, check your fuel gauges and switch to the tank with the most fuel. This ensures adequate fuel pressure and flow for the approach and landing. If you have been flying on one tank for an extended period and it is nearly empty, switching late in the approach is risky — the tank may run dry during the landing. Switch early, during the initial descent, not on short final.
Monitor tank status continuously during cruise.
Scan your fuel gauges as part of your regular instrument scan. Note the fuel level in each tank every 15–20 minutes. If the tanks are becoming unequal (one tank is draining faster than the other), investigate the cause. A fuel leak, a stuck fuel selector, or a crossfeed malfunction can cause unequal tank depletion. Catching this early gives you options; discovering it at low altitude during approach does not.
At KCLW, the off-field environment off Runway 34 is low-density and medium development.
The off-field environment off Runway 34's climb-out heading (335°) is scattered houses, small roads, and some open areas — not ideal for a forced landing. The runway is the preferred landing surface. If you experience an engine failure at low altitude during approach to KCLW, your priority is reaching the runway. At 800–1,000 ft AGL with 2 nm to the runway, best glide (76 KIAS) will get you there — maintain the speed and aim for the runway.
Fuel starvation from improper tank selection is the dominant accident pattern at KCLW.
KCLW's accident history shows FUEL_STARVATION as 11.1% of accidents — a significant portion. Most of these are caused by pilot failure to switch tanks, failure to monitor tank status, or failure to switch to the fullest tank during descent. This is a preventable accident. Establish a fuel-switching schedule, monitor tank status, and switch to the fullest tank during descent. Do not become a statistic.
Built from the real accident record
Scenario built from NTSB NYC08FA020 (2007 PA-28-181 fuel starvation / improper fuel management), CEN24LA050 (2023 PA-28-181 fuel starvation on final approach), WPR23LA203 (2023 PA-28-181 fuel starvation after takeoff), CEN21LA383 (2021 PA-28-181 fuel starvation / mismanagement), and regional precedents WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205. Localized to KCLW.
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.II.A — Preflight Assessment · PA.II.B — Engine Starting / Systems Preflight · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
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 KCLW