Total Power Loss Over the Gulf
Engine failure on climb-out from Venice Municipal — forced landing site selection in seconds, with water and developed terrain as the only options
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, climbing out on a 225° heading toward a personal flight to Sarasota. Field elevation 18 ft MSL. You are a commercial pilot with roughly 800 hours total time, current and proficient in the Piper Arrow. The airplane is a PA-28R-200, fuel-injected Lycoming IO-360, retractable gear, constant-speed prop.
It is a clear, calm Florida morning: OAT 22°C, light winds from the northeast, altimeter 30.01, visibility 10+ SM. Runway 22 departure environment: open water (Gulf of Mexico) off the departure end (southwest). Runway 04 departure environment: developed residential and commercial area to the northeast. You are not unfamiliar with KVNC — you have operated here before — but today's departure is routine and you are heads-down on the climb.
You are 500 ft AGL, climbing at 90 KIAS (Vy, gear up, prop in cruise), heading 225°, when the engine quits. Not rough — not sputtering — quits. RPM drops to zero in seconds. The propeller is still in cruise position. You have no engine instruments showing a problem: oil pressure was green at takeoff, fuel selector was on RIGHT (you switched tanks at 200 ft AGL as part of your climb checklist), mixture is at cruise lean, alternator is on.
Aircraft: Piper PA-28R-200, solo, 45 gallons usable fuel (full tanks), within CG and weight limits. The airplane was airworthy at departure; the last 100-hour inspection was 8 hours ago. Nothing was written up.
Pilot: you — a Commercial pilot, current, 800 hours total. You have flown the Arrow for 200 hours. You completed a thorough preflight, including oil quantity and condition. The engine started normally, ran smoothly through the run-up, and climbed without issue until this moment. You did not notice any engine instruments trending toward a problem.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 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 total engine failure in the Piper Arrow and forced landing site selection? (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 — no mechanical anomalies were found post-accident. The pilot had only seconds to choose a landing site and chose terrain below a ridge, which was unsuitable.
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 pilot had limited altitude and chose trees as the landing site.
NTSB WPR09FA015 (2008, FATAL): A Piper PA-28R-201T on a cross-country flight 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 probable cause was loss of engine power for undetermined reasons. A contributing factor was the pilot's failure to choose a suitable landing area — the pilot had altitude and time but chose trees instead of open terrain.
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. The pilot had limited altitude and made a forced landing in trees.
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 chose a field landing over a ditching, but the field had obstacles (fence).
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 probable cause was total loss of engine power for reasons that could not be determined. The pilot had limited altitude and chose a grass area near the airport, but the landing site had obstacles.
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 had altitude and time to choose a suitable landing site.
NTSB CEN26FA049 (2025, FATAL): 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 probable cause was fuel starvation due to improper fuel management (switching tanks without confirming fuel quantity).
At Venice Municipal Airport (KVNC), the off-field environment is critical: Runway 22's departure end (southwest) is open water — the Gulf of Mexico. Runway 04's departure end (northeast) is developed residential and commercial area. An engine failure on the Runway 22 departure at low altitude leaves two options: (1) turn back to the runway (tight, low, but survivable if executed correctly), or (2) ditch in the Gulf (dramatic, but survivable if the ditching is controlled). Landing in developed terrain is not survivable. The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal. KVNC has its own accident history (LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%), but these specific NTSB cases happened elsewhere. The scenario is localized to KVNC 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 is often undetermined in cause — no mechanical anomalies are found post-accident. The pilot has seconds to choose a landing site. The difference between survival and fatality is the choice of landing site and the execution of the approach. Runway 22 (paved, 5,000 ft) is survivable. The Gulf (open water, controlled ditching) is survivable. Developed terrain, trees, and unsuitable fields are not.
Key lesson — Total engine failure in the Piper Arrow can happen with no warning and no mechanical cause you could have prevented. At 500 ft AGL on departure, you have 30–40 seconds to choose a landing site. The correct decision is to establish best glide (79 KIAS) immediately, assess the options (runway vs. water vs. terrain), and commit to the best available site. Off Runway 22 at KVNC, that means either turning back to the runway (tight but survivable) or ditching in the Gulf (dramatic but survivable). Landing in developed terrain is not an option. The execution of the approach and the ditching brief — if ditching is necessary — determines survival.
Debrief — teaching points
Total engine failure in the Piper Arrow is often undetermined in cause.
The NTSB cases WPR12FA058, CEN20LA016, and ERA22LA067 show that total engine failures in the PA-28R frequently occur with no mechanical anomalies found post-accident. The cause remains undetermined. This is not a failure of preflight or maintenance — it is the reality of complex systems. You cannot prevent every failure. What you can control is the landing site choice and the execution of the approach. Establish best glide (79 KIAS) immediately and assess your options.
Best glide speed is 79 KIAS — establish it immediately.
At 500 ft AGL with a dead engine, your first action is to lower the nose to 79 KIAS best glide. This maximizes your glide distance and gives you time to think and choose a landing site. Delaying the establishment of best glide — by troubleshooting, turning back without gliding, or climbing at Vy — costs altitude and reduces your options. 79 KIAS is the speed that keeps you alive longest.
Landing site selection at low altitude is a 30-second decision.
At 500 ft AGL and 79 KIAS best glide, you have roughly 30–40 seconds of glide time. The landing site must be chosen within that window. At KVNC Runway 22 departure, the options are: (1) turn back to Runway 22 (paved, 5,000 ft, behind you), (2) ditch in the Gulf (open water, ahead), or (3) land in developed terrain (not survivable). The turn back is tight but doable if you establish best glide immediately. The ditch is survivable if controlled. The developed terrain is not an option.
Retractable gear should be DOWN for a forced landing — it absorbs impact energy.
In a forced landing, lower the gear. The gear absorbs impact energy and slows the airplane. A gear-up landing is a last resort — if the gear fails to extend at low altitude, a belly landing is acceptable. But if the gear extends normally, leave it down. For a ditching, gear down is also correct — the gear provides flotation and stability on water.
Full flaps (40°) for slowest touchdown speed — impact energy rises with the square of speed.
In a forced landing or ditching, add full flaps (40°) to minimize touchdown speed. The slowest possible speed minimizes impact energy. At 75 KIAS (Vref) with full flaps, you are at the slowest safe approach speed. Do not sacrifice flaps to maintain a higher airspeed — the impact energy reduction is worth the slower approach.
A controlled ditching in open water is survivable — landing in trees is not.
The NTSB cases WPR09FA015, NYC08FA053, and ERA10FA074 show that pilots who choose trees or unsuitable terrain do not survive. The cases WPR12FA058 and ERA22LA067 show that pilots who choose open water or fields (when available) have a better outcome. At KVNC Runway 22 departure, if you cannot make the runway, ditch in the Gulf. A controlled ditching — with gear and flaps configured for slowest speed, doors unlatched, master off before impact — is the correct decision.
Built from the real accident record
Scenario inspired by NTSB WPR12FA058 (2011 PA-28R-200 total power loss, undetermined cause), ERA10FA074 (2009 PA-28R-200 oil system failure / engine loss), WPR09FA015 (2008 PA-28R-201T power loss / unsuitable landing site), NYC08FA053 (2007 PA-28R-200 cylinder separation), CEN25LA288 (2025 PA-28RT-201T base-to-final engine failure), ERA22LA067 (2021 PA-28R-200 500-ft power loss), CEN20LA016 (2019 PA-28R-200 undetermined power loss), and CEN26FA049 (2025 PA-28R-201 fuel starvation). Localized to Venice Municipal Airport (KVNC), Venice, FL.
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 — Cockpit 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 KVNC