19 Mar 2020: Piper PA28R 180

19 Mar 2020: Piper PA28R 180 (N3943T) — Unknown operator

1 fatality • Pleasant Plain, OH, United States

Probable cause

The pilot’s encounter with convective turbulence and low-level wind shear in dark night instrument meteorological conditions that resulted in spatial disorientation and the loss of airplane control.

— NTSB Determination

Accident narrative

On March 18, 2020, about 2245 eastern daylight time, a Piper PA-28R-180 airplane, N3943T, was destroyed when it was involved in an accident near Pleasant Plain, Ohio. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight.

The instrument flight rules (IFR) flight originated about 1820 from Muskogee-Davis Regional Airport (MKO), Muskogee, Oklahoma. According to records obtained from the fixed base operator at MKO, the pilot purchased 30.5 gallons of 100 low lead aviation fuel prior to departure. The intended destination was Clermont County Airport (I69), Batavia, Ohio. The pilot was in communication with air traffic control (ATC) during the flight. Radar and automated dependent surveillance – broadcast (ADS-B) data showed that the airplane few northeast and climbed to 11,000 ft msl after departing MKO. About 2112 the airplane descended from 11,000 ft, and the pilot requested an RNAV approach to runway 22 at I69. At this point, the airplane was flying in dark night instrument meteorological conditions (IMC). The automated weather observation system (AWOS) at I69 reported wind from 230ºat 8 knots, visibility 7 miles with drizzle, and ceiling overcast at 600 ft agl.

ATC issued the pilot radar vectors to the pilot to proceed to the FIGPU, the initial approach fix (IAF) for the RNAV approach to runway 22. The airplane was 8 miles from FIGPU when ATC instructed the pilot to maintain 3,000 ft and cleared him for the RNAV approach for runway 22. The airplane was about 2.5 miles west of FIGPU when the airplane turned westbound. ATC advised the pilot that they observed the aircraft turning westbound and asked the pilot if he required assistance. The pilot responded that he was turning back and had an autopilot malfunction. The airplane then turned southeast, and ATC asked the pilot if he was proceeding to the JERAL, another IAF on the RNAV approach for runway 22. The pilot responded in the affirmative and the controller asked the pilot if he had corrected the autopilot issue. The pilot reported that he was manually flying the airplane.

The airplane was about 4.5 miles from JERAL when the airplane turned southbound. ATC advised the pilot that he appeared to be heading southbound. The pilot responded that he was experiencing "heavy turbulence" and "heavy downdrafts." The airplane then entered a rapidly descending left turn. ATC issued a low altitude alert to the pilot advised the pilot and advised him to climb to 4,000 ft immediately. The pilot did not respond and there were no further communications from the pilot. Radar contact was lost as the airplane was descended through 1,400 ft, about 14 miles north of I69 (see figure).

Figure. Flightpath with Pilot/ATC Communications.

The airplane wreckage was found severely fragmented amidst a densely wooded area. The area surrounding the accident site was interspersed with agricultural fields, wooded areas, and scattered residential housing adjacent to main roadways. The initial point of impact was a treetop. Impact marks were observed about 69-ft high in the tree. The wreckage was scattered throughout the wooded area on an approximate heading of 135°and came to rest near a small pond. The engine, propeller, and main instrument panel were located about 55 ft away from the main wreckage. Although there was extensive impact damage, examinations of the airframe, flight controls, and engine did not reveal any pre-impact anomalies.

The National Transportation Safety Board meteorological weather study documented a stationary frontal system over the area that resulted in an extensive area of IFR conditions, with low ceilings low visibilities, drizzle, and rain.  The study showed that the airplane was flying in area conducive to low-level windshear and convective turbulence at the time of the accident. There was no record of the pilot obtaining a preflight weather briefing, and his flight plan did not list an alternate airport.

An autopsy on the pilot was performed by the Montgomery County Coroner, Dayton, Ohio. The cause of death was blunt force trauma. Toxicology tests, performed by the Federal Aviation Administration (FAA), Civil Aerospace Medical Institute, Oklahoma City, Oklahoma, were negative for alcohol and other drugs.

Contributing factors

  • Pilot
  • Contributed to outcome
  • Contributed to outcome
  • Pilot
  • Lateral/bank control — Not attained/maintained

Conditions

Weather
IMC, wind 230/08kt, vis 7sm

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.