Engine Failure on the Runway 16 Departure
Total power loss at 400 ft AGL, dense development ahead, and the temptation to turn back — a decision that kills pilots in complex aircraft
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 16, climbing out on a 155° heading. Elevation 71 ft MSL. You are a commercial pilot with roughly 500 hours total, 150 in complex aircraft. This is a local flight — a 45-minute hop to a nearby airport and back.
It is a clear, calm morning in central Florida: OAT 22°C, altimeter 30.01, winds calm. Visibility 10+ SM. The Piper Arrow is within limits, full fuel, gear up, prop in cruise. You are climbing through 400 ft AGL at 90 KIAS (Vy, best rate of climb) when the engine suddenly loses all power. The tachometer unwinds to zero. No warning. No roughness. Total power loss.
Off Runway 16's departure end (heading 155°), the off-field environment is dense development — low-density residential, medium development, scattered parks. There is no open field, no water, no clear landing surface. The terrain is built-up. Behind you, the runway is receding. Ahead, you have roughly 30 seconds of glide time before you are committed to landing in the developed area.
Aircraft: Piper PA-28R-200 (Arrow), fuel-injected Lycoming IO-360, retractable gear, constant-speed prop. The engine was run up normally; no anomalies. Nothing was written up. The airplane was airworthy at departure.
Pilot: you — a commercial pilot, current, 500 hours total, 150 in complex aircraft. You are familiar with the Arrow's systems. You have trained for engine failure, but never experienced one. The temptation to turn back to the runway is strong — it is right there, behind you, and you are only 400 ft AGL.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already know about engine failure on takeoff in a complex aircraft? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR12FA058 (2011): A Piper PA-28R-200 on a personal flight from Whidbey Island Naval Air Station experienced total loss of engine power during cruise. The pilot attempted a forced landing near Coupeville, Washington, but impacted terrain below a ridge line. The probable cause was total loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation. The pilot's decision to attempt a return to the airport or a specific landing area at low altitude may have contributed to the accident.
NTSB ERA10FA074 (2009): A Piper PA-28R-200 experienced an oil problem and total engine loss during climb after takeoff near Wappinger, New York. The pilot made a forced landing in trees. The probable cause was total loss of engine power due to delamination of the No. 3 connecting rod bearing, with inadequate maintenance inspection of the engine oil system as a contributing factor. The pilot's failure to commit to a suitable landing area and instead attempt to return to the airport contributed to the poor outcome.
NTSB NYC08FA053 (2007): A Piper PA-28R-200 on a business flight experienced progressive engine roughness and loss of power during initial climb after a touch-and-go landing. The accident resulted from fatigue fracture of the number 2 cylinder attach studs and subsequent cylinder separation, which caused total loss of engine power. The pilot attempted to return to the runway but stalled and spun at low altitude.
The 'impossible turn' pattern is consistent across all these accidents and the regional precedents (WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162): a pilot experiences engine failure at low altitude on takeoff or initial climb, attempts to turn back to the runway, stalls in the turn due to insufficient altitude and airspeed, and spins. A spin at low altitude is unrecoverable. The survival rate for pilots who attempt to turn back is zero. The survival rate for pilots who commit to landing straight ahead in the best available surface is significantly higher.
At KCLW, the off-field environment off Runway 16's departure end (heading 155°) is dense development — low-density residential, medium development, scattered parks. There is no open water, no clear field, no alternate runway. The best landing option is a park or large parking lot. The worst option is attempting to turn back to the runway at 400 ft AGL.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Clearwater Air Park. KCLW has its own accident history (see field dominant patterns), but these specific events happened elsewhere. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: engine failure at low altitude on takeoff is unforgiving. The 'impossible turn' — attempting to return to the runway at low altitude — is a trap that kills pilots. The correct response is to commit to landing straight ahead in the best available surface, fly the airplane at best glide speed, and execute a controlled forced landing. That is the difference between a survivable accident and a fatal one.
Key lesson — After engine failure at low altitude on takeoff, do NOT attempt to turn back to the runway. The turn requires a steep bank, which increases stall speed. At 400 ft AGL, you do not have the altitude to complete the turn and land on the runway without stalling. Commit to landing straight ahead in the best available surface — a park, a large parking lot, an open area. Establish 79 KIAS best glide, lower the gear, and execute a controlled forced landing. The survival rate for pilots who commit to landing straight ahead is significantly higher than for those who attempt the impossible turn.
Debrief — teaching points
The 'impossible turn' is a fatal trap at low altitude.
After engine failure at 400 ft AGL on takeoff, the temptation to turn back to the runway is strong — it is right there, and you have altitude. But the turn requires a steep bank, which increases stall speed. At a 30° bank, stall speed increases from 60 KIAS to roughly 69 KIAS. At a 40° bank, it increases to roughly 77 KIAS. At 400 ft AGL, descending at 500 fpm, you do not have the altitude to complete a 180° turn and land on the runway without stalling. The NTSB data on engine-failure accidents shows this pattern repeatedly: pilots who attempt to turn back stall and spin. A spin at low altitude is unrecoverable. The survival rate is zero. Commit to landing straight ahead instead.
Best glide speed for the PA-28R is 79 KIAS — establish it immediately.
After engine failure, lower the nose to 79 KIAS (best glide at gross weight). This speed maximizes glide distance and gives you the most time and distance to identify and reach a suitable landing area. At 79 KIAS, you have a glide ratio of roughly 8:1 — from 400 ft AGL, you can glide roughly 3,200 ft horizontally. That is enough distance to find a park, a parking lot, or an open area in most developed regions. Do not attempt to stretch the glide by flying slower — that reduces glide distance and increases the risk of stalling.
Lower the gear after committing to a landing area, not immediately.
Lowering the gear immediately after engine failure increases drag and reduces glide distance from roughly 3,200 ft to roughly 2,000 ft. That is a significant loss of options. The correct sequence is: (1) establish 79 KIAS best glide, (2) identify the best landing area, (3) lower the gear, (4) add flaps as needed for the slowest possible touchdown speed. Lowering the gear early commits you to landing sooner and in a less-suitable area. In the PA-28R, the gear extends at up to 129 KIAS (Vle), so you have time to identify a landing spot before lowering it.
The constant-speed prop should be set to high RPM (full forward) to reduce drag.
In the PA-28R, the constant-speed prop is controlled by the prop control (RPM knob). After engine failure, if the engine is still running (partial power loss), set the prop control to high RPM (full forward) to reduce drag and maximize glide distance. If the engine is completely dead, the prop will windmill and provide some drag reduction. Do not cycle the prop or attempt to feather it — the windmilling prop is acceptable in a forced landing.
Fuel selector LEFT / RIGHT — check it during the restart attempt.
The PA-28R fuel selector is LEFT / RIGHT (not BOTH like a Cessna). Fuel starvation from an incorrect selector position is a known failure mode in Piper aircraft. If the engine fails and you attempt a restart, check the fuel selector — it should be on the tank with fuel. However, at 400 ft AGL with dense development ahead, a restart attempt is a luxury you may not have. Commit to landing straight ahead and check the fuel selector after you are on the ground.
Off Runway 16 at KCLW, the off-field environment is dense development — parks are your best option.
The off-field environment off Runway 16's departure end (heading 155°) is dense development — low-density residential, medium development, scattered parks. There is no open water, no clear field, no alternate runway. The best landing option is a park or large parking lot. Roads are narrower and more likely to have power lines. Residential areas are the worst option — houses, trees, and power lines. Identify a park or parking lot early and commit to it. Do not attempt to turn back to the runway.
Built from the real accident record
Scenario built from NTSB WPR12FA058 (2011 PA-28R total power loss / forced landing), ERA10FA074 (2009 PA-28R oil failure / engine loss), NYC08FA053 (2007 PA-28R cylinder separation / power loss), and the 'impossible turn' teaching precedents WPR17FA152, LAX93LA048, ERA14FA123, SEA90LA162. Real accidents occurred at other airports — NOT at KCLW.
NTSB reports: WPR12FA058 · ERA10FA074 · NYC08FA053 · WPR17FA152 · LAX93LA048 · ERA14FA123 · SEA90LA162
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.III.A — Stall Recognition and Recovery · PA.III.B — Spin Awareness
Relevant FARs: §91.3 · §91.13 · §91.185 · §91.207
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 Arrow scenarios · More scenarios at KCLW