4 Aug 2018: Extra EA 400 500 — Jeremiah 29:11 Inc

4 Aug 2018: Extra EA 400 500 (N13EP) — Jeremiah 29:11 Inc

5 fatalities • Ponca City, OK, United States

Probable cause

The pilot's loss of control for reasons that could not be determined with the available evidence.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHTOn August 4, 2018, about 1045 central daylight time, an Extra EA-400 airplane, N13EP, was destroyed when it was involved in an accident near Ponca City, Oklahoma. The pilot and 4 passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

A witness saw the airplane depart Ponca City Regional Airport (PNC), Ponca City, Oklahoma, on runway 17. He reported that the airplane was slow to climb as it departed to the south, especially for the shallow angle of climb. Another witness who saw the airplane depart remarked that the engine sounded unusual. This witness watched the airplane slowly climb from the runway and head toward the south before it turned toward the west. A pilot flying near the accident airplane recalled that the airplane maneuvered with large changes to the pitch and bank; later, it appeared to maneuver back toward the airport when it pitched nose down and turned, but “not like a spin.” He saw the wings level and the airplane impacted the ground. A post-impact fire ensued and largely consumed the airplane’s composite structure, destroying the airplane. PERSONNEL INFORMATIONPilot

The pilot’s logbook was not located during the investigation. On the pilot’s last application for a medical certificate, he reported 4,000 total hours of flight time.

The pilot’s last medical certificate was issued on July 28, 2016. He did not reapply for a medical certificate and there is no record of the pilot having completed the Basic Med checklist.

Pilot-Rated Passenger

The pilot-rated passenger’s logbook was not located during the investigation. On the application for his medical certificate, he reported 450 hours of flight time in the preceding 6 months.

The airplane was equipped with flight controls at both occupants’ seat. It could not be determined whether the pilot or pilot-rated passenger was flying the airplane at the time of the accident. AIRCRAFT INFORMATIONThe pilot purchased the airplane in July 2017; maintenance logbook entries from that time reported that the airplane had flown 211.3 hours in total. The last maintenance performed on July 13, 2018, recorded 412.3 hours total flight time. METEOROLOGICAL INFORMATIONThe density altitude was calculated at 3,025 ft. AIRPORT INFORMATIONThe pilot purchased the airplane in July 2017; maintenance logbook entries from that time reported that the airplane had flown 211.3 hours in total. The last maintenance performed on July 13, 2018, recorded 412.3 hours total flight time. WRECKAGE AND IMPACT INFORMATIONThe wreckage was located in a soy-bean field. The debris field was in a narrow V shape about 50 ft long from the initial impact point. All major components of the airplane were found at the accident site. The initial ground impact crater contained the engine and the forward portion of the cockpit, including portions of the cockpit flight controls. The angle of the engine resting in the soil was nearly vertical.

A post impact fire ensued and largely consumed the airplane’s composite structure. Postaccident examination of the airplane’s remaining airframe and cockpit controls was conducted. Flight control continuity was traced to all flight control surfaces. The flaps and landing gear both appeared to be in the retracted position. A majority of the cockpit instrumentation was destroyed; however, the airspeed indicator read 150 knots. A JPI engine data monitor unit was located; however, due to fire damage its data could not be extracted. No preimpact anomalies were detected with the airframe.

The engine was impact and fire damaged. The engine was removed and examined. The examination did not find any preimpact anomalies which would have precluded normal engine operation.

During the on-scene portion of the investigation, a damaged Appareo Stratus S2 device was located in the wreckage. Damage to the device required removal and reinstallation of the memory chips to a donor device. Information recovered did not coincide with the accident flight and was not pertinent to the investigation. ADDITIONAL INFORMATIONA current weight and balance sheet was not located during the investigation. An estimated weight and balance for the flight used the following sources for the weights:

Airplane Basic Weight – Manufacturer’s Information Manual Pilot’s Weight – last Federal Aviation Administration (FAA) medical certificate Pilot Rated Passenger’s Weight – last FAA medical certificate Adult Passenger’s Weight – last FAA medical certificate Children’s Weights – 50% percentile from Centers for Disease Control guidelines for weight based on age.

Because the weight and existence of baggage could not be determined, no additional weight was added. Estimates of the weight and balance revealed that, depending on the amount of fuel, baggage, and equipment on board and the location of the adult passenger, the center of gravity (CG) could have been within or aft of the recommended CG limits. Because the fuel load and location of the passengers and baggage could not be determined or may have shifted during flight, it is not known whether the airplane’s weight and balance at the time of the accident contributed to the accident. MEDICAL AND PATHOLOGICAL INFORMATIONThe Office of the Chief Medical Examiner, Oklahoma City, Oklahoma, performed autopsies on both the pilot and the pilot-rated passenger. The cause of death for both occupants was multiple blunt force injuries and the manner of death was ruled an accident.

The FAA Forensic Sciences Laboratory, Oklahoma City, Oklahoma, performed toxicology testing on samples from the occupants seated at the controls. Specimens of both occupants tested positive for ethanol, but the samples were marked putrefied.

Contributing factors

  • Pilot
  • Performance/control parameters — Not attained/maintained

Conditions

Weather
VMC, wind 170/11kt, 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.