Total Power Loss Over Clearwater
Engine failure on initial climb from a non-towered field — dense development surrounds you, and the decision window is measured in seconds
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, initial climb on a 335° heading. Elevation 71 ft MSL. It is a clear, calm morning: OAT 22°C, winds calm, altimeter 30.02. Visibility 10 SM. A routine local flight in a Piper Arrow PA-28R-200 — you are a commercial pilot with 800 hours total, current and proficient in complex aircraft.
You are 400 ft AGL, climbing at 90 KIAS (Vy, gear retracting), heading 335°, when the engine suddenly loses all power. The propeller is still turning (windmilling), but there is no thrust. The tachometer has dropped to zero. You have no warning — no roughness, no vibration, no prior indication. The engine simply quit.
Aircraft: Piper Arrow PA-28R-200, solo, full fuel (48 gallons usable), within limits. Constant-speed propeller, retractable gear (currently retracting), fuel-injected Lycoming IO-360. The preflight was standard; nothing was written up. The engine ran smoothly through the run-up.
Airspace: KCLW is non-towered, Class G airspace. You are climbing out on the 335° heading (Runway 34 departure). The off-field environment is poor in all directions: dense development, low-density residential, and medium development surround the airport. There are no open fields, no water, no obvious alternate landing areas within gliding distance.
Pilot: you — commercial, complex-current, 800 hours. You did not apply full power during the initial climb; you were at climb power (approximately 2,400 RPM, 65% power). The engine failure is total and immediate. Your decision window is measured in seconds, not minutes.
- {'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 enter the decision tree — what do you know about total engine failure in a complex aircraft like the PA-28R? (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 — post-accident examination of the airframe and engine revealed no evidence of preaccident mechanical malfunctions or failures that would have precluded normal operation. The pilot's failure to identify and commit to a suitable landing area 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 identify a suitable landing area (trees instead of an open field 0.3 nm away) was a secondary factor.
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 probable cause was fatigue fracture of the number 2 cylinder attach studs and subsequent cylinder separation, which caused total loss of engine power. The pilot's attempt to return to the departure airport in a steep turn at low altitude was a contributing factor.
NTSB ERA22LA067 (2021): A Piper PA-28R-200 on a personal flight experienced total loss of engine power during initial climb at 500 ft AGL. The pilot returned and landed on grass, striking the airport perimeter fence. The probable cause was total loss of engine power for reasons that could not be determined. The pilot's decision to return to the airport was correct; the execution was marginal due to the steep turn at low altitude.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at Clearwater Air Park. KCLW has its own accident history (FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 18.5%, GEAR_UP_LANDING 18.5%), but these specific NTSB 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: total engine failure in the PA-28R can happen with no warning, no prior indication, and no mechanical anomaly that post-accident examination can find. The fix is not mechanical — it is airmanship: establish best glide immediately (79 KIAS), identify the safest landing area (the runway, if reachable; an open field or parking lot if not), lower the gear and flaps to minimize touchdown speed, and commit to a stable, controlled descent. The pilots who survived did these things. The pilots who did not — who attempted steep turns at low altitude, who landed in trees instead of open fields, who left the gear up — did not.
Key lesson — Total engine failure in the PA-28R is often undetermined in cause — post-accident examination finds no mechanical anomaly. The outcome depends entirely on airmanship: establish 79 KIAS best glide immediately, identify the safest landing area within glide distance (the runway if reachable, an open field or parking lot if not), lower the gear and flaps to minimize touchdown speed, and execute a stable, controlled descent. At 400 ft AGL over dense development, the decision window is measured in seconds. The pilots who survived committed quickly to a landing area and flew a stable approach. The pilots who did not — who attempted marginal turns back to the runway, who landed in trees, who left the gear up — did not survive.
Debrief — teaching points
Total engine failure in the PA-28R can happen with no warning.
The NTSB accident corpus for the PA-28R shows repeated cases of total engine failure with no prior indication — no roughness, no vibration, no warning. The engine simply quits. Post-accident examination often finds no mechanical anomaly. The cause may be undetermined. You cannot prevent this failure; you can only respond to it. The response is automatic: lower the nose to 79 KIAS best glide, identify the safest landing area within glide distance, and commit to a stable, controlled descent.
Best glide speed for the PA-28R is 79 KIAS — establish it immediately.
At 79 KIAS best glide, the PA-28R has the maximum glide distance and the maximum time to identify a landing area and set up the approach. Any other speed — faster or slower — reduces glide distance and time. At 400 ft AGL with an engine-out, every second and every foot of altitude matters. Establish 79 KIAS immediately. Do not attempt restarts, do not attempt steep turns, do not attempt to diagnose. Fly the airplane first.
Landing gear DOWN minimizes impact energy — lower it as soon as the landing area is committed.
In a forced landing, landing gear down is the correct choice. The gear absorbs impact energy and slows the airplane. Vle (max gear extended) for the PA-28R is 129 KIAS — well above best glide speed of 79 KIAS, so the gear is safe to extend at any point in the descent. Lower the gear as soon as the landing area is committed. A gear-up landing will damage the airplane; a gear-down landing will slow it and absorb energy.
Full flaps (40°) minimize touchdown speed — add them on final approach.
Vfe (max flap extended) for the PA-28R is 103 KIAS — above best glide speed of 79 KIAS, so full flaps are safe to add at any point in the descent. Full flaps slow the airplane to the minimum approach speed and steepen the descent slightly. Impact energy rises with the square of touchdown speed, so the slowest possible speed matters most. Add full flaps on final approach, once the landing area is committed and the descent is stable.
At KCLW, the off-field environment is dense development — no open fields, no parks, no obvious alternates.
The USGS NLCD ground cover off all runway ends at KCLW is dense development, low-density residential, and medium development. There are no open fields, no parks, no water. If the engine fails on departure, the landing area options are limited: return to the runway (if glide distance allows), land in a parking lot (tight but survivable), or land in trees or on roads (high-risk). Know this before you line up on Runway 34. The off-field environment is poor in all directions.
Steep turns at low altitude with an engine-out are a trap — shallow turns only.
At 400 ft AGL with an engine-out, a steep bank turn uses altitude rapidly. A 20° bank at 79 KIAS loses roughly 100 ft of altitude per 180° of turn. A 30° bank loses more. The NTSB accident corpus shows repeated cases where pilots attempted steep turns back to the runway and lost the margin. Shallow turns only — 10–15° bank — to preserve altitude and glide distance.
Built from the real accident record
Scenario built from NTSB WPR12FA058 (2011 PA-28R-200 total engine failure, undetermined cause), ERA10FA074 (2009 PA-28R-200 oil system failure / connecting rod bearing), WPR09FA015 (2008 PA-28R-201T engine loss / unsuitable landing area), NYC08FA053 (2007 PA-28R-200 cylinder separation), CEN25LA288 (2025 PA-28RT-201T engine failure on base-to-final), ERA22LA067 (2021 PA-28R-200 engine loss at 500 ft AGL), CEN20LA016 (2019 PA-28R-200 total power loss undetermined), and CEN26FA049 (2025 PA-28R-201 fuel starvation / emergency landing). Anonymized and localized to KCLW.
NTSB reports: WPR12FA058 · ERA10FA074 · WPR09FA015 · NYC08FA053 · CEN25LA288 · ERA22LA067 · CEN20LA016 · CEN26FA049
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.V.A — Preflight Inspection · PA.V.B — Powerplant Operation
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