No fatalities

2019-07-19: Piper PA-46 (Malibu/Meridian/Mirage/Matrix/M-Class) (N811SK) — Akron Aerostar — Poughkeepsie-Hudson Valley (ex Dutchess County), United States of America

Poughkeepsie-Hudson Valley (ex Dutchess County), United States of AmericaLanding (descent or approach)

On July 19, 2019, a Piper PA-46 (Malibu/Meridian/Mirage/Matrix/M-Class) (registration N811SK) operated by Akron Aerostar was involved in an aviation accident near Poughkeepsie-Hudson Valley (ex Dutchess County), United States of America during landing or approach. No fatalities were reported. Investigators recorded the probable cause as: A total loss of engine power due to fuel exhaustion as the result of a higher-than-expected fuel quantity reduction. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A); 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781190876Data APIEditorial standards

A pilot diverted for a restroom stop, later reported a fuel emergency light, flew past the airport, and performed a forced landing due to fuel exhaustion. Post-accident inspections found no fuel system leaks.

Flight Details

The pilot was in cruise flight at an altitude of 19,000 feet mean sea level (msl) for approximately 1 hour and 10 minutes on an easterly heading. He requested a diversion from his filed destination to an airport along his route to use a restroom. Two miles west of his amended destination at 12,000 ft msl, the pilot advised the controller of a “fuel emergency light” and requested an expedited approach. The controller acknowledged the low fuel warning and cleared the airplane to descend.

Instead of descending over the airport, the airplane continued eastward for nearly 8 miles before reversing course. After reversing, the pilot assumed a parallel reciprocal track and only turned toward the airport when the airplane intercepted the extended centerline of the landing runway. The pilot then reported being unable to reach the airport and performed a forced landing less than 1 mile from the runway.

Fuel System Examination

Both fuel tanks were breached during the accident sequence. Detailed postaccident inspections revealed no leaks in either the supply or return sides of the fuel system. A computer tomography scan and flow-testing of the engine-driven fuel pump showed no leaks or evidence of fuel leakage. The engine ran successfully in a test cell.

Data Analysis

Data from an engine and fuel monitoring system indicated that, during the two flights preceding the accident flight, the fuel quantity reduction was consistent with fuel consumption rates at respective power settings (climb, cruise, etc.). During the accident flight, the reduction in fuel quantity was consistent with indicated fuel flow throughout the climb. However, after engine power was reduced, the fuel quantity continued to decrease at a rate consistent with a climb power setting, while the fuel flow indicated a rate consistent with a cruise 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, shortly before the accident.

Based on the available data and findings, the engine likely lost power due to exhaustion of the available fuel supply. However, 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.