Fuel Tank Confusion on Descent
A fuel selector mistake at low altitude near Zephyrhills — the margin between a precautionary landing and a forced landing is minutes
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 01, climbing out on a 360° heading. Elevation 90 ft MSL. It is a clear, calm Florida morning: OAT 18°C, altimeter 30.01, winds calm. Visibility 10 SM. A routine personal flight to a nearby airport, approximately 45 minutes cruise.
You are a commercial pilot with 850 hours total time, 200 hours in the Piper Arrow. You are familiar with the airplane's fuel system: LEFT and RIGHT tanks, each 37.5 usable gallons. The fuel selector is a three-position lever: LEFT, RIGHT, OFF. You have flown this airplane dozens of times. Complacency is a risk.
Preflight: You visually checked both fuel tanks — both appeared full to the filler neck. You did not dip the tanks with a fuel stick; you relied on the visual check and the fuel gauges. The gauges read FULL on both sides. You filed no flight plan; this is a local flight. You departed at 0900 local with 75 gallons total (approximately 2 hours endurance at cruise power).
Cruise: You climbed to 2,500 ft MSL, set cruise power (2,200 RPM, 65% power), and trimmed for level flight. The fuel selector was set to RIGHT tank — a habit from your last flight, when you burned the right tank first. You did not consciously verify the selector position before takeoff; you assumed it was where you left it. The engine ran smoothly. Fuel flow was 10 GPH. You have been cruising for 35 minutes.
Descent: At 0935 local, you begin descent to return to KZPH. You reduce power to 1,500 RPM, establish a descent at 500 ft/min, and plan to arrive at pattern altitude (1,090 ft MSL, approximately 1,000 ft AGL) in about 10 minutes. The engine is running smoothly. You have not checked fuel quantity or tank status since departure. You have not switched tanks during cruise.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'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 Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA13LA111 (2013, FATAL): A Piper PA-28R on an IFR flight from Georgia to Delaware experienced total loss of engine power due to fuel exhaustion after the pilot attempted multiple missed approaches at three different airports. The pilot did not land at any of the airports equipped with adequate instrument approach procedures while operating in low IMC. The probable cause was the pilot's failure to land at multiple airports and his delay in declaring a fuel-related emergency, which resulted in a loss of engine power due to fuel exhaustion.
NTSB WPR24LA167 (2024): A Canadian Car & Foundry 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.
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 accident resulted from improper fuel management and failure to switch to the right tank containing usable fuel, leading to fuel starvation and a forced landing on a road.
NTSB ERA17LA205 (2017): A Cessna P206 on a post-maintenance break-in flight lost all engine power due to fuel starvation when the pilot mismanaged fuel selection and ran the right tank dry. The pilot made a forced landing in trees short of the runway after the engine quit during approach.
The common thread: fuel starvation in single-engine aircraft with LEFT/RIGHT fuel selectors is a trap. The pilot runs one tank to exhaustion while the other has fuel. The engine quits suddenly — there is no partial power, no restart option. At low altitude on approach, the margin between a precautionary landing and a forced landing is minutes. At KZPH, the off-field environment off Runway 01 is GOOD (pasture/hay, open developed areas), but a forced landing off-field with gear down is a crash. Gear up is the correct choice.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills Municipal Airport. KZPH has its own accident history (see field dominant patterns: forced landing 29.2%, loss of control 29.2%), but these specific fuel-starvation events happened elsewhere. The scenario is localized to KZPH to make the off-field environment and runway geometry real for you as a student here.
The consistent lesson: fuel management in the Piper Arrow is not optional. Verify fuel quantity with a fuel stick (dip stick) during preflight, not relying on gauges alone. Switch tanks every 15–30 minutes during cruise to maintain lateral balance. Check fuel status before descent. Check fuel status before short final. Know which tank you are on at all times. The cost of a fuel-management mistake is total engine failure at the worst possible moment.
Key lesson — In the Piper Arrow, the fuel selector is LEFT / RIGHT — not BOTH. Running one tank to exhaustion while the other has fuel is a classic trap. At low altitude on approach, an engine failure from fuel starvation is a forced landing. Off Runway 01 at KZPH, the off-field environment is GOOD (pasture/hay, open developed areas), but a forced landing with gear down is a crash. Gear up is the correct choice. Prevent the emergency with fuel management discipline: dip the tanks during preflight, switch tanks every 15–30 minutes during cruise, and verify fuel status before descent and before short final.
Debrief — teaching points
The Piper Arrow fuel selector is LEFT / RIGHT — not BOTH. Running one tank dry is a classic trap.
Unlike Cessnas (which have a BOTH position), the Piper Arrow requires active fuel management. The pilot must switch between LEFT and RIGHT tanks. Running one tank to exhaustion while the other has fuel is a fatal mistake. At low altitude on approach, an engine failure from fuel starvation is a forced landing with no restart option. The engine simply quits. Prevent this by switching tanks every 15–30 minutes during cruise and verifying fuel status before descent.
Visual fuel checks at the filler neck are not reliable — use a fuel stick (dip stick) during preflight.
Fuel gauges in general aviation aircraft are notoriously inaccurate, especially at low fuel levels. A visual check at the filler neck can be deceiving — the fuel may be sloshing, or the tank may have residual fuel that does not show on the gauge. The only reliable way to verify actual fuel quantity is to dip each tank with a fuel stick during preflight. This takes 2 minutes and gives you exact numbers. Relying on gauges alone is a gamble.
Before descent, verify fuel quantity and tank status — do not assume the gauges are accurate or that you remember which tank you are on.
A fuel check before descent is a critical decision point. Verify the fuel selector position visually. Check the fuel gauges and do the math: how much fuel have you burned? Is the remaining quantity consistent with the gauges? If there is any doubt, switch to the tank with more fuel. At KZPH, you have approximately 10 minutes of descent and approach time — plenty of time to verify fuel status and make corrections before you are committed to landing.
In a forced landing off-field in the Piper Arrow, gear UP is the correct choice — gear down is a crash.
The Piper Arrow's retractable gear is designed for smooth runways. In a forced landing off-field (pasture, rough terrain, trees), gear down will catch on rough ground and the airplane will flip or nose over. Gear up is the correct choice. Retract the gear at 200 ft AGL or higher, descend at 79 KIAS best glide, and land on the belly. The cost is the airplane, not the lives. This is not a judgment call — it is the difference between a survivable landing and a crash.
Fuel starvation causes total engine failure — there is no partial power, no restart option, just silence.
When an engine fails from fuel starvation, it does not cough or sputter — it quits suddenly and completely. There is no restart option at low altitude. The pilot has seconds to decide: can I reach the runway, or do I commit to a forced landing off-field? At 400 ft AGL on short final, the decision window is measured in seconds. Prevent this emergency with fuel discipline: dip the tanks, switch tanks regularly, and verify fuel status before descent and before short final.
Built from the real accident record
Scenario built from NTSB ERA13LA111 (2013 PA-28R fuel exhaustion / missed approaches), WPR24LA167 (2024 fuel tank selection error / starvation), GAA19CA534 (2019 PA-28 fuel starvation on descent), and ERA17LA205 (2017 P206 fuel mismanagement / forced landing). Localized to KZPH.
NTSB reports: CEN22FA419 · ERA22FA261 · ERA13LA111 · WPR12FA058 · WPR24LA167 · GAA19CA534 · DFW05CA087 · ERA17LA205
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.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 Arrow scenarios · More scenarios at KZPH