Fuel exhaustion Accident Beechcraft C90GTx King Air N8116L,
ASN logo
ASN Wikibase Occurrence # 144773
 
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:Tuesday 3 April 2012
Time:09:20
Type:Silhouette image of generic BE9L model; specific model in this crash may look slightly different    
Beechcraft C90GTx King Air
Owner/operator:Lider Taxi Aereo
Registration: N8116L
MSN: LJ-2042
Year of manufacture:2012
Total airframe hrs:14 hours
Engine model:Pratt & Whitney Canada PT6A-135A
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:sea 17 miles N of Oranjestad, Sint Eustatius -   Caribbean Netherlands
Phase: En route
Nature:Ferry/positioning
Departure airport:Fort Lauderdale, FL (FXE)
Destination airport:TGPY
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot and pilot-rated passenger had taken delivery of the newly manufactured airplane at the manufacturer's facility in Wichita, Kansas the day before the accident. They then flew it to Fort Lauderdale, Florida, after making a stop in Marianna, Florida, for fuel. Upon arriving in Fort Lauderdale, the pilots gave their fuel request to the customer service agent at the fixed base operator (FBO), advising them that they would be departing the following morning. On the morning of the accident, the pilot filed a flight plan while the pilot-rated passenger conducted the airplane preflight. He did not remove the fuel caps and look in both wing tank fuel filler openings. After filing the flight plan, the pilot walked around the airplane without performing a preflight or looking in the wing tank fuel filler openings. After takeoff, the pilots climbed the airplane to a cruising altitude of 27,000 feet. The flight was uneventful until the pilots observed that the fuel quantity indicators were reading lower than anticipated. Sometime later, both engine lost power; the pilots reported that they were having engine problems and declared an emergency. They then ditched the airplane in the Caribbean Sea, were uninjured, and were later rescued.

The pilot stated that, based on the fueling ticket, he concluded that the airplane had been refueled with 134 gallons of fuel before departure, which would have been sufficient for the airplane to reach their destination. Once in flight, he realized that the fuel quantity indicators were reading lower than anticipated; he looked at the fuel ticket again to confirm that 134 gallons of fuel had been delivered. However, review of the fueling process revealed that after arrival in Fort Lauderdale, the pilot had requested that the FBO personnel top off the nacelle tanks. This was accomplished, but only 25 gallons of fuel was needed to comply with the request, and this amount was accurately listed on the fuel ticket. Further review revealed that the number 134, which the pilot thought was the amount of fuel uploaded, was in actuality the employee number of the fueler.

Review of the airplane's Pilot's Operating Handbook and Airplane Flight Manual (POH/AFM) revealed that this fuel discrepancy should have been caught even before the flight departed, as the POH/AFM checklists for operating the airplane required the pilots to confirm the fuel quantity during preflight, before engine starting, and before takeoff. The fuel discrepancy could also have been detected once airborne if the fuel quantity switch on the fuel control panel had been in the "TOTAL" position during flight, which would have given an indication of the total amount of fuel onboard. However, the pilot advised that the fuel quantity switch was in the "NACELLE" position during the flight and about every 20 minutes he would check the "wing" (total) quantity. This procedure did not conform with the guidance contained in the POH/AFM which advised that the "NACELLE" position was to be used to verify nacelle fuel quantity during operations with the "NO FUEL XFR" annunciator illuminated.

Additionally, the accident could have been avoided 2 hours into the flight, while over the island of Hispaniola, when the pilot noticed that he had an approximate 40-knot tailwind but the amount of fuel onboard was less than usual after 2 hours of flying. However, the pilot decided to continue despite his proximity to airports on Hispaniola that were suitable for diversion. By the time he began to be concerned about a possible fuel leak or indication failure, he was once again over open water. As the situation worsened, the pilot finally decided to divert to Aruba, but by then it was too late, and he was forced to ditch the airplane.
Probable Cause: A complete loss of engine power due to fuel exhaustion as a result of the pilot's failure to verify that sufficient fuel was onboard prior to flight. Contributing to the accident was the pilot's misreading of the fuel ticket and his improper operation of the fuel control panel , and his delay in recognizing the fuel shortage.

Sources:

NTSB
https://www.taiwannews.com.tw/en/news/1885396
http://internationaljustice.rnw.nl/caribiana/bulletin/noodlanding-vliegtuig-op-zee-nabij-aruba
https://www.defensie.nl/actueel/nieuws/2012/04/03/46194607/Defensiehelikopter_redt_gecrashte_piloten_uit_zee
http://www.awe24.com/20120403/10328/ULTIMO_INFORME_A_rescata_tur_2_persona_abordo_cu_a_ditch_cu_avion
https://amigoe.com/aruba/107179-vliegtuigje-stort-in-zee-inzittenden-gered
https://www.faa.gov/data_research/accident_incident/preliminary_data/events01/media/08_8116L.txt
https://www.ntsb.gov/aviationquery/brief.aspx?ev_id=20120404X75417&key=1_
https://flightaware.com/live/flight/N8116L

Location

Revision history:

Date/timeContributorUpdates
03-Apr-2012 12:38 Thepilot83 Added
03-Apr-2012 13:46 RobertMB Updated [Time, Aircraft type, Cn, Operator, Location, Source, Damage, Narrative]
03-Apr-2012 14:51 RobertMB Updated [Source, Narrative]
03-Apr-2012 15:19 RobertMB Updated [Aircraft type, Narrative]
03-Apr-2012 15:36 RobertMB Updated [Source, Narrative]
04-Apr-2012 12:33 Geno Updated [Location, Source, Narrative]
02-May-2012 19:40 Geno Updated [Time, Location, Source, Narrative]
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
27-Nov-2017 20:36 ASN Update Bot Updated [Operator, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]
27-Mar-2020 06:56 Cocodala Updated [Country, Destination airport, Source]
27-Mar-2020 06:56 harro Updated [Other fatalities, Country]
23-May-2022 04:04 Ron Averes Updated [Location, Source]
23-May-2022 04:18 Ron Averes Updated [Location]
12-Jun-2022 08:47 Ron Averes Updated [Location, Country]

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