ANC08LA010 · Piper 601P
Piper 601P · Accident: loss of engine power en route
From Frederick Douglass Greater Rochester International Airport (ROC) to Danbury Municipal Airport (DXR)
Event
- NTSB case
- ANC08LA010
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper 601P
- Aircraft type
- Piper 601
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N717SB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Frederick Douglass Greater Rochester International Airport (ROC), Rochester, NYTo Danbury Municipal Airport (DXR), Danbury, CT
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Reason for occurrence undetermined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot was continuing a cross-country flight after having stopped for fuel. About 20 minutes into the flight, the pilot said both engines started running rough, and he turned the airplane toward the nearest airport and descended. The pilot reported that he did not think the airplane would make it to the airport, and that due to the rugged terrain, he felt it was better to ditch the airplane in a large lake he was flying over. The pilot reported there were no mechanical anomalies prior to the loss of engine power. He said he felt that fuel contamination was the cause of the engine problem, and that not fueling during heavy rain might have prevented the problem. Fuel samples were taken from the fuel supply where he added fuel, and the equipment used to fuel the airplane. No other instances of fuel contamination were reported, and according to the FAA inspector the fuel samples were tested, and found to be clean. The airplane was not recovered from the lake, and has not been examined by the NTSB.
Probable cause
The loss of engine power during cruise flight for an undetermined reason.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC08LA010
- Event ID
- 20071031X01694
- Case number
- ANC08LA010
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: ad7d331d3b36943d9df406fb31bae97f92ea7738b181a03044ebe5322c790a3e; retrieved 2026-09-22T03:18:33.434Z.