Fuel Starvation on Approach to Zephyrhills
Improper tank selection, low-fuel descent, and a forced landing decision — the margin between landing and crashing is fuel management
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, a local 45-minute flight to a nearby airport and back. Elevation 90 ft MSL. The morning was clear and calm; you filed no flight plan, just a local VFR hop. You are a Private pilot with roughly 250 hours total, current and proficient.
The Cessna 172N was fueled yesterday afternoon — you recall the FBO saying 'topped off.' You did a quick preflight this morning: visually checked both fuel tanks (they looked full), checked the oil, cycled the controls, and called CTAF to announce your departure. You did not run the engine long enough to verify the fuel gauges were reading correctly, and you did not calculate fuel burn or time-to-reserve. The flight plan was informal: 'I'll be back in an hour.'
You are now on descent to return to KZPH after 52 minutes of flight. You are at 1,500 ft MSL (1,410 ft AGL), 8 nm out on a straight-in approach to Runway 19. The fuel gauges show the right tank at roughly 1/4 tank and the left tank at roughly 1/8 tank. The engine is running smoothly. You have not switched fuel tanks during the flight — you have been running on the right tank the entire time. You are descending at 500 fpm, airspeed 90 KIAS, heading 180°. KZPH is non-towered (CTAF); you have announced your position and intentions.
Aircraft: Cessna 172N, solo, fuel selector on RIGHT. Lycoming O-320, fixed-pitch prop, steam panel. The airplane is within limits.
Pilot: you — a Private pilot, current, 250 hours. You did not verify fuel quantity with a dip stick or by running the engine long enough to verify gauge accuracy. You have not switched tanks during the flight. You are on descent to land after a local flight that consumed more fuel than you anticipated.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'C172N'}
- {'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 C172N? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CHI02FA247 (2002): A Cessna 172N on a night personal flight from Minnesota to Wisconsin experienced fuel exhaustion during final approach. The pilot had failed to refuel before departure and did not plan fuel adequately. The airplane was forced to land in a cornfield. The pilot was fatally injured. The probable cause was the pilot's failure to refuel before departure, inadequate fuel planning, and unsuitable terrain during the forced landing. Contributing factors were pilot fatigue and night conditions.
NTSB CEN25LA099 (2025): A Cessna 172N on a cross-country flight lost total engine power during a go-around after an aborted landing due to fuel exhaustion. The pilot had made a poor flight plan and decided not to refuel at an intermediate stop despite instructor guidance. The probable cause was poor flight planning and decision-making, resulting in fuel exhaustion.
NTSB NYC06LA179 (2006): A Cessna 172N on a local flight experienced partial loss of engine power during cruise due to improper maintenance of the throttle shaft during the most recent annual inspection. The pilot made a forced landing that resulted in collision with trees. The accident was fatal. The probable cause was improper maintenance of the throttle shaft, which resulted in partial loss of engine power.
NTSB CEN25LA168 (2025): A Cessna 172N on an instructional flight lost engine power on final approach when the throttle cable was found disconnected from the carburetor. The pilot executed a forced landing to a field. The probable cause was improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic.
The regional fuel-management precedents (WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205) all show the same pattern: improper fuel tank selection, failure to verify fuel quantity before departure, and inadequate fuel management during descent and approach. In every case, the pilot ran a tank dry or exhausted fuel during the critical phase of flight.
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_INFLIGHT 29.2%), but these specific events happened elsewhere. The scenario is localized to KZPH to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: fuel mismanagement is insidious. It builds gradually — a pilot does not refuel, or does not verify fuel quantity, or does not switch tanks proactively — and by the time it is obvious (engine quit on final approach), it may be too late for a comfortable recovery. The fix — visual fuel verification during preflight, a deliberate fuel management plan, and proactive tank switching before descent — is simple. The failure is always a delay or a complacent assumption that 'the gauges look fine' or 'I have plenty of fuel.'
Key lesson — In the C172N, fuel management is the pilot's responsibility. The fuel selector is BOTH — both tanks feed the engine simultaneously — but the pilot must verify fuel quantity visually (dip stick or filler cap check) during preflight, not rely on gauges alone. Plan fuel burn for the entire flight, including descent and approach. Switch tanks proactively before descent, not during approach. If the engine quits on final approach due to fuel starvation, establish 65 KIAS best glide immediately and land in the best available off-field option — do not try to stretch the glide to the runway. Off Runway 19 at KZPH, the off-field environment is marginal (open developed areas, parks, evergreen forest, low-density development) — a forced landing is survivable, but it is preventable through proper fuel planning.
Debrief — teaching points
Fuel gauges in the C172N are notoriously unreliable — visual verification is the only reliable fuel check.
The C172N's fuel gauges are mechanical floats that can stick, corrode, or read inaccurately. A 'full' gauge may not mean the tank is full. A 'quarter' gauge may not mean the tank is a quarter full. The only reliable way to verify fuel quantity is to visually check each tank during preflight: open the filler cap, look inside, or use a dip stick. This takes 30 seconds per tank. The NTSB cases show that pilots who relied on gauges alone ran out of fuel. Pilots who visually verified fuel quantity did not.
Fuel burn increases during descent and approach — plan fuel for the entire flight, not just cruise.
The C172N burns roughly 5 gal/hr at cruise power (75% power, 2,200 RPM). During descent and approach, power is reduced, but the descent phase is often longer and more power-intensive than pilots expect. A pilot who plans fuel only for cruise will run short on descent. Always calculate fuel burn for climb, cruise, descent, and approach. Add a 30-minute reserve. If the numbers do not work, divert or refuel.
Switch fuel tanks proactively during cruise, not during descent or approach.
The C172N fuel selector is BOTH — both tanks feed the engine simultaneously. However, if one tank runs dry, the engine will continue to draw from the other tank as long as the selector remains on BOTH. If the selector is on a specific tank (LEFT or RIGHT) and that tank runs dry, the engine will quit. The correct procedure is to switch tanks proactively during cruise (e.g., every 30 minutes or every 15 gallons burned) to balance fuel consumption and ensure both tanks are used evenly. Never wait until descent to switch tanks. If you switch tanks during descent and the new tank is empty or nearly empty, you may not have time to switch back before the engine quits.
Fuel starvation (engine quit due to running a tank dry) can occur even when the other tank has fuel.
If the fuel selector is on the empty tank, the engine will quit even if the other tank is full. The engine will not restart until the selector is switched to the tank with fuel. This is a critical distinction: fuel exhaustion (all tanks empty) and fuel starvation (selector on empty tank while other tank has fuel) are different problems with different solutions. Fuel starvation is recoverable if you have altitude and time to switch tanks and restart. Fuel exhaustion is not.
Best glide in the C172N is 65 KIAS — establish this speed immediately if the engine quits.
If the engine quits on approach due to fuel starvation or any other cause, establish 65 KIAS best glide immediately. This is the speed that maximizes glide distance and gives you the most time and distance to find a landing spot. Do not try to stretch the glide to the runway if the runway is not reachable — land in the best available off-field option. Off Runway 19 at KZPH, the off-field environment is marginal (open developed areas, parks, evergreen forest, low-density development) — a forced landing is survivable if you land at the right speed and in the right spot.
Full flaps on a forced landing minimize impact energy — touchdown speed is critical.
On a forced landing, the slowest possible touchdown speed is the goal. Impact energy rises with the square of touchdown speed. Full flaps (30° in the C172N) reduce stall speed to 40 KIAS (Vs0). Landing at 40 KIAS instead of 65 KIAS reduces impact energy by roughly 60%. Add full flaps as you descend toward the landing spot. The steeper descent path is secondary; the slowest possible touchdown speed is the priority.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle-shaft maintenance failure / forced landing), CHI02FA247 (2002 C172N fuel exhaustion / night forced landing), CEN25LA168 (2025 C172N throttle disconnection / forced landing), CEN25LA099 (2025 C172N fuel exhaustion on go-around), and regional fuel-management precedents WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205. Anonymized and localized to KZPH.
NTSB reports: NYC06LA179 · CHI02FA247 · CEN25LA168 · CEN25LA099 · WPR24LA167 · GAA19CA534 · DFW05CA087 · 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 · §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 Cessna 172N scenarios · More scenarios at KZPH