Engine Out Over Congested Development
Total power loss on initial climb off Runway 05 — no good forced-landing site ahead, and the decision window is seconds
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 05, climbing out on a 042° heading. Elevation 22 ft MSL. This is a non-towered field (CTAF); you will self-announce on 118.475 MHz.
It is a clear, calm morning in late spring: OAT 24°C, altimeter 29.98, visibility 10 SM. Light winds from the north. A routine local flight — nothing unusual in the weather or the forecast. You have filed no flight plan; this is a VFR local area flight.
You are 300 ft AGL, climbing at 73 KIAS (Vy), heading 042°, when the engine suddenly loses all power. The tachometer drops to zero. The propeller is windmilling. You have no engine. Off the Runway 05 climb-out (heading 042°), the terrain ahead is medium-density residential development — houses, trees, roads, and some open space. There is no obvious clear field, no obvious road, no obvious park. The best off-field option is marginal: low-density development, wooded wetland, and some open developed areas (parks/large lots).
Aircraft: Cessna 172N, solo, full fuel, within limits. The airplane was released from the maintenance shop three days ago after an annual inspection. The logbook entry notes 'throttle shaft inspected and serviced.' Nothing else was written up.
Pilot: you — a Private pilot, current, roughly 250 hours total. You completed a normal run-up, including a full-power check. The engine ran smoothly. You did not notice anything amiss during the takeoff roll or the initial climb. The power loss is sudden and complete.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'C172N'}
- {'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? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC06LA179 (2006, FATAL): A Cessna 172N on a personal local flight experienced partial loss of engine power during cruise due to improper maintenance of the throttle shaft during the most recent annual inspection. The pilot made a forced landing that resulted in collision with trees. The probable cause was improper maintenance of the throttle shaft, which resulted in a partial loss of engine power during cruise flight. The pilot's decision to attempt to avoid trees during the forced landing approach contributed to the loss of control.
NTSB CEN25LA168 (2025): A Cessna 172N on an instructional flight lost total engine power on final approach when the throttle cable was found disconnected from the carburetor. The pilot executed a forced landing to a field. The accident resulted from improper maintenance following carburetor replacement, with an apprentice's work not adequately inspected by the supervising mechanic. The pilot's early recognition of the power loss and commitment to a forced landing were factors in the survivability of the accident.
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. The pilot's attempt to avoid obstacles during the forced landing approach contributed to the impact with the house. The teaching point: when forced to land in congested terrain, commit to the landing and fly it smoothly rather than maneuvering to avoid obstacles.
NTSB ERA13FA325 (2013): A Beech 23 lost total engine power at 250 feet AGL shortly after takeoff and struck a tree and houses during a forced landing. The pilot's inadequate preflight preparation and decision to operate an unairworthy aircraft with a compromised fuel system contributed to the accident. The pilot's attempt to maneuver around obstacles at low altitude increased the risk of loss of control.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: loss of control on the ground, hard landings, forced landings, loss of control inflight, runway excursions), but these specific NTSB events happened elsewhere. 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 or partial engine failure on initial climb leaves no time for troubleshooting. The decision is where to land, not why the engine quit. Pilots who commit early to a forced landing and fly it smoothly have better outcomes than pilots who delay, search for terrain, or maneuver to avoid obstacles. At 300 ft AGL over residential development, the margin for error is zero.
Key lesson — Total engine failure on initial climb at 300 ft AGL over residential development is a forced-landing emergency. Establish 65 KIAS best glide immediately, commit to the best available landing site (runway, open field, or water), and fly a stable, controlled approach. Do not delay to troubleshoot. Do not maneuver to avoid obstacles — that risks a stall or loss of control. A firm but controlled landing in marginal terrain is survivable; an uncontrolled impact is not. Off Runway 05 at KVDF, the terrain is medium-density development with some open space — marginal but not impossible. The 180° turn back to Runway 23 is feasible at 300 ft AGL if executed smoothly and without delay.
Debrief — teaching points
At 300 ft AGL, altitude is the limiting factor — there is no time for troubleshooting.
When the engine fails on initial climb at 300 ft AGL, you have roughly 60–90 seconds of glide time before touchdown. That time is consumed by establishing best glide, scanning for terrain, and executing the approach. There is no time to check the throttle, cycle the magnetos, or attempt a restart. The decision is where to land, not why the engine quit. Troubleshooting can wait until after you are on the ground — or it can wait until never, if you waste altitude trying to fix the engine.
Establish 65 KIAS best glide immediately — this is the first action.
Best glide speed for the C172N is 65 KIAS at gross weight. This speed maximizes glide distance and gives you the most time and distance to find a landing site. Establishing best glide immediately — before you think about anything else — is the correct first action. Lower the nose, trim for 65 KIAS, and then scan for terrain. Every second counts.
Commit to a landing site early — do not search for perfect terrain.
Off Runway 05 at KVDF, the terrain is medium-density residential development with some open space — marginal but not impossible. A park, a field, a road, or any open area is a viable landing site. The pilot who commits to a landing site at 300 ft AGL and flies a stable approach has a better outcome than the pilot who searches for perfect terrain and runs out of altitude. Commit early, commit decisively, and fly the landing smoothly.
Fly a stable, controlled approach — do not maneuver to avoid obstacles.
At 65 KIAS (or slower), you are close to the stall speed (Vs0 is 40 KIAS in landing configuration). A sharp turn, a climb, or a steep bank to avoid an obstacle risks a stall or loss of control. The pilot who maneuvers to avoid trees or power lines at low altitude often stalls and loses control. The pilot who commits to a landing site and flies it straight in — accepting the risk of hitting an obstacle — has a better outcome. A firm but controlled landing is survivable; a stall at 100 ft AGL is not.
The 180° turn back to the airport is feasible at 300 ft AGL if executed smoothly.
The 'impossible turn' back to the departure runway is a real risk at low altitude. However, at 300 ft AGL with a dead engine, a smooth 180° turn back to Runway 23 (the reciprocal of Runway 05) is feasible if you maintain 65 KIAS and do not increase the bank angle excessively. The turn will use altitude, but you have enough to make it if you are smooth and decisive. If you delay the turn or attempt it at a lower altitude, the margin disappears.
Post-maintenance engine failures demand a thorough preflight and run-up.
NTSB NYC06LA179 and CEN25LA168 both involved engine failures caused by improper maintenance — a throttle shaft failure and a disconnected throttle cable. Both occurred shortly after maintenance. A thorough preflight and a full-power run-up are your only defense against a maintenance-induced failure. If the engine runs smoothly at full power during the run-up, the risk is low — but if you skip the run-up or do not run to full power, you may not discover the problem until you are in the air.
Built from the real accident record
Scenario built from NTSB NYC06LA179 (2006 C172N throttle shaft failure / forced landing into trees), CEN25LA168 (2025 C172N disconnected throttle cable on final approach), CHI92DER01 (1992 Quickie carburetor ice on initial climb over residential area), and ERA13FA325 (2013 Beech 23 engine failure at 250 ft AGL over congested development). Localized to Tampa Executive Airport (KVDF), a non-towered field with medium development off Runway 05's climb-out.
NTSB reports: NYC06LA179 · CEN25LA168 · CHI02FA247 · CEN25LA099 · 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.II.C — Takeoff and Climb
Relevant FARs: §91.3 · §91.7 · §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 172N scenarios · More scenarios at KVDF