Engine Failure Over Tampa Development
Total power loss on initial climb off Runway 10 — dense development ahead, marginal forced-landing options, and a decision window measured in seconds
The scenario
Departing Tampa International Airport (KTPA), Tampa, FL — Runway 10, initial climb on a 092° heading. Field elevation 26 ft MSL. This is a busy Class B airport with a 24-hour towered ATCT; you have received your IFR clearance and are cleared for takeoff.
It is a clear morning in late spring: OAT 24°C, altimeter 29.98, light winds from 090° at 4 kt. Visibility 10 SM. The runway is long (6,999 ft) and well-maintained. Off the Runway 10 departure end (heading 092°), the terrain is dense development — residential neighborhoods, shopping centers, medium-density commercial — interspersed with small parks and open lots. There are no large open fields, no water, no clear forced-landing sites. The terrain is unforgiving.
You are 300 ft AGL, climbing at 79 KIAS (Vy, best rate of climb), heading 092°, when the engine loses power completely. The tachometer unwinds to zero. The propeller is still turning (windmilling), but there is no engine thrust. You have roughly 20–30 seconds of useful decision time before altitude becomes critical. The airport is behind you. Dense development is ahead and below.
Aircraft: Cessna 172R, solo, full fuel, within limits. Lycoming IO-360-L2A fuel-injected engine, fixed-pitch prop, steam panel, fuel selector on BOTH. The airplane was returned from a 100-hour inspection three days ago; the last flight was yesterday, a local 0.8-hour flight with no anomalies reported.
Pilot: you — a Private pilot, current, roughly 180 hours total. You completed a full preflight, including fuel sampling (clear and bright), mixture control check, and engine run-up (all engine instruments green, magnetos checked). You did not notice any anomaly. You were cleared for takeoff and executed a normal takeoff roll.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'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 C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN14CA023 (2013): A Cessna 172R student pilot touched down too far down the runway during a touch-and-go landing and delayed aborting the takeoff, resulting in collision with trees at the runway end. The probable cause was the student pilot's delay in aborting the takeoff. The lesson: recognize when a landing is unstable or unsafe, commit to the go-around decision early, and execute it decisively.
NTSB CEN14CA152 (2014): A Cessna 172R drifted left during landing on a narrow runway, struck a snow bank, and nosed over. The probable cause was the student pilot's failure to maintain directional control during landing. The lesson: maintain directional control throughout the landing, especially on narrow runways or in crosswind conditions.
NTSB ERA12CA325 (2012): A Cessna 172R struck the airport perimeter fence and trees during an aborted takeoff after the pilot discovered the flight control lock was still installed. The probable cause was the pilot's failure to remove the flight control lock before takeoff and his failure to use the required checklist. The lesson: use the checklist every time; a flight control lock left installed will cause loss of control on takeoff.
NTSB ATL04CA170 (2004): A Cessna 172R on an instructional flight experienced a dual control conflict when the student pilot took control during initial climb and refused to release the throttle, preventing the CFI from executing a go-around. The aircraft struck an airport fence. The probable cause was intentional control interference by the student. The lesson: understand the protocol for control transfer; the PIC must maintain authority and be prepared to take control if the other pilot is not responding.
Regional precedents (MIA91LA128, CHI92DER01, CHI92DEM03, CHI89DEM10) show a consistent pattern: engine failure on initial climb over congested terrain leaves no good landing options. The pilots who survived were those who committed to the best available site immediately and executed a controlled landing. The pilots who died were those who tried to stretch the glide over obstacles, attempted to turn back to the runway when altitude was insufficient, or struck power lines or buildings.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa International Airport. KTPA has its own accident history (dominant pattern: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 11.1%, LOSS_OF_CONTROL_GROUND 8.9%), but these specific events happened elsewhere. The scenario is localized to KTPA Runway 10 to make the off-field environment real and consequential for you as a student here: dense development, no large open fields, no water, no clear forced-landing sites.
The consistent thread across all these events: engine failure on initial climb is survivable if you commit to the best available landing site immediately and execute a controlled approach. The fatal accidents occur when pilots delay the landing decision, attempt to turn back to the runway when altitude is insufficient, or aim for obstacles (power lines, buildings, trees) instead of the best available open area.
Key lesson — Off Runway 10 at KTPA, the departure environment is dense development — no large open fields, no water, no clear forced-landing sites. An engine failure on initial climb requires an immediate decision: turn back to the airport if altitude permits (roughly 300+ ft AGL), or commit to the best available landing site ahead (park, parking lot, open street). The decision window is 20–30 seconds. Delay or indecision is fatal.
Debrief — teaching points
Engine failure on initial climb is survivable if you commit to a landing site immediately.
At 300 ft AGL with zero power, you have 20–30 seconds of useful decision time. The best outcome is to turn back to the airport if altitude permits (roughly 300+ ft AGL at the moment of failure). If you cannot make the airport, commit to the best available landing site ahead — do not delay, do not try to diagnose, do not try to restart. The C172R's best glide speed is 65 KIAS; establish that speed immediately and fly toward your chosen landing site. Delay or indecision kills.
Off Runway 10 at KTPA, the off-field environment is dense development — no good forced-landing sites.
The departure environment off Runway 10 (heading 092°) is dense residential and commercial development, interspersed with small parks and parking lots. There are no large open fields, no water, no clear forced-landing sites. A forced landing will be into obstacles — trees, buildings, power lines, fences. Your best options are a small park or a large parking lot. Know this before you line up on Runway 10. If you are uncomfortable with the departure environment, request a different runway or delay the flight.
A turn back to the runway at 300 ft AGL is feasible; at 250 ft AGL it is marginal; below 200 ft AGL it is not recommended.
The 'impossible turn' debate is real. At 300 ft AGL with zero power, a 180° turn back to Runway 10 will cost you 150–200 ft of altitude — you will roll out at roughly 100–150 ft AGL, very low but with the runway ahead. At 250 ft AGL, the turn is marginal — you will roll out at 50–100 ft AGL. Below 200 ft AGL, the turn is not recommended; commit to the best landing site ahead instead. Know your airplane's turn performance and your own limits.
Forced landing site selection: open area > paved surface > obstacles.
When you must land in the development, prioritize: (1) open area (park, parking lot, open street), (2) paved surface (parking lot, street), (3) avoid obstacles (power lines, buildings, trees). A small park with trees on the edges is better than a parking lot with light poles. A parking lot is better than a residential street with power lines. A residential street is better than landing between homes. Know the hierarchy and commit to the best site available.
Full flaps (30°) on final approach maximize the slowest possible touchdown speed.
The maximum flap speed for full flaps (30°) in the C172R is 85 KIAS. If you are at 65 KIAS best glide or slower on final approach, full flaps are safe and will give you the slowest possible touchdown speed. Impact energy rises with the square of touchdown speed — the slowest possible speed matters most. Add full flaps as the landing site is made and you are committed to the landing.
Post-maintenance flights warrant extra vigilance on engine instruments.
The C172R in this scenario was returned from a 100-hour inspection three days ago. After any maintenance, especially fuel system work, fuel contamination or improper fuel selector rigging can cause in-flight power loss. On the first flight after maintenance, monitor engine instruments closely during climb. If you notice any anomaly (rough running, RPM drop, fuel flow change), return to the airport immediately for a maintenance inspection.
Built from the real accident record
Scenario built from NTSB CEN14CA152, CEN14CA023, ERA12CA325, ATL04CA170 (C172R control/checklist failures on takeoff/initial climb), and regional forced-landing precedents MIA91LA128, CHI92DER01, CHI92DEM03, CHI89DEM10. Localized to KTPA Runway 10 departure environment.
NTSB reports: CEN14CA152 · CEN14CA023 · ERA12CA325 · ATL04CA170 · MIA91LA128 · CHI92DER01 · CHI92DEM03 · CHI89DEM10
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 172R scenarios · More scenarios at KTPA