Engine Failure on Initial Climb — Runway 04
Total power loss at 300 ft AGL over medium development. No good forced-landing site. Decision window is seconds.
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Runway 04, on a VFR local flight. Elevation 30 ft MSL. It is a clear, calm morning — winds 080° at 3 kt, visibility 10+ SM, OAT 22°C. The tower is active (0600–0000 local). You are cleared for takeoff on Runway 04 (true heading 038°).
Runway 04 is 5,006 ft long — plenty of runway for a C172R. The climb-out environment off the Runway 04 end (heading 038°, northeast) is marginal: medium development, wooded wetland, low-density development. Not ideal, but not a water ditch. If the engine fails after liftoff and you have altitude, you have options.
Aircraft: Cessna 172R, solo, full fuel (53 gal usable), within CG and weight limits. The Lycoming IO-360-L2A is fuel-injected, 160 hp. You completed a thorough preflight: fuel quantity verified, fuel selector on BOTH, mixture set for field elevation (30 ft — essentially full rich), boost pump OFF (not needed at this altitude). Engine run-up was normal — all systems green, engine instruments in the green, no anomalies.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 15 hours in the C172R. This is your first departure from KSRQ; you are not familiar with the field. You have not flown from a towered airport in two weeks.
You line up on Runway 04, advance the throttle to full power, and begin the takeoff roll. The engine is running smoothly. Airspeed is building: 20 kt, 30 kt, 40 kt. At 51 KIAS (Vr — rotation speed), you gently back the yoke and the nose comes up. The airplane lifts off cleanly at 57 KIAS (short-field liftoff). You are airborne.
You are now at 100 ft AGL, climbing at 79 KIAS (Vy — best rate of climb), heading 038° as cleared. The engine is running smoothly. The tower has instructed you to climb to 2,000 ft and maintain that altitude until further notice. You are in Class C airspace (ceiling 4,000 MSL). Everything is normal.
At 300 ft AGL, the engine suddenly loses all power. The tachometer drops to zero. The propeller is still turning (windmilling), but there is no engine thrust. You have 300 ft of altitude, a dead engine, and medium development directly ahead. The decision window is measured in seconds.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before the decision tree — what do you know about engine failure on initial climb in a C172R? (Pick all that apply.)
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 probable cause was the student pilot's delay in aborting the takeoff. The lesson: early recognition of a problem (in this case, a long landing) and immediate commitment to a go-around or abort is critical. Delaying the decision costs altitude and runway.
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 probable cause was the pilot's failure to remove the flight control lock before takeoff and his failure to use the required checklist. The lesson: thorough preflight inspection and systematic use of checklists prevent preventable failures.
NTSB MIA91LA128 (1991, fatal): 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. The probable cause was the pilot's improper adjustment of the carburetor mixture control. The lesson: recognize engine performance degradation during takeoff and commit to a forced landing decision early.
NTSB NYC89DHM07 (1989): A Woods Formula Vee homebuilt experienced total engine failure at approximately 100 feet during initial climb and made a forced landing on an airport access road. The probable cause could not be determined. The lesson: recognize engine roughness early and commit to landing straight ahead rather than attempting a turn back to runway when altitude is marginal.
NTSB CHI04CA108 (2004): A Piper PA-18-150 lost engine power at 150 feet AGL during initial climb when the fuel selector was found in the OFF position. The pilot made a forced landing between houses, striking a power pole and trees, with the aircraft coming to rest inverted. The probable cause was the failure to verify fuel selector position before takeoff. The lesson: systematic pre-takeoff checks and commitment to the best available landing site are critical.
The off-field environment off Runway 04 at KSRQ is medium development, wooded wetland, and low-density development — not open water, not a clear field, but not a dense urban area. A forced landing in this environment is survivable if you commit to the best available site (a road, a clearing, open ground) and execute a stable approach. The turn back to the runway at 300 ft AGL is marginal and risky; the straight-ahead forced landing is the safer, more predictable outcome.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KSRQ. KSRQ has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 19.2%, FORCED_LANDING 15.4%, RUNWAY_EXCURSION 11.5%, HARD_LANDING 11.5%, LOSS_OF_CONTROL_INFLIGHT 11.5%), but these specific events happened elsewhere. The scenario is localized to KSRQ to make the off-field environment real and consequential for you as a student here.
Key lesson — Engine failure at 300 ft AGL over congested terrain is survivable if you commit immediately to the best available forced-landing site straight ahead, establish best glide (65 KIAS), and execute a stable approach. The turn back to the runway is marginal at this altitude and risky — it may not work. The straight-ahead forced landing is the safer, more predictable outcome. Recognize the problem early, commit to the best available site, and fly the airplane to the landing. Do not attempt to stretch the glide or maneuver to a marginal runway.
Debrief — teaching points
Engine failure at 300 ft AGL over congested terrain is survivable — but only if you commit immediately to the best available forced-landing site straight ahead.
The off-field environment off Runway 04 at KSRQ is medium development, wooded wetland, and low-density development. There is no open field, no clear road, no park — but there are roads, clearings, and open ground scattered through the development. At 300 ft AGL with a dead engine, you have roughly 30 seconds of glide time. Scanning for the best available site (a road, a clearing, open ground) and committing to it immediately is the difference between a survivable forced landing and a collision with trees or obstacles. Do not attempt to stretch the glide or maneuver to a marginal runway — commit to the best site straight ahead.
Best glide speed is 65 KIAS in the C172R — establish it immediately and maintain it.
Best glide maximizes glide distance and gives you the most time to find a landing site and execute the approach. At 65 KIAS, the C172R descends at roughly 500 fpm — 300 ft ÷ 500 fpm = 36 seconds of glide time. Every second counts. Establish 65 KIAS immediately when power is lost and maintain it throughout the descent. Do not climb or descend from best glide — it is the speed that gives you the most distance and time.
Flaps reduce touchdown speed — impact energy rises with the square of speed, so the slowest possible touchdown speed matters most.
Full flaps (30°) in the C172R slow the airplane to roughly 55 KIAS — a significant reduction from best glide. The touchdown speed is the slowest possible, which minimizes impact energy. At 300 ft AGL over medium development, full flaps are the correct choice — you are committed to landing in a confined space (a road, a clearing), and the slowest possible touchdown speed is critical. The descent rate increases slightly with full flaps, but the speed reduction is worth it.
The turn back to the runway at 300 ft AGL is marginal and risky — it may not work.
A 180° turn back to the runway at 300 ft AGL with a dead engine requires altitude and airspeed you are marginal on. The turn costs 150–200 ft of altitude; you will be at 100–150 ft AGL when you roll out. The runway is 0.5 nm away. You have 12–15 seconds of glide time. The approach is very steep and very tight. Even if you make the runway, the margin is thin. The straight-ahead forced landing is the safer, more predictable outcome — commit to the best available site in front of you, not a marginal turn back to the runway.
Recognize engine failure early and commit to the forced landing decision immediately — do not delay.
At 300 ft AGL, every second counts. The moment you recognize total power loss, establish best glide (65 KIAS), scan for the best landing site, and commit to it. Do not spend time troubleshooting (boost pump, mixture, fuel selector) — the engine is not restarting in flight. Do not attempt a turn back to the runway unless you are certain you have the altitude to make it. Commit to the best available site straight ahead and execute a stable approach. The NTSB accident data shows that delays in the forced landing decision — attempting to stretch the glide, attempting a marginal turn back, attempting to restart the engine — are the mechanism of fatal accidents.
The C172R fuel selector is BOTH — fuel starvation from a selector-position error is not a C172R failure mode.
Unlike Pipers (which use L/R/OFF), the C172R fuel selector is BOTH. Fuel starvation from a selector-position error is not a C172R failure mode. However, fuel contamination, fuel pump failure, or fuel line blockage can cause total power loss. The preflight inspection — checking fuel quantity, fuel color, fuel selector position, and fuel system integrity — is critical. If the engine quits and the fuel selector is already on BOTH, do not spend time cycling it; commit to the forced landing.
Built from the real accident record
Scenario inspired by NTSB CEN14CA152, CEN14CA023, ERA12CA325, ATL04CA170 (C172R control and takeoff accidents), and regional precedents MIA91LA128, ERA13FA325, NYC89DHM07, CHI04CA108 (engine-out forced landings over congested terrain). Localized to KSRQ.
NTSB reports: CEN14CA152 · CEN14CA023 · ERA12CA325 · ATL04CA170 · MIA91LA128 · ERA13FA325 · NYC89DHM07 · CHI04CA108
ACS tasks: PA.I.F — Weather Information · PA.II.A — Preflight Inspection · PA.II.B — Engine Starting / Systems Preflight · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
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 KSRQ