Fuel Tank Confusion on Approach to Clearwater
A Piper Warrior's LEFT/RIGHT fuel selector and inadequate preflight planning create a power-loss emergency at low altitude near a non-towered field
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, on a local VFR flight. Elevation 71 ft MSL. The field is non-towered (CTAF 122.8); you self-announce on the common frequency. Runway 34 is 4,108 ft of asphalt, heading 335° magnetic. The off-field environment on the Runway 34 climb-out (heading 335°) is low-density development, medium development, and open developed areas (parks, large parking lots) — not ideal for a forced landing, but not water.
It is a clear, calm Florida morning: OAT 22°C, winds calm to light, visibility 10 SM. You filed no flight plan; this is a local 1.5-hour round trip. You are returning to KCLW after a 1-hour flight to a nearby field and back. The return flight was uneventful.
You are now 8 nm south of KCLW, descending through 1,200 ft MSL, on a heading of 335° to enter the pattern for Runway 34. You have been in the air for 1 hour 15 minutes total. The engine is running smoothly at 2,000 RPM, cruise power. You are planning to descend to pattern altitude (1,000 ft AGL, roughly 1,070 ft MSL at KCLW's 71 ft elevation) and enter a left downwind for Runway 34.
Aircraft: Piper PA-28-161 Warrior, solo, 48-gallon total fuel capacity (24 gallons per tank, LEFT and RIGHT). You did a preflight this morning and visually confirmed fuel in both tanks — they looked 'about half full' to you. You did not dip the tanks or use a fuel quantity gauge. You did not calculate fuel burn or plan tank switches. The fuel selector is currently on the LEFT tank.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown the Warrior before but are not type-current in the last 90 days. You are familiar with the LEFT/RIGHT fuel selector but have not given much thought to fuel management on a short local flight. You assumed the tanks were full or near-full and did not verify.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
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 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 pilot had inadequate preflight planning and fuel management, with contributing factors including headwinds and lack of wheel fairings. The accident resulted in a forced landing. The probable cause was the pilot's inadequate preflight planning and fuel management, which resulted in a total loss of engine power due to fuel exhaustion.
NTSB ERA09LA456 (2009): A Piper PA-28-161 on a local sightseeing flight experienced engine power loss during approach. The pilot executed a forced landing short of the runway. The accident resulted from the pilot's inadequate preflight inspection and failure to ensure an adequate quantity of fuel was available for the flight. The lesson: a visual fuel check ('looks about half full') is not a preflight inspection. Dip the tanks.
NTSB LAX06CA026 (2005): A Piper PA-28-161 on a 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 pilot had inadequate preflight and in-flight planning, miscalculated fuel consumption, and failed to divert to an alternate airport before the fuel situation became critical. 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.
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 had usable fuel in the right tank but did not switch back to it. The accident resulted from improper fuel management and failure to switch to the known-good tank, 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, requiring a forced landing that struck a dirt berm. The lesson: know which tank you are on, verify the selector position visually, and understand the fuel state of each tank before descent.
The common thread across all these accidents: the Piper Warrior's LEFT/RIGHT fuel selector requires active pilot management. There is no BOTH position. If one tank is empty and you switch to it, the engine will quit. Fuel exhaustion is not a mechanical failure — it is a planning and management failure. The accidents cited above occurred at other airports and in other aircraft — NOT at KCLW. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent lesson: (1) Dip both tanks during preflight, not just a visual check. (2) Calculate fuel burn and plan tank switches in advance (e.g., every 1.5 hours). (3) Before descent, switch to the tank with the most fuel and verify the selector position. (4) If power is lost at low altitude, establish best glide (73 KIAS) immediately and evaluate runway vs. off-field landing. (5) If fuel state is uncertain, divert before the situation becomes critical.
Key lesson — The Piper Warrior's 48-gallon fuel capacity (24 per tank) and LEFT/RIGHT selector demand active management. A visual fuel check is not a preflight inspection. Dip the tanks. Plan tank switches in advance. Before descent, switch to the fullest tank and verify the selector position. If the engine quits at low altitude, establish 73 KIAS best glide immediately. At KCLW, the off-field environment on the Runway 34 climb-out is low-density and medium development — survivable but not ideal. The runway is your best option if reachable. If not, commit to the best off-field landing and execute a controlled descent.
Debrief — teaching points
The Piper Warrior has LEFT and RIGHT fuel tanks with NO BOTH position — tank management is the pilot's job.
The Warrior's 48-gallon capacity (24 per tank) and LEFT/RIGHT selector require active pilot management. There is no BOTH position and no crossfeed system. If one tank is empty and you switch to it, the engine will quit immediately. This is not a design flaw; it is a design reality. You must know which tank you are on, verify the selector position visually, and understand the fuel state of each tank before descent. A 'looks about half full' visual check is not a preflight inspection — dip both tanks with a fuel stick or use a fuel quantity gauge.
Fuel exhaustion is a planning and management failure, not a mechanical failure.
The NTSB accidents cited above (ERA11CA423, ERA09LA456, LAX06CA026) all resulted from inadequate preflight planning and fuel management. The pilots did not dip the tanks, did not calculate fuel burn, did not plan tank switches, and did not verify fuel state before descent. The Warrior's 48-gallon capacity at a typical cruise burn of 8–9 gal/hr gives roughly 5–6 hours of endurance — plenty for most local flights. But if you do not know how much fuel you have, you cannot plan the flight. Dip the tanks. Calculate fuel burn. Plan tank switches.
Plan tank switches in advance — do not wait until descent to manage fuel.
A common practice is to switch tanks every 1.5 hours of flight. This balances tank depletion and ensures you know which tank is feeding the engine. Before descent, switch to the tank with the most fuel and verify the selector position visually. This is not optional — it is the correct procedure. If you do not know which tank has more fuel (because you did not dip them), divert to a nearby airport before descent becomes critical.
The Warrior's fuel gauge is notoriously unreliable — do not rely on it for per-tank data.
The Warrior's fuel quantity gauge gives a rough total fuel indication, but it does not reliably distinguish between LEFT and RIGHT tanks. A gauge reading of 'half tank' tells you the total is roughly 24 gallons, but it does not tell you whether the LEFT tank has 20 gallons and the RIGHT has 4, or vice versa. Dip the tanks. The fuel stick is the only reliable way to know per-tank fuel quantity.
At KCLW, the off-field environment on Runway 34 climb-out is low-density and medium development — not water, but not ideal.
The off-field environment off Runway 34's departure end (heading 335°) is low-density development, medium development, and open developed areas (parks, large parking lots). This is survivable terrain for a forced landing, but it is not a wide-open field. If the engine quits on the Runway 34 departure, establish best glide (73 KIAS) immediately and evaluate whether you can return to the airport or commit to the best off-field landing. Off Runway 16 (heading 155°), the environment is dense development — worse. Know the off-field environment before you line up on the runway.
Best glide in the Warrior is 73 KIAS — establish it immediately if the engine fails.
At 73 KIAS best glide, the Warrior glides roughly 0.3–0.4 nm per 1,000 ft of altitude. At 600 ft AGL on base for Runway 34, you have roughly 30 seconds of glide time and can cover roughly 0.3–0.4 nm. The runway is roughly 0.5 nm away on base — reachable if you can make a shallow turn and align. If the engine quits, lower the nose to 73 KIAS, trim for hands-off flight, and evaluate the runway vs. off-field landing. Do not attempt hard turns that risk a stall at low altitude.
Built from the real accident record
Scenario built from NTSB CEN22LA324 (2022 PA-28-161 fuel exhaustion), ERA11CA423 (2011 PA-28-161 fuel exhaustion on 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 (fuel starvation during descent), WPR12LA023 (fuel selector mismanagement), and ERA17LA205 (fuel starvation on approach). Anonymized and localized to KCLW.
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.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.151
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 KCLW