ASN Wikibase Occurrence # 188814
This record has been locked for editing.
| Date: | Friday 22 July 2016 |
| Time: | 10:40 |
| Type: |  Van's RV-9A |
| Owner/operator: | Private |
| Registration: | N807LK |
| MSN: | 91528 |
| Year of manufacture: | 2015 |
| Total airframe hrs: | 53 hours |
| Engine model: | Superior XP-320 |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | E of Springfield-Beckley Municipal Airport, OH -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Bristol/johnson/kingsport, TN (TRI) |
| Detroit/grosse Ile, MI (ONZ) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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
Probable Cause: The pilot’s decision to fly into known thunderstorms, which resulted in an in-flight breakup.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?nNumberTxt=807LK
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 22-Jul-2016 16:44 | Geno | Added |
| 22-Jul-2016 18:36 | Geno | Updated [Total fatalities, Total occupants, Other fatalities, Source, Narrative] |
| 23-Jul-2016 02:45 | Geno | Updated [Time, Aircraft type, Registration, Cn, Operator, Phase, Nature, Source, Damage, Narrative] |
| 23-Jul-2016 07:11 | junior sjc | Updated [Aircraft type] |
| 23-Jul-2016 11:27 | Aerossurance | Updated [Time, Location, Narrative] |
| 23-Jul-2016 13:50 | Geno | Updated [Time, Aircraft type, Registration, Cn, Operator, Phase, Nature, Source, Damage, Narrative] |
| 23-Jul-2016 15:19 | Aerossurance | Updated [Time, Location, Narrative] |
| 08-Sep-2017 19:48 | ASN Update Bot | Updated [Time, Aircraft type, Departure airport, Destination airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation