ERA20LA011 · Piper PA46 310P
Piper PA46 310P · Accident: loss of engine power (total) on approach
From Frederick Douglass Greater Rochester International Airport (ROC) to Harrisburg International Airport (MDT)
Event
- NTSB case
- ERA20LA011
- 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 PA46 310P
- Aircraft type
- Piper PA46
- 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
- N4385K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Frederick Douglass Greater Rochester International Airport (ROC), Rochester, NYTo Harrisburg International Airport (MDT), Harrisburg, PA
- Aircraft age
- About 35 years (built 1984)
- 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
- Approach · IFR final approach
- Defining eventThe 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 (total)
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was performing a visual approach for landing when the engine lost total power. Unable to restore engine power, the pilot performed a forced landing to a river.
After recovery, the external engine components were dried, cleaned, and reinstalled (magnetos, fuel manifold), and the starter was replaced due to water immersion. The engine was then placed in a test cell where it started immediately, accelerated smoothly, and ran continuously without interruption.
Radar and on-board data revealed that the airplane experienced lateral g-forces in the turn to final and during its approach in a gusting crosswind, consistent with a slip. Although the airplane’s operating handbook cautioned against prolonged slips or skids or other “radical or extreme maneuvers which could cause uncovering of the fuel outlet,” whether the slip during the accident flight was sufficient to uncover the fuel port and result in the loss of engine power could not be determined.
Probable cause
A total loss of engine power for reasons that could not be determined following a successful engine run.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20LA011
- Event ID
- 20191004X00403
- Case number
- ERA20LA011
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 7365162beea2b598b2f1b58a1e7ebc6ca1e5cf03bab13e4b8221ab2d16e22732; retrieved 2026-09-16T10:17:08.559Z.