Engine Failure Forces Pilot and Stepdaughter to Crash into Lake – A Survival
The accident in context
Type: Piper PA-32-300 Cherokee Six Departure airport:Orlando, FL (ORL) Destination airport: Venice, FL (VNC) The private pilot was conducting his third flight of the day when, during climb about 10 minutes after takeoff, the engine lost partial power, regained power, then lost all power. The pilot was unable to restart the engine and ditched the airplane in a lake. Postaccident examination of the engine did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.
The left main fuel tank was breached and absent of fuel. The left wingtip fuel tank was separated from the wing and was not recovered. However, adequate fuel remained in the airplane.
The Piper PA-32-300 accident is unusual because the engine problem was real, but the investigation could not determine why total power was lost. The aircraft was on a flight from Orlando toward Venice when the engine lost partial power, recovered briefly and then lost all power. The pilot and stepdaughter ditched in a lake.
Reconstructing the sequence
The investigation could not determine if the drain for the right wingtip fuel tank was locked open before or during impact, nor could it determine the position of the fuel selector when engine power was lost. Probable Cause: A total loss of engine power for reasons that could not be determined because postaccident examination did not reveal any evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation
The postaccident fuel evidence was complicated. The right main tank contained about 25 gallons, while the left main tank was breached and empty. The right wingtip tank contained water and its drain was found locked open. The fuel selector was found between the right main and right wingtip positions. The investigator could not determine the selector position at the moment power was lost or whether the open drain had been open before impact.
What the evidence shows
That uncertainty is the central finding. The probable cause was total loss of engine power for reasons that could not be determined because examination did not reveal a pre-impact mechanical failure that would have prevented normal operation. The article should therefore resist the temptation to call it a simple fuel-starvation accident; the physical evidence supports several possibilities but does not close the case to one mechanism.
Why the sequence matters
The reconstructed sequence can be read as a chain of six decision points: Orlando departure → Partial power loss → Power returns then fails → Restart unsuccessful → Lake ditching → Occupants survive. Each step changed the aircraft’s available options. The important analytical point is not to isolate the final impact from the preceding events; the final outcome was produced by the accumulation of the earlier changes in aircraft state, position, workload and available escape options.
The ATC/radar perspective is most useful when it is synchronized with the aircraft evidence. In this case the critical transition is the move from orlando departure to occupants survive. Once the aircraft reached the later stages of the sequence, the crew had fewer safe alternatives than they had at the beginning. That is the operational value of reconstructing the event rather than describing it only from the final crash scene.
The lake ditching also demonstrates why the postaccident evidence matters as much as the emergency call. The remaining fuel, selector position and damaged tanks created a complex forensic picture. Investigators could establish that the engine lost power and that the airplane landed in the lake, but they could not reconstruct every fuel-system state at the instant of power loss. A high-quality account should preserve that uncertainty rather than turning one piece of physical evidence into a definitive explanation.
Key Takeaways / Lessons Learned
The decisive safety issue in this incident was specific to the sequence: Partial power loss; Power returns then fails; Restart unsuccessful. Treating those events as isolated anomalies would miss the way they interacted.
Sources and investigation material
- https://data.ntsb.gov/
- https://www.aviation.govt.nz/assets/aircraft/airworthiness-directives/aeroplanes/pa32.pdf
Accident Facts
- Aircraft
- Piper
- Category
- Crash, Fuel, Engine failure
- Reconstruction
- 9:41