FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN16LA281 · Vans RV9 A

22 Jul 2016 · Springfield, OH, United States

Vans RV9 A · Accident: inflight upset en route

From Tri-Cities Regional TN/VA Airport (TRI) to Grosse Ile Municipal Airport (ONZ)

Report a problem

Event

NTSB case
CEN16LA281
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Vans RV9 A

Aircraft type
Vans RV9
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N807LK
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tri-Cities Regional TN/VA Airport (TRI), BRISTOL/JOHNSON/KINGSPORT, TNTo Grosse Ile Municipal Airport (ONZ), DETROIT/GROSSE ILE, MI
Aircraft age
About 1 year (built 2015)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Inflight upset
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft structures
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN16LA281
Event ID
20160722X63338
Case number
CEN16LA281
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 880e6d12ad92b1c1d61c10c9ce270360d6078ac0ead5f74a55b668f583a9d395; retrieved 2026-09-14T21:56:10.584Z.