FlightEdge
Sample scenario-based training
SAMPLE SBTTakeoff / Initial Climb

Total Power Loss on the Runway 04 Departure

Engine failure at 400 ft AGL, the temptation to turn back, and why the 'impossible turn' is unrecoverable

Cessna 172R · Venice Municipal Airport (KVNC) · Private · Takeoff / Initial Climb

The scenario

Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 04, climbing out on a 045° heading. Elevation 18 ft MSL. Clear skies, light winds from the north, visibility 10+ SM. A perfect Florida morning for a local flight.

You are a Private pilot with 180 hours total time, current and proficient. The Cessna 172R is within limits, full fuel (48 gallons usable), and the preflight was thorough. Engine start was normal. You taxied to Runway 04, performed a normal run-up (all systems green, engine temps and pressures nominal), and lined up for departure.

You advance the throttle to full power. The engine responds normally. Airspeed builds: 20 knots, 30, 40, 50 (Vr). You rotate at 51 KIAS and the airplane lifts off cleanly. You are climbing at 79 KIAS (Vy, best rate of climb) on a heading of 045°.

At 400 ft AGL — roughly 10 seconds after liftoff — the engine suddenly loses all power. The propeller is still turning (windmilling), but there is no thrust. The airplane is in a climb attitude with no power. The runway is behind you. Ahead and to the left (north and west) is open terrain — scrub, grassland, and scattered trees. To the right (east) is more of the same. Behind you is the runway.

Aircraft: Cessna 172R, solo, full fuel, within limits. Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, steam panel, fuel selector on BOTH. The engine was running perfectly at departure. Nothing was written up.

Pilot: you — a Private pilot, current, roughly 180 hours total. You have never experienced a total engine failure. You have trained for it in the simulator, but not in the real airplane at 400 ft AGL.

The decision

Before we get into the decision tree — what do you already know about engine failure immediately after takeoff in a single-engine airplane? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB ANC18LA013 (2017): A Cessna 172R 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 pilot's response to the engine failure is not detailed in the public docket, but the outcome was a forced landing.

NTSB WPR18LA039 (2017): 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, avoiding the 'impossible turn' trap. The airplane impacted a fence during rollout, but the crew survived. The lesson: commit to a forward landing and accept the terrain ahead.

NTSB ERA14LA142 (2014): 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 pilot's decision to return to the airport was made at a higher altitude (during climb, not immediately after takeoff), where a return was feasible. At 400 ft AGL, a return is not feasible.

NTSB WPR17FA152 (2017, FATAL): A 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 ft 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.

NTSB LAX93LA048 (1992, FATAL): 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 ft. 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.

NTSB ERA14FA123 (2014, FATAL): 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.

NTSB SEA90LA162 (1990, FATAL): 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 consistent thread across all these accidents: total engine failure at low altitude (200–400 ft AGL) followed by an attempted turn back to the runway results in a stall/spin that is unrecoverable. The 'impossible turn' is not a myth — it is a documented, repeating pattern in the NTSB accident database. The correct response is to commit to a forward landing in the terrain ahead, establish 65 KIAS best glide, and accept the landing spot available. A hard landing in open terrain is survivable; a stall/spin at 200 ft AGL is not.

At KVNC, the off-field environment off Runway 04's departure end (heading 045°) is open scrub and grassland with scattered trees — suitable for a forced landing. The runway is behind you; the terrain ahead is your landing spot. Commit to it.

Key lesson — Total engine failure at 400 ft AGL on the Runway 04 departure at KVNC is unrecoverable for a return to the runway. The 'impossible turn' — attempting a 180° turn back to the runway at low altitude — results in a stall/spin that is fatal. The correct response is immediate: lower the nose to 65 KIAS best glide, level the wings, and commit to a forward landing in the open terrain ahead. A controlled forward landing is survivable; a stall/spin at low altitude is not.

Debrief — teaching points

The 'impossible turn' is real and documented.

Attempting to return to the runway after engine failure at 400 ft AGL is statistically unrecoverable. The turn requires altitude and airspeed you do not have. As you bank, the airplane's descent rate increases (a banked airplane descends faster than a wings-level airplane). The turn takes longer than you expect and costs more altitude than you have. By the time the runway is in sight, you are at 200 ft AGL in a steep descent with no power and no recovery options. The NTSB precedents (WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162) all show the same outcome: attempted turn back, stall/spin, fatal impact. The rule is absolute: below 1,000 ft AGL with total engine failure, do not attempt to return to the runway.

Establish best glide immediately — 65 KIAS for the C172R.

The moment you recognize total engine failure, lower the nose to establish 65 KIAS best glide. This is the speed that maximizes glide distance and gives you the most time and distance to manage the emergency. At 65 KIAS, the C172R will glide approximately 1,500 ft for every 1,000 ft of altitude lost. At 400 ft AGL, you have roughly 30–45 seconds of glide time. Use that time to pick a landing spot and set up a controlled approach, not to troubleshoot the engine or attempt a turn back.

Accept the forward landing — the terrain ahead is your landing spot.

At KVNC, the off-field environment off Runway 04's departure end is open scrub and grassland with scattered trees. This is suitable for a forced landing. Commit to a clear area ahead, establish 65 KIAS best glide, and execute a controlled approach. A hard landing in open terrain is survivable; a stall/spin at 200 ft AGL is not. Do not try to stretch the glide to reach a 'better' field farther away — commit to the terrain you can reach.

A forward slip is a valid emergency maneuver — but only if you have altitude and control.

A forward slip can increase descent rate and help you reach a landing spot you might otherwise overshoot. But a slip requires precise control and altitude awareness. At 400 ft AGL with total engine failure, a slip adds complexity. Establish best glide first, pick a landing spot, and use a slip only if you need to lose altitude more quickly. Do not use a slip to try to reach the runway — the altitude cost is too high.

Engine failure at low altitude is an immediate emergency — not a troubleshooting problem.

When the engine fails at 400 ft AGL, you do not have time to troubleshoot. Cycling the mixture, checking the fuel selector, or trying to restart the engine will cost you critical altitude and time. The correct response is immediate: lower the nose to 65 KIAS best glide, level the wings, and commit to a landing. If the engine restarts during the glide, that is a bonus — but do not count on it. Treat total engine failure as total engine failure.

The C172R is fuel-injected — no carburetor heat, but mixture control and boost pump are available.

The C172R's Lycoming IO-360-L2A is fuel-injected, so there is no carburetor heat. If the engine is running rough before failure, the response is to check the mixture (lean or rich as appropriate), cycle the boost pump, and verify the fuel selector is on BOTH. But at 400 ft AGL on departure, the engine should be running normally — if it is not, that is a sign to return to the airport before climbing further. Once total power loss occurs, troubleshooting is secondary to establishing best glide and committing to a landing.

Built from the real accident record

Scenario built from NTSB ANC18LA013, WPR18LA039, ERA14LA142, ERA12LA294 (C172R total engine power loss events) and regional precedents WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162 (low-altitude engine-failure stall/spin accidents). Real events occurred at other airports — NOT at KVNC.

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.A — 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 172R scenarios · More scenarios at KVNC