Engine Failure on Initial Climb — Brooksville
Partial power loss at 400 ft AGL off Runway 03 over congested residential development — no good forced-landing site ahead
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 03, initial climb on a 026° heading. Field elevation 76 ft MSL. You are a Private pilot with 180 hours total time, current and proficient. This is your second visit to KBKV; you are not deeply familiar with the field or its surrounding terrain.
It is a warm, humid Florida morning in late May: OAT 26°C, dew point 20°C, altimeter 29.94. Scattered clouds at 2,500 ft, light rain shower two miles to the northeast. Visibility 8 SM. Density altitude is approximately 1,800 ft — the field's 76 ft elevation plus a temperature/pressure offset. The C172M's 150 hp Lycoming O-320 will climb at roughly 500 fpm in these conditions at gross weight.
The off-field environment off Runway 03's climb-out (heading 026°) is mixed: mostly pasture and hay fields in the immediate 0.5 nm, but medium-density residential development begins at roughly 0.7 nm and extends for 2+ nm. There are no large open fields, no parks, no water bodies suitable for a forced landing. The terrain is flat; trees are scattered but present.
You have completed a normal preflight and run-up. The engine ran smoothly during the run-up; all systems checked. You did not apply carburetor heat during the run-up because the engine showed no roughness. You are cleared for takeoff on Runway 03. Tower is active (current time 0900 local; tower operates 0700–2200).
Aircraft: Cessna 172M, solo, full fuel (36 gal usable), within CG and weight limits. Carbureted Lycoming O-320-E2D, 150 hp, fixed-pitch prop, fixed gear, fuel selector on BOTH. Steam panel (vacuum-driven attitude and heading indicators). Nothing was written up; the airplane was airworthy at departure.
Pilot: You — Private pilot, 180 hours total, roughly 40 hours in type (C172M). You have not experienced an engine failure on takeoff. You are familiar with the C172M's marginal climb performance, especially in heat and at gross weight. You know best glide is 65 KIAS and that the O-320 is carbureted and susceptible to carburetor ice in moist conditions.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we enter the decision tree — what do you know about engine failure on initial climb in the C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR09FA316 (2009): 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 a go-around, with contributing factors of lack of experience with turf airstrips and delayed go-around initiation. The lesson: at low altitude with marginal power, commit to landing rather than attempting a go-around.
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 teaching angle: recognize early that return-to-runway is not feasible and commit to the best available forced-landing site rather than attempting to 'milk it around' over populated areas.
NTSB CHI03LA083 (2003): An amateur-built Steen Skybolt experienced partial engine power loss during takeoff and the pilot attempted to return to the runway, landing short in a field. The probable cause was partial loss of engine power for undetermined reasons, with contributing factors including the pilot's improper decision to attempt runway return and unsuitable terrain. The teaching angle: accept forced landing in available field early rather than attempting marginal runway return from low altitude, which risks landing short in worse terrain.
NTSB WPR12LA092 (2012): A Piper PA-28R-201T experienced partial engine power loss between 300 and 500 feet AGL after takeoff from Kalispell, Montana, and made a forced landing on a residential street. The probable cause was magneto malfunction, with contributing factors including non-adherence to the manufacturer's recommended magneto overhaul schedule. The teaching angle: at low altitude with partial power loss over congested area, commit immediately to safest available landing site (even if suboptimal) rather than attempting to stretch climb or maneuver.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history (dominant patterns: hard landing 26.9%, forced landing 11.5%, runway excursion 11.5%), but these specific fatal and serious events happened elsewhere. The scenario is localized to KBKV to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: engine failure or partial power loss on initial climb at low altitude is unforgiving. The decision window is measured in seconds, not minutes. Off Runway 03 at KBKV, the off-field environment is pasture and hay initially (0–0.7 nm), but medium-density residential development begins at 0.7 nm and extends for 2+ nm. There is no large open field suitable for a forced landing beyond the immediate departure area. A delayed response or an attempt to stretch the glide over houses is the path to a fatal accident. Early recognition of the problem, immediate corrective action (carb heat if roughness), and a commitment to the best available forced-landing site (if power is truly lost) are the only defenses.
Key lesson — In warm, moist Gulf Coast air, the C172M'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 on initial climb, the decision window is measured in seconds. Off Runway 03 at KBKV, the off-field environment transitions from pasture to residential development within 0.7 nm. If engine power is truly lost and return to the airport is not feasible, commit immediately to the best available forced-landing site in the open area — do not attempt to stretch the glide over populated development.
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 KBKV. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The C172M'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 C172M, 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 KBKV Runway 03, an engine failure on initial climb is a forced landing in pasture or residential development.
The off-field environment off Runway 03's climb-out (heading 026°) is pasture and hay fields for the first 0.7 nm, but medium-density residential development begins at 0.7 nm and extends for 2+ nm. There is no large open field, no park, no water body suitable for a forced landing beyond the immediate departure area. If the engine fails on the Runway 03 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in pasture (if you are still in the first 0.7 nm) or in residential development (if you have drifted farther). 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 03.
The 'impossible turn' is real — commit to forced landing early rather than attempting a marginal return to the runway.
At 400 ft AGL on initial climb, a 180° turn back to the departure runway is marginal at best, especially with a rough or failing engine. The NTSB accident data (WPR09FA316, CHI03LA083, WPR12LA092) consistently show that pilots who attempt a marginal return to the runway from low altitude often land short in worse terrain or stall/spin trying to stretch the glide. The safer decision is to recognize early that return-to-runway is not feasible and commit to the best available forced-landing site — in this case, the pasture area ahead if you are still in the first 0.7 nm. Do not attempt to 'milk it around' over populated development.
Proactive carb heat use in conducive conditions is not optional.
The C172M POH and the FAA Pilot's Handbook of Aeronautical Knowledge both recommend applying carburetor heat when conditions are conducive to icing — before the symptom appears. In a Gulf Coast summer departure, with OAT near 26°C and dew point near 20°C, that means applying carb heat during the run-up check (and confirming the expected RPM drop, then recovery) and considering its use during climb in visible moisture or high humidity. Waiting for the roughness to appear at 400 ft AGL over residential development is waiting too long.
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 off-airport landing / tree strike on takeoff), and regional precedents CHI92DER01 (1992 engine-out over residential), CHI03LA083 (2003 partial power loss / forced landing decision), WPR12LA092 (2012 partial power loss over congested area), FTW85LA278 (1985 engine failure / forced landing over hazardous terrain). Anonymized and localized to KBKV.
NTSB reports: WPR09FA316 · GAA16CA011 · GAA15CA088 · ERA14CA430 · CHI92DER01 · CHI03LA083 · WPR12LA092 · FTW85LA278
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 172M scenarios · More scenarios at KBKV