29 Jan 2020: Beech 60 B60

29 Jan 2020: Beech 60 B60 (N50JR) — Unknown operator

No fatalities • Big Spring, TX, United States

Probable cause

A total loss of engine power in both engines due to fuel exhaustion, which resulted in a landing short of the runway.

— NTSB Determination

Accident narrative

On January 29, 2020, about 1710 central standard time, a Beechcraft BE60 airplane, N50JR, sustained substantial damage when it was involved in an accident about ½ mile southwest of Edwards Lucian Wells Ranch Airport (TX31), Big Spring, Texas. The commercial pilot and sole occupant received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, before departing Abilene Regional Airport (KABI), Abilene, Texas for Odessa Airport (KODO), Odessa, Texas, he asked the fixed base operator (FBO) to add 20 gallons of 100LL aviation gasoline to both fuel tanks. Fuel receipts and statements from FBO personnel confirm that the fuel requested was added to the airplane. A review of Federal Aviation Administration (FAA) archived air traffic control (ATC) communications revealed that after departing KABI, the pilot climbed to a cruising altitude of 10,500 ft. At 1656, the pilot advised ATC of left engine issues and indicated they may have to land at Big Spring, Texas (KBPG). At 1659, the pilot confirmed that he intended to land at KBPG. At 1700, the pilot informed ATC that the right engine was running and the left engine was shut down. He stated that he was able to maintain altitude and wished to continue to KODO. About one minute later, the pilot, once again, advised ATC that he would continue to KODO and would not need assistance upon arrival. Shortly thereafter, the pilot requested a heading for KBPG and stated that the right engine had failed. At 1703, ATC asked the pilot if he would make it to the airport, to which he replied that he may not, but was trying. After being offered an alternate airport by ATC, the pilot stated that he preferred KBPG and reported the airport in sight. At 1704, the pilot called ATC and told them the engine was failing and he saw a different airport that he would attempt a landing at. About 1705, the pilot notified ATC that he was over the airport and would try to land. About a minute later, the pilot stated that he was entering the traffic pattern for the runway and was going to be able to make it. About 1707, the pilot stated that he was on left downwind for the airport and was 90% sure he could make the airport. About two minutes later, another airplane on the same frequency told ATC that he was hearing the broadcast of an emergency locator transmitter and heard a transmission, "I'm going to crash." The wreckage was located about 10 minutes later 200 to 300 yards before the threshold of runway 02. The airplane came to rest upright and sustained substantial damage to the wings and fuselage. The pilot later reported to the NTSB that about 10 miles east of KBPG, both engines lost power due to a "lack of fuel flow." Following the loss of engine power, he looked for a place to land and saw TX31 that appeared to be within gliding distance. He overflew the airport and turned onto final for the north runway. On short final, he lowered the landing gear and "the plane quit flying, the airspeed went to nothing and the plane landed short of the runway." When the FAA aviation safety inspector arrived on scene, they attempted to drain fuel from the fuel tanks. They were able to drain "a couple tablespoons" of fuel from the left tank, but were unable to drain the right tank due to the terrain and the position of the airplane. There was no blue discoloration present on either of the wings or engine nacelles and neither fuel tank was breached. The battery remained connected, and when power was applied to the electrical system, both fuel quantity gauges indicated empty.

Contributing factors

  • cause Fluid level
  • cause Pilot

Conditions

Weather
VMC

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.