Engine Failure Over Tampa Development
Total power loss at 400 ft AGL on initial climb off Runway 04 — dense development ahead, water behind, and a constant-speed prop that demands immediate energy management
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 04, initial climb on a 037° heading. Elevation 8 ft MSL. Non-towered field; you are on CTAF 122.8. The runway is short (3,583 ft) and sits in the heart of downtown Tampa's dense development.
It is a clear, calm morning: OAT 22°C, winds calm to light, altimeter 29.98, visibility 10+ SM. A textbook VFR day. You are climbing out at 96 KIAS (Vy, best rate of climb) in the Cirrus SR20, solo, full fuel (44 gallons usable), within weight and balance. The airplane was fueled last night; you performed a thorough preflight this morning and found nothing amiss.
At 400 ft AGL, roughly 0.5 nm northeast of the runway, the engine loses all power. The propeller is still windmilling; there is no fire, no smoke, no warning. The tachometer has dropped to zero. The airspeed is 96 KIAS and you are in a shallow climb attitude. Ahead of you is dense residential and commercial development — low-rise buildings, trees, power lines, and narrow streets. Behind you is Runway 04 and the open water of Tampa Bay beyond it.
Aircraft: Cirrus SR20, fuel-injected Continental IO-360-ES, constant-speed propeller, glass panel (Avidyne Perspective), fixed gear, CAPS parachute system. Fuel selector is on LEFT tank. You have no mechanical warning lights; the engine simply quit.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have 40 hours in the SR20. You are familiar with KTPF from three previous landings. You did not declare an emergency before departure; this is a local VFR flight.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'SR20'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about engine failure in the SR20 during initial climb? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB ATL04FA139 (2004, FATAL): A Piper PA-28-181 on a personal international flight collided with a building during climb-out from Fort Lauderdale Executive Airport after engine failure at 500 feet. The pilot attempted to stretch the glide toward the airport over a populated area and lost control. The probable cause was inadequate preflight planning causing fuel exhaustion and the pilot's failure to maintain flying speed, resulting in an inadvertent stall. The pilot did not commit to a forced landing in the populated area; instead, he tried to reach the airport.
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 landing decision early; the airplane struck obstacles.
NTSB LAX87LA118 (1987): A Cessna 172RG on a local pleasure flight experienced engine surge and total power loss during takeoff climb, forcing a landing on an occupied road where it collided with automobiles. The cause of the engine failure could not be determined despite detailed examination. The pilot attempted to maneuver around obstacles rather than committing to the best available landing site.
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 (not applicable to the SR20, which is fuel-injected). The pilot did not commit to a forced landing decision immediately; attempting to stretch the glide or maneuver around obstacles over residential area increased risk.
The consistent thread across all these events: engine failure during initial climb over populated areas kills pilots who delay the forced landing decision and attempt to stretch the glide toward the airport or maneuver around obstacles. The correct response is to commit to the best available landing site immediately — a street, a park, open ground, or (if altitude permits and no safe landing site exists) the CAPS parachute.
At KTPF, the off-field environment off Runway 04's climb-out (heading 037°) is dense residential and commercial development — no good forced-landing site. Off Runway 22's climb-out (heading 217°) is open water — a ditching. The turn-back maneuver at 400 ft AGL to Runway 04 is marginal but possible. The key decision is made in the first 10 seconds: commit to best glide speed (96 KIAS), assess the landing options, and make a decisive choice — do not delay.
Real accidents cited above occurred at other airports and in other aircraft — NOT at KTPF. KTPF has its own accident history (forced landing 19.4%, loss of control 16.7%, ditching 11.1%), but these specific events happened elsewhere. The scenario is localized to KTPF to make the off-field environment real and consequential for you as a student here.
Key lesson — Engine failure during initial climb over populated areas is survivable if you commit to a forced landing decision immediately. At 400 ft AGL over dense development off Runway 04 at KTPF, your options are: (1) land on a street or in a park in the development ahead, (2) attempt a turn-back maneuver to Runway 04 (marginal at 400 ft AGL), or (3) deploy CAPS if altitude is adequate and no safe landing site exists. Do not delay the decision. Do not attempt to stretch the glide toward the airport. Do not maneuver around obstacles. Commit to the best available landing site and execute it decisively. The SR20's best glide speed is 96 KIAS — establish it immediately and buy time to assess your options.
Debrief — teaching points
Establish best glide speed immediately — 96 KIAS in the SR20.
The moment the engine fails, lower the nose to establish 96 KIAS best glide. This is the speed that maximizes glide distance and gives you the most time to assess landing options. In the SR20, the constant-speed propeller will windmill and create drag, but best glide speed accounts for that. Do not climb, do not try to stretch altitude, do not delay. Nose down to 96 KIAS immediately.
Commit to a forced landing decision within 10 seconds.
At 400 ft AGL with an engine failure, you have roughly 60–90 seconds of glide time. Spend the first 10 seconds establishing best glide and assessing your options. By 20 seconds, you must have committed to a landing site. Indecision kills. The NTSB cases show that pilots who delay the forced landing decision and attempt to stretch the glide or maneuver around obstacles end up in worse situations. Commit early.
Off Runway 04 at KTPF, the off-field environment is dense development — no good forced-landing site.
The USGS NLCD ground cover off Runway 04's climb-out (heading 037°) is dense residential and commercial development. There are buildings, trees, power lines, and narrow streets. There is no open field, no park, no road. A forced landing in this environment is survivable only if you land on a street or find a small park. Plan for this before you depart. Know your off-field options.
The turn-back maneuver at 400 ft AGL is marginal but possible.
A 180° turn back to Runway 04 at 400 ft AGL with no engine power requires good energy management and a steep bank. The descent rate will increase slightly due to the bank. You will lose 150–200 ft AGL during the turn. If you commit to the turn-back at 400 ft AGL, you must roll out at 150–200 ft AGL with the runway in sight. This is marginal; it requires good airmanship. If you are uncomfortable with the turn-back, commit to a forced landing in the development ahead.
CAPS parachute is the right call when there is no safe landing site and altitude is adequate.
The SR20's CAPS parachute is designed for unrecoverable situations — loss of control, unrecoverable spin, and (at adequate altitude) engine failure with no safe landing site. At 300–350 ft AGL over dense development with no good forced-landing site, CAPS is the correct response. The parachute descent is nearly vertical (roughly 1,000 fpm); you cannot steer significantly. You will land in whatever is below, but the descent rate is survivable. CAPS is not failure; it is the system working as designed.
A street or park in the development is better than attempting to stretch the glide to the airport.
The NTSB cases show that pilots who attempt to stretch the glide toward the airport over populated areas end up stalling, spinning, or colliding with obstacles. A controlled landing on a street or in a park in the development ahead is a better outcome. You will damage the airplane, but you will survive. Attempting to reach the airport and failing is fatal.
Built from the real accident record
Scenario inspired by NTSB ATL04FA139 (2004, engine failure on climb-out over congested area), ERA13FA325 (2013, engine failure at 250 ft over populated area), LAX87LA118 (1987, engine failure during takeoff climb), and CHI92DER01 (1992, engine failure during initial climb over residential area). Real events occurred at other airports — NOT at KTPF. Localized to Peter O Knight Airport, Tampa, FL.
NTSB reports: ATL04FA139 · ERA13FA325 · LAX87LA118 · CHI92DER01
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
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 Cirrus SR20 scenarios · More scenarios at KTPF