Engine Failure on the Runway 22 Climb-Out
Total power loss at 400 ft AGL over dense residential development — no good forced-landing site ahead, and the decision window is measured in seconds
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 22, climbing out on a 220° heading. Field elevation 11 ft MSL. You are a Private pilot, roughly 200 hours total time, on a local VFR flight in a Cessna 172N. Solo, full fuel, within limits.
Conditions are VFR and benign: clear skies, light winds, visibility 10 SM. OAT 26°C. The airplane was released from maintenance yesterday — a routine throttle cable inspection and adjustment as part of a post-annual sign-off. The mechanic's work was not independently verified by the shop foreman before the airplane was returned to service.
You are cleared for takeoff on Runway 22. The runway is 6,000 ft of asphalt; you rotate at 55 KIAS, climb at 73 KIAS (Vy). At 400 ft AGL, heading 220°, the engine suddenly loses power. The tachometer unwinds rapidly. You have no throttle response — the throttle is already full forward and the engine is dying.
Off Runway 22's climb-out (heading 220°), the off-field environment is dense residential development — houses, streets, small parks. There is no open field, no water, no road suitable for a forced landing. The terrain is built-up and unforgiving. You are at 400 ft AGL with a dead engine and no good landing site ahead.
KPIE tower is active (current time 1000 local, within 0600–2300 operating hours). You are in Class D airspace (ceiling 1,600 MSL). The tower is aware of your departure and will be monitoring your climb-out.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'C172N'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about engine failure on initial climb in a C172N? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC06LA179 (2006): 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 probable cause was improper maintenance of the throttle shaft, which resulted in partial loss of engine power during cruise flight.
NTSB CEN25LA168 (2025): A Cessna 172N on an instructional flight lost total engine power on final approach when the throttle cable was found disconnected from the carburetor. The pilot executed a forced landing to a field. The accident resulted from improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic. This is the exact failure mode in this scenario: a throttle control disconnection resulting in total loss of engine power.
NTSB CHI83LA094 (1983): A Piper PA-22-135 lost engine power during takeoff climb at 150 feet AGL and struck 60-foot trees near the runway end while attempting to return to the airport. The accident resulted from a fractured mixture control cable that caused total engine power loss. The pilot's attempt to turn back to the runway at 150 ft AGL was unsuccessful; the airplane struck trees.
NTSB SEA92LA095 (1992): A Ryan ST-3KR lost engine power during initial climb after takeoff due to fatigue failure of the crankshaft counterweight cap screws. The pilot made a forced landing on a residential street where the aircraft impacted an embankment, ground looped, and was destroyed by post-impact fire. The accident resulted from loss of engine power due to crankshaft fatigue failure, with a contributing factor of lack of suitable terrain for forced landing. The pilot's attempt to land on a street in a congested area resulted in impact with an embankment.
NTSB MIA91LA128 (1991): A Sonerai-II homebuilt aircraft experienced total engine failure shortly after takeoff and made a forced landing in an alley, where it touched down hard, bounced, and struck a telephone pole. Witnesses noted reduced power on takeoff, but the pilot did not commit decisively to a landing area until it was too late. The accident resulted from the pilot's improper adjustment of the carburetor mixture control and delay in committing to a landing area.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. However, the failure modes and the decision patterns are identical: engine failure on initial climb or takeoff, followed by either a successful forced landing in a suitable area or an unsuccessful attempt to turn back to the runway or land on an unsuitable surface. The consistent lesson: recognize engine failure early, establish best glide immediately, commit decisively to the best available landing area ahead, and execute the landing smoothly.
At KPIE Runway 22, the off-field environment on the climb-out (heading 220°) is dense residential development — houses, streets, small parks. There is no open field, no water, no road suitable for a forced landing. The park in this scenario is the best available option. The NTSB precedents show that pilots who delay committing to a landing area or attempt to land on unsuitable surfaces (streets, alleys, parking lots) often strike obstacles and are killed. Commit early to the best available area, even if it is not ideal.
Key lesson — Engine failure on initial climb over congested terrain is survivable if you commit decisively to the best available landing area ahead. At 400 ft AGL with a dead engine, the turn back to the runway is marginal and the approach will be unstable. Establish best glide at 65 KIAS immediately, identify the best available landing area (open grass, park, field — not a street or parking lot), configure with full flaps to minimize touchdown speed, and execute a smooth landing. The NTSB precedents (NYC06LA179, CEN25LA168, CHI83LA094, SEA92LA095, MIA91LA128) all show that delay in committing to a landing area or attempting to land on unsuitable surfaces results in impact with obstacles. Commit early, commit decisively, and execute the landing smoothly.
Debrief — teaching points
Engine failure on initial climb is a low-altitude emergency with a short decision window.
At 400 ft AGL with a dead engine, you have roughly 20–30 seconds of useful altitude before you must commit to a landing area. There is no time for extended troubleshooting, no time for multiple attempts to restart, and no time for indecision. Recognize the failure immediately (dead engine, no throttle response, tachometer unwinding), establish best glide at 65 KIAS, and commit to a landing area within the first 10 seconds. The NTSB precedents show that pilots who delay this decision — trying to restart the engine, attempting to turn back to the runway, or scanning for a 'better' landing area — run out of altitude and strike obstacles.
The 'impossible turn' at 400 ft AGL is a real hazard — commit to landing ahead, not behind.
At 400 ft AGL on initial climb, a 180° turn back to the runway requires altitude and coordination you may not have. The turn consumes altitude rapidly; by the time you roll out, you may be at 200 ft AGL or lower with a high descent rate and an unstable approach. The NTSB CHI83LA094 case shows a pilot attempting to turn back at 150 ft AGL who struck trees near the runway end. The safer decision at 400 ft AGL is to commit to the best available landing area ahead, not the runway behind you. The park in this scenario is the correct choice.
Full flaps in a forced landing minimize touchdown speed — impact energy rises with the square of speed.
In a forced landing, the dominant value of full flaps is the slowest possible touchdown speed. A touchdown at 55 KIAS (with full flaps) has roughly 30% less impact energy than a touchdown at 65 KIAS (clean). The steeper approach path is secondary. In this scenario, full flaps (30°) should be used to minimize touchdown speed in the park landing. The C172N's Vfe (max flap extended) is 85 KIAS, so full flaps can be deployed at approach speeds without risk of structural damage.
Throttle cable failure or disconnection results in total loss of engine power with no recovery option.
The NTSB CEN25LA168 case (2025 C172N) shows a throttle cable disconnected from the carburetor following improper maintenance. The pilot had no throttle response and no way to restart the engine. The failure is not rare: NYC06LA179 (2006) was a throttle shaft failure; CHI83LA094 (1983) was a fractured mixture control cable. During preflight, the throttle should be cycled smoothly through full range and checked for full forward and full aft travel with no binding. If the throttle feels stiff, does not move smoothly, or does not produce the expected RPM change, do not fly the airplane — have a mechanic inspect the throttle cable and linkage.
Post-maintenance flights are high-risk — verify the work before departing.
The NTSB CEN25LA168 case involved improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic. The airplane was released to service with a disconnected throttle cable. In this scenario, the airplane was released from maintenance yesterday with a throttle cable inspection and adjustment that was not independently verified. Post-maintenance flights should be treated as high-risk: conduct an extended preflight, including a full throttle cycle check, and consider a short local flight before any cross-country departure. If anything feels wrong, ground the airplane and have a mechanic re-inspect the work.
Forced landing in congested terrain requires commitment to the best available area — not a street, parking lot, or unsuitable surface.
The NTSB precedents (SEA92LA095, MIA91LA128, CHI92DER01) show pilots attempting to land on streets, alleys, and parking lots in congested areas, resulting in impact with embankments, telephone poles, and other obstacles. In this scenario, the park is the best available option — it is open grass surrounded by trees and power lines, but it is the only suitable landing area. A street in the residential development is too narrow and lined with obstacles. Commit to the best available area, even if it is not ideal, and execute a smooth landing. The alternative — attempting to land on an unsuitable surface — is often fatal.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle shaft failure / forced landing into trees), CEN25LA168 (2025 C172N throttle cable disconnection / engine-out on final), CHI83LA094 (1983 PA-22 engine failure on initial climb / attempted return to runway), and SEA92LA095 (1992 Ryan ST-3KR engine failure / forced landing in congested area). Localized to KPIE Runway 22 departure environment.
NTSB reports: NYC06LA179 · CHI02FA247 · CEN25LA168 · CEN25LA099 · SEA92LA095 · MIA91LA128 · CHI83LA094 · CHI92DER01
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.III.A — Takeoff and Climb
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 172N scenarios · More scenarios at KPIE