Fuel Starvation on Descent to Tampa
Engine power loss from fuel tank mismanagement — dense development surrounds the field, and the decision window is measured in seconds
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, after a 200-nautical-mile cross-country flight. Elevation 26 ft MSL. You are descending through 2,500 ft MSL, 12 nm northeast of the field, on a heading of 182° (inbound to Runway 19R). ATC has cleared you to descend to 1,500 MSL and expects you to report the field in sight.
It is a hot, hazy Florida afternoon in late summer: OAT 32°C, altimeter 29.89, density altitude approximately 2,800 ft. Scattered clouds at 3,500 ft, visibility 8 SM in haze. Light and variable winds, gusting to 8 kt. The cross-country flight was 2 hours 15 minutes; you have been leaning the mixture since 2,000 ft MSL on descent. Fuel quantity: you estimate 8 gallons remaining (roughly 45 minutes of reserve at cruise power).
Aircraft: Cessna 172M, solo, within limits. Carbureted Lycoming O-320-E2D, 150 hp, fixed-pitch prop, fuel selector on BOTH. The airplane was airworthy at departure; you performed a standard preflight and noted fuel quantity visually in both tanks (left and right appeared equal).
Pilot: you — a Private pilot, current, roughly 250 hours total. You are familiar with KTPA from training; this is a return to your home field. You did not file IFR and are VFR. The flight was routine; no mechanical issues reported.
At 2,500 ft MSL, descending at 500 fpm, the engine begins to run rough. The tachometer is unwinding. You are still 12 nm from the field, over dense development (Tampa's urban sprawl). The tower is active and monitoring your descent.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about fuel starvation in the C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN25LA355 (2025): A Cessna 172 lost engine power during a second touch-and-go landing after a 200-nautical-mile cross-country flight. The pilot had adequate fuel remaining in one tank but failed to switch fuel tanks despite the engine running rough on descent. The probable cause was the pilot's mismanagement of available fuel, which resulted in fuel starvation from an empty tank while usable fuel remained in the other tank.
NTSB ATL03FA142 (2003): A Cessna 172M on an instructional flight from Perry, Georgia experienced engine power loss shortly after takeoff due to water-contaminated fuel. The probable cause was the CFI's inadequate preflight inspection and failure to detect water contamination in the fuel tanks. The contaminated fuel caused engine roughness and power loss indistinguishable from fuel starvation.
NTSB CEN24LA168 (2024): A Cessna 172M on an IFR flight experienced engine power loss due to carburetor icing during descent. The pilot delayed the use of carburetor heat, allowing ice to accumulate beyond the point where heat could restore full engine power. The probable cause was the pilot's delayed use of carburetor heat.
Regional precedent 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.
Regional precedent 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 probable cause was improper fuel management and failure to switch to the right tank containing usable fuel.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (dominant pattern: forced landing 22.2%, loss of control inflight 11.1%, loss of control ground 8.9%), but these specific fuel-starvation events happened elsewhere. The scenario is localized to KTPA 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 during a flight — one tank is used preferentially, the other is neglected — and the first symptom is engine roughness on descent when the empty tank is selected or when BOTH is selected and one tank draws air. By the time the roughness is obvious, the decision window is measured in seconds. The fix — proactive fuel tank management and immediate tank switching when power loss occurs — is simple. The failure is always a delay or a misdiagnosis (confusing fuel starvation with carburetor icing or mixture issues).
Key lesson — In the C172M, fuel tank management is critical. The fuel selector is BOTH, but both tanks must be monitored and switched deliberately during flight. If one tank runs dry, the engine will quit even if the other tank has fuel. On descent to KTPA, engine roughness is fuel starvation until proven otherwise. Switch tanks immediately. At 2,500 ft MSL over dense development, the decision window is 60–90 seconds. Delay costs altitude; altitude costs options.
Debrief — teaching points
The C172M fuel selector is BOTH, but both tanks must be managed deliberately.
The C172M has no crossfeed system. When the selector is on BOTH, the engine draws from both tanks simultaneously — but if one tank runs dry, the engine will quit even if the other tank has fuel. This is the trap: pilots assume BOTH means 'balanced consumption,' but it means 'simultaneous draw.' If you depart with unequal fuel (one tank fuller than the other), the engine will eventually draw air from the empty tank and quit. Preflight fuel quantity visually in both tanks and plan tank switching intervals in advance. On a 2-hour cross-country, plan to switch tanks every 45 minutes.
Engine roughness on descent is fuel starvation until proven otherwise.
In the C172M, engine roughness and a dropping tachometer on descent can be caused by carburetor icing, mixture issues, or fuel starvation. The diagnostic sequence is: (1) Check fuel selector — is it on BOTH? If yes, switch to RIGHT tank. (2) If roughness persists, apply carburetor heat. (3) If roughness persists, enrich the mixture. But the FIRST action on descent is always to check the fuel selector. Fuel starvation is the most common cause of engine roughness on descent in the C172M, and it is the fastest to diagnose and fix.
Preflight fuel sampling is not optional — water-contaminated fuel is invisible.
NTSB ATL03FA142 shows a fatal accident caused by water-contaminated fuel that was not detected during preflight. Water in the fuel causes engine roughness and power loss indistinguishable from fuel starvation. The only way to detect water is to sample fuel from the lowest point of each tank (the fuel drain valve) into a clear container and look for water droplets or cloudiness. This takes 30 seconds per tank and is the most critical preflight check. Do it every time, especially after the airplane has sat for more than a few days.
At KTPA, the off-field environment off Runway 19R's climb-out is dense development — buildings, streets, parks.
The off-field environment off Runway 19R's departure end (heading 182°) is dense development — buildings, streets, medium development, pasture/hay. There is no open field, no road, no water. A forced landing in this terrain is survivable but serious. If the engine fails on descent to KTPA and altitude is insufficient to reach the field, you are committed to a forced landing in the development. Best glide is 65 KIAS. Establish that speed immediately and look for the largest open area — a park, a large parking lot, or a pasture. Doors unlatched, master off just before impact, flaps for slowest possible touchdown speed.
Density altitude at KTPA on a hot afternoon is significant — climb performance is marginal.
On a hot, hazy Florida afternoon (OAT 32°C), the density altitude at KTPA (elevation 26 ft MSL) is roughly 2,800 ft. The C172M's 150 hp Lycoming O-320 is marginal on climb at high density altitude. This is not directly relevant to fuel starvation, but it is relevant to the overall margin: if the engine fails on descent, you have less altitude to work with than you might expect. Plan accordingly.
Built from the real accident record
Scenario built from NTSB CEN25LA355 (2025 C172M fuel starvation on descent after cross-country), ATL03FA142 (2003 C172M water-contaminated fuel / inadequate preflight), CEN24LA168 (2024 C172M carburetor icing power loss), ERA23LA141 (2023 C172M oil starvation), and regional fuel-management precedents WPR24LA167, GAA19CA534, WPR12LA023, CEN25LA081. Localized to KTPA.
NTSB reports: ATL03FA142 · CEN25LA355 · CEN24LA168 · ERA23LA141 · WPR24LA167 · GAA19CA534 · WPR12LA023 · CEN25LA081
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.A — Preflight Inspection · 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.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 172M scenarios · More scenarios at KTPA