FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

Power Loss on the Base-to-Final Turn

Carburetor ice, partial power loss, and a tight decision window in the traffic pattern — the C172M's marginal climb and low altitude leave no room for hesitation

Cessna 172M · St. Petersburg Clearwater International Airport (KPIE) · Private · Approach / Landing

The scenario

Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, on a local VFR training flight. Elevation 11 ft MSL. You are a Private pilot with 180 hours total time, current and proficient. This is a familiar home field.

It is a warm, humid Florida afternoon in late spring: OAT 24°C, dew point 18°C, altimeter 29.92. Scattered clouds at 2,500 ft, light rain shower two miles to the east. Visibility 8 SM. Classic Gulf Coast conditions — warm, moist air at reduced power is the FAA icing probability chart's 'serious icing at glide power' scenario.

You have completed a local training flight and are now on the downwind leg for Runway 18, 1,200 ft AGL, heading 351°, at 70 KIAS. The tower is active (it is 1400 local; tower operates 0600–2300). You are in Class D airspace. The approach is stable; you are planning a normal landing.

Aircraft: Cessna 172M, solo, full fuel, within limits. Carbureted Lycoming O-320-E2D, 150 hp, fixed-pitch prop, steam panel, fuel selector on BOTH. The airplane was airworthy at departure; nothing was written up. The C172M is the lower-powered variant — climb performance is marginal, especially in warm, humid conditions.

Pilot: you — a Private pilot, 180 hours, current. You did not apply carburetor heat during the run-up because the engine ran smoothly. You did not apply it during the approach because you were focused on the landing and did not consider carb ice a threat in warm air.

The decision

Before we get into the decision tree — what do you already know about carburetor ice in the C172M and the approach phase? (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 were 75°F OAT and 55°F dew point — conducive to serious carburetor icing per the FAA icing probability chart. The pilot made a forced landing in a field. The probable cause was carburetor icing at glide power, with the pilot having failed to apply carburetor heat proactively in conducive conditions.

NTSB CEN24LA168 (2024): A Cessna 172M on an IFR flight to Bemidji Regional Airport experienced engine power loss due to carburetor icing during descent in night IMC. The pilot touched down on a building roof and impacted a retaining wall and ground. The probable cause was the pilot's delayed use of carburetor heat, which resulted in ice accumulation beyond the point where heat could restore full engine power.

NTSB CEN22LA181 (2022): A Cessna 172M on a personal flight experienced partial engine power loss during a go-around attempt from a low approach to an upsloping turf runway. The probable cause was the pilot's failure to use carburetor heat during the approach and his unsuitable flight profile for the runway configuration, which resulted in a partial loss of engine power and an impact with terrain during the attempted go-around.

The local environment at KPIE makes this scenario consequential: Runway 18's climb-out environment (heading 171°) is medium development, parks, and open developed areas — not ideal for a forced landing, but workable. Runway 36's climb-out (heading 351°) is open water and parks — a ditching scenario. Off Runway 22's climb-out (heading 220°) is dense development — poor. The runway you choose and the time you have to diagnose and act determine the outcome.

The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. ERA09LA379 happened at a different field; CEN24LA168 was in Bemidji, Minnesota; CEN22LA181 was at a turf runway in the Midwest. The scenario is localized to KPIE to make the off-field environment real and consequential for you as a student here.

The consistent thread across all these events: carburetor ice in the C172M is insidious. It builds gradually, the first symptom is roughness and a dropping tachometer (not a dramatic power cut), and by the time it is obvious, it may be too late for a comfortable recovery. The fix — full carburetor heat, immediately, at the first sign of roughness in conducive conditions — is simple. The failure is always a delay. In the approach phase, where altitude is already low and options are limited, the margin for error is zero.

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. In the approach phase at 1,200 ft AGL, the decision window is measured in seconds — not minutes. Proactive carb heat use during the approach in conducive conditions is not optional; it is the correct procedure. The C172M's marginal climb performance (150 hp) means a go-around with a degrading engine is risky — the better call is to recognize the symptom early and apply carb heat before you are committed to the landing.

Debrief — teaching points

Carburetor ice forms in conditions you would not expect — and the approach phase is a high-risk time.

The FAA icing probability chart shows 'serious icing at glide power' at temperatures between roughly 15°C and 25°C when relative humidity is high — exactly the Gulf Coast afternoon conditions at KPIE. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power (glide power, approach 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. In the approach phase, where you are already at reduced power and low altitude, the risk is acute.

The first symptom is subtle — a dropping tachometer and engine roughness — and it appears when you are committed to the pattern.

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. In the approach phase, you are already at 1,200 ft AGL on downwind — committed to the pattern. Scan the tachometer as part of your regular instrument scan, especially in conducive conditions. If the RPM is unwinding and you cannot explain it, assume carb ice.

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.

Proactive carburetor heat use during the approach in conducive conditions is the correct procedure.

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 approach, with OAT near 24°C and dew point near 18°C, that means considering carb heat during the descent and approach. Waiting for the roughness to appear at 1,200 ft AGL on downwind is waiting too long. The margin for error in the approach phase is zero.

The C172M's marginal climb performance (150 hp) makes a go-around with a degrading engine risky.

The C172M is the lower-powered variant of the 172 family — 150 hp, not 160 or 180. Climb performance is marginal, especially in warm, humid conditions at gross weight. If you initiate a go-around with a rough, power-down engine, the climb will be sluggish and you may not be able to regain altitude. The better call is to recognize the carb-ice symptom early (on downwind, before you are committed to the landing) and apply carb heat immediately. If you are already on base or final with a degrading engine, a straight-in emergency landing to the runway is safer than a go-around.

At KPIE, the off-field environment varies by runway. Know where you are and what is below you.

Runway 18's climb-out (heading 171°) is medium development and parks — workable for a forced landing. Runway 36's climb-out (heading 351°) is open water — a ditching scenario. Runway 22's climb-out (heading 220°) is dense development — poor. Runway 04's climb-out (heading 40°) is open water — a ditching scenario. In the approach phase, you are committed to landing on the runway you are approaching. Know the off-field environment for that runway and understand that the runway is your goal, not a backup option.

Built from the real accident record

Scenario built from NTSB ERA09LA379 (2009 C172M carburetor ice on base-to-final), CEN24LA168 (2024 C172M delayed carb heat / night IMC power loss), CEN22LA309 (2022 C172M stuck exhaust valve / forced landing), CEN22LA181 (2022 C172M carb heat failure on go-around), and WPR13LA035 (2012 C172M throttle cable failure). Localized to KPIE.

NTSB reports: ERA09LA379 · CEN24LA168 · CEN22LA309 · CEN22LA181 · WPR13LA035

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.VIII.D — Approach and Landing

Relevant FARs: §91.3 · §91.13 · §91.185

Run this scenario yourself

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 KPIE