The U.S. aircraft register, updated daily
Accidents · NTSB CEN16LA281 · Final report

Amateur-built RV9 accident near Springfield, Ohio, July 22, 2016

On July 22, 2016 at about 2:40 pm local time, a 2015 amateur-built RV9, registered N807LK, was destroyed in an accident during enroute (cruise) near Springfield, Ohio. It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s decision to fly into known thunderstorms, which resulted in an in-flight breakup.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
July 22, 2016 · about 2:40 pm local time
Place
Springfield, Ohio · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built RV9 A, built 2015
Registration
N807LK · no longer on the register · serial 91528
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

Before takeoff on a personal cross-country flight, the private pilot received two official weather briefings of all the forecast and observed weather conditions along the flight route, which included thunderstorms and convective SIGMETs. A review of air traffic control (ATC) information revealed that, while en route to the destination airport, the pilot was in contact with ATC and attempting to circumnavigate oncoming weather and precipitation. The pilot requested ATC assistance and stated that he could avoid the clouds if ATC could help him avoid the precipitation, indicating that he was aware of the weather conditions but that he likely did not have onboard weather information. The Middletown sector approach controller provided two route options: one of the options would have allowed the pilot to completely avoid the precipitation and taken him farther away from his destination, and the other option would have allowed the pilot to proceed between two areas of precipitation and stay closer to his intended route. The controller obtained PIREPs from two pilots who had previously transitioned through the two areas of precipitation, and they reported that they "didn't really have any problems" flying through the area. The controller also provided the pilot the intensity of the two cells and the estimated distance between the two areas of precipitation. After the controller relayed this information to the pilot, he chose to fly between the two areas of heavy precipitation. The controller then transferred communication to the Urbana sector approach controller. After the pilot checked in with the Urbana approach controller, the controller issued the pilot several heading suggestions to the northwest to avoid the precipitation, but the pilot responded that he wanted to continue on his present heading and then continued flying east toward the severe weather. Despite several subsequent suggestions by the controller to the pilot to change course to avoid the weather, according to radar data, the airplane continued flying east toward the severe weather. In the final 3.5 minutes of the flight, while flying east, the airplane made a left 360° turn while descending about 2,900 ft per minute (fpm), then resumed a climb while heading east. Less than 1 minute later, the airplane made a right 310° turn while descending about 1,200 fpm. The airplane then flew northeast and descended about 4,600 fpm to 3,440 ft above ground level. Subsequently, the descent rate increased to about 6,450 fpm, at which point radar contact was lost. The airplane entered an area of an outflow boundary and thunderstorms and likely encountered heavy precipitation, severe-to-extreme turbulence, updrafts and downdrafts, and wind shear. A witness saw the airplane in a steep descent and heard the engine operating; the airplane then disappeared behind a tree line, at which point she heard the sound of an impact. The airplane impacted a corn field heading north. The vertical stabilizer and rudder were found 0.61 to 0.63 nautical miles southwest of the main wreckage, respectively, and exhibited overload signatures consistent with an in-flight breakup. A postaccident examination of the airframe and engine did not reveal any anomalies, other than the separated components, that would have precluded normal operation. Although the Middletown sector controller provided general information about the observed weather, she did not provide specific information, such as the direction relative to the airplane and distance to the bands of weather and the widths of the weather bands, as required by Federal Aviation Administration Order 7110.65. The controller's workload did not prevent her from providing general weather information and suggesting headings to the pilot, which indicates that the controller could have provided more specific adverse weather information without detriment to other duties, as required. However, it is unlikely that this affected the pilot's decision about the route he flew. The pilot's continued flight into known thunderstorms resulted in the in-flight breakup of the airplane. Although toxicology testing detected ethanol in the pilot's muscle and liver, the ratio of the detected ethanol suggested that some or all the ethanol was from sources other than ingestion.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Loss of control in flight during enroute (cruise)
  2. Inflight upset during enroute (cruise) defining event
  3. Other weather encounter during enroute (cruise)
  4. Windshear or thunderstorm during enroute (cruise)

The NTSB's findings

  • cause Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Effect on equipment
  • cause Environmental issues › Conditions/weather/phenomena › Convective weather › Thunderstorm › Decision related to condition
  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft structures › Empennage structure › Vertical stabilizer › Capability exceeded
  • cause Aircraft › Aircraft structures › Empennage structure › Rudder › Capability exceeded
  • cause Aircraft › Aircraft oper/perf/capability › (general) › (general) › Capability exceeded

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,375 hours in all; 63.7 in this make and model; 15.1 in the last 90 days; 13.5 in the last 30 days
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: fatal

Passenger

  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 53.2 hours
  • Last inspection: condition inspection, June 16, 2016
  • Seats: 2
  • Landing gear: fixed
  • Engine: Superior XP-320 (piston); 68 hours total

The flight

  • Departed from: TRI Bristol/Johnson/Kingsport TN at 12:50 pm
  • Destination: ONZ Detroit/Grosse Ile MI
  • Flight plan: VFR

Weather at the time

  • Light: daylight
  • Wind: from 040° at 4 knots
  • Visibility: 7 statute miles
  • Sky: broken clouds at 1,500 ft
  • Temperature: 77°F (25°C), dew point 72°F (22°C)
  • Altimeter: 30.06 inHg
  • Observation at 2:56 pm from KSGH, 10 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

19 documents, released by the NTSB on June 20, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.