The U.S. aircraft register, updated daily
Accidents · NTSB ERA19LA231 · Final report

Piper PA46 accident near Poughkeepsie, New York, July 19, 2019

On July 19, 2019 at about 6:40 pm local time, a 1985 Piper PA46, registered N811SK, was substantially damaged in an accident during enroute near Poughkeepsie, New York (Dutchess County airport). It was a personal flight under general aviation rules (Part 91). 3 people were seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 19, 2019 · about 6:40 pm local time
Place
Poughkeepsie, New York · Dutchess County · map
Type
Accident
Injuries
3 people were seriously injured and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft
Piper PA46 310P, built 1985 · all PA46s on the register
Registration
N811SK · no longer on the register · serial 46-8508046
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Fuel exhaustion during enroute defining event
  2. Landing area overshoot during emergency descent

The NTSB's findings

  • Aircraft › Aircraft systems › Fuel system › (general) › Unknown/Not determined
  • Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • Aircraft › Fluids/misc hardware › Fluids › Fuel › Unknown/Not determined

Pilot

  • Certificate: private
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,300 hours in all; 300 in this make and model
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: serious injuries

The aircraft

  • Airframe total time: 2,641 hours
  • Last inspection: annual inspection, March 12, 2019
  • Maximum gross weight: 4,101 lb
  • Landing gear: retractable
  • Engine: Continental TSIO-550-C (1 (piston); 1,053 hours total

The flight

  • Departed from: AKR Akron OH at 4:48 pm
  • Destination: POU Poughkeepsie NY
  • Flight plan: IFR
  • Runway 25, 1,358 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 220° at 8 knots, gusting 15
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 91°F (33°C), dew point 73°F (23°C)
  • Altimeter: 29.81 inHg
  • Observation at 6:53 pm from KPOU, 5 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers21

Documents from the investigation the NTSB's docket: the evidence folder behind the report

17 documents, released by the NTSB on June 6, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.