Engine Failure on Climb — Sarasota Bradenton
Total power loss in a complex aircraft at low altitude: gear management, landing-site selection, and the margin between survival and impact
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Sarasota, FL — Runway 04, climbing out on a 038° heading. Elevation 30 ft MSL. The runway is short-field length (5,006 ft) and you are climbing out over a mixed environment: medium development, wooded wetland, and low-density residential to the north. To the south (Runway 22 departure direction), the off-field environment is open water and parks — a ditching zone.
It is a clear, calm morning in early spring: OAT 18°C, altimeter 30.02, light winds from 080°. Visibility unlimited. A textbook VFR day. You are climbing through 400 ft AGL at 90 KIAS (Vy, gear up, prop in cruise). The engine is running smoothly; all engine instruments are green. KSRQ tower is active (Class C, part-time 0600–0000 local); you are in controlled airspace.
At 500 ft AGL, heading 038°, the engine suddenly loses all power. No roughness, no warning, no gradual fade — total loss. The propeller is still windmilling; the engine is not seized. But there is no power. You have roughly 30 seconds to diagnose, decide on a landing site, and configure the airplane. The terrain ahead is medium development and wooded wetland — marginal but workable. Behind you is the airport.
Aircraft: Piper PA-28R-200, solo, full fuel (48 gal usable), within limits. Lycoming IO-360 (fuel-injected, no carburetor heat). Retractable gear, constant-speed prop. You completed a thorough preflight; the engine ran smoothly through run-up. Nothing was written up. The airplane was airworthy at departure.
Pilot: you — a Commercial pilot, current, roughly 800 hours total. You are familiar with the PA-28R's systems. You have practiced forced landings in this airplane. You know the gear and prop are in the critical path of an emergency. Your decision window is measured in seconds.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about total engine failure in the PA-28R at low altitude? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR12FA058 (2011, FATAL): 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 a total loss of engine power for reasons that could not be determined — no mechanical anomalies were found post-accident. The pilot's failure to choose a suitable landing area was a contributing factor.
NTSB ERA10FA074 (2009, FATAL): A Piper PA-28R-200 experienced an oil problem and total engine loss during climb after takeoff. The pilot made a forced landing in trees near Wappinger, New York. The probable cause was a 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 did not recognize the early warning signs (oil temperature rising, oil pressure dropping) and continued the flight.
NTSB NYC08FA053 (2007, FATAL): 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 departure airport but did not have sufficient altitude to make the runway.
NTSB CEN25LA288 (2025): A Piper PA-28RT-201T experienced total engine failure during base-to-final turn while returning to the departure airport for a precautionary landing. The pilot executed a forced landing to a field, striking a fence. The cause of engine failure was undetermined pending further examination. The pilot made the correct decision to return to the airport, but did not have sufficient altitude to reach the runway.
NTSB ERA22LA067 (2021): A Piper PA-28R-200 on a personal flight experienced total loss of engine power during initial climb at 500 feet AGL. The pilot returned and landed on grass, striking the airport perimeter fence. The probable cause was a total loss of engine power for reasons that could not be determined. The pilot had sufficient altitude and glide distance to return to the airport, but the margin was thin.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Sarasota Bradenton International Airport. KSRQ has its own accident history (dominant pattern: loss of control ground, forced landing, runway excursion, hard landing, loss of control inflight), but these specific engine-failure events happened elsewhere. The scenario is localized to KSRQ 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 is often undetermined — no mechanical anomalies are found post-accident. The failure may be oil starvation, cylinder separation, bearing failure, or something else entirely. The pilot's response is the only variable under control. At 500 ft AGL with zero power, the decision window is measured in seconds. The best outcome is a return to the airport; the acceptable outcome is a controlled landing in a workable off-field site. The worst outcome is a steep turn at low altitude, a descending spiral, and an uncontrolled impact.
At KSRQ, the off-field environment is critical: off Runway 04 (climb-out 038°), the terrain is marginal (medium development, wooded wetland); off Runway 22 (climb-out 218°), the terrain is ditching (open water, parks). A Runway 04 departure with an engine failure at 500 ft AGL gives you a marginal landing site ahead. A Runway 22 departure with an engine failure gives you open water. This is not hypothetical; it is the NLCD ground cover off those runway ends.
Key lesson — Total engine failure in the PA-28R at low altitude is a forced-landing emergency. At 500 ft AGL, you have roughly 2 nm of glide distance at 79 KIAS best glide. The decision is binary: return to the airport (if you have the altitude and glide distance) or commit to a landing site ahead. A steep turn at low altitude to try to stretch the glide is a trap — it increases descent rate and consumes altitude faster than you are turning. Establish best glide immediately, lower the gear (unless the terrain is rough enough to risk cartwheeling), and commit to a landing site. The margin between survival and impact is measured in seconds and feet of altitude.
Debrief — teaching points
Best glide in the PA-28R is 79 KIAS — establish it immediately and hold it.
At 500 ft AGL with zero power, your first action is to lower the nose and establish 79 KIAS best glide. This speed maximizes glide distance and gives you the most time and distance to manage the emergency. Every second spent trying to restart the engine, cycling the fuel selector, or attempting a steep turn back to the airport is altitude lost. Establish best glide first; diagnose second.
At 500 ft AGL with zero power, a 180° turn back to the airport is marginal — a steep turn is unrecoverable.
In a PA-28R at 500 ft AGL with zero power, a shallow 180° turn back to the airport is workable if you establish best glide during the turn and commit to the maneuver. A steep turn to try to turn back faster increases descent rate and consumes altitude faster than you are turning — this is a descending spiral trap. At 150 ft AGL, a steep turn is unrecoverable. The lesson: at low altitude with zero power, commit to a maneuver (either turn back or land ahead) and fly it smoothly. Do not try to turn back faster.
Gear down or gear up? It depends on the terrain.
In a forced landing, the gear should be DOWN if the terrain is smooth (runway, field, grass, sand) — it increases drag, slows the airplane, and reduces impact energy. The gear should be UP if the terrain is rough (trees, rocks, heavy development) — it reduces the risk of catching a gear leg and cartwheeling. At KSRQ, off Runway 04, the terrain is marginal (medium development, wooded wetland) — a judgment call. Off Runway 22, the terrain is open water — a ditching, and gear position is irrelevant. Know the off-field environment before you take off.
Flaps for the slowest possible touchdown speed — impact energy rises with the square of speed.
In a forced landing, full flaps (40°) slow the airplane to roughly 55 KIAS (Vs0, stall speed in landing configuration). The touchdown speed is minimized, and impact energy is minimized. Full flaps also increase the descent rate slightly, but the trade is worth it: impact energy rises with the square of speed, so a 10 KIAS reduction in touchdown speed is a significant reduction in impact energy. Use full flaps in a forced landing unless the descent rate is so steep that you lose control authority.
The PA-28R fuel selector is LEFT / RIGHT — fuel starvation is a Piper-specific trap.
The PA-28R has two fuel tanks (left and right) and a fuel selector that must be set to LEFT, RIGHT, or OFF. If one tank is empty and the selector is on that tank, the engine will quit — fuel starvation, not fuel exhaustion. This is a Piper-specific failure mode. In a forced landing, confirm the fuel selector is on a tank with fuel. If the engine failure is due to fuel starvation, switching tanks may restore power. But at 500 ft AGL with zero power, you do not have time to diagnose fuel starvation — you must commit to a landing site.
At KSRQ, the off-field environment is critical to the decision.
Off Runway 04 (climb-out 038°), the terrain is marginal (medium development, wooded wetland) — a workable forced-landing site. Off Runway 22 (climb-out 218°), the terrain is ditching (open water, parks) — a forced landing off Runway 22 is a ditching, not a field landing. This is not hypothetical; it is the NLCD ground cover. A Runway 04 departure with an engine failure at 500 ft AGL gives you a marginal landing site ahead. A Runway 22 departure with an engine failure gives you open water. Know this before you line up on the runway.
Declare emergency on tower frequency, but fly the airplane first.
When the engine fails, your first action is to establish best glide and decide on a landing site. Your second action is to declare emergency on tower frequency: 'KSRQ Tower, [N-number], total engine loss, [altitude], [location], declaring emergency.' The radio call is important — it alerts ATC and gets emergency services ready — but flying the airplane comes first. You have roughly 30 seconds to establish best glide and commit to a landing site. The radio call takes 5 seconds; use it, but do not let it distract you from flying the airplane.
Built from the real accident record
Scenario built from NTSB WPR12FA058 (2011 PA-28R-200 total engine loss, forced landing), ERA10FA074 (2009 PA-28R-200 engine failure / oil system), NYC08FA053 (2007 PA-28R-200 cylinder separation), CEN25LA288 (2025 PA-28RT-201T engine failure on approach), ERA22LA067 (2021 PA-28R-200 engine loss at 500 ft), CEN20LA016 (2019 PA-28R-200 undetermined engine loss), and CEN26FA049 (2025 PA-28R-201 fuel starvation). Localized to KSRQ.
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.A — Preflight Assessment · PA.V.C — Engine Management · PA.VIII.D — Gear and Flap Management
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 KSRQ