Fuel Management Failure on Descent
Engine power loss from fuel starvation during approach — a forced landing in open terrain near Brooksville
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a local VFR flight to a nearby airport and back. Elevation 76 ft MSL. The field is towered, part-time (0700–2200 local); it is currently 1530 local, tower is active.
You are a Private pilot with roughly 180 hours total time. This is your third flight in this C172N; you are familiar with the airplane but not deeply. The flight plan is simple: depart Runway 09, climb to 2,500 ft MSL, cruise to a nearby field for a touch-and-go, and return to KBKV for landing. Total flight time planned: 1.5 hours. You have not flown this route before.
Preflight: You visually checked the fuel tanks — both appeared full to the filler neck. The fuel gauges in the cockpit read FULL on both sides. You did not dip-stick the tanks or verify the exact quantity. The airplane was last flown yesterday; the previous pilot topped off the fuel. You accepted the fuel state as full.
Engine: Lycoming O-320, carbureted, fixed-pitch prop. Fuel selector is set to BOTH. You completed a normal run-up; the engine ran smoothly at 1,700 RPM and 2,000 RPM. No anomalies.
Climb-out: You depart Runway 09 (true heading 90°), climb to 2,500 ft MSL, and cruise for 45 minutes. The flight is uneventful. You are now on descent into the diversion field. The engine is running normally. You are 15 nm from KBKV, descending through 1,800 ft MSL on a heading of 270° for a straight-in approach to Runway 27.
At 1,200 ft MSL, 8 nm from KBKV, the engine begins to lose power. The tachometer is unwinding. The engine is not rough — it is simply losing RPM. You have not switched fuel tanks during the flight. The fuel gauges still read FULL, but the engine is starving.
Airspace: KBKV is Class D (ceiling 1,500 MSL), towered. You are in the Class D now, descending for landing. The tower is aware of your position and descent.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 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 made an inadequate fuel plan. The airplane was forced to land in a cornfield. The accident was fatal. The probable cause was the pilot's failure to refuel the airplane prior to departure, leading to fuel exhaustion during the flight, inadequate preflight and inflight planning, 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 accident resulted from poor flight planning and the pilot's decision not to refuel at an intermediate stop despite instructor guidance. The pilot made a forced landing.
NTSB NYC06LA179 (2006): A Cessna 172N on a personal 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 a partial loss of engine power during cruise flight.
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 accident resulted from improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic. The pilot executed a forced landing to a field.
Regional fuel-starvation precedents (WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205) all show the same pattern: pilots relying on fuel gauges without dip-sticking or visual inspection, failing to switch tanks or verify tank selection, and running tanks to exhaustion during descent or approach. The C172N's fuel selector is set to BOTH for normal operations, but fuel gauges are notoriously unreliable — a FULL reading does not guarantee full tanks.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history dominated by hard landings and forced landings, but these specific events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: fuel mismanagement — whether from failure to refuel, inadequate preflight verification, improper tank selection, or reliance on unreliable fuel gauges — is the leading cause of engine failure in light aircraft. The C172N's fuel system is simple and robust, but it requires disciplined preflight and inflight management. Dip-sticking the tanks before every flight is not optional; it is the standard of care.
Key lesson — Fuel gauges in the C172N are unreliable. A FULL reading does not guarantee full tanks. Verify fuel quantity by dip-sticking or detailed visual inspection before every flight. During flight, monitor fuel consumption against your flight plan and switch tanks (if applicable) on a regular schedule. At KBKV, the off-field environment off all runway ends is suitable for a forced landing (pasture, hay, open development), but a forced landing is always a last resort. The accident is preventable with proper preflight verification and inflight fuel management.
Debrief — teaching points
Fuel gauges in the C172N are notoriously unreliable — dip-sticking is the standard of care.
The C172N's fuel gauges are mechanical, capacitive, and prone to error. A FULL reading does not guarantee full tanks. Fuel can slosh, gauges can stick, and the previous pilot's refueling may have been incomplete. Before every flight, dip-stick the tanks or perform a detailed visual inspection of the fuel level at the filler neck. Do not rely on the fuel gauges alone. This is not optional; it is the standard of care in general aviation.
Fuel starvation during descent shows as a gradual loss of power, not a sudden quit.
When fuel pressure drops due to starvation or exhaustion, the engine does not quit suddenly — it loses power gradually. The tachometer unwinds, the engine runs at reduced RPM, and thrust decreases. This can be mistaken for a mechanical failure (throttle, mixture, carb heat) if you are not thinking about fuel. At low altitude during descent, a gradual power loss is fuel starvation until proven otherwise. Check fuel quantity and tank selection immediately.
The C172N fuel selector is BOTH for normal operations — no tank switching is required for a local flight.
The C172N has a single fuel selector with positions: OFF, LEFT, RIGHT, and BOTH. For normal operations, the selector is set to BOTH, which feeds from both tanks equally. There is no need to switch tanks during a local flight. However, if you do not switch tanks during a longer flight, both tanks will deplete together. If the fuel gauges are inaccurate and you do not dip-stick the tanks before flight, you may depart with less fuel than you think.
Best glide speed in the C172N is 65 KIAS — establish it immediately when power is lost.
Best glide speed for the C172N at gross weight is 65 KIAS. This speed maximizes glide distance and gives the most time and distance to manage the emergency. When engine power is lost or failing, lower the nose immediately to 65 KIAS. Do not try to climb or maintain altitude — that will only reduce glide distance. At 65 KIAS, you have the best chance of reaching the runway or a suitable forced-landing field.
Full flaps on a forced landing minimizes impact energy — touchdown speed is critical.
Impact energy rises with the square of touchdown speed. The slowest possible touchdown speed is the most important factor in a forced landing. When the runway or field is made, add full flaps (30°) to slow the airplane to the slowest possible speed. A touchdown at 50 KIAS with full flaps is far safer than a touchdown at 65 KIAS without flaps. The steeper descent path from full flaps is secondary to the speed reduction.
Off Runway 27 at KBKV, the off-field environment is suitable for a forced landing — pasture, hay, and open development.
The off-field environment off Runway 27's departure end (heading 270°) is mostly low-density development, pasture, hay, and grassland. These are suitable for a controlled forced landing. If the engine is failing at low altitude and the runway is marginal, a controlled landing in a suitable field is the right call. Do not try to stretch a glide to the runway if a good field is available below you. A controlled forced landing in a field is better than an uncontrolled landing on the runway or a stall/spin trying to reach the runway.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle shaft failure / forced landing), CHI02FA247 (2002 C172N fuel exhaustion / night forced landing), CEN25LA168 (2025 C172N throttle cable disconnection / forced landing), CEN25LA099 (2025 C172N fuel exhaustion during go-around), and regional fuel-starvation precedents WPR24LA167, GAA19CA534, WPR12LA023, ERA17LA205. Localized to KBKV.
NTSB reports: NYC06LA179 · CHI02FA247 · CEN25LA168 · CEN25LA099 · WPR24LA167 · GAA19CA534 · WPR12LA023 · ERA17LA205
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.B — Engine Starting / Systems Preflight · PA.III.A — Normal Approach and Landing · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.23 · §91.103
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 KBKV