Engine Failure on Initial Climb — Runway 05
Total power loss at 400 ft AGL over congested development. No good forced-landing site. Decision and commitment are everything.
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 05, initial climb on a 42° heading. Elevation 22 ft MSL. You are a Private pilot with roughly 250 hours total time; this is a local VFR flight in a Cessna 172M.
It is a hot, humid Florida afternoon in late July: OAT 32°C, dew point 26°C, altimeter 29.89. Scattered clouds at 3,500 ft, visibility 8 SM. Density altitude is approximately 2,800 ft — the airplane will climb like it is at 2,800 ft elevation, not 22 ft. The C172M's 150 hp Lycoming O-320 is already marginal on climb in these conditions.
You are cleared to depart Runway 05 (true heading 42°). The runway is 5,000 ft long, plenty for a normal takeoff. You line up, advance the throttle, and the airplane accelerates normally. Rotation at 55 KIAS, liftoff at approximately 60 KIAS. You are climbing at 78 KIAS (Vy, best rate of climb) at a shallow angle — the high density altitude is limiting climb performance.
At 400 ft AGL, heading 042°, the engine suddenly loses all power. The propeller is windmilling; there is no response to throttle. The airplane is over medium-density residential development — houses, trees, streets. There is no open field, no park, no clear area ahead. The runway is behind you. You have roughly 30 seconds to decide and commit.
Aircraft: Cessna 172M, solo, full fuel, within limits. Lycoming O-320-E2D, carbureted, fixed-pitch prop, steam panel. The airplane was airworthy at departure; nothing was written up. Magnetos checked green during run-up. Fuel selector on BOTH. Carburetor heat was off during takeoff (normal procedure).
Pilot: you — Private, current, 250 hours. You have flown this airplane before. You are not in an emergency mindset; you are on a routine local flight. The power loss is sudden and total.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about total engine failure on initial climb in a C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR09FA316 (2009, FATAL): A Cessna 172M on approach to Tieton State Airport in mountainous terrain failed to land and initiated a go-around at low altitude. The pilot struck trees at the runway end. The probable cause was the pilot's failure to maintain clearance from trees during a go-around, with contributing factors including lack of experience with turf airstrips and delayed go-around initiation. The lesson: at low altitude, commit to the landing or go-around early. Do not maneuver to avoid obstacles at 200 ft AGL.
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. The pilot descended through trees and a house. The probable cause was carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The lesson: recognize power loss early, establish best glide immediately, and commit to the best available landing area — do not try to stretch the glide over congested development.
NTSB ERA13FA325 (2013): A Beech 23 lost total engine power at 250 ft AGL shortly after takeoff and struck a tree and houses during a forced landing. The probable cause was inadequate preflight preparation and operation of an unairworthy aircraft. The lesson: preflight discipline matters. But also: when power is lost over congested area, accept the least-damaging option quickly rather than maneuvering.
NTSB CHI92DEM03 (1992): A Johansen Kitfox homebuilt lost total engine power during initial climb due to ignition system spark plug failure and collided with pine trees. The probable cause was total ignition system failure not detected during pre-takeoff magneto check. The lesson: during initial climb power loss, prioritize finding any available landing area quickly. Evasive maneuvering to avoid obstacles increases risk of stall or loss of control.
NTSB MIA91LA128 (1991, FATAL): A Sonerai-II homebuilt experienced total engine failure shortly after takeoff and made a forced landing in an alley. The airplane touched down hard, bounced, and struck a telephone pole. The probable cause was improper adjustment of the carburetor mixture control. The lesson: ensure proper engine setup before takeoff. When forced to land in congested area, commit to the landing and manage the approach to minimize bounce and secondary impacts.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF's own dominant accident pattern is LOSS_OF_CONTROL_GROUND (18.4%), HARD_LANDING (18.4%), FORCED_LANDING (15.8%), and LOSS_OF_CONTROL_INFLIGHT (13.2%). The scenario is localized to KVDF to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: total engine failure on initial climb over congested development is survivable only if the pilot commits early to the best available landing area and executes a controlled approach. Maneuvering to avoid obstacles or search for a better area at low altitude increases descent rate, reduces altitude margin, and often results in striking the obstacle anyway. The correct decision is to establish best glide, identify the best available option, and commit to it.
Key lesson — Total engine failure at 400 ft AGL over residential development is a forced landing, not a go-around or a stretch back to the runway. Establish 65 KIAS best glide immediately. Identify the best available landing area — a park, open field, or street — and commit to it. Do not maneuver to search for a better area at low altitude. The best available option is the correct option. Survival depends on early commitment and a controlled approach, not on finding the perfect landing site.
Debrief — teaching points
Establish best glide immediately — 65 KIAS in the C172M.
The moment you recognize total power loss, lower the nose to establish 65 KIAS best glide. This is the speed that maximizes glide distance and gives you the most time to identify a landing area and set up a controlled approach. At 400 ft AGL, you have roughly 2 minutes of glide time. Use it to get the airplane stable and to scan for the best available landing area. Do not climb, do not maneuver steeply, do not search for a perfect site. Establish best glide and trim for hands-off flight.
Commit to the best available landing area — do not search for a better one at low altitude.
At 400 ft AGL over residential development, there is no perfect landing site. The park with scattered trees is better than the street with power lines. The street is better than the dense houses. Identify the best available option and commit to it. Maneuvering to search for a better area at low altitude increases descent rate, reduces altitude margin, and often results in striking an obstacle anyway. The NTSB accident pattern is clear: pilots who maneuver to avoid obstacles at 200 ft AGL often strike the obstacle they were trying to avoid. Commit early, when you have altitude and time.
High density altitude reduces climb performance — the C172M is marginal in heat.
The C172M's 150 hp Lycoming O-320 is the lower-powered variant of the 172 family. At a density altitude of 2,800 ft on a hot, humid day, the airplane climbs like it is at 2,800 ft elevation. The climb rate is shallow and the airplane is slow to gain altitude. This is not a failure; it is the airplane's design. Recognize that in high-DA conditions, you will not climb as fast as you expect. Plan your departure and initial climb accordingly. If you lose an engine on initial climb in high-DA conditions, you have less altitude margin than you would at sea level.
Total engine failure is not the same as partial power loss or carburetor ice.
Carburetor ice causes engine roughness and a gradual power loss — you have time to apply carb heat and recover. Total engine failure — no response to throttle, propeller windmilling, no power at all — is a different emergency. The causes include magneto failure, total fuel starvation, or catastrophic engine failure. Carburetor heat will not fix it. Cycling the magnetos or fuel selector will not fix it. The correct response is to establish best glide and prepare for a forced landing. Do not waste time trying to restart the engine.
The runway is behind you — do not try to stretch the glide back to it.
At 400 ft AGL on initial climb, the runway is behind you and you are descending. Trying to stretch the glide back to the runway means shallowing the descent angle, which increases glide distance but also increases the time you spend over congested development. By the time you realize you cannot make the runway, you are too low and too far away to commit to a good landing area. The correct decision is to accept that the runway is gone and commit to the best available landing area ahead.
Built from the real accident record
Scenario built from NTSB WPR09FA316 (2009 C172M go-around failure / tree strike), GAA16CA011 (2015 C172M approach path / threshold light strike), GAA15CA088 (2015 C172M gust lock / loss of control), ERA14CA430 (2014 C172M navigation error / off-airport landing), and regional precedents CHI92DER01 (1992 Quickie carburetor ice / forced landing over residential), ERA13FA325 (2013 Beech 23 total power loss / tree strike), CHI92DEM03 (1992 Kitfox ignition failure / tree strike), MIA91LA128 (1991 Sonerai total engine failure / alley landing). Localized to Tampa Executive Airport (KVDF), Runway 05.
NTSB reports: WPR09FA316 · GAA16CA011 · GAA15CA088 · ERA14CA430 · CHI92DER01 · ERA13FA325 · CHI92DEM03 · MIA91LA128
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.III.A — Normal 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 172M scenarios · More scenarios at KVDF