Fuel Tank Confusion on Descent to Zephyrhills
Fuel exhaustion, marginal off-field options, and the cost of a missed preflight fuel check — a forced landing decision at 1,200 ft AGL
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, descending into the field on a 180° heading after a 1.5-hour cross-country flight from a nearby airport. Field elevation 90 ft MSL; the runway is essentially at sea level in central Florida.
It is a hot, hazy afternoon in mid-July: OAT 32°C, altimeter 29.89, density altitude approximately 1,800 ft. The Cessna 150M is loaded near gross weight — two adults, full fuel tanks (or so you thought), and light baggage. You are on a personal cross-country flight, no flight plan filed, VFR. KZPH is non-towered (CTAF); you will self-announce on 122.7.
You are at 1,200 ft AGL on a 3° descent to Runway 19, airspeed 70 KIAS, heading 180°. The engine is running smoothly. You have not monitored fuel tank status carefully during the flight — you were heads-down on navigation and the engine sounded fine. You are about 2 minutes from the runway. Then, without warning, the engine sputters, loses power, and quits. Total power loss. No restart.
Aircraft: Cessna 150M, two occupants, near gross weight. Continental O-200-A carbureted engine, 100 hp. Fixed-pitch prop, fixed gear, fuel selector BOTH/OFF. The fuel gauges showed 'full' at departure, but you did not visually verify the tanks during preflight — you trusted the gauges and the previous pilot's word.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown the C150 before, but not extensively. You are not familiar with Zephyrhills. You did not file a flight plan. You did not brief an alternate airport or a fuel reserve. You are now 1,200 ft AGL with a dead engine and 2 minutes of glide time remaining.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'C150'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about fuel exhaustion and forced landing in the C150? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR18FA249 (2018, FATAL): A Cessna 150L on a discovery flight lost engine power shortly after takeoff due to fuel exhaustion. The flight instructor made an abrupt turn back toward the runway, exceeding the critical angle of attack and entering an aerodynamic stall/spin at an altitude too low for recovery. The accident was attributed to fuel exhaustion and inadequate preflight inspection. The probable cause: loss of engine power due to fuel exhaustion, and exceedance of the critical angle of attack when the flight instructor made an abrupt turn back toward the runway, resulting in a stall/spin at too low an altitude for recovery.
NTSB CEN18FA384 (2018, FATAL): A Cessna 150 on a personal relocation flight from New York to Missouri ran out of fuel during a night approach to an unlit airport. The accident resulted from fuel exhaustion combined with the pilot's decision to continue into dark night conditions with a known electrical problem, resulting in loss of control and terrain impact. The probable cause: total loss of engine power due to fuel exhaustion and the pilot's subsequent exceedance of the critical angle of attack, resulting in an aerodynamic stall.
NTSB CEN25LA391 (2025): A Cessna 150G on a cross-country flight experienced total engine power loss due to fuel exhaustion and made a forced landing to a field, striking a fence. The accident resulted from inadequate fuel planning by the pilot. The probable cause: the pilot's inadequate fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.
NTSB ERA25LA264 (2025): A Cessna 150 sustained substantial damage to both wings, nose gear, and firewall when it made a forced landing on railroad tracks. The accident resulted from the pilot's inadequate fuel planning, which led to total loss of engine power due to fuel exhaustion.
The consistent thread across all these accidents: fuel exhaustion in the C150 is preventable. It results from inadequate preflight fuel checks (trusting gauges instead of visually verifying each tank), poor fuel planning (no reserve, no alternate, no headwind planning), and complacency (assuming the previous pilot left the tanks full). The C150's 40-gallon total fuel capacity and 100 hp engine give it a cruise endurance of roughly 5–5.5 hours at 55% power — but that assumes proper fuel management and a headwind-free flight. Add a headwind, high density altitude, or a climb to altitude, and the endurance shrinks rapidly.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills. KZPH has its own accident history (see field dominant patterns: forced landing 29.2%, loss of control 29.2%), but these specific NTSB 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 key lesson: visual fuel quantity check during preflight is non-negotiable. Fuel gauges in the C150 are notoriously unreliable. Open the fuel caps, look into each tank, and verify the fuel level with your eyes. If you cannot see fuel in the tank, do not fly. Fuel planning must account for headwind, density altitude, and a 30-minute reserve (14 CFR §91.151). If you cannot account for a 30-minute reserve, you do not have enough fuel to depart.
Key lesson — In the C150, fuel exhaustion is always a preflight failure: either a missed visual fuel check or inadequate fuel planning. The engine quit on descent to Zephyrhills because the fuel gauges lied and you did not verify the tanks visually. At 1,200 ft AGL on descent, the decision window is measured in seconds. Best glide (60 KIAS) and a straight-in approach to the runway are the correct response. A steep turn back to the departure end is a stall/spin trap at low altitude. Know your off-field environment before you depart — off Runway 19 at KZPH, the terrain is marginal (developed areas, parks, forest). The runway is your best option.
Debrief — teaching points
Visual fuel quantity check is mandatory — fuel gauges are unreliable.
The C150's fuel gauges are notoriously inaccurate, especially at low fuel levels. During preflight, open the fuel caps and look into each tank. Verify the fuel level with your eyes. If you cannot see fuel in the tank, do not fly. Do not trust the previous pilot's word, and do not assume the gauges are accurate. This is the single most common cause of fuel exhaustion accidents in light aircraft. A 30-second visual check prevents a forced landing.
Fuel planning must account for headwind, density altitude, and a 30-minute reserve.
14 CFR §91.151 requires a 30-minute fuel reserve for day VFR flight. The C150 at 55% power has a cruise endurance of roughly 5–5.5 hours, but that assumes no headwind and sea-level conditions. Add a 20-knot headwind and high density altitude (as in central Florida in July), and endurance shrinks to 4–4.5 hours. If your planned flight time is 1.5 hours, you need 1.5 + 0.5 (reserve) = 2 hours of fuel. At 55% power, that is roughly 10 gallons. Verify that you have at least 10 gallons in the tanks before you depart. If you cannot account for a 30-minute reserve, you do not have enough fuel.
Best glide in the C150 is 60 KIAS — establish it immediately if the engine quits.
When the engine quits, lower the nose to 60 KIAS and trim for hands-off flight. At 1,200 ft AGL and 60 KIAS best glide, the C150 has roughly 2–2.5 minutes of glide time and will cover approximately 2–2.5 nautical miles. This is your decision window. Use it to assess the situation, identify a landing site, and plan the approach. Do not waste time troubleshooting or attempting a restart — the engine is dead, and you are flying the airplane.
A steep turn back to the runway at low altitude is a stall/spin trap.
The C150's light wing loading makes it gust- and stall-prone, especially on the base-to-final turn. At low altitude with a dead engine, a steep turn back to the runway will cause the airspeed to decay and the stall warning to sound. If you hold the steep bank and pull back to maintain altitude, you will stall and spin. The correct response is a shallow turn (15–20° bank) at best glide speed. If you cannot reach the runway with a shallow turn, select an off-field landing site and commit to it. The NTSB WPR18FA249 accident killed a flight instructor who made an abrupt turn back to the runway at low altitude — the stall/spin was unrecoverable.
Know your off-field environment before you depart.
Off Runway 19 at KZPH (heading 180°), the off-field environment is marginal — mostly developed areas, parks, and evergreen forest. There is no obvious clear field for a forced landing. This makes the runway your best option on descent. If you were departing Runway 19, you would know that the off-field environment behind you (heading 360°) is also marginal. The runway is your escape route on departure. Know the terrain off each runway end before you line up.
Maintain best glide speed (60 KIAS) throughout the approach — do not increase descent rate.
Once you have committed to a landing site, maintain 60 KIAS best glide speed throughout the approach. Do not increase the descent rate by lowering the nose — this increases your approach speed and your touchdown speed. Impact energy rises with the square of touchdown speed. A 70 KIAS touchdown has roughly 36% more impact energy than a 60 KIAS touchdown. Maintain 60 KIAS, flare smoothly, and touch down as slowly as possible. The hard landing in this scenario (n12) resulted from a 70 KIAS approach — the airplane bounced and sustained damage to the nose gear and firewall.
Built from the real accident record
Scenario built from NTSB CEN18FA384 (2018 C150 fuel exhaustion / night approach), WPR18FA249 (2018 C150L fuel exhaustion / stall/spin on turn-back), CEN25LA391 (2025 C150G fuel exhaustion / forced landing), ERA25LA264 (2025 C150 fuel exhaustion / railroad impact), and regional fuel-management precedents WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205. Localized to KZPH.
NTSB reports: CEN18FA384 · WPR18FA249 · CEN25LA391 · ERA25LA264 · WPR24LA167 · GAA19CA534 · DFW05CA087 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.B — Engine Starting / Systems Preflight · PA.III.D — Fuel System Management · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.103 · §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 Cessna 150M scenarios · More scenarios at KZPH