Engine Failure on Initial Climb
Total power loss at 500 ft AGL over central Florida — landing-site selection and gear management in a forced descent
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, climbing out on a 180° heading. Elevation 90 ft MSL; the runway is essentially at sea level in central Florida's flat terrain.
It is a clear, calm morning: OAT 22°C, altimeter 29.98, light winds from the northeast. Visibility 10 SM. You are climbing through 500 ft AGL at 90 KIAS (Vy, best rate of climb with gear up), heading 180°. The engine instruments are green — oil temp and pressure nominal, fuel pressure steady, ammeter in the green. You have been airborne for 90 seconds.
Then, without warning, the engine loses all power. The propeller windmills. The airspeed is 90 KIAS, the altitude is 500 ft AGL, and you have roughly 60–90 seconds of glide time before touchdown. You are in Class G airspace, non-towered. KZPH has no tower; you are on CTAF (122.8).
Aircraft: Piper PA-28R-200, solo, full fuel (48 gallons usable), within limits. Lycoming IO-360 fuel-injected, constant-speed prop, retractable gear. The airplane was airworthy at departure; the preflight was standard. Nothing was written up.
Pilot: you — a Commercial pilot, current, roughly 800 hours total. You are familiar with KZPH; you have flown from here before. You did not declare an emergency yet. You are focused on the immediate problem: total power loss at 500 ft AGL, and a landing-site decision in the next 60 seconds.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already 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, 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 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 accident was fatal.
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 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 accident was fatal.
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 probable cause was loss of engine power due to fatigue fracture of the number 2 cylinder attach studs and subsequent cylinder separation. The accident was fatal.
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.
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, prompting the pilot to return and land on grass, striking the airport perimeter fence. The accident resulted from a total loss of engine power for reasons that could not be determined.
NTSB CEN20LA016 (2019): A Piper PA-28R-200 experienced a sudden total loss of engine power during cruise flight after an uneventful takeoff and climb. The accident was attributed to a total loss of engine power for undetermined reasons; post-recovery examination found no mechanical anomalies.
The consistent thread across all these events: total engine failure in the PA-28R can occur suddenly, with no warning, and for reasons that may not be apparent in post-accident examination. The Lycoming IO-360 is a robust engine, but connecting rod bearing delamination, cylinder attach stud fatigue, oil-system failure, and other mechanical issues can occur without obvious preflight signs. The engine can fail with no warning — no rough running, no power loss warning, just sudden silence. This is not a failure of preflight technique; it is a mechanical reality. Your only defense is immediate recognition, best-glide speed, and rapid landing-site assessment. Preflight inspection is important, but it cannot prevent all mechanical failures.
At KZPH, the off-field environment off Runway 19's climb-out (heading 180°) is marginal — mostly open developed (parks/large lots), evergreen forest, and low-density development. Off Runway 01's climb-out (heading 360°), the environment is good — mostly pasture/hay, open developed areas, and evergreen forest. A forced landing on Runway 01 or in the open fields off Runway 01 is survivable. A forced landing in the trees or developed areas off Runway 19 is more hazardous. The real accidents cited above occurred at other airports — NOT at Zephyrhills Municipal. KZPH has its own accident history (see field dominant patterns: FORCED_LANDING 29.2%, LOSS_OF_CONTROL_INFLIGHT 29.2%, STALL_SPIN 16.7%), but these specific NTSB events happened elsewhere. The scenario is localized to KZPH to make the off-field environment real and consequential for you as a student here.
The key lesson: in a total engine failure at low altitude, the decision window is measured in seconds. Best glide speed (79 KIAS), landing-site assessment, and execution are the only tools you have. The return to the airport is the best option if altitude and distance permit. If not, commit to the best available field and execute a controlled landing with the gear down and flaps for the slowest possible touchdown speed. Impact energy rises with the square of touchdown speed — the slowest possible speed matters most.
Key lesson — Total engine failure in the PA-28R can occur suddenly and without warning. At 500 ft AGL on initial climb, the decision window is 60–90 seconds. Establish 79 KIAS best glide immediately. If the airport is within glide range (roughly 0.5 nm at 500 ft AGL), turn back and land on the runway — it is the safest option. If not, commit to the best available open field, lower the gear below Vle 129 KIAS, add flaps for the slowest possible touchdown speed, and execute a controlled landing. Off Runway 19's climb-out at KZPH, the off-field environment is marginal (open developed, evergreen forest, low-density development); off Runway 01, it is good (pasture/hay, open developed). Know the off-field environment before you depart.
Debrief — teaching points
Best glide speed in the PA-28R is 79 KIAS — establish it immediately on engine failure.
In a total engine failure, the first action is to establish best glide speed (79 KIAS at gross weight). This speed maximizes glide distance and gives you the most time and distance to manage the emergency. At 500 ft AGL, you have roughly 90 seconds of glide time at best glide speed. Every second counts. Do not waste time troubleshooting (prop cycling, fuel selector switching) before establishing best glide. Establish best glide first, then troubleshoot if time permits.
The return to the airport is the best option if altitude and distance permit.
At 500 ft AGL on initial climb from KZPH, the airport is roughly 0.5 nm behind you. A 180° turn back to Runway 01 (the reciprocal of Runway 19) will consume roughly 250–300 ft of altitude. You will arrive at pattern altitude or slightly below. This is workable. The runway is 5,072 ft long and clear of obstacles. A forced landing on the runway is the best possible outcome. If the airport is within glide range, turn back and land on the runway. Do not commit to an off-field landing if the airport is reachable.
Gear DOWN in a forced landing — it is designed to absorb impact energy.
In a forced landing, lower the gear at or below Vle 129 KIAS. The landing gear is designed to absorb impact energy. A gear-up landing will result in significant airframe damage (fuselage and wing damage as the airplane slides on its belly). A gear-down landing will result in gear collapse and localized damage, but the gear absorbs the impact energy and reduces the severity of the accident. Lower the gear and accept the gear collapse as the price of a survivable landing.
Flaps for the slowest possible touchdown speed — impact energy rises with the square of speed.
In a forced landing, add flaps gradually to reduce touchdown speed. Full flaps (40°) at Vfe 103 KIAS will reduce your approach speed to roughly 75 KIAS. The slowest possible touchdown speed minimizes impact energy. Impact energy rises with the square of touchdown speed — a 10 KIAS reduction in touchdown speed has a significant effect on survivability. Add flaps as the landing site is made, but do not add them so early that you lose glide distance. The trade-off is between glide distance and touchdown speed; manage it carefully.
Know the off-field environment off each runway end before you depart.
At KZPH, the off-field environment off Runway 19's climb-out (heading 180°) is marginal — mostly open developed (parks/large lots), evergreen forest, and low-density development. Off Runway 01's climb-out (heading 360°), the environment is good — mostly pasture/hay, open developed areas, and evergreen forest. If you depart Runway 19 and lose the engine on initial climb, you are committed to a marginal off-field landing. If you depart Runway 01, you have a good off-field environment. Consider the off-field environment when choosing your departure runway. In an emergency, this knowledge will guide your landing-site decision.
Total engine failure in the PA-28R can occur suddenly and without warning.
The NTSB accidents cited in this scenario show that the Lycoming IO-360 can experience total power loss due to connecting rod bearing delamination, cylinder attach stud fatigue, oil-system failure, and other mechanical issues that may not be apparent in preflight inspection. The engine can fail with no warning — no rough running, no power loss warning, just sudden silence. This is not a failure of preflight technique; it is a mechanical reality. Your only defense is immediate recognition, best-glide speed, and rapid landing-site assessment. Preflight inspection is important, but it cannot prevent all mechanical failures.
Built from the real accident record
Scenario built from NTSB WPR12FA058 (2011 PA-28R-200 total engine loss, undetermined cause), ERA10FA074 (2009 PA-28R-200 oil-system failure / connecting rod bearing), NYC08FA053 (2007 PA-28R-200 cylinder separation), CEN25LA288 (2025 PA-28RT-201T base-to-final engine failure), ERA22LA067 (2021 PA-28R-200 initial-climb power loss), CEN20LA016 (2019 PA-28R-200 cruise power loss), and CEN26FA049 (2025 PA-28R-201 fuel starvation after tank switch). Real events occurred at other airports — NOT at Zephyrhills Municipal. Localized to KZPH to make off-field landing options real and consequential.
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 — Engine Starting · PA.VIII.A — Slow Flight · PA.VIII.C — Power-Off Stalls
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 KZPH