Engine Failure on Climb — Tampa Executive
Total power loss in a complex aircraft: gear management, landing-site selection, and the decision clock at 500 feet AGL
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, Florida — Runway 05, climbing out on a 042° heading. Elevation 22 ft MSL. Clear skies, light winds from 080° at 4 knots, temperature 26°C, altimeter 30.01. Visibility 10+ SM. A textbook VFR morning.
You are a commercial pilot with 800 hours total time, 120 hours in the Piper Arrow. You are current and proficient. The Arrow is a complex aircraft — retractable gear, constant-speed prop, fuel-injected Lycoming IO-360, fuel selector LEFT/RIGHT. You have flown this airplane regularly and know its systems.
You are climbing through 500 feet AGL, gear retracting, prop in cruise, heading 042°, at 90 KIAS (Vy, best rate of climb). The engine is running smoothly. The preflight was normal; the engine started and ran without issue. Oil temperature and pressure are in the green. You are alone in the airplane, within limits, full fuel.
At 500 feet AGL, the engine suddenly loses all power. No cough, no sputter — total loss. The prop is still turning (windmilling), but there is no engine power. The airplane is still climbing slightly, but the climb is slowing. You have roughly 30 seconds before you are descending and must make a landing decision.
Off Runway 05's departure end (heading 042°), the off-field environment is GOOD: mostly wooded wetland, medium development, pasture/hay. You have options. Off Runway 36's departure end (heading 360°), the off-field environment is DITCHING — open water and medium development. Off Runway 18's departure end (heading 180°), the environment is MARGINAL — low-density development, wooded wetland, open developed areas (parks/large lots). The airport is non-towered (CTAF). You are in Class G airspace below 3,000 ft MSL; above that, you are in Tampa Class B (3,000–10,000 MSL).
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we enter the decision tree — what do you know about engine failure in the Piper Arrow and forced-landing priorities? (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 revealed no mechanical failures that would have precluded normal operation. The pilot's failure to select 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 accident was attributed to 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 choice to land in trees rather than a clear field contributed to the fatal outcome.
NTSB WPR09FA015 (2008, FATAL): A Piper PA-28R-201T experienced progressive engine power loss at 14,500 feet. The pilot attempted to return to Minden, Nevada, but made a forced landing in trees near Markleeville, California. The accident resulted from loss of engine power for undetermined reasons. The pilot's failure to choose a suitable landing area — trees instead of open terrain — was a contributing factor to the fatal outcome.
NTSB NYC08FA053 (2007, FATAL): A Piper PA-28R-200 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's inability to reach a suitable landing area at low altitude was a contributing factor.
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 rather than commit to a forward field was marginal at low altitude.
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 accident resulted from total loss of engine power for reasons that could not be determined. The pilot's attempt to return to the airport at very low altitude was marginal.
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 total loss of engine power for undetermined reasons; post-recovery examination found no mechanical anomalies. The pilot's landing-site selection and execution were critical to the survivable outcome.
NTSB CEN26FA049 (2025): A Piper PA-28R-201 on a personal IFR flight diverted from the destination due to weather and fuel concerns. The pilot experienced fuel starvation after switching tanks and declared an emergency, attempting a forced landing near Pittsfield, Illinois. The accident illustrates the fuel-selector trap in the Arrow: LEFT/RIGHT selection is critical, and fuel starvation after tank switching is a real failure mode.
The real accidents cited above occurred at other airports and in other regions — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (dominant patterns: LOSS_OF_CONTROL_GROUND 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%), but these specific NTSB cases happened elsewhere. The scenario is localized to KVDF to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: total engine loss in the Piper Arrow is rare but catastrophic. The causes range from undetermined (the majority) to mechanical failures (bearing delamination, cylinder separation) to fuel starvation (tank-switching error). The survival outcomes depend almost entirely on landing-site selection and gear configuration. Gear-up landings in open fields have significantly higher survival rates than gear-down landings or landings in trees/obstacles. The decision window at 500 feet AGL is measured in seconds — not minutes.
Key lesson — In the Piper Arrow, total engine loss is survivable if you make the right decisions in the first 30 seconds: (1) establish 79 KIAS best glide immediately, (2) commit to a landing site — either the airport if reachable, or a forward field if not, (3) leave the gear UP for a field landing (gear-up reduces impact forces and improves survivability), and (4) select the smoothest, most open landing surface available. Off Runway 05 at KVDF, the GOOD terrain (wooded wetland, pasture, medium development) offers survivable forced-landing options. Off Runway 36, the DITCHING environment (open water) offers none. Landing-site selection is the single biggest factor in survival.
Debrief — teaching points
Total engine loss in the Piper Arrow is rare but survivable with correct decision-making.
The NTSB accident corpus shows that total engine loss in the PA-28R can result from undetermined causes (the majority), mechanical failures (bearing delamination, cylinder separation, oil starvation), or fuel starvation (tank-switching error). The engine may quit without warning. The survival outcome depends almost entirely on your actions in the first 30 seconds: establish best glide, commit to a landing site, and configure the airplane for the best possible impact. The NTSB data shows that pilots who make these decisions quickly and correctly survive; those who delay or make poor choices do not.
Best glide speed in the PA-28R is 79 KIAS — establish it immediately and hold it.
79 KIAS is the speed that maximizes glide distance and gives you the most time and distance to manage the emergency. At 500 feet AGL, establishing 79 KIAS immediately gives you 2–3 minutes of glide time and roughly 1–2 nm of glide distance. This is your decision window. Do not climb, do not descend steeply, do not speed up. Fly 79 KIAS.
Gear-up landing in a field is more survivable than gear-down landing.
In a forced landing in a field, the gear-up configuration reduces impact forces and improves survivability. Gear-down landing in a field can cause the nose gear to dig in, pitching the airplane forward and potentially causing a flip. The NTSB data consistently shows that gear-up landings have better survival outcomes. Gear-down landing on a runway is acceptable (the runway is long and smooth), but gear-up in a field is the correct choice.
Landing-site selection is the single biggest factor in survival.
A smooth, open field at 79 KIAS is far more survivable than a fragmented area with obstacles, trees, or water. At KVDF, the off-field environment off Runway 05's departure end is GOOD — wooded wetland, pasture, medium development. The off-field environment off Runway 36 is DITCHING — open water. Off Runway 18, it is MARGINAL — low-density development, wooded wetland. Know the off-field environment before you depart. In a forced landing, commit to the best available landing site and fly the approach at 79 KIAS with the gear up.
The return-to-airport decision at low altitude is marginal — commit early or commit to a forward field.
At 500 feet AGL, the airport is reachable if you commit immediately. A 0.5 nm return at 79 KIAS best glide is feasible — you have 2–3 minutes of glide time. But if you delay the decision, the airport becomes unreachable and you are forced to land forward. The NTSB data shows that pilots who attempt a marginal return at very low altitude (below 300 feet AGL) often fail to reach the airport and impact terrain short of the runway. Commit to the return early, or commit to a forward field. Do not waffle.
The Piper Arrow's fuel selector is LEFT/RIGHT — fuel starvation from tank-switching error is a real failure mode.
The Arrow's fuel system requires active management: you must switch tanks to maintain balance and avoid fuel starvation. Forgetting to switch tanks, or switching to an empty tank, can cause total fuel starvation and engine loss. The NTSB case CEN26FA049 illustrates this: the pilot switched tanks during an emergency and selected an empty tank, causing fuel starvation. Know your fuel system. Brief yourself on tank switching before flight. In an emergency, verify the fuel selector is on a full tank before troubleshooting other systems.
Preflight inspection of the engine oil system is critical — oil starvation can cause catastrophic engine failure.
The NTSB case ERA10FA074 shows that inadequate maintenance inspection of the engine oil system contributed to a bearing delamination and total engine loss. The Lycoming IO-360 is a robust engine, but oil starvation can cause bearing failure and catastrophic power loss. Preflight the oil level, color, and consistency. If the oil is dark, gritty, or low, do not fly. In-flight, monitor oil temperature and pressure continuously. An abnormal oil temperature or pressure reading is a warning sign of potential oil system problems.
Built from the real accident record
Scenario inspired by NTSB WPR12FA058 (2011 PA-28R total engine failure, undetermined cause), ERA10FA074 (2009 PA-28R oil-related engine loss), WPR09FA015 (2008 PA-28R-201T power loss and unsuitable landing area), NYC08FA053 (2007 PA-28R cylinder separation), CEN25LA288 (2025 PA-28RT engine failure on base-to-final), ERA22LA067 (2021 PA-28R total power loss at 500 ft AGL), CEN20LA016 (2019 PA-28R undetermined power loss), and CEN26FA049 (2025 PA-28R fuel starvation after tank switch). Localized to Tampa Executive Airport (KVDF), Florida. Real accidents occurred at other airports and in other regions — NOT at KVDF.
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.II.C — Takeoff and Climb · PA.III.A — Stall / Spin Awareness
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 KVDF