Engine Failure on Initial Climb — Runway 05 Departure
Total power loss at 400 ft AGL over congested development with no suitable forced-landing site. Decision window: seconds.
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 05, initial climb on a 045° heading. Field elevation 142 ft MSL. It is a hot, humid Florida afternoon in late July: OAT 34°C, dew point 26°C, altimeter 29.92. The density altitude is approximately 2,800 ft — well above field elevation, reducing aircraft performance. Scattered clouds at 3,500 ft, visibility 10 SM. A typical summer day at KLAL.
You are climbing through 400 ft AGL at 74 KIAS (Vy, best rate of climb) on a 045° heading when the engine suddenly loses all power. The tachometer unwinds to zero. No sputtering, no roughness — total, immediate power loss. You are over low-density residential development: scattered houses, small streets, trees. There is no open field, no park, no clear area. The airport is behind you and below. KLAL tower is active (24-hour ATCT); you are in Class D airspace.
Aircraft: Cessna 172S, solo, full fuel, within limits. Lycoming IO-360-L2A fuel-injected engine, G1000 glass panel, fixed gear, fixed-pitch prop. The preflight was routine; nothing was written up. The engine started and ran normally through the run-up. Mixture was set to lean at altitude (you are at 400 ft AGL, so mixture should be near full rich — a critical detail). Fuel selector on BOTH. Fuel pump was on.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have flown the C172S before but not extensively. You did not review the C172S emergency procedures or forced-landing site selection before this flight. You are not familiar with the terrain off Runway 05. You have never experienced a total engine failure on initial climb.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb in a C172S? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA12CA496 (2012): A Cessna 172S veered left during a touch-and-go takeoff attempt and struck trees after departing the runway. The accident was attributed to the pilot's failure to maintain directional control during the takeoff roll. The aircraft was damaged but the occupants survived.
NTSB WPR11CA295 (2011): A Cessna 172S on an instructional flight attempted a short/soft field takeoff with excessive flap setting at a density altitude 2,000 feet above the maximum listed in the POH. The aircraft failed to climb, struck trees, and was destroyed. The probable cause was the pilot's decision to attempt the takeoff at a density altitude outside the aircraft's performance envelope combined with use of a flap setting higher than the manufacturer's recommendation.
NTSB CHI92DER01 (1992): A Goehring Quickie lost engine power during initial climb after a touch-and-go landing and made a forced landing in a residential area after descending through trees and a house. The accident was attributed to carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The pilot did not commit to a forced landing early and attempted to stretch the glide over congested area.
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 accident resulted from the pilot's improper adjustment of the carburetor mixture control. The pilot did not ensure proper engine setup before takeoff.
NTSB ERA13FA325 (2013): A Beech 23 lost total engine power at 250 feet AGL shortly after takeoff from Suburban Airport, Maryland, and struck a tree and houses during a forced landing. The accident was attributed to the pilot's inadequate preflight preparation and decision to operate an unairworthy aircraft with a compromised fuel system. The pilot did not commit to a forced landing in the safest available area.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KLAL. KLAL has its own accident history dominated by loss of control (23.7%), loss of control on the ground (19.4%), and forced landings (17.2%). The scenario is localized to KLAL Runway 05 to make the off-field environment real and consequential: low-density development with scattered houses and trees — not a suitable forced-landing site. The decision to turn back toward the airport or commit to a forced landing in the development is the core of this scenario.
The consistent thread across all these events: total engine failure on initial climb is rare but catastrophic. The decision window is measured in seconds. The correct response is: (1) establish best glide immediately (68 KIAS in the C172S), (2) level the wings and scan for the safest landing area, (3) commit to that area without delay, (4) configure for slowest possible touchdown speed (full flaps), and (5) execute the landing. Attempting to troubleshoot, turn back to the airport at marginal altitude, or stretch the glide over congested area all increase the risk of stall, loss of control, or impact with obstacles.
Key lesson — Total engine failure on initial climb over congested development at 400 ft AGL leaves no time for troubleshooting or recovery attempts. Establish best glide (68 KIAS) immediately, level the wings, and commit to the safest available landing area — whether that is the airport (if reachable) or a forced landing in an open area (street, yard, field). Full flaps for slowest possible touchdown speed. Master switch OFF just before impact. Doors unlatched. The decision window is seconds; the outcome depends on immediate, correct action.
Debrief — teaching points
Total engine failure on initial climb is a forced-landing emergency — there is no time for troubleshooting.
At 400 ft AGL with a dead engine, the decision window is 30–40 seconds. Attempting to troubleshoot the fuel pump, mixture, or fuel selector consumes precious altitude and time. The correct response is to establish best glide immediately (68 KIAS in the C172S), level the wings, and commit to the safest available landing area. Troubleshooting can wait until the airplane is on the ground.
Best glide speed in the C172S is 68 KIAS — establish it immediately and maintain it.
Best glide maximizes glide distance and time. At 68 KIAS, the C172S descends at roughly 500 fpm, giving you 30–40 seconds of glide time from 400 ft AGL. Any deviation from best glide (climbing, turning steeply, slowing below best glide) reduces glide distance and time. Establish 68 KIAS immediately and hold it until touchdown.
At low altitude with a dead engine, shallow turns only — steep turns increase stall risk and reduce glide distance.
A steep bank at 400 ft AGL with a dead engine is a high-risk maneuver. The stall speed increases with bank angle; at 30° of bank, the stall speed is roughly 46 KIAS (vs. 40 KIAS level). A steep turn also reduces glide distance because altitude is consumed by the turn rather than by forward glide. If you must turn back to the airport, use a shallow bank (15° or less) and maintain best glide speed.
Off Runway 05 at KLAL, the terrain is low-density development — not a suitable forced-landing site.
The off-field environment off Runway 05's departure end (heading 045°) is low-density residential development with scattered houses, trees, and streets. There is no open field, no park, no clear area. If the engine fails on the Runway 05 departure, the airport (behind you) is the best forced-landing site if you can reach it. If not, commit to a forced landing in the nearest open area (street, yard) in the development.
Full flaps for slowest possible touchdown speed — impact energy rises with the square of speed.
In a forced landing, the slowest possible touchdown speed is the priority. Full flaps (30°) reduce the stall speed to roughly 38 KIAS and allow the slowest touchdown speed. The descent rate increases slightly, but the impact energy is minimized. Full flaps is the correct choice for any forced landing, whether on a runway, street, yard, or field.
Master switch OFF just before touchdown — minimize fire risk on impact.
The master switch controls the electrical system. Turning it OFF just before impact minimizes the risk of electrical fire on impact. This is a standard forced-landing procedure. Reach for the master switch as you approach touchdown, but do not take your eyes off the landing area.
Mixture at low altitude on a hot day should be near full rich — a lean mixture can cause engine failure.
At 400 ft AGL on a hot day (OAT 34°C), the mixture should be near full rich, not leaned. A lean mixture at low altitude can cause engine roughness or failure due to inadequate fuel flow. The C172S mixture control should be enriched as you descend from altitude. Failure to enrich the mixture at low altitude is a common cause of engine failure on initial climb.
Built from the real accident record
Scenario built from NTSB ERA12CA496 (2012 C172S loss of directional control on takeoff), CEN12CA510 (2012 C172S landing directional control loss), WPR11CA295 (2011 C172S density altitude / flap setting exceedance), WPR11CA035 (2010 C172S tree strike during landing), and regional precedents CHI92DER01 (1992 engine failure over residential area), MIA91LA128 (1991 engine failure on initial climb), ERA13FA325 (2013 engine failure at 250 ft AGL), CHI92DEM03 (1992 ignition failure on initial climb). Localized to KLAL.
NTSB reports: ERA12CA496 · CEN12CA510 · WPR11CA295 · WPR11CA035 · CHI92DER01 · MIA91LA128 · ERA13FA325 · CHI92DEM03
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 172S scenarios · More scenarios at KLAL