Total Power Loss on Climb — Brooksville
Engine failure at 500 ft AGL over good off-field terrain. The decision to return or press forward determines survival.
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, climbing out on a 090° heading. Elevation 76 ft MSL. You are a commercial pilot with 800 hours total, 120 hours in the Piper Arrow. This is a personal flight to Jacksonville, FL — a 1.5-hour trip, VFR, no flight plan filed.
It is a clear, calm morning: OAT 18°C, altimeter 30.01, winds calm. Visibility unlimited. The off-field environment off Runway 09's climb-out (heading 090°) is open developed land — parks, large lots, pasture, and hay fields. Good forced-landing terrain. You are not over water, mountains, or dense forest.
You are at 500 ft AGL, climbing at 90 KIAS (Vy, gear up, prop in climb), heading 090°, when the engine suddenly loses all power. The propeller is no longer turning. The tachometer reads zero. You have roughly 3–4 minutes of glide time at best glide speed (79 KIAS) before you touch down. The tower is aware of your departure; you are in Class D airspace (KBKV tower is open, 0700–2200 local).
Aircraft: Piper PA-28R-200 Arrow, solo, full fuel (48 gallons usable), within limits. Lycoming IO-360, fuel-injected (no carburetor heat). Constant-speed prop, retractable gear. Fuel selector on RIGHT tank. You completed a full preflight and run-up; nothing was written up. The airplane was airworthy at departure.
Pilot: You — a commercial pilot, current, 800 hours total, 120 hours in the Arrow. You have never experienced a total engine failure in this airplane. You have practiced forced landings in the simulator but never in the real airplane. Your decision in the next 30 seconds will determine whether you return to KBKV or commit to a field landing ahead.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 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 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 near Coupeville, Washington. The pilot attempted a forced landing 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.
NTSB ERA10FA074 (2009, FATAL): A Piper PA-28R-200 experienced an oil problem and total engine loss during climb after takeoff near Wappinger, New York. The pilot made a forced landing in trees. 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.
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.
NTSB ERA22LA067 (2021): A Piper PA-28R-200 on a personal flight experienced total loss of engine power during initial climb at 500 ft 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.
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 real accidents cited above occurred at other airports and in other aircraft — NOT at Brooksville–Tampa Bay Regional Airport (KBKV). KBKV has its own accident history dominated by hard landings (26.9%), forced landings (11.5%), and runway excursions (11.5%), but these specific NTSB cases happened elsewhere. The scenario is localized to KBKV 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 Piper Arrow can happen for reasons that are not always detectable in a preflight inspection — bearing delamination, cylinder fatigue, undetermined mechanical failure. The decision in the first 30 seconds — return to the airport or commit to a field landing — is the critical moment. At 500 ft AGL on climb-out, the return is marginal but possible if the airport is close and the wind is calm. If the airport is far or the wind is strong, a field landing in good terrain is the safer choice. The off-field environment off Runway 09 at KBKV — open developed land and pasture — is good forced-landing terrain. Know your off-field options before you depart.
Key lesson — Total engine failure in the Piper Arrow can occur without warning, even after a full preflight and run-up. At 500 ft AGL on climb-out, you have 3–4 minutes of glide time at best glide speed (79 KIAS). The decision to return to the departure airport or commit to a field landing must be made in the first 30 seconds. Return is marginal at 500 ft AGL — it depends on distance, wind, and terrain. If the airport is far or the wind is strong, a field landing in good terrain is safer. Off Runway 09 at KBKV, the terrain is open developed land and pasture — good forced-landing options exist. In a forced landing, lower the gear (Vle 129 KIAS — safe at 79 KIAS) and add full flaps (Vfe 103 KIAS — safe at 79 KIAS) for the slowest possible touchdown speed. Gear-up landings in the Arrow are risky — the retractable gear is designed to absorb impact energy.
Debrief — teaching points
Total engine failure in the Piper Arrow can happen without warning.
The NTSB cases cited (WPR12FA058, ERA10FA074, NYC08FA053, ERA22LA067, CEN20LA016) show total engine failures in the PA-28R that occurred after full preflight and run-up checks. The causes ranged from bearing delamination (ERA10FA074) to cylinder fatigue (NYC08FA053) to undetermined mechanical failure (WPR12FA058, CEN20LA016). These are not failures that a preflight inspection would catch. The lesson is not 'do a better preflight' — it is 'know your off-field options and your decision window before you depart.' At 500 ft AGL on climb-out, you have 3–4 minutes of glide time at best glide speed (79 KIAS). That is your decision window.
At 500 ft AGL on climb-out, the decision to return to the airport is marginal.
The return-to-airport decision at 500 ft AGL depends on three factors: (1) distance to the airport, (2) wind direction and strength, and (3) terrain between you and the runway. In this scenario, KBKV is 0.8 nm behind you, the wind is calm, and the terrain is open developed land — the return is feasible. But if the airport were 2 nm away, or the wind were a 15-knot headwind, or the terrain were dense forest, the return would be marginal or impossible. Know your distance to the airport and the wind direction before you depart. If the return is marginal, commit to a field landing in good terrain instead of stretching the glide to the runway.
Off Runway 09 at KBKV, the off-field environment is open developed land and pasture — good forced-landing terrain.
The USGS NLCD ground cover off Runway 09's climb-out (heading 090°) is mostly open developed land (parks, large lots), pasture, and hay fields. This is survivable forced-landing terrain. There are no mountains, no dense forest, no water. A forced landing in this terrain, with the gear down and full flaps, is a reasonable outcome. Know the off-field environment off each runway end at your home airport. If the terrain is poor (dense forest, mountains, water), the return-to-airport decision becomes more defensible even at low altitude.
In a forced landing, lower the gear and add full flaps for the slowest possible touchdown speed.
The Piper Arrow's landing gear is designed to absorb impact energy. Vle (max gear-extended speed) is 129 KIAS; at 79 KIAS best glide, gear extension is safe. Full flaps (Vfe 103 KIAS) are also safe at 79 KIAS. The slowest possible touchdown speed minimizes impact energy — impact energy rises with the square of speed. A touchdown at 55 KIAS (Vs0, stall speed landing) has roughly 1/3 the impact energy of a touchdown at 90 KIAS. The NTSB data shows gear-down landings in complex aircraft have significantly better survival rates than gear-up landings in the same terrain. The decision to retract the gear in a forced landing is almost always wrong.
Declare an emergency on the tower frequency immediately.
If you experience a total engine failure at low altitude, declare an emergency on the tower frequency immediately: 'KBKV Tower, [N-number], total engine failure, returning for emergency landing Runway 27' (or 'declaring emergency, forced landing in field'). The tower will clear the airspace, track your descent, and coordinate emergency services. If you do not communicate, the tower will not know where you are or what happened. Communication is the first step in any emergency.
Best glide speed in the PA-28R is 79 KIAS — establish it immediately and hold it.
Best glide speed maximizes glide distance and gives you the most time to make decisions. In the PA-28R, best glide is 79 KIAS at gross weight. Establish it immediately when the engine fails, and hold it throughout the descent. Do not climb (which reduces glide distance), do not descend too steeply (which also reduces glide distance), and do not slow below 79 KIAS (which reduces glide distance). Fly 79 KIAS until you are committed to a landing.
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 return), ERA22LA067 (2021 PA-28R total loss at 500 ft AGL), CEN20LA016 (2019 PA-28R undetermined power loss), and CEN26FA049 (2025 PA-28R fuel starvation / forced landing). Anonymized and localized to KBKV.
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.VII.A — Systems and Equipment Malfunctions
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 KBKV