ERA19LA231 · Piper PA46 310P
Piper PA46 310P · Accident: fuel exhaustion en route
From Akron Fulton International Airport (AKR) to Dutchess County Airport (POU)
Event
- NTSB case
- ERA19LA231
- 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
- N811SK
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Akron Fulton International Airport (AKR), Akron, OHTo Dutchess County Airport (POU), Poughkeepsie, NY
- Aircraft age
- About 34 years (built 1985)
- 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
- 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
- Fuel exhaustion
- 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
- Aircraft › Aircraft systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was in cruise flight at an altitude of 19,000 feet mean sea level (msl) for about 1 hour and 10 minutes on an easterly heading when he requested a diversion from his filed destination to an airport along his route of flight to utilize a restroom. Two miles west of his amended destination at 12,000 ft msl, the pilot advised the controller that he had a “fuel emergency light" and wanted to expedite the approach. The controller acknowledged the low fuel warning and cleared the airplane to descend from its assigned altitude. Instead of conducting the descent over the airport, the airplane continued its easterly heading past the airport for nearly 8 miles before reversing course. After reversing course, instead of assuming a direct heading back to the airport, the pilot assumed a parallel reciprocal track and didn’t turn for the airport until the airplane intercepted the extended centerline of the landing runway. The pilot informed the controller that he was unable to make it to the airport and performed a forced landing less than 1 mile from the landing runway. Both fuel tanks were breached during the accident sequence, and detailed postaccident inspections of the airplane’s fuel system revealed no leaks in either the supply or return sides of the system. A computer tomography scan and flow-testing of the engine-driven fuel pump revealed no leaks or evidence of fuel leakage. The engine ran successfully in a test cell. Data recovered from an engine and fuel monitoring system revealed that, during the two flights before the accident flight, the reduction in fuel quantity was consistent with the fuel consumption rates depicted at the respective power settings (climb, cruise, etc). During the accident flight, the reduction in fuel quantity was consistent with the indicated fuel flow throughout the climb; however, the fuel quantity continued to reduce at a rate consistent with a climb power setting even after engine power was reduced, and the fuel flow indicated a rate consistent with a cruise engine power setting. The data also showed that the indicated fuel quantity in the left and right tanks reached 0 gallons within about 10 minutes of each other, and shortly before the accident. Given this information, it is likely that the engine lost power due to an exhaustion of the available fuel supply; however, based on available data and findings of the fuel system and component examinations, the disparate rates of indicated fuel flow and fuel quantity reduction could not be explained.
Probable cause
A total loss of engine power due to fuel exhaustion as the result of a higher-than-expected fuel quantity reduction. Contributing was the pilot’s continued flight away from his selected precautionary landing site after identification of a fuel emergency, which resulted in inadequate altitude and glide distance available to complete a successful forced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA19LA231
- Event ID
- 20190719X55851
- Case number
- ERA19LA231
- 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, coordinates, 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: e3711f0a957e1e270c81bce4dc0bd4084b5281c52ca3da89098407e4935ad656; retrieved 2026-09-16T09:27:47.324Z.