Engine Failure on Initial Climb — No Good Options
Total power loss at 400 ft AGL off Runway 16 over dense development. Decision-making under extreme time pressure.
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, initial climb on a 155° heading. Field elevation 71 ft MSL. This is a non-towered field; you will self-announce on CTAF 122.8.
It is a clear, calm morning: OAT 22°C, winds calm, visibility 10 SM. A perfect VFR day. You are climbing out on a local flight, solo, full fuel, within weight and balance limits. The airplane was preflighted by you — a thorough walk-around, controls free and correct, flight control lock removed, engine instruments green.
You are 400 ft AGL, climbing through 65 KIAS (Vbg, best glide speed), heading 155°, when the engine quits. Complete power loss. The propeller windmills. The tachometer falls to zero. No warning, no cough, no sputter — just silence.
Ahead and below: dense residential development. Houses, trees, roads, power lines. Off Runway 16's climb-out end (heading 155°), the USGS NLCD ground cover is mostly dense development, low-density development, and medium development. There is no open field, no park, no water, no road wide enough to land on safely. The terrain is built-up.
Aircraft: Cessna 172R, fuel-injected Lycoming IO-360-L2A, 160 hp, fixed gear, fixed-pitch prop, steam/vacuum panel. Best glide 65 KIAS. You have roughly 3–4 minutes of glide time from 400 ft AGL, depending on how you fly it.
Pilot: you — a Private pilot, current, roughly 250 hours total. You did a thorough preflight. The engine ran smoothly on the ground. Nothing was written up. The airplane was airworthy at departure.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about engine failure on initial climb over congestion? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN14CA023 (2013): A Cessna 172R student pilot touched down too far down the runway during a touch-and-go landing and delayed aborting the takeoff, resulting in collision with trees at the runway end. The accident was attributed to the student pilot's delay in aborting the takeoff — a failure to recognize early that the landing was unstable and to commit to the abort decision.
NTSB ERA12CA325 (2012): A Cessna 172R on a Part 135 flight struck the airport perimeter fence and trees during an aborted takeoff after the pilot discovered the flight control lock was still installed. The accident resulted from the pilot's failure to remove the flight control lock before takeoff and his failure to use the required checklist. This is a preflight failure — the kind that can be prevented by a thorough walk-around and a disciplined checklist.
NTSB ATL04CA170 (2004): A Cessna 172R on an instructional flight experienced a dual control conflict when the student pilot took control during initial climb and refused to release the throttle, preventing the CFI from executing a go-around. The aircraft struck an airport fence. This accident resulted from intentional control interference — a rare but catastrophic failure of crew resource management.
NTSB SEA96LA072 (1996, Piper PA-16): Total loss of engine power shortly after takeoff from Martha Lake Airport. The accident resulted from loss of engine power for undetermined reasons, with a contributing factor being the lack of suitable terrain for a forced landing. The pilot failed to commit to a forced-landing site and attempted to stretch the glide toward unsuitable terrain.
NTSB LAX85FA097 (1985, Cessna 182P): Total engine power loss shortly after takeoff due to water-contaminated fuel. The pilot made a forced landing in a tree to avoid a congested residential area. The pilot survived. The lesson: when forced landing over congestion is unavoidable, actively choose the least-bad option (trees, a field, a road) rather than accepting a crash into houses or vehicles.
NTSB LAX89LA071 (1988, Stinson Globe GC-1B): Total engine power loss during initial climb. The pilot lost control while attempting to maneuver toward a clearing. The accident resulted from the pilot's failure to maintain airspeed during the emergency landing, leading to aerodynamic stall and loss of control. At low altitude, maintaining safe airspeed is non-negotiable.
NTSB LAX87LA118 (1987, Cessna 172RG): Engine surge and total power loss during takeoff climb, forcing a landing on an occupied road where it collided with automobiles. The cause of the engine failure could not be determined despite detailed examination. The lesson: understand that engine failure on initial climb over congestion may leave no safe landing site. Pre-flight planning and early abort decisions are critical.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Clearwater Air Park. KCLW has its own accident history (forced landing, loss of control, gear-up landing, hard landing, fuel starvation are the dominant patterns), but these specific events happened elsewhere. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: engine failure on initial climb over congestion is survivable if the pilot recognizes it early, establishes best glide speed immediately, assesses the terrain, and commits to the least-bad landing option. Delays in decision-making, attempts to stretch the glide, and loss of airspeed during the emergency descent are the killers.
Key lesson — Off Runway 16 at KCLW, the climb-out environment is dense residential development — houses, trees, power lines. There is no open field, no park, no water. An engine failure on initial climb leaves no good options. The correct response is: (1) lower the nose to 65 KIAS (best glide) immediately; (2) assess the terrain and commit to the least-bad landing site (trees, a road, or a remembered open area); (3) maintain safe airspeed throughout the descent; (4) avoid high pitch attitude and stall risk. If you can return to the runway with a shallow turn and safe airspeed, do so. If not, land in the least-bad option ahead. Delays in decision-making and attempts to stretch the glide are fatal.
Debrief — teaching points
Best glide speed is 65 KIAS in the C172R — establish it immediately on engine failure.
When the engine quits, the first action is to lower the nose and establish 65 KIAS (best glide). This speed maximizes glide distance and time — roughly 1.5–2 nm from 400 ft AGL depending on wind and weight. At 65 KIAS, you have the best chance of reaching a suitable landing site. Any other speed — higher or lower — reduces glide distance. Establishing best glide is not optional; it is the foundation of every engine-failure response.
Off Runway 16 at KCLW, the climb-out environment is dense development — no open field, no park, no water.
The USGS NLCD ground cover off Runway 16's climb-out end (heading 155°) is mostly dense development, low-density development, and medium development. Houses, trees, power lines, roads. There is no open field to land on. An engine failure on initial climb off Runway 16 forces a landing in congestion. Understand this before you line up on the runway. If you are uncomfortable with the risk, use Runway 34 instead (climb-out heading 335°, which has low-density development and open developed areas — parks/large lots — as off-field options).
When forced landing over congestion is unavoidable, actively choose the least-bad option.
Trees, a residential street, a remembered open area — these are your options off Runway 16. A tree landing is survivable if you maintain airspeed and accept the impact. A road landing is risky but possible if the road is wide enough and clear of power lines. A remembered open area (school field, park) is the best option if you can reach it. The NTSB LAX85FA097 pilot chose trees and survived. The NTSB LAX87LA118 pilot collided with automobiles on a road. The difference is decision-making: commit to the least-bad option and fly the airplane to that site.
Maintain safe airspeed throughout the emergency descent — avoid high pitch attitude and stall risk.
At low altitude over congestion, the temptation is to pitch up and stretch the glide toward an open area. This is a trap. Pitching up reduces airspeed, increases the descent rate, and risks a stall. The NTSB LAX89LA071 pilot lost control while attempting to maneuver toward a clearing — the stall was the killer. Maintain 65 KIAS (best glide) or slightly faster if you are maneuvering. A stall at 200 ft AGL is not recoverable.
A shallow turn back to the runway is possible if the engine fails early and you have altitude.
If the engine fails at 400 ft AGL and you are within 0.5 nm of the runway, a shallow bank (15–20°) and 65 KIAS allows you to turn back and land on the runway. Keep the bank angle shallow to avoid stall risk. A steep bank (30°+) at low altitude over a descending turn is marginal on airspeed and risks a stall. If you are farther from the runway or lower on altitude, commit to a landing site ahead instead of attempting the turn back.
Declare a Mayday on CTAF 122.8 — other aircraft in the area need to know.
KCLW is non-towered. Self-announce on CTAF 122.8. If you experience engine failure on initial climb, declare a Mayday: 'Clearwater CTAF, Cessna [N-number], engine failure, initial climb, declaring emergency.' Other aircraft will hear you and avoid the area. You have done what you can on the radio; now focus on flying the airplane.
Built from the real accident record
Scenario inspired by NTSB CEN14CA152, CEN14CA023, ERA12CA325, ATL04CA170 (C172R control/checklist failures on takeoff), and regional precedents SEA96LA072, LAX85FA097, LAX89LA071, LAX87LA118 (engine failure over congestion with no suitable forced-landing site). Real events occurred at other airports — NOT at KCLW.
NTSB reports: CEN14CA152 · CEN14CA023 · ERA12CA325 · ATL04CA170 · SEA96LA072 · LAX85FA097 · LAX89LA071 · LAX87LA118
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.II.C — 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 172R scenarios · More scenarios at KCLW