Engine Failure on Initial Climb — Dense Development Below
Total power loss at 400 ft AGL over Tampa's residential neighborhoods. No good forced-landing site. Every second counts.
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 10, initial climb on heading 092° over dense residential development. Field elevation 26 ft MSL. This is a towered Class B airport; ATC is active 24 hours.
It is a hot, humid Florida summer morning: OAT 32°C, dew point 26°C, altimeter 29.89. Scattered clouds at 3,500 ft, visibility 10 SM. The runway is long (6,999 ft) and the crosswind is light. Density altitude is approximately 3,200 ft — the airplane will climb like it is at 3,200 ft elevation, not sea level. The C172M's 150 hp Lycoming O-320 is marginal in these conditions, especially at gross weight.
You are 400 ft AGL, climbing through 78 KIAS (Vy, best rate of climb), heading 092°, when the engine suddenly loses power. The tachometer drops to 1,200 RPM and continues to fall. The airplane is no longer climbing — it is maintaining altitude at best. Below you is a dense grid of residential neighborhoods, shopping centers, and light commercial development. There are no open fields, no parks large enough for a safe landing, no water, no roads wide enough to land on. The nearest airport is behind you (KTPA) or ahead at distance (KPIE, 9.1 nm away). You are in Class B airspace; ATC is aware of your departure.
Aircraft: Cessna 172M, solo, full fuel, within limits. Lycoming O-320-E2D, 150 hp, carbureted, fixed-pitch prop, fuel selector on BOTH. The airplane was released from maintenance two days ago after a routine 100-hour inspection. The pre-takeoff run-up was normal — magnetos checked, engine smooth, no anomalies noted.
Pilot: you — a Private pilot, current, roughly 250 hours total. You are familiar with KTPA from previous training but have not flown this particular aircraft before today. You did not apply carburetor heat during the run-up because the engine ran smoothly. You did not apply it after takeoff because the initial climb was normal.
- {'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 get into the decision tree — what do you already know about engine failure on initial climb in a C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR09FA316 (2009, FATAL): A Cessna 172M on approach to Tieton State Airport in mountainous terrain failed to land and initiated a go-around at low altitude, striking trees at the runway end. The probable cause was the pilot's failure to maintain clearance from trees during the go-around, with contributing factors including lack of flight experience and delayed go-around initiation. The lesson: at low altitude over unsuitable terrain, commit to the landing decision early. A go-around at 200 ft AGL over trees is a fatal trap.
NTSB GAA15CA088 (2015): A Cessna 172M struck trees during takeoff when the pilot attempted to abort after discovering the gust lock was still installed in the yoke. The probable cause was the pilot's failure to remove the gust lock during preflight inspection, combined with crosswind conditions that pushed the aircraft off the runway. The lesson: a thorough preflight inspection is the first line of defense. Post-maintenance flights are particularly vulnerable to assembly errors.
NTSB CHI92DER01 (1992): A Goehring Quickie lost engine power during initial climb after a touch-and-go landing and made a forced landing in a residential area after descending through trees and a house. The probable cause was carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The lesson: recognize early signs of power loss (decreased rate of climb, RPM drop) and commit to the best available landing site immediately rather than attempting to stretch the glide over congested terrain.
NTSB CHI89DEM10 (1989, FATAL): A Fletcher Sonerai-2L homebuilt aircraft lost engine power during initial climb after takeoff due to a loose cylinder head that had been improperly installed during recent valve replacement. The probable cause was improper maintenance by the pilot/owner. The lesson: post-maintenance engine failures are a real risk. Improper assembly or adjustment during service can cause in-flight power loss with no warning.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (see field dominant patterns: forced landings, loss-of-control events, gear-up landings), but these specific 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 failure on initial climb over unsuitable terrain is unforgiving. The decision window is measured in seconds. Carburetor ice in warm, humid conditions, post-maintenance assembly errors, and ignition system failures are all real risks. The fix is early recognition, immediate action (carb heat, diagnostics, forced-landing commitment), and a clear decision: return to the airport if power is marginal, or commit to the best available landing site if power is lost. At 400 ft AGL over Tampa's dense development, there is no third option.
Key lesson — In warm, humid Florida conditions, the C172M's carbureted O-320 can accumulate carburetor ice on initial climb even at 32°C. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At low altitude over dense development, the decision window is measured in seconds — not minutes. Off Runway 10 at KTPA, the off-field environment is residential neighborhoods and commercial development: a delayed response means a forced landing in trees or structures, not a field landing. Commit early to the best available site.
Debrief — teaching points
Carburetor ice forms in warm, humid conditions — not just in cold weather.
The FAA icing probability chart shows serious carburetor icing risk at glide power in temperatures between roughly 20°C and 30°C when relative humidity is high — exactly the Florida summer conditions at KTPA. OAT 32°C with dew point 26°C is a classic carb-ice environment. The C172M's Lycoming O-320 is carbureted; it has no fuel injection, no alternate air system. Carburetor heat is the only tool. Recognize these conditions during preflight and be ready to apply carb heat on initial climb.
The first symptom is subtle — a dropping tachometer and loss of climb performance.
In a fixed-pitch airplane like the C172M, carburetor ice first shows as a loss of climb rate and an unexplained RPM decrease. There is no dramatic power cut. Pilots who are not actively monitoring the tachometer and vertical speed indicator miss the early warning. By the time the roughness is obvious, significant ice has accumulated. Scan the tachometer and VSI as part of your regular instrument scan, especially on initial climb 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, the off-field environment is dense residential development — there is no suitable forced-landing site.
The off-field environment off Runway 10's departure end (heading 092°) is dense residential development, shopping centers, and light commercial areas. There is no open field, no park large enough for a safe landing, 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 trees, structures, or parking lots — all hazardous. This is not a worst-case scenario; it is the geographic reality. Best glide is 65 KIAS. Flaps for slowest possible touchdown speed. Know this before you line up on Runway 10.
Post-maintenance engine failures are a real risk — do not assume a normal run-up guarantees in-flight reliability.
NTSB CHI89DEM10 and GAA15CA088 both involved post-maintenance failures: a loose cylinder head and a gust lock left installed. A normal pre-takeoff magneto check and run-up do not detect all assembly errors. After any maintenance, especially engine work or control system work, be alert for any unusual behavior on initial climb. If something feels wrong — rough running, unexpected power loss, sluggish climb — return to the airport immediately for a precautionary landing and inspection. Do not press on.
At low altitude over unsuitable terrain, commit to a forced landing immediately — do not attempt to stretch the glide to the airport.
NTSB WPR09FA316 and CHI92DER01 both show the fatal trap of attempting to stretch a glide over trees or unsuitable terrain. At 300 ft AGL over dense development, if the engine is failing and the airport is not assured, commit to the best available landing site immediately — a parking lot, a wide street, a park. A controlled forced landing in an open area is survivable. An uncontrolled descent into trees or structures is not. Establish 65 KIAS best glide, pick your landing site, and execute the approach. Do not try to make the airport.
Built from the real accident record
Scenario built from NTSB WPR09FA316 (2009 C172M go-around/tree strike in mountainous terrain), GAA16CA011 (2015 C172M threshold light strike on approach), GAA15CA088 (2015 C172M gust-lock takeoff abort), ERA14CA430 (2014 C172M field landing/tree strike on takeoff), and regional precedents MIA91LA128, CHI92DER01, CHI92DEM03, CHI89DEM10 (engine-out forced landings over congested terrain). Anonymized and localized to KTPA.
NTSB reports: WPR09FA316 · GAA16CA011 · GAA15CA088 · ERA14CA430 · 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 · PA.II.E — Takeoff and Climb
Relevant FARs: §91.3 · §91.13 · §91.185 · §91.527
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