Engine Failure on Initial Climb — Lakeland
Total power loss at 500 ft AGL over central Florida — the decision window is seconds, and off-field options vary sharply by runway
The scenario
Departing Lakeland Linder International Airport (KLAL), Lakeland, FL — Runway 10, climbing out on a 090° heading. Elevation 142 ft MSL. It is a clear, calm morning in central Florida: OAT 22°C, winds calm, altimeter 30.01. Visibility 10 SM. A routine personal flight to Jacksonville, FL, 140 nm north.
You are a Commercial pilot with roughly 800 hours total, 200 hours in the Piper Arrow. You completed a thorough preflight: oil quantity and color normal, fuel quantity confirmed (full tanks, 36 gallons usable), engine instruments green during run-up. The airplane is within weight and balance limits. Nothing was written up on the maintenance log.
You are cleared for takeoff on Runway 10. Rotation at 75 KIAS, positive rate, gear up. You are climbing at 90 KIAS (Vy, best rate of climb) through 500 ft AGL when the engine suddenly loses all power. The propeller is still turning (windmilling), but there is no thrust. The engine instruments show zero manifold pressure and zero RPM. You have roughly 30 seconds of useful altitude to make a decision.
Runway 10's climb-out environment (heading 090°) is marginal: low-density development, open developed areas (parks/large lots), and dense development to the east. Runway 28's climb-out (heading 270°) is poor: medium development, evergreen forest, and low-density development. Runway 05's climb-out (heading 045°) is good: low-density development, wooded wetland, and open developed areas. Runway 23's climb-out (heading 225°) is good: medium development, pasture/hay, and open developed areas.
KLAL is Class D airspace, towered 24 hours. The tower is aware of your departure. You are in radio contact. The nearest suitable alternate landing area is not obvious — you are surrounded by development and forest. Your decision in the next 30 seconds will determine whether this is a survivable forced landing or a catastrophic impact.
- {'label': 'Field', 'value': 'KLAL · Lakeland Linder'}
- {'label': 'Runways', 'value': '5/23 · 10/28'}
- {'label': 'Elevation', 'value': '142 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about engine failure on initial climb in a complex airplane like the Piper Arrow? (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 — post-accident examination revealed no mechanical malfunctions or failures that would have precluded normal operation. The pilot's failure to choose a suitable landing area contributed to the fatal outcome.
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's decision to land in trees, rather than seeking an open area, 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 accident resulted from fatigue fracture of the number 2 cylinder attach studs and subsequent cylinder separation, causing total loss of engine power. The pilot's failure to choose a suitable landing area contributed to the fatal outcome.
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 survived because he chose to return to the airport and land on available grass, rather than committing to an off-field area.
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's decision to return to the airport, even from base-to-final, was the correct call.
The consistent thread across all these events: total engine loss in a Piper Arrow is rare but catastrophic. The cause is often undetermined (mechanical failure, oil starvation, or bearing failure). The survival outcome depends entirely on the pilot's decision-making in the first 30 seconds: establish best glide (79 KIAS), declare emergency, and commit to the best available landing area. Pilots who return to the runway or land in open areas survive. Pilots who land in trees or fail to choose a suitable area do not.
At KLAL, the runway is the best option if you have the altitude and glide distance to make it. Off-field options vary sharply by runway: Runway 10's departure (090°) is marginal; Runway 28's departure (270°) is poor. Runway 05's departure (045°) and Runway 23's departure (225°) are good. The real accidents cited above occurred at other airports — NOT at KLAL. However, KLAL's dominant accident pattern (LOSS_OF_CONTROL_INFLIGHT 23.7%, LOSS_OF_CONTROL_GROUND 19.4%, FORCED_LANDING 17.2%) reflects the challenge of complex-airplane operations at a busy, towered field.
Key lesson — Total engine loss at 500 ft AGL in a Piper Arrow leaves roughly 30 seconds and 2 nm of glide distance. Establish best glide (79 KIAS) immediately, declare emergency, and commit to the best available landing area — the runway if you can make it, or an open field if you cannot. The Piper Arrow's retractable gear is an asset in a forced landing: lower the gear and flaps to reduce touchdown speed and landing distance. Gear-down landings are survivable; gear-up landings are survivable but damage the airplane. Delayed decision-making, poor off-field choices, or landing in trees are fatal. The first 30 seconds determine the outcome.
Debrief — teaching points
Total engine loss at low altitude is a forced landing — not an engine-restart scenario.
In the Piper Arrow, total loss of power (zero RPM, zero manifold pressure) at 500 ft AGL is a forced landing. Troubleshooting — cycling the prop, switching fuel tanks, checking magnetos — takes time you do not have. The priority is to establish best glide (79 KIAS), declare emergency, and commit to a landing area. Troubleshooting is for cruise altitude; at 500 ft AGL, the airplane comes first.
Best glide in the PA-28R is 79 KIAS — establish it immediately after power loss.
Best glide speed for the PA-28R is 79 KIAS at gross weight. This speed maximizes glide distance and gives you the most time and distance to evaluate landing options. At 500 ft AGL with 79 KIAS best glide, you have roughly 2 nm of glide distance and 30 seconds of altitude. Any deviation from best glide — climbing, descending too steeply, or flying too fast — reduces your options.
In a forced landing, lower the gear and flaps — they reduce touchdown speed and landing distance.
The Piper Arrow's retractable gear and constant-speed prop are assets in a forced landing. Lower the gear (Vle is 129 KIAS; you will be at 79 KIAS, well within limits) and add flaps gradually as you approach the landing area. Flaps reduce stall speed to 55 KIAS (Vs0, landing configuration), minimizing impact energy. A gear-down landing is the correct configuration. Gear-up landings are survivable but damage the airplane and increase the risk of nose-over.
The runway is the best option if you have the altitude and glide distance to make it.
At KLAL, the runway is 5,000 ft (Runway 05/23) or 8,500 ft (Runway 10/28) — a sure thing if you can make it. A 180° turn back to the runway at 500 ft AGL is marginal but possible with a shallow bank (10–15°) and best glide (79 KIAS). If you have the altitude and glide distance, return to the runway. Off-field landings are a last resort.
Off-field landing areas vary sharply by runway departure heading — know them before you depart.
At KLAL, Runway 10's departure (090°) is marginal: low-density development, parks, and dense development. Runway 28's departure (270°) is poor: medium development, evergreen forest, and low-density development. Runway 05's departure (045°) and Runway 23's departure (225°) are good: low-density development, wooded wetland, pasture/hay, and open developed areas. If you depart Runway 10 and lose power, straight ahead (090°) is marginal; turning back to the runway is the better choice. Know the off-field environment before you line up.
Declare emergency immediately — the tower will clear all traffic and give you priority.
At KLAL, the tower is active 24 hours. When you lose power, key the mic: 'KLAL Tower, [N-number], engine failure, declaring emergency, descending to landing area.' The tower will clear all traffic and give you priority for landing or emergency services. Do not hesitate to declare — that is what the emergency system is for.
Built from the real accident record
Scenario built from NTSB WPR12FA058 (2011 PA-28R total engine loss, undetermined cause), ERA10FA074 (2009 PA-28R oil-system failure / connecting rod bearing), NYC08FA053 (2007 PA-28R cylinder separation), CEN25LA288 (2025 PA-28RT engine failure on base turn), ERA22LA067 (2021 PA-28R engine loss at 500 ft AGL), and CEN20LA016 (2019 PA-28R total power loss, undetermined). Localized to KLAL with runway-specific off-field environment.
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.III.A — Preflight Inspection · PA.V.C — 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 KLAL