Fuel Starvation on Climb
A fuel selector oversight and inadequate preflight planning turn a local flight into a power-loss emergency over water
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, climbing out on a 062° heading toward a local practice area 15 nm northeast. Elevation 7 ft MSL. The morning is clear, calm, and VFR: OAT 22°C, visibility 10 SM, scattered clouds at 3,500 ft. Class D airspace; tower is open and active (0800 local).
Aircraft: Cessna 172R, solo, fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, fixed gear. The fuel selector is BOTH. You are planning a 1.5-hour local flight: 30 minutes out, 30 minutes in the practice area, 30 minutes back. You topped off the tanks this morning — or so you thought.
Preflight: You visually inspected both wing tanks and the fuel quantity indicators (mechanical, not electronic). The left tank appeared full; the right tank appeared to have about 3/4 capacity. You did not use a fuel dipstick to verify actual quantity. The fuel selector was on BOTH during the preflight walk-around. You did not verify it again before engine start.
Pilot: You — a Private pilot, current, roughly 250 hours total. You have flown this airplane (a school C172R) a dozen times. You are familiar with KSPG and the local practice area. You did not file a flight plan; this is a local VFR flight. You did not brief fuel reserves or plan a diversion.
Engine start and taxi: Normal. The engine starts smoothly, runs at idle, and climbs to 1,000 RPM on the mag check. You taxi to Runway 07, receive a takeoff clearance from tower, and line up.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'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 C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA12LA294 (2012): A Cessna 172R operated by Eastern Kentucky University lost engine power due to fuel exhaustion during climb. The aircraft made a forced landing in a field, striking a tree during rollout. The probable cause was fuel exhaustion attributed to inadequate fuel management, failure to supervise the student's preflight inspection, and inadequate operator fueling policies. The fuel quantity indicators showed 'full,' but the actual fuel on board was significantly less.
NTSB ERA12FA002 (2011): A Temco GC-1B Swift experienced total loss of engine power over the Chesapeake Bay and ditched in the water after a controlled glide. The probable cause was fuel starvation resulting from the pilot's failure to verify the fuel selector position before flight. The pilot did not use a dipstick to verify actual fuel on board and did not check the fuel selector position after the power loss — a critical omission that cost precious seconds.
NTSB ANC17LA043 (2017): A Cessna T207 on a Part 135 scheduled commuter flight lost all engine power during approach due to fuel starvation. The aircraft made a controlled ditching. Contributing factors included unreliable fuel quantity indicators and a company history of fuel management issues. The lesson: do not rely solely on fuel quantity indicators; use dipstick verification.
NTSB LAX97LA278 (1997): A Cessna 150G on a banner towing operation lost engine power and ditched in the Pacific Ocean off California. The probable cause was fuel starvation caused by the pilot's failure to switch to the auxiliary tank as required by operating procedures. The lesson: follow fuel management procedures rigorously; use checklists to avoid omissions.
NTSB LAX98LA168 (1998): A Cessna T210M ditched in the Pacific Ocean 2 miles south of Santa Barbara after engine failure on final approach. The probable cause was fuel starvation caused by the pilot's mismanagement of fuel through improper fuel tank selector positioning. The lesson: maintain proper fuel tank selector position throughout flight, especially during approach.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport. KSPG has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 20%, FORCED_LANDING 16.4%, DITCHING 12.7%), but these specific fuel exhaustion events happened elsewhere. The scenario is localized to KSPG to make the off-field environment real and consequential: off Runway 07's departure end (heading 062°), the off-field environment is open water — Tampa Bay. An engine failure on the Runway 07 departure at low altitude is a ditching, not a field landing.
The consistent thread across all these events: fuel exhaustion in the C172R is almost always caused by inadequate preflight planning, failure to verify actual fuel on board (dipstick check), or complacency about fuel management. The C172R's fuel quantity indicators are notoriously unreliable. Visual inspection alone is not sufficient. A 1.5-hour flight with 'topped off' tanks and no fuel reserve planning leaves no margin for error. 14 CFR §91.23 requires a 30-minute fuel reserve for day VFR — that is the law, not a suggestion.
Key lesson — Fuel exhaustion in the C172R is preventable through rigorous preflight planning and verification. Use a dipstick to verify actual fuel on board — do not rely on fuel quantity indicators or visual inspection alone. Plan for a 30-minute fuel reserve (14 CFR §91.23). Brief fuel reserves and plan a diversion before flight. If the engine loses power at low altitude over water, a controlled ditching at 65 KIAS best glide is the correct outcome — but it should never have been necessary.
Debrief — teaching points
Fuel quantity indicators in the C172R are unreliable — a dipstick check is mandatory.
The C172R's mechanical fuel quantity indicators are notoriously inaccurate. They can show 'full' when the tanks are actually 1/4 to 1/2 empty. A visual inspection of the tanks during preflight is not sufficient. You must use a fuel dipstick (or equivalent calibrated measuring device) to verify the actual quantity of fuel in each tank before every flight. This is not optional; it is the only way to know how much fuel you actually have on board. NTSB ANC17LA043 explicitly cites unreliable fuel quantity indicators as a contributing factor to a fatal ditching.
14 CFR §91.23 requires a 30-minute fuel reserve for day VFR — plan accordingly.
The regulation states: 'No person may operate a civil aircraft in VFR conditions unless there is enough fuel to fly to the first point of intended landing and, assuming normal cruising speed, to fly after that for at least 30 minutes.' A 1.5-hour flight plan with 'topped off' tanks leaves no margin. If you top off at 40 gallons usable (C172R standard), cruise at 9 GPH, and fly 1.5 hours, you will burn 13.5 gallons and land with 26.5 gallons — but only if the tanks were actually full. If the visual inspection was wrong and you actually have 30 gallons on board, you will run out of fuel before reaching the airport. Always plan for a 30-minute reserve; always verify actual fuel on board with a dipstick.
Best glide speed for the C172R is 65 KIAS — establish it immediately upon engine failure.
If the engine fails at low altitude, lower the nose immediately to 65 KIAS best glide. This speed maximizes glide distance and gives you the most time and distance to manage the emergency — whether that means reaching the airport or setting up a controlled ditching. Do not try to climb, do not try to stretch the glide, do not try to turn back to the departure runway at 400 ft AGL. Fly 65 KIAS, keep the nose down, and let the airplane do what it does best: glide.
Off Runway 07 at KSPG, the off-field environment is open water — a forced landing is a ditching.
The off-field environment off Runway 07's departure end (heading 062°) is open water — Tampa Bay. There is no alternate landing surface. If the engine fails on the Runway 07 departure and altitude is insufficient to return to the airport, the outcome is a controlled ditching. Doors should be unlatched before water contact, master off just before impact, and flaps used for the slowest possible touchdown speed. A controlled ditching is survivable; an uncontrolled one is not. Know this before you line up on Runway 07.
Declare an emergency early — do not spend time diagnosing at low altitude.
When the engine begins to lose power at 800 ft AGL over water, declare an emergency immediately and return to the airport at best glide. Do not spend 20 seconds checking the mixture, fuel selector, or boost pump. The fuel selector is BOTH; the boost pump is already running; the mixture is already near full rich at sea level. If the engine is losing power, the problem is almost certainly fuel exhaustion or fuel starvation — and none of those checks will fix it. Declare, return, land. The time you spend diagnosing is altitude you lose.
Built from the real accident record
Scenario built from NTSB ERA12LA294 (2012 C172R fuel exhaustion / forced landing), ERA12FA002 (2011 fuel selector mismanagement / ditching), ANC17LA043 (2017 fuel starvation / controlled ditching), LAX97LA278 (1997 fuel tank switching omission), and LAX98LA168 (1998 fuel selector positioning error). Localized to KSPG with real off-field environment (open water off Runway 07 departure).
NTSB reports: ERA12LA294 · ERA12FA002 · ANC17LA043 · LAX97LA278 · LAX98LA168
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.B — Engine Starting / Systems Preflight · PA.II.C — Taxiing · PA.III.A — Normal Takeoff and Climb · PA.IX.C — Emergency Approach and Landing
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 172R scenarios · More scenarios at KSPG