Power Loss on the Runway 10 Departure
Partial engine failure over dense Tampa development — no good forced-landing site, and the clock is ticking
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 10, climbing out on a 092° heading. Field elevation 26 ft MSL. You are a Private pilot with 200 hours total, current and proficient. Solo flight, full fuel, within limits.
It is a warm, humid Florida morning in late spring: OAT 27°C, dew point 21°C, altimeter 29.94. Scattered clouds at 2,800 ft, light rain shower two miles to the northeast. Visibility 9 SM. The off-field environment off Runway 10's departure end (heading 092°) is dense development, open developed areas (parks and large lots), and wooded wetland — no clear field, no road, no water. If the engine fails on this departure, you are landing in a built-up area.
You are cleared for takeoff on Runway 10. The run-up was normal — engine temps and pressures green, mags checked, carb heat tested. You rotate at 55 KIAS, climb out at 73 KIAS (Vy), and reach 400 ft AGL. The airplane is climbing normally. Then, at 450 ft AGL, the engine begins to run rough. The tachometer is unwinding. Power is noticeably down.
Aircraft: Cessna 172N, solo, full fuel, within limits. Carbureted Lycoming O-320, fixed-pitch prop, steam panel, fuel selector on BOTH. The airplane was airworthy at departure. Nothing was written up.
Pilot: you — Private, current, 200 hours. You did not apply carburetor heat during the run-up because the engine ran smoothly. You did not apply it after takeoff because you were focused on the climb and did not think the conditions warranted it. Now, at 450 ft AGL over dense Tampa development, the engine is failing.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 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 engine failure on initial climb over a built-up area? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN14FA435 (2014, FATAL): A Cessna 172N experienced partial engine power loss during initial climb from Natchitoches Regional Airport (Louisiana). The pilot attempted a forced landing in a soybean field but overflew it and struck trees. The probable cause was partial loss of engine power due to an exhaust valve rocker retaining stud backing out of the cylinder head, combined with the pilot's failure to configure and fly the aircraft to land in the available field. The pilot did not survive.
NTSB NYC06LA179 (2006, FATAL): 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 but struck trees. The probable cause was improper maintenance, with a contributing factor being the pilot's failure to land in the best available site.
NTSB CEN24LA362 (2024): A Cessna 172N encountered light rain and carburetor ice at 1,800 ft AGL, resulting in engine roughness and power loss. The probable cause was carburetor ice formation in conditions conducive to serious icing, with insufficient time and altitude for carburetor heat to clear the accumulated ice. The pilot had not applied carburetor heat proactively in conditions that clearly warranted it.
The local environment at KTPA makes this scenario particularly unforgiving: Runway 10's departure end (heading 092°) is dense development, parks/large lots, and wooded wetland — no clear field, no road, no water. An engine failure on the Runway 10 departure at low altitude is a forced landing in a built-up area, not a field landing. There is no open field. The development is the off-field environment. This is not hypothetical; it is the USGS NLCD ground cover off that runway end.
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 patterns: forced landing 22.2%, loss of control inflight 11.1%, loss of control ground 8.9%), but these specific fatal 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: engine power loss on initial climb over unsuitable terrain leaves almost no margin. The decision to attempt a return to the airport vs. commit to a forced landing must be made immediately — within 10–15 seconds. Delay costs altitude. Overflying a potential landing site to try to reach the runway costs altitude and often results in impact with obstacles. The correct response is early recognition, immediate action (carb heat if icing is suspected, or commit to forced landing if power is not recovering), and a disciplined approach to the best available site.
For carburetor ice specifically: the C172N's Lycoming O-320 is carbureted. In warm, moist Gulf Coast air, ice can form at 27°C with high dew point — exactly the conditions you will encounter on a Tampa morning departure. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At low altitude over unsuitable terrain, the decision window is measured in seconds — not minutes. Off Runway 10 at KTPA, the off-field environment is dense development: a delayed response means a forced landing in a built-up area, not a field landing.
Key lesson — In warm, moist Gulf Coast air, the C172N's carbureted O-320 can accumulate serious carburetor ice even at cruise power and above-freezing temperatures. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At low altitude over unsuitable terrain, the decision to attempt a return to the airport vs. commit to a forced landing must be made immediately. Off Runway 10 at KTPA, the off-field environment is dense development: a delayed response means a forced landing in a built-up area, not a field landing. Commit early, fly the best available site, and land at the slowest possible speed.
Debrief — teaching points
Carburetor ice forms in conditions you would not expect.
The FAA icing probability chart shows 'serious icing at glide power' at temperatures between roughly 20°C and 30°C when relative humidity is high — exactly the Gulf Coast morning conditions at KTPA. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The C172N's Lycoming O-320 is carbureted; it has no alternate air system. Carburetor heat is the only tool.
The first symptom is subtle — a dropping tachometer and engine roughness.
In a fixed-pitch airplane like the C172N, carburetor ice first shows as engine roughness and an unexplained RPM decrease. There is no dramatic power cut. Pilots who are not actively monitoring the tachometer miss the early warning. By the time the roughness is obvious, significant ice has accumulated. Scan the tachometer as part of your regular instrument scan, especially in conducive conditions.
Apply full carburetor heat — not partial — and expect an initial RPM drop.
When you apply carb heat to an iced carburetor, the RPM will drop further before it rises. This is expected and normal: the heat is melting ice and the resulting water is briefly disrupting combustion. Do not remove carb heat when the RPM drops — that is the heat working. Hold it full on. The RPM will recover as the ice clears, typically within 15–30 seconds depending on ice accumulation. Partial carb heat can worsen the situation by partially melting ice into water ingestion without fully clearing the restriction.
At KTPA Runway 10, an engine failure on departure is a forced landing in development.
The off-field environment off Runway 10's departure end (heading 092°) is dense development, parks/large lots, and wooded wetland. There is no alternate landing surface — no open field, no road, no water. If the engine quits on the Runway 10 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in a built-up area. This is not a worst-case scenario; it is the geographic reality. Best glide is 65 KIAS. Doors unlatched before landing. Master off just before impact. Flaps for slowest possible touchdown speed — impact energy rises with the square of touchdown speed, so the slowest possible speed matters most. Know this before you line up on Runway 10.
The decision to return vs. commit to a forced landing must be made immediately — within 10–15 seconds.
At 450 ft AGL over unsuitable terrain with a rough engine, you have roughly 20–30 seconds of useful decision time before altitude becomes critical. Delay costs altitude. A 180° turn back to the departure runway at 450 ft AGL in a C172N with partial power loss is marginal at best. If power is not recovering quickly (within 10–15 seconds of applying carb heat or other corrective action), commit to the best available forced-landing site and execute it. Overflying a potential site to try to reach the runway costs altitude and often results in impact with obstacles.
Built from the real accident record
Scenario built from NTSB CEN14FA435 (2014 C172N partial power loss / forced landing into trees), NYC06LA179 (2006 C172N throttle shaft maintenance failure / power loss), CEN24LA362 (2024 C172N carburetor ice / power loss), and regional precedents MIA91LA128, CHI92DER01, CHI92DEM03, CHI89DEM10. Localized to KTPA Runway 10 departure environment.
NTSB reports: CEN14FA435 · WPR12LA093 · NYC06LA179 · CEN24LA362 · MIA91LA128 · CHI92DER01 · CHI92DEM03 · CHI89DEM10
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
Relevant FARs: §91.3 · §91.13 · §91.185
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 KTPA