Engine Failure on Initial Climb at Zephyrhills
Carburetor ice and marginal climb performance force an off-airport landing decision in a 150-hp Cessna 172M
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, climbing out on a 180° heading. Elevation 90 ft MSL; the runway is essentially at sea level. Non-towered field, Class G airspace. CTAF 122.8.
It is a warm, humid Florida afternoon in late spring: OAT 28°C, dew point 22°C, altimeter 29.92. Scattered clouds at 2,500 ft, light rain shower two miles to the northeast. Visibility 8 SM. Classic Gulf Coast conditions — exactly the environment the FAA icing probability chart marks as 'serious icing at glide power, moderate icing at cruise power.' The off-field environment off Runway 19 (climb-out heading 180°) is marginal: mostly open developed areas (parks, large lots), evergreen forest, and low-density development — workable for a forced landing, but not ideal.
You are 400 ft AGL, climbing through 78 KIAS (Vy), heading 180°, when the engine begins to run rough. Power is noticeably down — the tachometer is dropping. The field is behind you. Off-field options ahead are mixed: some open areas, some trees, some scattered development. KZPH is non-towered; you are on CTAF.
Aircraft: Cessna 172M, solo, full fuel, within limits. Carbureted Lycoming O-320-E2D, 150 hp, fixed-pitch prop, steam panel, fuel selector on BOTH. Nothing was written up; the airplane was airworthy at departure. The 172M is the lower-powered variant — climb performance is marginal, especially in heat and at gross weight.
Pilot: you — a Private pilot, current, roughly 200 hours total. 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 heads-down on the climb and the conditions did not register as icing-conducive.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about the C172M's climb performance and carburetor ice? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA09LA379 (2009): A Cessna 172M student pilot on a solo instructional flight experienced engine power loss during the base-to-final turn in the traffic pattern. The ambient conditions (75°F OAT, 55°F dew point) were conducive to serious carburetor icing per the FAA icing probability chart. The pilot made a forced landing in a field. The probable cause was a partial loss of engine power for undetermined reasons — consistent with carburetor icing.
NTSB DFW05CA237 (2005): A Cessna 172M lost engine power during initial climb due to carburetor icing and made a forced landing in a field. The pilot stalled while maneuvering to avoid a fence — a classic trap: low altitude, low airspeed, pilot trying to stretch the approach to the runway instead of accepting the forced landing. The probable cause was the pilot's failure to maintain airspeed, with contributing factors being the loss of engine power and high density altitude.
NTSB CEN22LA309 (2022): A Cessna 172M experienced engine power loss during cruise flight due to a stuck exhaust valve. The pilot performed a forced landing in a field between corn crops, resulting in substantial fuselage damage. The lesson: not all engine failures are carburetor ice. Mechanical failures — stuck valves, throttle cable failures, propeller issues — also force off-airport landings.
NTSB WPR13LA035 (2012): A Cessna 172M on an aerial photography mission experienced loss of engine power when the pilot applied full throttle during climb. The throttle control cable outer jacket fragmented, preventing proper throttle control. The pilot made a forced landing. Maintenance history and preflight rigor matter — a frayed cable can fail catastrophically.
NTSB CHI07LA177 (2007): A Cessna 172M departed 243 pounds over gross weight and out of balance. During initial climb at 100–150 ft AGL, the engine lost power; the aircraft stalled and impacted terrain. The probable cause was improper weight and balance and failure to maintain airspeed. The C172M is marginal on climb performance at gross weight — overweight and out-of-balance is a recipe for disaster on takeoff.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills Municipal Airport. KZPH has its own accident history (see field dominant patterns: FORCED_LANDING 29.2%, LOSS_OF_CONTROL_INFLIGHT 29.2%, STALL_SPIN 16.7%), but these specific NTSB events happened elsewhere. The scenario is localized to KZPH to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: the C172M is a 150-hp airplane with marginal climb performance. Carburetor ice, mechanical failures, weight-and-balance errors, and high density altitude all conspire to rob the airplane of the climb performance it barely has. Early recognition of engine anomalies, proactive carb heat use in conducive conditions, and a willingness to execute a controlled forced landing rather than stall trying to stretch a glide are the 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. The C172M's 150-hp engine is marginal on climb — any power loss at low altitude is serious. Off Runway 19 at KZPH, the off-field environment is marginal but workable (parks, forest, scattered development). A controlled forced landing in the best available surface is preferable to stalling trying to stretch a glide to the runway.
Debrief — teaching points
The C172M is a 150-hp airplane — climb performance is marginal, especially at gross weight, in heat, or at high density altitude.
The C172M is the lower-powered variant of the 172 family. At gross weight, in warm air, or at high density altitude, the climb performance is noticeably marginal. Any loss of power on initial climb is serious because there is little reserve. The NTSB CHI07LA177 accident (overweight departure, stall on climb) and DFW05CA237 (high density altitude contributing factor) both highlight this. Know your airplane's limits and respect them.
Carburetor ice forms in conditions you would not expect — and the C172M is particularly susceptible.
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 afternoon conditions at KZPH. 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. ERA09LA379 and DFW05CA237 both involved carb ice in above-freezing conditions.
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.
Off Runway 19 at KZPH, the off-field environment is marginal but workable — parks, forest, scattered development.
The off-field environment off Runway 19's departure end (heading 180°) is marginal: mostly open developed areas (parks, large lots), evergreen forest, and low-density development. This is workable for a forced landing — not ideal, but better than open water or dense development. If the engine fails on the Runway 19 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in this environment. Know the off-field options before you line up on the runway.
A controlled forced landing is not failure — it is airmanship.
When the engine is failing and altitude is insufficient to return to the airport, a controlled forced landing in the best available surface is the correct outcome — not a stall/spin trying to stretch a glide to the runway. Best glide is 65 KIAS. Doors unlatched before touchdown. 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. Survival rates in controlled forced landings are significantly better than in uncontrolled ones. DFW05CA237 shows the trap: the pilot stalled trying to avoid a fence instead of accepting the forced landing. ERA09LA379 shows the right outcome: a controlled forced landing in a field.
Built from the real accident record
Scenario built from NTSB ERA09LA379 (2009 C172M carburetor ice / forced landing), DFW05CA237 (2005 C172M carb ice / stall on final), CEN22LA309 (2022 C172M stuck valve / forced landing), WPR13LA035 (2012 C172M throttle cable failure / forced landing), and CHI07LA177 (2007 C172M overweight / stall on climb). Localized to KZPH.
NTSB reports: ERA09LA379 · DFW05CA237 · CEN22LA309 · WPR13LA035 · CHI07LA177
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 KZPH