Fuel Starvation on Short Final
Improper fuel tank selection during descent, power loss at 400 ft AGL, and a forced landing in unfamiliar terrain — the decision window is seconds
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 13, on a local personal flight. Elevation 18 ft MSL. It is a clear, calm Friday afternoon in late March: OAT 24°C, winds calm to 3 knots, visibility 10 SM, altimeter 30.01. KVNC is non-towered (CTAF 122.8); you will self-announce on the common frequency.
You conducted a preflight inspection this morning. The fuel tanks appeared full — you visually confirmed both caps and saw fuel at the filler necks. You did not dip the tanks with a fuel stick. The airplane's fuel gauges read FULL on both left and right. You filed no flight plan; this is a local flight, roughly 45 minutes out and back.
You depart Runway 13 at 1400 local, climb to 2,000 ft MSL, and cruise southwest at 100 KIAS for 35 minutes. At 1435, you decide to return to KVNC. You descend and enter the downwind for Runway 13 at 1,200 ft MSL. The runway is in sight. You are on a 5-mile downwind, heading 315°, at 90 KIAS.
Aircraft: Cessna 172N, solo, fuel selector on BOTH. The left tank shows 3/4 full; the right tank shows 1/2 full on the gauges. You have been on BOTH the entire flight. You did not switch tanks during cruise — no reason to, the gauges looked fine.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have flown this airplane a dozen times. You are familiar with KVNC. You are not fatigued. The flight has been uneventful.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'C172N'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
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 not refueled before departure despite having only 1.5 hours of fuel on board and planning a 2-hour flight. The pilot made a forced landing in a cornfield in darkness. The probable cause was the pilot's failure to refuel before departure, inadequate fuel planning, pilot fatigue, and night conditions. The accident was fatal.
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 been advised by an instructor to refuel at an intermediate stop but chose not to. The probable cause was poor flight planning and the pilot's decision not to refuel despite instructor guidance.
NTSB NYC06LA179 (2006): A Cessna 172N on a personal local flight experienced partial loss of engine power during cruise. The accident was attributed 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.
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 — an apprentice's work was not adequately inspected by the supervising mechanic. The pilot executed a forced landing to a field.
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.
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 known-good tank containing usable fuel.
The common thread across all these events: fuel mismanagement is the dominant cause. In the C172N specifically, the fuel selector is BOTH — it draws from both tanks simultaneously. The tanks may not deplete evenly; one tank can run dry while the other still has fuel. Fuel gauges are notoriously inaccurate, especially at low fuel levels. Visual fuel-stick dipping before flight is the only reliable way to confirm fuel quantity. Switching tanks reactively during an emergency (when power is already lost) is a last-resort gamble — the selected tank may be empty or contaminated.
At KVNC, you are surrounded by open fields and scattered development. A forced landing off the airport is survivable if you fly the best-glide descent correctly, pick the best landing area, and execute the forced landing checklist. The real accidents cited above occurred at other airports and in other aircraft — NOT at KVNC. The scenario is localized to KVNC to make the off-field environment real and consequential for you as a student here.
The lesson is not complicated: confirm fuel quantity visually before every flight, manage fuel tank selection proactively during cruise (switching tanks every 15–20 minutes to balance depletion), and never rely on fuel gauges alone. If power is lost during descent, switch to the tank showing the most fuel on the gauge — but understand that this is a gamble if you did not dip the tanks before flight.
Key lesson — Fuel mismanagement is the dominant cause of forced landings in the C172N. The fuel selector is BOTH — it draws from both tanks simultaneously, but the tanks may not deplete evenly. Fuel gauges are inaccurate, especially at low levels. Visual fuel-stick dipping before flight is the only reliable way to confirm fuel quantity. If power is lost during descent, switching to the tank showing the most fuel is a last-resort gamble — the selected tank may be empty or contaminated. The correct response is to establish best glide (65 KIAS) immediately and pick the best landing area ahead. At KVNC, you are surrounded by open fields — a forced landing is survivable if you fly the descent correctly and execute the checklist.
Debrief — teaching points
Fuel gauges in the C172N are notoriously inaccurate, especially at low fuel levels.
The C172N's fuel gauges are capacitive and prone to error, particularly when tanks are less than half full or when the airplane is in a bank or climb. A gauge reading 'full' may not be full; a gauge reading '1/2' may be less. The ONLY reliable way to confirm fuel quantity before flight is to visually dip each tank with a fuel stick and record the quantity in gallons. This is not optional — it is the foundation of fuel planning. If you did not dip the tanks before flight, you do not know how much fuel you have.
The C172N fuel selector is BOTH — it draws from both tanks simultaneously, but the tanks may not deplete evenly.
The C172N's fuel system feeds from both tanks when the selector is on BOTH. However, the tanks may not deplete at the same rate due to fuel line routing, vent differences, or other factors. One tank can run dry while the other still has fuel. If you have been on BOTH for the entire flight and one tank runs dry, the engine will lose power. Switching to the other tank may restore power — but only if that tank has usable fuel. Proactive tank switching during cruise (every 15–20 minutes) helps balance depletion and prevents one tank from running completely dry.
Fuel starvation in the C172N may show as engine roughness before total power loss.
When one tank runs dry and the engine begins to draw air instead of fuel, the first symptom is often engine roughness and a dropping tachometer — similar to carburetor ice. This is a critical warning sign. If you experience unexplained engine roughness during descent, immediately switch the fuel selector to the tank showing the most fuel on the gauge. Do not assume it is carburetor ice; fuel starvation is equally likely in a C172N with poor fuel management.
At KVNC, the off-field environment is a mix of open fields and scattered development — a forced landing is survivable if you fly it correctly.
KVNC is surrounded by open fields to the southwest and scattered development to the north and east. A forced landing off the airport is survivable if you establish best glide (65 KIAS) immediately, pick the best landing area ahead, and execute the forced landing checklist: fuel selector OFF, mixture LEAN, master OFF just before impact, doors unlatched, full flaps for slowest touchdown speed. Impact energy rises with the square of touchdown speed — the slowest possible speed matters most. Do not try to stretch a glide to the runway if power is lost; pick the best field ahead and land there.
Switching fuel tanks reactively during an emergency is a last-resort gamble.
If power is lost during descent and you have not dipped the tanks before flight, switching to the other tank is a gamble. The selected tank may be empty, contaminated, or have a fuel selector issue. The gamble may pay off (the other tank has fuel and power returns) or it may fail (the other tank is empty and power is lost completely). The correct response is to establish best glide immediately and pick the best landing area ahead. Switching tanks is a secondary action, not the primary one.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle malfunction / forced landing), CHI02FA247 (2002 C172N fuel exhaustion / night forced landing), CEN25LA168 (2025 C172N throttle disconnection / forced landing), CEN25LA099 (2025 C172N fuel exhaustion go-around), and regional fuel-mismanagement precedents WPR24LA167, GAA19CA534, DFW05CA087, ERA17LA205. Localized to KVNC.
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.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors · PA.II.B — Engine Starting / Systems Preflight · PA.III.A — Preflight Inspection · PA.V.A — Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.185 · §91.207
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 KVNC