Fuel Exhaustion & Starvation · NTSB ERA09FA303

AERO COMMANDER 500 S — Daytona Beach, FL

1 fatal High-time pilot
DateMay 25, 2009
LocationDaytona Beach, FL
AircraftAERO COMMANDER 500 S
Purpose of flightPersonal
ConditionsDay · Visual Meteorological Cond
Phase / occurrenceInitial climb Fuel exhaustion
Pilot age45
Pilot total time1,470 hrs · Experienced
Time in type574 hrs
Fatalities1, 1 serious

Probable cause

A total loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight inspection.

NTSB findings

  • Personnel issues-Task performance-Inspection-Preflight inspection-Pilot - C
  • Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level - C

What happened

The pilot departed in the twin-engine airplane with an unknown quantity of fuel and a fuel quantity indicating system that was known to be inaccurate. Immediately after takeoff, approximately 1/2 mile beyond the departure end of the runway, witnesses reported the engine noise from the accident airplane as "surging" as the airplane passed overhead, and one witness described a "radical" turn back to the airport. Two witnesses stated that only one engine was running, and added that it was "revving," and would then stop before revving up again. During the descent to the airport, radar data showed the airplane at 93 knots 700 feet and 1 mile from the runway, and at 90 knots at 500 feet and 1/2 mile from the runway, but the airplane crashed prior to the approach end of the runway. Postaccident examination of the wreckage revealed no evidence of a preaccident mechanical malfunction. The fuel system had a capacity of 226 gallons, was serviced through a single port on top of the left wing, and the tanks were interconnected to a center fuel sump that fed both engines. The fuel cells were opened through access panels and each was intact and contained only trace amounts of fuel. The airplane was leveled, the drain petcock was opened at the center fuel cell sump, and 1 quart of fuel was drained.

An editorial "what led to it / how to avoid it" analysis for this accident is generated separately and will appear here.

View the official NTSB docket →