Engine Failure Over Tampa Development
Total power loss on initial climb off Runway 04 — no good forced-landing option ahead, dense development below, and a decision window measured in seconds
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 04, climbing out on a 37° heading into a warm, humid Gulf Coast morning. Elevation 8 ft MSL. The runway is short (3,583 ft) and narrow; you are familiar with it from training.
It is late spring in Tampa: OAT 27°C, dew point 21°C, altimeter 29.91. Scattered clouds at 2,500 ft, light rain showers visible to the northeast. Visibility 7 SM. The humidity is high — classic carburetor-icing conditions, even though the temperature is well above freezing. KTPF is non-towered (CTAF); you self-announce on 122.8. You are in Class G airspace below 1,200 ft AGL; above that, you enter the overlying Tampa Class B (1,200 MSL to 10,000 MSL).
You are 300 ft AGL, climbing through 79 KIAS (Vy, best rate of climb), heading 037°, when the engine begins to run rough. Power is noticeably down — the tachometer is dropping. The off-field environment ahead is dense development: medium-density residential, some low-rise commercial, scattered trees. There is no open field, no park, no road suitable for a forced landing. KTPF's runway is behind you and below. You have roughly 20–30 seconds of useful decision time.
Aircraft: Piper PA-28-161 Warrior, solo, full fuel, within limits. Carbureted Lycoming O-320-D, fixed-pitch prop, steam panel, fuel selector on RIGHT tank (you switched to RIGHT after takeoff per procedure). Nothing was written up; the airplane was airworthy at departure.
Pilot: you — a Private pilot, current, roughly 250 hours total. You did not apply carburetor heat during the run-up because the engine ran smoothly. You did not apply it after takeoff because you were focused on the climb and the density of the development below.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-161'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb over a congested area? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB NYC07CA181 (2007): A Piper PA-28-161 on a personal flight attempted takeoff from a 1,500-foot turf airstrip with rising terrain and struck trees during initial climb. The probable cause was the pilot's inadequate preflight planning regarding weight and balance, combined with a right magneto malfunction that reduced available power. The lesson: engine failure on initial climb over terrain or development is survivable only if the pilot commits immediately to a forced landing in the least-hazardous available site.
NTSB ATL04FA139 (2004, FATAL): A Piper PA-28-181 on a personal flight collided with a building during climb-out from Fort Lauderdale Executive Airport after engine failure at 500 feet. 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 attempted to clear buildings and stalled; the outcome was fatal. The lesson: do not attempt to stretch glide or maneuver around obstacles over populated areas. Commit to the least-hazardous landing site available.
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 lesson: when engine fails during initial climb over congested area, select the least-hazardous forced landing site available (occupied road vs. buildings/trees) and execute it decisively.
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 probable cause was carburetor ice, with lack of suitable terrain for forced landing as a contributing factor. The lesson: commit to forced landing decision immediately when power is lost during initial climb; attempting to stretch glide or maneuver around obstacles over residential area increases risk of striking structures.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport. 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.
The consistent thread across all these events: engine failure on initial climb over congested development is survivable only if the pilot recognizes the emergency immediately, commits to a forced landing in the least-hazardous available site, and executes it decisively. Attempting to stretch glide, maneuver around obstacles, or turn back to the airport at 300 ft AGL invites a stall/spin or collision with structures. The decision window is 20–30 seconds. Carburetor ice is a preventable cause — apply carb heat proactively in conducive conditions and leave it on.
Key lesson — In warm, moist Gulf Coast air, the PA-28-161's carbureted O-320-D can accumulate serious carburetor ice even at cruise power and above-freezing temperatures. Apply full carburetor heat at the first sign of engine roughness or unexplained RPM loss. At 300 ft AGL over dense development, the decision window is measured in seconds — not minutes. Off Runway 04 at KTPF, the off-field environment is dense development: a delayed response or failed engine-recovery attempt means a forced landing in a street, parking lot, or among buildings. Commit to the least-hazardous landing site available and execute it decisively.
Debrief — teaching points
Carburetor ice forms in conditions you would not expect.
The FAA icing probability chart shows 'serious icing at glide power' at temperatures between roughly 20°C and 30°C when relative humidity is high — exactly the Gulf Coast morning conditions at KTPF. You do not need visible ice, freezing temperatures, or IMC. Warm, moist air at reduced power is the classic carb-ice environment. The PA-28-161's Lycoming O-320-D is carbureted; it has no alternate air system. Carburetor heat is the only tool.
The first symptom is subtle — a dropping tachometer and engine roughness.
In a fixed-pitch airplane like the PA-28-161, carburetor ice first shows as engine roughness and an unexplained RPM decrease. There is no dramatic power cut. Pilots who are not actively monitoring the tachometer miss the early warning. By the time the roughness is obvious, significant ice has accumulated. Scan the tachometer as part of your regular instrument scan, especially in conducive conditions.
Apply full carburetor heat — not partial — and expect an initial RPM drop.
When you apply carb heat to an iced carburetor, the RPM will drop further before it rises. This is expected and normal: the heat is melting ice and the resulting water is briefly disrupting combustion. Do not remove carb heat when the RPM drops — that is the heat working. Hold it full on. The RPM will recover as the ice clears, typically within 15–30 seconds depending on ice accumulation. Partial carb heat can worsen the situation by partially melting ice into water ingestion without fully clearing the restriction.
At KTPF Runway 04, an engine failure on departure is a forced landing in development.
The off-field environment off Runway 04's departure end (heading 37°) is dense development: medium-density residential, low-rise commercial, scattered trees. There is no alternate landing surface. If the engine quits on the Runway 04 departure and altitude is insufficient to return to the airport, the outcome is a forced landing in a street, parking lot, or open area among buildings. This is not a worst-case scenario; it is the geographic reality. Best glide is 73 KIAS. Flaps for slowest possible touchdown speed — impact energy rises with the square of touchdown speed, so the slowest possible speed matters most. Know this before you line up on Runway 04.
Proactive carb heat use in conducive conditions is not optional.
The PA-28-161 POH and the FAA Pilot's Handbook of Aeronautical Knowledge both recommend applying carburetor heat when conditions are conducive to icing — before the symptom appears. In a Gulf Coast summer departure, with OAT near 27°C and dew point near 21°C, that means applying carb heat during the run-up check (and confirming the expected RPM drop, then recovery) and considering its use during climb in visible moisture or high humidity. Waiting for the roughness to appear at 300 ft AGL over development is waiting too long.
Engine failure on initial climb over congested development: commit to forced landing immediately.
At 300 ft AGL over dense development, the decision window is 20–30 seconds. Do not attempt to stretch glide to the airport, do not attempt to maneuver around obstacles, and do not attempt the 'impossible turn' back to the runway. Commit to the least-hazardous landing site available — a wide street, parking lot, or open area — establish 73 KIAS best glide, and execute the landing decisively. Attempting to clear buildings or turn back at low altitude invites a stall/spin or collision with structures. Survival rates in controlled forced landings are significantly better than in uncontrolled ones.
Built from the real accident record
Scenario built from NTSB ERA21LA079 (2020 PA-28 go-around obstacle strike), NYC07CA181 (2007 PA-28 takeoff climb engine failure over terrain), ATL04FA139 (2004 PA-28 engine failure at 500 ft over populated area), and local-environment precedents LAX87LA118 (1987 engine failure over congested area), ERA13FA325 (2013 forced landing over residential), CHI92DER01 (1992 carburetor ice on initial climb). Anonymized and localized to KTPF.
NTSB reports: ERA21LA079 · NYC08CA200 · MIA08CA069 · NYC07CA181 · 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 Piper Warrior scenarios · More scenarios at KTPF