27 Apr 2014: BEECH A36 — DAKOTA N8465S LLC

27 Apr 2014: BEECH A36 (N3078Y) — DAKOTA N8465S LLC

No fatalities • Wann, OK, United States

Probable cause

The pilot's inadequate preflight inspection and planning and inflight fuel management, which resulted in a loss of engine power due to fuel exhaustion and a subsequent forced landing in an area of unsuitable terrain.

— NTSB Determination

Accident narrative

On April 27, 2014, at 1338 central daylight time, the pilot of a Beech A36, N3078Y, made a forced landing near Wann, Oklahoma, after a total loss of engine power during cruise flight. The pilot and two passengers were seriously injured. The airplane was substantially damaged. The airplane was registered to and operated by Dakota N8465S, Montgomery, Alabama, under the provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed at the time of the accident, and an instrument flight rules flight (IFR) plan had been filed. The cross-country flight originated from Washington County Memorial Airport (K38), Washington, Kansas, at 1207, and was originally en route to Shawnee Regional Airport (SNL), Shawnee, Oklahoma, but diverted to Claremore Regional Airport (GCM), Claremore, Oklahoma.According to the pilot, he obtained a weather briefing and filed an IFR flight plan, then departed K38 en route to GCM. He said the airplane departed with 20 gallons of fuel in each wing tank. After flying for 1 hour, 18 minutes, he switched to the right tank and the engine lost power. Several attempts were made to restore power to no avail. During the forced landing, the airplane's right wing collided with a tree before the airplane impacted terrain. The accident location was near the intersection of Highways 5 and 406. The pilot and front seat passenger were airlifted to a hospital with non-life threatening but serious injuries. The second passenger was transported to a local hospital with serious injuries. He told state troopers that they had been diverting to SNL for fuel and because of strong headwinds encountered during the flight.

A Federal Aviation Administration (FAA) inspector and representatives from Continental Motors, Inc., and Textron Aviation examined the airplane. They reported finding no fuel in the uncompromised left wing fuel tank. The right wing fuel tank had been compromised, but they reported finding no fuel stains on the ground or any an odor of fuel in the immediate area. An on-scene examination of the engine revealed no obvious discrepancies. The Hobbs hour meter displayed 717.4 hours at the accident site.

According to FlightAware, a global aviation software and data services company that tracks flights throughout the world, the accident airplane had originally departed Montgomery Regional Airport (MGM), Montgomery, Alabama, at 0958 on April 25. It is not known how much fuel was on board the airplane when it departed MGM. The flight continued to Horseshoe Bend Airport (6M2), Horseshoe Bend, Alabama, arriving there at 1232 the same day. The reported time en route to 6M2 was 2 hours, 37 minutes. According to the fuel receipt, 46.01 gallons of fuel was purchased at 1238 on April 25; however, it is not known whether the airplane was fueled to capacity at that time. The accident airplane then departed 6M2 at 1317, and flew to K38, arriving there at 1519. The reported time en route was 2 hours, 2 minutes. There was no evidence that the airplane was refueled at K38.

Under the auspices of the National Transportation Safety Board, the engine was functionally tested at Teledyne Continental Motor in Mobile, Alabama, on July 16, 2014. Several external engine components were replaced to facilitate the test run, but the engine tested satisfactory at all power settings and no anomalies were noted.

The JPI EDM 700 (JP Instruments Engine Data Management) and a JPI Fuel Scan 450 were removed from the airplane and shipped to the National Transportation Safety Board's Vehicle Recorder Division for download. According to an e-mail from the laboratory, the JPI EDM 700 had no internal EPROM chips and no data was stored on the device. The JPI Fuel Scan 450 displayed also did not store data.

Contributing factors

  • cause Fluid level
  • cause Pilot
  • cause Fluid management
  • Contributed to outcome

Conditions

Weather
VMC, wind 170/13kt, vis 10sm

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.