Total Power Loss on Departure — The Impossible Turn
Engine failure at 400 ft AGL, the instinct to return to the runway, and why that instinct kills pilots
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 04, climbing out on a 040° heading. Field elevation 11 ft MSL. This is a towered airport (ATCT part-time, currently open 0600–2300 local). You are in Class D airspace; above 1,600 ft MSL you will enter the overlying Tampa Class B.
It is a clear, calm Florida morning: OAT 18°C, light winds from 080° at 3 kt, altimeter 30.01. Visibility 10 SM. A textbook VFR day. You have filed a VFR flight plan to a nearby airport 45 nm away. The airplane is a Cessna 172R, solo, full fuel (48 gal usable), within weight and balance limits. The preflight was thorough; nothing was written up. The engine ran smoothly during the run-up.
You are cleared for takeoff on Runway 04. You roll down the 6,000-ft runway, rotate at 51 KIAS, and climb out at 79 KIAS (Vy, best rate of climb). At 400 ft AGL, heading 040°, the engine suddenly goes silent. No sputtering, no roughness — complete, total power loss. The propeller is windmilling. You have roughly 30 seconds of useful decision time before altitude becomes critical.
Off Runway 04's climb-out end (heading 040°), the off-field environment is mostly open water — Tampa Bay and the surrounding waterways — with some open developed areas (parks, large parking lots). A forced landing off the departure end of Runway 04 is a ditching, not a field landing. There is no alternate landing surface ahead.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have trained for engine failures, but always in the pattern or at altitude. You have never experienced a total power loss at 400 ft AGL on a departure. Your instinct right now is to turn back to the runway. That instinct is about to be tested.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about engine failure on departure in a light airplane? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ANC18LA013 (2017, Cessna 172R): A Cessna 172 on a personal flight from Carroll County Airport experienced total engine power loss shortly after takeoff during initial climb. The accident resulted from a total loss of engine power for reasons that could not be determined despite postaccident examination and testing. The probable cause was undetermined — the engine showed no preimpact mechanical malfunctions or failures that would have precluded normal operation. This is the nightmare scenario: a perfectly good engine that simply stops, for reasons that cannot be found.
NTSB WPR18LA039 (2017, Cessna 172R): A Cessna 172R experienced total engine power loss due to crankshaft fatigue fracture during climb. The instructor performed a forced landing to a field past the runway. The accident was attributed to fatigue separation of the crankshaft due to a fatigue fracture, which resulted in total loss of engine power and a subsequent off-airport landing and impact with a fence. The instructor's decision to land straight ahead, not attempt a turn back to the runway, likely saved both lives.
NTSB ERA14LA142 (2014, Cessna 172R): A Cessna 172R experienced rapid oil pressure loss during climb, returned to the departure airport, and lost all engine power during an ILS approach, resulting in a forced landing on a highway. The accident was attributed to total loss of engine power due to maintenance personnel's improper installation of the lower vacuum pump. This is a maintenance trap — a post-maintenance flight that goes wrong.
NTSB ERA12LA294 (2012, Cessna 172R): A Cessna 172R operated by Eastern Kentucky University lost engine power due to fuel exhaustion during climb and made a forced landing in a field, striking a tree during rollout. The accident resulted from fuel exhaustion attributed to inadequate fuel management, failure to supervise the student's preflight inspection, and inadequate operator fueling policies. The student did not verify fuel quantity during preflight; the instructor did not supervise.
Regional precedent — NTSB WPR17FA152 (2017, FATAL, Jansen Pazmany PL-2): An experimental Jansen Pazmany PL-2 lost engine power shortly after takeoff from El Monte, California. The pilot attempted to return to the runway but stalled and spun at approximately 200 feet AGL, impacting terrain in a near-vertical attitude. The accident resulted from fuel starvation of undetermined cause and the pilot's decision to return to the runway at low altitude, which led to an aerodynamic stall and spin. This is the 'impossible turn' in action — the pilot's instinct to return to the runway cost him his life.
Regional precedent — NTSB LAX93LA048 (1992, FATAL, Rans S-10 Sakota): A Rans S-10 Sakota on a personal flight experienced engine power loss shortly after takeoff and stalled/spun while maneuvering to land at 150–200 feet. The accident resulted from loss of engine power and pilot failure to maintain airspeed above stall speed, with insufficient altitude for recovery as a contributing factor. The pilot tried to make a turn back to the airport; the airplane stalled and spun.
Regional precedent — NTSB ERA14FA123 (2014, FATAL, Williams Christopher T Sonex): A Sonex experimental aircraft experienced partial engine power loss due to an improperly seated spark plug during initial climb, and the pilot made a steep 180-degree turn back toward the airport at low altitude, resulting in a stall and spiral descent into a canal. The accident resulted from the pilot's failure to maintain adequate airspeed during the emergency return, compounded by improper engine repair prior to flight. Even with high experience, the instinct to return to the airport after engine failure must be overridden.
Regional precedent — NTSB SEA90LA162 (1990, FATAL, Vaden James L JV SA 102 Cavalier): A Vaden SA102 Cavalier experimental homebuilt experienced engine power loss during initial climb and entered a spin when the pilot failed to maintain airspeed during the left turn. The accident resulted from the pilot's failure to maintain airspeed following engine power loss; the reason for the power loss was not determined. Maintain wings level and straight flight after engine failure; avoid turning at low altitude.
The consistent thread across all these events: after engine failure at low altitude, the pilot's instinct is to turn back to the runway. That instinct is almost always fatal. The 'impossible turn' — a steep turn back to the runway at 400 ft AGL — costs altitude and airspeed simultaneously. At 400 ft AGL in a C172R, a 180° turn requires roughly 200–300 ft of altitude. You do not have it. The turn steepens, the airspeed decays, the stall warning sounds, and the airplane spins. Spin recovery at 200 ft AGL is impossible.
The correct response to total engine failure at 400 ft AGL is: (1) Lower the nose to 65 KIAS best glide immediately. (2) Keep wings level. (3) Scan for the best landing option ahead — a park, a parking lot, a field, or smooth water. (4) Accept the forward landing. The runway is behind you; it is unreachable. Land straight ahead. This is not failure — it is airmanship. The pilots who survived (WPR18LA039, the instructor who landed in the field) are the ones who accepted the forward landing and did not attempt the impossible turn.
At KPIE, Runway 04's departure end (heading 040°) is open water — Tampa Bay and surrounding waterways. An engine failure on the Runway 04 departure at 400 ft AGL is a ditching, not a field landing. There is no alternate landing surface ahead. A controlled ditching — wings level, 65 KIAS, doors unlatched, master off before impact, flaps for slowest touchdown speed — is survivable. A stall/spin is not.
Key lesson — The 'impossible turn' — attempting to return to the runway after engine failure at low altitude — is a stall/spin trap. At 400 ft AGL in a C172R, a 180° turn costs 200–300 ft of altitude and causes airspeed decay that leads to a stall. Spin recovery at 200 ft AGL is impossible. The correct response is to lower the nose to 65 KIAS best glide, keep wings level, and accept a forward landing. Off Runway 04 at KPIE, that means a controlled ditching in Tampa Bay — survivable if executed properly. The runway is behind you; it is unreachable. Land straight ahead.
Debrief — teaching points
The 'impossible turn' is a stall/spin trap at low altitude.
After engine failure at 400 ft AGL, the instinct to turn back to the runway is powerful — and almost always fatal. A 180° turn in a C172R at 400 ft AGL costs roughly 200–300 ft of altitude. To maintain altitude in a turn, you must increase back-pressure, which slows the airplane. At 400 ft AGL, you do not have the altitude to both turn and maintain airspeed. The turn steepens, the airspeed decays below 60 KIAS, the stall warning sounds, and the airplane spins. Spin recovery at 200 ft AGL is impossible. The NTSB accident precedents (WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162) all show the same fatal pattern. Do not attempt the impossible turn.
Best glide speed (65 KIAS) is the entire solution after engine failure.
Immediately after engine failure, lower the nose to establish 65 KIAS best glide. This speed maximizes glide distance and gives you the most time and distance to find a landing spot. At 65 KIAS in a C172R, you have roughly 2 minutes of glide time from 400 ft AGL. Use that time to scan for the best landing option ahead — a park, a parking lot, a field, or smooth water. Do not waste altitude trying to turn back to the runway. Maintain 65 KIAS and fly straight ahead.
Wings level is the second priority — it preserves altitude and control.
After establishing best glide speed, keep the wings level. A bank angle costs altitude; a steep bank costs altitude rapidly. At 400 ft AGL with no power, every foot of altitude is precious. A shallow bank at 65 KIAS will descend at roughly 500 ft/min; a steep bank will descend much faster and may lead to a stall. Keep the wings level and fly straight ahead.
Accept the forward landing — the runway is behind you and unreachable.
After engine failure at 400 ft AGL, the runway is behind you and descending. It is unreachable. Accept this fact immediately. Scan ahead for the best landing option — a park, a parking lot, a field, or smooth water — and commit to landing there. Do not second-guess yourself at the last moment and attempt a turn back to the runway. That hesitation will cost you the altitude and airspeed you need for a safe forward landing. Land straight ahead.
A controlled ditching in water is survivable; a stall/spin is not.
Off Runway 04 at KPIE, the departure end is open water — Tampa Bay. If engine failure occurs on the Runway 04 departure at 400 ft AGL, a controlled ditching is the correct outcome. Maintain 65 KIAS, aim for smooth water, and execute the ditching checklist: fuel selector BOTH, mixture rich, master off just before impact, doors unlatched before water contact, flaps for slowest possible touchdown speed. Impact energy rises with the square of touchdown speed, so the slowest possible speed matters most. A controlled ditching is survivable; a stall/spin is not.
Engine failure can happen to any engine, at any time, for reasons that may never be found.
NTSB ANC18LA013 shows a Cessna 172R that experienced total engine power loss for reasons that could not be determined despite postaccident examination and testing. The engine showed no preimpact mechanical malfunctions or failures. This is the nightmare scenario: a perfectly good engine that simply stops. You cannot prevent it. You can only respond correctly when it happens. The correct response is: best glide speed, wings level, forward landing. Do not attempt the impossible turn.
Built from the real accident record
Scenario built from NTSB ANC18LA013 (2017 C172R total power loss, undetermined cause), WPR18LA039 (2017 C172R crankshaft fatigue fracture), ERA14LA142 (2014 C172R vacuum pump failure), and ERA12LA294 (2012 C172R fuel exhaustion). Regional precedents: WPR17FA152 (2017 Jansen Pazmany, impossible turn stall/spin), LAX93LA048 (1992 Rans S-10, low-altitude stall/spin), ERA14FA123 (2014 Sonex, steep turn stall/spin), SEA90LA162 (1990 Vaden SA102, spin after engine failure). Real accidents occurred at other airports — NOT at KPIE.
NTSB reports: ANC18LA013 · WPR18LA039 · ERA14LA142 · ERA12LA294 · WPR17FA152 · LAX93LA048 · ERA14FA123 · SEA90LA162
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 172R scenarios · More scenarios at KPIE