FlightEdge
Sample scenario-based training
SAMPLE SBTTakeoff / Initial Climb

The Impossible Turn

Engine failure at 400 feet AGL, the temptation to turn back, and why airspeed discipline saves lives

Cessna 172M · 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 into a clear, hot Florida morning. Elevation 18 ft MSL; the runway is essentially at sea level. Field elevation is 18 feet.

It is late July, 0900 local. OAT 32°C, dew point 24°C, altimeter 29.92. Scattered clouds at 3,500 ft, visibility 10 SM. High density altitude — roughly 2,800 ft density altitude — means the C172M will climb like a loaded truck. The 150-hp Lycoming O-320 is marginal in these conditions, especially at gross weight.

You are a Private pilot, roughly 180 hours total, on a local flight. You did a normal preflight: checked the fuel tanks visually (they looked clear), ran the engine on the ground (it ran smoothly), and cycled the carburetor heat (normal RPM drop and recovery). Nothing was written up. The airplane was released as airworthy.

You line up on Runway 04, advance the throttle to full power, and rotate at 55 KIAS. The airplane lifts off. You are climbing at 78 KIAS (Vy, best rate of climb) through 200 ft AGL. The engine is running smoothly. The runway is behind you. Ahead and to the left (north), the off-field environment is open water — a bay or estuary. To the right (south and east), dense residential development and roads.

At 400 ft AGL, the engine suddenly loses power. The tachometer drops to idle. The propeller is still turning (it is fixed-pitch), but there is no thrust. You have roughly 30 seconds of useful decision time before altitude becomes critical. The airport is behind you. Water is ahead. You have a choice to make.

The decision

Before we get into the decision tree — what do you already know about engine failure at low altitude? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB ATL03FA142 (2003, FATAL): A Cessna 172M on an instructional flight from Perry, Georgia experienced engine power loss shortly after takeoff due to water-contaminated fuel. The CFI's inadequate preflight inspection failed to detect the contamination. The pilot attempted to return to the runway at low altitude, stalled, and impacted terrain. The probable cause was the CFI's failure to detect water-contaminated fuel and the pilot's failure to maintain adequate airspeed during the emergency return.

NTSB CEN25LA355 (2025): A Cessna 172M lost engine power during a second touch-and-go landing after a 200-nautical-mile cross-country flight. The pilot had not switched fuel tanks despite adequate fuel remaining on board. The probable cause was fuel starvation due to mismanagement of available fuel.

NTSB CEN24LA168 (2024): A Cessna 172M on an IFR flight experienced engine power loss due to carburetor icing during descent in night IMC. The pilot touched down on a building roof and impacted a retaining wall. The probable cause was delayed use of carburetor heat, which resulted in ice accumulation beyond the point where heat could restore full engine power.

NTSB ERA23LA141 (2023): A Cessna 172M on an instructional flight experienced total loss of engine power due to inadequate oil lubrication. The engine was 55 hours past its required 100-hour inspection. The probable cause was a total loss of engine power due to lack of oil lubrication.

Regional precedents (WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162) all show the same fatal pattern: engine failure at low altitude, followed by an attempted steep turn back to the runway, followed by a stall/spin at insufficient altitude for recovery. The real events occurred at other airports and in other aircraft types, but the mechanism is universal. The lesson is unambiguous: commit to a forward landing immediately upon recognizing engine failure at low altitude. Do not attempt a steep turn back.

At KVNC, the off-field environment off Runway 04's departure end (heading 045°) is open water — a bay or estuary to the north. An engine failure on the Runway 04 departure at low altitude is a ditching, not a field landing. This is not hypothetical; it is the USGS NLCD ground cover off that runway end. The scenario is localized to KVNC to make the off-field environment real and consequential for you as a student here.

The consistent thread across all these events: engine failure at low altitude is survivable if you commit to a forward landing and maintain airspeed. It is fatal if you attempt a steep turn back to the runway. The C172M's 150-hp Lycoming O-320 is marginal in climb; it is even more marginal in a turn at low altitude with no power. The stall speed increases in a bank. The altitude required for recovery is altitude you do not have. Accept the forward landing. Survive.

Key lesson — Engine failure at low altitude (below 1,000 ft AGL) is survivable only if you commit to a forward landing immediately and maintain airspeed at 65 KIAS (best glide). Do not attempt a steep turn back to the runway — the stall speed increases in a bank, and you do not have enough altitude for recovery. The NTSB data is clear: pilots who attempt the turn back at low altitude with engine failure often stall and spin. Pilots who accept a forward landing and maintain airspeed survive. Off Runway 04 at KVNC, the forward environment is open water — a controlled ditching at 65 KIAS is survivable. A stall/spin at 300 ft AGL is not.

Debrief — teaching points

Engine failure at low altitude is survivable only if you commit to a forward landing immediately.

The moment you recognize total engine failure at low altitude (below 1,000 ft AGL), your decision is made: you are landing forward, not turning back. Lower the nose to 65 KIAS (best glide), trim for hands-off flight, and commit to the landing ahead. Do not spend mental energy on whether you can make the runway — you cannot, not reliably. The NTSB data shows that pilots who attempt the turn back at low altitude with engine failure often stall and spin. Pilots who accept the forward landing and maintain airspeed survive.

The stall speed increases in a bank — a steep turn at low altitude with no power is a stall trap.

In a 25° bank, the stall speed in the C172M rises from 53 KIAS (clean) to roughly 58 KIAS. In a 30° bank, it rises to roughly 60 KIAS. At 400 ft AGL with no power, you are descending at roughly 500 fpm. A steep turn eats altitude rapidly. The combination — steep bank, rising stall speed, rapid altitude loss — is a stall trap. The airplane stalls without warning. The wing drops. You are in a spin at 300 ft AGL. Spin recovery requires roughly 500 ft of altitude in a C172M. You do not have it. The real accidents (ATL03FA142, WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162) all show this pattern.

Best glide speed is 65 KIAS — maintain it, even in a turn.

Best glide speed in the C172M is 65 KIAS. This speed maximizes glide distance and gives you the most time and distance to manage the emergency. If you must turn (to avoid obstacles or to reach a better landing area), maintain 65 KIAS even in the turn — keep the bank angle shallow (15° or less) and accept that the turn will be slow. Do not try to force a steep turn to get back to the runway faster. The shallow turn at 65 KIAS is the safest option.

Fly the airplane first; troubleshoot the engine later.

At 400 ft AGL with no power, your priority is flying the airplane, not troubleshooting the engine. Lower the nose to 65 KIAS, trim for hands-off flight, and commit to a landing. Do not go heads-down trying to restart the engine, cycle the fuel selector, or check the magnetos. At low altitude, that distraction is fatal. The engine is not going to restart in the next 30 seconds. Fly the airplane. Troubleshoot after you land.

At KVNC Runway 04, the forward environment is open water — a controlled ditching is survivable.

The off-field environment off Runway 04's departure end (heading 045°) is open water — a bay or estuary to the north. An engine failure on the Runway 04 departure at low altitude is a ditching, not a field landing. A controlled ditching at 65 KIAS with full flaps (40°) for slowest possible touchdown speed is survivable. Impact energy rises with the square of touchdown speed — the slowest possible speed is critical. Fuel selector BOTH, mixture rich, master off just before impact, doors unlatched. Survive the ditching by maintaining airspeed and a controlled descent.

Preflight inspection and fuel management prevent engine failure.

The real accidents cited (ATL03FA142, CEN25LA355, CEN24LA168, ERA23LA141) all had preventable causes: water-contaminated fuel (inadequate preflight), fuel starvation (failure to switch tanks), delayed carburetor heat (inadequate response to symptoms), and oil starvation (inadequate maintenance). A thorough preflight — including fuel sump checks for water, fuel selector verification, and engine run-up — catches most of these. Fuel management during flight (switching tanks on long flights, monitoring engine instruments) prevents starvation. Carburetor heat applied proactively in conducive conditions prevents icing. These are not optional steps; they are the difference between a routine flight and a fatal accident.

Built from the real accident record

Scenario built from NTSB ATL03FA142 (2003 C172M water-contaminated fuel, stall/spin after engine failure), CEN25LA355 (2025 C172M fuel starvation on touch-and-go), CEN24LA168 (2024 C172M carburetor icing, delayed carb heat), ERA23LA141 (2023 C172M oil starvation), and regional precedents WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162 (all stall/spin after engine failure at low altitude during attempted turnback). Anonymized and localized to KVNC.

NTSB reports: ATL03FA142 · CEN25LA355 · CEN24LA168 · ERA23LA141 · 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

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 172M scenarios · More scenarios at KVNC