Engine Failure on Initial Climb — Runway 22 Departure
Total power loss at 400 ft AGL over dense development. No suitable forced-landing site ahead. Decision window: seconds.
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 22, initial climb on a 220° heading. Field elevation 11 ft MSL. The runway is 6,000 ft of asphalt; Runway 18/36 (9,730 ft concrete) is available but Runway 22 is assigned and active.
It is a clear, calm VFR morning: OAT 18°C, altimeter 29.98, winds light and variable. Visibility 10 SM. The weather is benign. Off Runway 22's departure end (heading 220°), the off-field environment is dense development — residential neighborhoods, medium-density commercial, low-density development. There are no open fields, no parks large enough for a safe landing, no water. The terrain is built-up.
You are climbing through 400 ft AGL, airspeed 90 KIAS (Vy, best rate of climb), gear retracting, prop in cruise, heading 220°, when the engine loses all power. The tachometer drops to zero. Manifold pressure collapses. The propeller is no longer turning. You have roughly 30 seconds of useful decision time before altitude becomes critical.
Aircraft: Piper PA-28R-201, solo, full fuel, within limits. Lycoming IO-360, fuel-injected, constant-speed prop, retractable gear. The airplane was dispatched on a routine flight. Nothing was written up; the airplane was airworthy at departure. However, the airplane recently returned from avionics maintenance — a new glass panel was installed three days ago.
Pilot: you — a Commercial pilot, current, roughly 800 hours total. You have 120 hours in the PA-28R. You performed a thorough preflight, including checking the engine instruments, oil pressure, and fuel quantity. You did not notice anything amiss. You are not familiar with this particular airplane's recent maintenance history in detail.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 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 engine failure on initial climb 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 CEN22FA419 (2022, FATAL): A Piper PA-28R-201 on a personal flight from Myrtle Beach, South Carolina experienced total engine failure during initial climb after departure. The probable cause was a missing vacuum pump drive pad gasket installed during avionics maintenance, which caused oil exhaustion and catastrophic engine failure. The mechanic's failure to install the required gasket in accordance with the maintenance manual, and the Director of Maintenance's failure to verify the installation before returning the airplane to service, were the direct causes. The pilot did not survive.
NTSB ERA22FA261 (2022, FATAL): A Piper PA-28RT on a personal flight lost engine power due to oil starvation caused by high-cycle fatigue failure of an oil pressure sensor line that was improperly installed with a rigid line instead of flexible hose. Maintenance personnel failed to follow the avionics installation guidance. The pilot's failure to perform an adequate preflight inspection was a contributing factor. The outcome was fatal.
NTSB ERA13LA111 (2013, FATAL): A Piper PA-28R on an IFR flight experienced total loss of engine power due to fuel exhaustion after the pilot attempted multiple missed approaches at three different airports in low IMC. The pilot delayed declaring a fuel-related emergency. The outcome was fatal.
NTSB WPR12FA058 (2011, FATAL): A Piper PA-28R-200 on a personal flight experienced total loss of engine power during cruise. The probable cause could not be determined because postaccident examination did not reveal evidence of mechanical malfunction. The pilot attempted a forced landing near Coupeville, Washington, but impacted terrain below a ridge line. The outcome was fatal.
Regional precedents (SEA92LA095, MIA91LA128, CHI83LA094, CHI92DER01) show a consistent pattern: when engine failure occurs at low altitude over congested terrain, the pilots who survived were those who committed immediately to the best available landing site (street, parking lot, field) and executed a controlled touchdown. The pilots who attempted to stretch the glide, turn back to the runway, or maneuver around obstacles did not survive.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. However, KPIE's own accident corpus shows that LOSS_OF_CONTROL_INFLIGHT (21.2%), LOSS_OF_CONTROL_GROUND (15.2%), and STALL_SPIN (12.1%) are the dominant patterns at this field. The scenario is localized to KPIE to make the off-field environment real and consequential: Runway 22's departure end is dense development with no suitable forced-landing site.
The consistent thread across all these events: total engine failure on initial climb is survivable if the pilot establishes best glide speed immediately and commits to the best available landing site. The failure is always a delay — either in establishing glide speed, or in committing to a landing site, or in attempting to turn back to the runway or stretch the glide at marginal altitude.
Key lesson — In a PA-28R, total engine failure on initial climb over congested development is survivable if you establish 79 KIAS best glide immediately and commit to the best available landing site (street, parking lot, field). Do not attempt to turn back to the runway at 400 ft AGL — the altitude is too low and the risk of a stall/spin is too high. Do not stretch the glide or attempt to land on a rooftop or between buildings. Commit to the largest, clearest landing surface ahead. The decision window is measured in seconds — not minutes.
Debrief — teaching points
Total engine failure in a PA-28R is catastrophic — the propeller stops turning and manifold pressure collapses.
Unlike a partial power loss, total engine failure in the PA-28R means zero RPM and zero manifold pressure. The Lycoming IO-360 is fuel-injected; there is no carb heat or carb ice to troubleshoot. The engine is not running. The propeller is not turning. The only action is to establish best glide speed and find a landing site. Restart attempts (cycling the fuel selector, checking the mixture, applying throttle) are futile if the engine has truly quit. Spend no more than 10–15 seconds on diagnostics; then commit to the landing.
Best glide speed for the PA-28R is 79 KIAS — establish it immediately and hold it.
At 79 KIAS, the PA-28R achieves the maximum glide distance and the maximum time aloft. This is the speed to establish immediately after a total power loss. Do not attempt to climb, do not attempt to stretch the glide, do not attempt to turn back to the runway at a different airspeed. Establish 79 KIAS and maintain it. Every second counts; the glide distance is measured in hundreds of feet, not miles.
At 400 ft AGL on initial climb, turning back to the runway is extremely risky — the altitude is marginal and the turn can lead to a stall or spiral dive.
The 'impossible turn' is a real phenomenon. At 400 ft AGL with zero power, a 180° turn back to the runway requires altitude and airspeed that may not be available. A steep bank at low airspeed in a descent can lead to a stall. At 200 ft AGL, a stall means a spin or spiral dive — there is no altitude to recover. The safer choice is to commit to the best available landing site ahead, even if it is not the runway. A controlled landing on a street or parking lot is better than an uncontrolled impact in a spin.
Off Runway 22 at KPIE, the departure end is dense development — residential and commercial — with no suitable forced-landing site.
The USGS NLCD ground cover off Runway 22's departure end (heading 220°) is dense development, medium development, and low-density development. There are no open fields, no parks large enough for a safe landing, no water. A forced landing in this environment requires committing to a street, parking lot, or rooftop — not attempting to maneuver around obstacles or stretch the glide. Know the off-field environment before you depart. If the off-field environment is unsuitable (as it is off Runway 22), consider using Runway 18 or 36 instead, which have better off-field options.
Post-maintenance engine failures are a known risk — inadequate preflight inspection and maintenance errors are the leading causes.
NTSB CEN22FA419 and ERA22FA261 both involved engine failures caused by maintenance errors (missing gasket, improper sensor line installation) that were not caught by the pilot's preflight inspection. The pilot's preflight is the last line of defense. After any maintenance, especially avionics work that involves the engine compartment, perform a thorough preflight: check oil pressure, manifold pressure, and engine instruments on the ground. On the first flight after maintenance, stay close to the airport and be prepared for an engine failure. If the airplane has recently been in the shop, consider using the longest runway available and departing over the most suitable off-field terrain.
Built from the real accident record
Scenario built from NTSB CEN22FA419 (2022 PA-28R-201 engine failure post-maintenance, oil starvation), ERA22FA261 (2022 PA-28RT oil starvation from improper sensor line installation), ERA13LA111 (2013 PA-28R fuel exhaustion after missed approaches), WPR12FA058 (2011 PA-28R-200 unexplained total power loss), and regional precedents SEA92LA095, MIA91LA128, CHI83LA094, CHI92DER01 (forced landings in congested terrain). Anonymized and localized to KPIE.
NTSB reports: CEN22FA419 · ERA22FA261 · ERA13LA111 · WPR12FA058 · SEA92LA095 · MIA91LA128 · CHI83LA094 · 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 · PA.V.C — Engine Failure During Takeoff
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 Arrow scenarios · More scenarios at KPIE