Fuel exhaustion Accident Beechcraft 58 Baron N501CE,
ASN logo
ASN Wikibase Occurrence # 224241
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 22 April 2019
Time:08:51
Type:Silhouette image of generic BE58 model; specific model in this crash may look slightly different    
Beechcraft 58 Baron
Owner/operator:Private
Registration: N501CE
MSN: TH-1888
Year of manufacture:1999
Total airframe hrs:3834 hours
Engine model:Continental IO-500C
Fatalities:Fatalities: 6 / Occupants: 6
Aircraft damage: Substantial
Category:Accident
Location:6 miles from Kerrville Municipal Airport, TX -   United States of America
Phase: Approach
Nature:Executive
Departure airport:Houston-West Houston Airport, TX (IWS/KIWS)
Destination airport:Kerrville Airport, TX (ERV/KERV)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot was conducting an instrument flight rules (IFR) flight in a twin-engine airplane with five passengers. During a GPS approach to the destination airport, both engines lost total power within 10 seconds of each other; the left engine regained near full power about 40 seconds later, which it maintained until the end of recorded data. As the pilot continued the approach, he did not ensure the flaps were up or feather the propeller of the inoperative right engine, which was contrary to the airplane manufacturer's emergency procedures guidance.

As the airplane descended with the right engine inoperative below the cloud ceiling to about 500 ft agl, its flightpath leveled and airspeed decreased below the minimum controllable airspeed (Vmc). The airplane's continued flight profile below Vmc with the unfeathered propeller of the inoperative right engine, the left engine near full power, and the airplane's aft center of gravity resulted in a right-turning spin and ground impact.

The pilot's filed flight plan indicated a minimum fuel load required of 58 gallons, although this did not account for the instrument approach and alternate airports. However, the pilot's flight planning log indicated only 50 or 54 gallons of fuel onboard. Thus, based solely on the pilot's logs, there was insufficient fuel onboard the airplane to embark on the flight. Because the airplane was beyond its maximum gross weight with just 50 gallons of fuel onboard, it is likely that the pilot did not want to add additional fuel. Thus, the pilot's decision to depart on the accident flight without adequate fuel onboard showed poor judgement.

Although the pilot departed without an adequate fuel reserve for the IFR flight, an actual fuel load of 50 or 54 gallons would have been sufficient to reach the destination airport (the airplane burned about 42 gallons just before the crash site about 6 miles from the airport). However, when the airplane was fueled at the pilot's request 8 days (five flights) before the accident flight, it was not completely filled. Because the pilot was not present for the fueling and did not crosscheck the fuel receipt with his fuel-planning logs, he did not recognize that the error meant he had less than 50 gallons of fuel onboard before departing on the accident flight. As evidenced by the close correlation between the pilot's fuel logs and the engine data monitoring (EDM) fuel consumption data for the accident flight and the five flights before it, the pilot mainly relied on EDM data to determine the quantity of fuel onboard the airplane. Thus, the fueling error introduced 8 days before the accident was carried through the pilot's planning logs for the next six flights, including the accident flight.

Further review of the accident airplane's fueling records, the pilot's flight-planning logs, and fuel consumption data from the EDM revealed that the airplane actually had about 12 gallons less fuel than the pilot indicated in his fuel log for the accident flight. Thus, the lack of sufficient fuel for the accident flight resulted in the airplane's engine power loss during the approach.

In addition, the abnormally high resistances in both fuel quantity transmitters would have caused the cockpit fuel quantity indicators for both wings to read about 5 gallons higher each than the actual fuel present, corresponding to an additional 1/16th tank on each of the indicators. Thus, because of the high resistances in both fuel quantity transmitters, the pilot's belief that 50 (or 54) gallons of fuel were onboard at takeoff (rather than the actual fuel level of 38 gallons) may have been corroborated by the fuel quantity indicators; however, the effect of the inaccurate indications on the pilot's actions are uncertain.

Probable Cause: The pilot's inadequate preflight fuel planning and fuel management, which resulted in a loss of engine power due to fuel exhaustion. Also causal was the pilot's failure to follow the one-engine inoperative checklist and maintain the airplane's minimum controllable airspeed by properly configuring the airplane, which resulted in a loss of airplane controllability.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: CEN19FA124
Status: Investigation completed
Duration: 1 year and 3 months
Download report: Final report

Sources:

NTSB
https://flightaware.com/live/flight/N501CE/history/20190422/1229Z/KIWS/KERV

https://flightaware.com/resources/registration/N501CE

Location

Images:




Photo: NTSB

Media:

Revision history:

Date/timeContributorUpdates
22-Apr-2019 17:39 Captain Adam Added
22-Apr-2019 17:42 Captain Adam Updated [Aircraft type, Source]
22-Apr-2019 17:46 Captain Adam Updated [Time, Aircraft type]
22-Apr-2019 17:49 Captain Adam Updated [Registration, Cn, Operator, Source]
22-Apr-2019 18:34 harro Updated [Time, Departure airport, Destination airport, Photo]
22-Apr-2019 21:58 Iceman 29 Updated [Source, Embed code]
23-Apr-2019 11:24 Iceman 29 Updated [Nature, Source, Embed code, Photo]
23-Apr-2019 18:23 Aerossurance Updated [Location, Nature, Source, Narrative]
22-Jul-2020 08:01 ASN Update Bot Updated [Time, Nature, Departure airport, Destination airport, Source, Embed code, Damage, Narrative, Accident report, ]
22-Jul-2020 08:04 harro Updated [Departure airport, Destination airport, Source, Embed code, Narrative, Photo, Accident report, ]
24-Jul-2020 10:48 Aerossurance Updated [Embed code]
30-Apr-2021 13:25 harro Updated [Embed code]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org