FlightEdge
Sample scenario-based training
SAMPLE SBTTakeoff / Initial Climb

Partial Power Loss on Initial Climb

Engine failure over congested development on the Runway 03 departure — no good forced-landing site ahead, and the decision window is seconds

Cessna 172N · Brooksville–Tampa Bay Regional Airport (KBKV) · Private · Takeoff / Initial Climb

The scenario

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 03, initial climb on a 026° heading. Elevation 76 ft MSL. The runway is 4,200 ft of concrete, well-maintained. The field is towered, part-time (0700–2200 local); it is currently 0900 local and the tower is active. You are in Class D airspace; Tampa Class B overlies the field at 6,000 ft MSL.

The off-field environment off Runway 03's climb-out (heading 026°) is mixed: pasture and hay fields, open developed areas (parks, large lots), and medium-density residential development. It is NOT open water, NOT a highway, NOT a clear field. It is a patchwork of small farms, scattered houses, and developed areas. A forced landing here will be a challenge — you will be looking for the least-bad option among imperfect choices.

You are 300 ft AGL, climbing through 73 KIAS (Vy, best rate of climb), heading 026°, when the engine begins to lose power. The tachometer is unwinding. The power loss is partial, not total — the engine is still running, but noticeably down. The runway is now 0.8 nm behind you. You have roughly 30 seconds to diagnose and decide.

Aircraft: Cessna 172N, solo, full fuel, within limits. Lycoming O-320 carbureted engine, fixed-pitch prop, steam panel. The airplane passed a preflight and an engine run-up. Nothing was written up. The last annual inspection was 6 months ago.

Pilot: you — a Private pilot, current, roughly 180 hours total. You are unfamiliar with KBKV; this is your first departure from this field. You did not brief the off-field environment. You are focused on the climb.

The decision

Before we get into the decision tree — what do you know about partial engine power loss on initial climb in the C172N? (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) due to an exhaust valve rocker retaining stud backing out of the cylinder head. The pilot attempted a forced landing in a soybean field but overflew it and struck trees, resulting in a fatal accident. The probable cause was the mechanical failure combined with the pilot's failure to configure and fly the aircraft to land in the available field rather than overshoot it.

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 that resulted in collision with trees. The accident was attributed to improper maintenance combined with the pilot's failure to commit to an available landing site.

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 accident resulted from magneto malfunction. The contributing factor was the pilot's failure to commit early to the safest available landing site.

The local environment at KBKV makes this scenario particularly challenging: the off-field environment off Runway 03's climb-out (heading 026°) is a patchwork of pasture, open development (parks, large lots), and medium-density residential development. There is no single clear field, no highway, no water. A forced landing here requires early recognition that return to the runway is not feasible and immediate commitment to the least-bad available option. The NTSB CEN14FA435 pilot who overflew the soybean field and struck trees did not make this commitment. The pilot who commits early to a pasture or open field survives.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport. KBKV has its own accident history (see field dominant patterns: hard landings, forced landings, runway excursions), but these specific fatal 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: partial engine power loss on initial climb is insidious. The engine is still running, so pilots delay the decision to commit to a forced landing. They attempt to return to the runway or stretch the glide, and by the time they realize the runway is not feasible, they are too low and too far away. The correct decision is to diagnose quickly (carb heat, mag check, throttle position), and if power does not recover, commit immediately to the best available landing site rather than attempt a marginal return to the runway.

Key lesson — Partial engine power loss on initial climb over congested development requires immediate diagnosis (carb heat, mag check) and, if power does not recover, early commitment to a forced landing in the best available terrain. At 300 ft AGL over mixed pasture and development, return to the runway is marginal at best. The correct decision is to accept the forced landing in available open terrain rather than attempt to stretch the glide over houses and power lines. Commit early; do not overshoot the available field.

Debrief — teaching points

Partial power loss is different from total engine failure — diagnosis and response are different.

When the engine is still running but producing less power, the first response is diagnosis: carburetor heat (if carbureted), magneto check, throttle position, fuel selector. A total engine failure requires immediate best-glide speed and landing site selection. A partial power loss may be recoverable with the correct action. In the C172N, carburetor ice is a common cause of partial power loss in warm, moist conditions. A magneto check during run-up can reveal a weak mag before takeoff; a partial power loss in flight may indicate a mag that was marginal on the ground. Post-maintenance failures (throttle shaft, exhaust valve stud) are also possible. Diagnose first; then decide.

At 300 ft AGL over congested development, return to the runway is marginal at best.

The 'impossible turn' is a real phenomenon: at low altitude with partial power loss, a 180° turn back to the departure runway requires altitude and control authority you may not have. The NTSB data shows that pilots who attempt marginal returns to the runway often undershoot into terrain ahead of the runway or lose control in the turn. The correct decision at 300 ft AGL with partial power loss over development is to accept that return to the runway is not the priority. Scan the terrain ahead for the best available landing site — a pasture, open field, or large cleared area — and commit to landing there rather than attempt a marginal return.

Commit early to the best available landing site; do not overshoot it.

The NTSB CEN14FA435 pilot identified a soybean field as a landing site but overflew it and struck trees. The pilot's failure was not the identification of the field; it was the failure to commit to landing in it. At low altitude with partial power loss, the descent rate is fixed by physics. If you identify a landing site and then try to stretch the glide to a better one, you will overshoot both. The correct decision is to identify the best available option and commit to it — land in the pasture, not the road; land in the field, not the house. Early commitment is the key.

Best glide speed for the C172N is 65 KIAS — establish it immediately when power is lost.

Best glide speed maximizes glide distance and gives the most time to manage the emergency. At 65 KIAS, the C172N will glide approximately 8–9 nm from 5,000 ft AGL. At 300 ft AGL, that translates to roughly 0.5 nm of glide distance — enough to reach a landing site ahead if you commit early. Slower speeds reduce glide distance; faster speeds increase descent rate and impact energy. Establish 65 KIAS immediately when power is lost and maintain it until landing.

Full flaps on a forced landing minimize impact energy — touchdown speed is the dominant factor.

Impact energy rises with the square of touchdown speed. A forced landing at 40 KIAS (Vs0, stall speed in landing configuration with full flaps) is significantly less damaging than a landing at 65 KIAS (best glide). Full flaps (30°) in the C172N reduce the stall speed from 48 KIAS (clean) to 40 KIAS (landing). As the landing site is made and altitude is assured, add full flaps to slow the airplane to the minimum safe speed. This is the single most important factor in surviving a forced landing.

Off-field environment matters — know what is ahead of you on departure.

The off-field environment off Runway 03 at KBKV is a patchwork of pasture, open development, and medium-density residential development. There is no single clear field, no highway, no water. A forced landing here requires early recognition of the available options and commitment to the best one. Before every departure, brief the off-field environment for the runway in use. Know what is ahead of you. If the engine fails, you will not have time to figure it out.

Built from the real accident record

Scenario built from NTSB CEN14FA435 (2014 C172N partial power loss on initial climb, forced landing in field), NYC06LA179 (2006 C172N throttle-shaft maintenance failure, partial power loss), WPR12LA092 (2012 PA-28R partial power loss 300–500 ft AGL over congested area), and local-environment precedents CHI92DER01, CHI03LA083, FTW85LA278. Anonymized and localized to KBKV.

NTSB reports: CEN14FA435 · WPR12LA093 · NYC06LA179 · CEN24LA362 · 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

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 172N scenarios · More scenarios at KBKV