Engine Failure Over Residential Development
Total power loss on initial climb from Runway 05 — no good landing site ahead, distraction and weight management in a high-performance airplane
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 05, initial climb on a 42° heading. Field elevation 22 ft MSL. You are a commercial pilot with 800 hours total time, 200 hours in the SR22. This is a personal cross-country flight in your own aircraft.
It is a clear, calm morning: OAT 24°C, winds calm, altimeter 30.01. Visibility 10 SM. The Cirrus Perspective glass panel is functioning normally. You have filed IFR but are departing VFR under the Class G airspace; you will pick up your clearance after reaching 3,000 ft MSL and transitioning into the overlying Tampa Class B airspace.
The aircraft is loaded: you, two passengers, full fuel (81 gallons usable), and baggage. The weight-and-balance calculation shows the airplane at 3,520 lb — 120 lb over the maximum gross weight of 3,400 lb. You rationalized it: the CG is within limits, the overweight is modest, and the flight is short. You did not reduce fuel or ask a passenger to stay behind.
You line up on Runway 05 (true heading 42°), advance the throttle to full power, and rotate at 60 KIAS. The airplane lifts off cleanly. You are climbing at 85 KIAS, gear down (fixed), flaps retracted. You are 400 ft AGL, 0.8 nm from the runway, heading 042°.
Ahead of you (to the northeast, off the runway 05 climb-out): medium-density residential development — single-family homes, tree-lined streets, power lines, a few small parks. No open fields, no roads suitable for a forced landing, no water. The terrain is flat but thoroughly built up. Behind you is the airport. To your left (north) and right (south) are similar: developed residential areas, wooded wetland, no clear forced-landing options.
At 500 ft AGL, 1.2 nm from the runway, the engine loses power completely. The tachometer drops to zero. The propeller is still in constant-speed mode. You have no engine. You are over residential development with a dead engine, 500 ft AGL, and no good landing site in any direction.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about engine failure in the SR22 at low altitude over developed terrain? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ERA24LA007 (2023): A Cirrus SR22 struck trees approximately 1.1 miles from the departure end of the runway during initial climb at night. The pilot was distracted by primary flight display anomalies and terrain alerts. The probable cause was the pilot's failure to maintain a positive climb rate while distracted, with a contributing factor being operation over maximum gross weight. The airplane was 120 lb over maximum gross weight, which reduced its initial climb performance. The pilot's distraction by the PFD anomaly prevented him from recognizing the loss of climb performance until it was too late.
NTSB ERA18LA253 (2018): A Cirrus SR22 on takeoff experienced loss of directional control when the pilot's seat slid backward during rotation. The pilot had not properly secured the seat before flight. As the airplane accelerated, the seat slid back, the pilot could no longer reach the rudder pedals, and the airplane veered off the runway into trees and shrubs. The probable cause was the pilot's failure to properly secure the seat before initiating takeoff.
Regional precedent NTSB CHI92DER01 (1992): A Quickie homebuilt lost engine power during initial climb and made a forced landing in a residential area. The accident was attributed to carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The pilot attempted to stretch the glide over congested development and struck trees and a house. The lesson: recognize power loss early and commit to a forced landing rather than attempting to stretch the glide over congested terrain.
Regional precedent 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 accident was attributed to inadequate preflight preparation and operation of an unairworthy aircraft. The lesson: preflight discipline is critical; when power is lost over congested area, accept the least-damaging option quickly rather than maneuvering.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport. KVDF has its own accident history (see field dominant patterns: loss of control ground 18.4%, hard landing 18.4%, forced landing 15.8%), but these specific events happened elsewhere. The scenario is localized to KVDF to make the off-field environment real and consequential for you as a pilot based here.
The consistent thread across all these events: engine failure on initial climb over developed terrain is unforgiving. There is no time for extended troubleshooting, no altitude for complex maneuvering, and no good landing site. The decisions that matter are made in the first 30 seconds: establish best glide immediately, assess whether you can make the runway, and commit to a forced landing if you cannot. Overweight operation (ERA24LA007) reduces climb performance and makes this situation worse. Distraction (ERA24LA007) prevents recognition of the problem until it is too late. Preflight discipline (ERA13FA325) prevents mechanical failures. The SR22's CAPS parachute is the last resort — it is designed for exactly this situation, but it should be a last resort, not a first option.
Key lesson — Engine failure on initial climb over developed terrain demands immediate action: establish best glide (88 KIAS) instantly, assess runway reachability, and commit to a forced landing if you cannot make the airport. Overweight operation reduces climb performance and climb rate — do not depart overweight. Distraction by PFD anomalies or other issues must not prevent you from recognizing and responding to power loss. CAPS is the last resort for unrecoverable situations; it is not a substitute for good decision-making and airmanship. Off Runway 05 at KVDF, the off-field environment is residential development — no good forced-landing site exists. The runway is your only option if you can make it.
Debrief — teaching points
Establish best glide immediately — 88 KIAS in the SR22.
The moment you recognize total engine failure, lower the nose to 88 KIAS best glide. This is the speed that maximizes glide distance and gives you the most time and distance to assess your options. Do not attempt to restart the engine, do not check systems, do not maneuver — establish best glide first. At 500 ft AGL over developed terrain, you have roughly 90 seconds of glide time at best glide. That is your decision window. Waste it troubleshooting and you lose options.
Overweight operation reduces climb performance and climb rate — it makes engine failure on initial climb more likely to be fatal.
NTSB ERA24LA007 shows a 120 lb overweight SR22 that lost climb performance and struck trees on initial climb. The maximum gross weight of the SR22 is 3,400 lb. Operating above that weight reduces climb rate, reduces altitude gain, and reduces your options if the engine fails. Do not depart overweight. If the weight-and-balance calculation shows overweight, reduce fuel, ask a passenger to stay behind, or reduce baggage. The extra 120 lb is not worth the risk.
The SR22 fuel selector is LEFT / RIGHT — no BOTH position. Fuel starvation from improper tank selection is a real failure mode.
Unlike some other aircraft, the SR22 has no BOTH position on the fuel selector. You must select LEFT or RIGHT. If the engine fails and you suspect fuel starvation, check the fuel selector immediately — but do this while maintaining best glide. Switching tanks may restore power, but if it does not, you need to focus on the forced landing. Do not spend more than 10 seconds troubleshooting the fuel selector; if it does not work, move on to landing the airplane.
Distraction by PFD anomalies or other issues must not prevent you from recognizing power loss.
NTSB ERA24LA007 shows a pilot distracted by PFD anomalies and terrain alerts who failed to recognize and respond to loss of climb performance until it was too late. The Cirrus Perspective glass panel is powerful and can be distracting. If you see a PFD anomaly, acknowledge it, but do not let it distract you from flying the airplane. If the engine fails, the PFD anomaly is secondary. Fly the airplane first, troubleshoot second.
Off Runway 05 at KVDF, the off-field environment is residential development — no good forced-landing site exists.
The off-field environment off Runway 05's climb-out (heading 42°) is medium-density residential development: single-family homes, tree-lined streets, power lines, small parks. There is no open field, no road suitable for a forced landing, no water. If you lose the engine on the Runway 05 departure, your only option is to turn back to the airport. If you cannot make the airport, you will land in the development. The small park is the best available option, but it is small and surrounded by trees. Know this before you line up on Runway 05.
CAPS is the last resort — it is designed for unrecoverable situations, not for avoiding a forced landing.
The Cirrus CAPS whole-airframe parachute is the POH's primary response to unrecoverable loss of control, unrecoverable spin, or engine failure without a safe landing option. If you have a forced-landing site available (a park, a field, the runway), attempt the forced landing. CAPS should be deployed only when the situation is truly unrecoverable — when a forced landing would result in a stall, spin, or impact with obstacles that would be worse than a parachute descent. CAPS is a last resort, not a first option.
Built from the real accident record
Scenario built from NTSB ERA24LA007 (2023 SR22 engine failure on climb, distraction by PFD anomaly, overweight), ERA18LA253 (2018 SR22 seat-slide loss of control on takeoff), and regional forced-landing precedents CHI92DER01, ERA13FA325, CHI92DEM03, MIA91LA128. Real events occurred at other airports — NOT at Tampa Executive.
NTSB reports: ERA24LA007 · ERA18LA253 · 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.A — Preflight Assessment · PA.II.B — Engine Starting / Systems Preflight
Relevant FARs: §91.3 · §91.9 · §91.103 · §91.107
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 Cirrus SR22 scenarios · More scenarios at KVDF