ERA16FA006 · Columbia Aircraft MFG LC41 550FG
Columbia Aircraft MFG LC41 550FG · Accident: windshear or thunderstorm en route
From McGhee Tyson Airport (TYS) to Monroe County Airport (BMG)
Event
- NTSB case
- ERA16FA006
- 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
- Unknown
- 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
Columbia Aircraft MFG LC41 550FG
- Aircraft type
- Columbia LC41
- 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
- N1058S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From McGhee Tyson Airport (TYS), Knoxville, TNTo Monroe County Airport (BMG), Bloomington, IN
- Aircraft age
- About 8 years (built 2007)
- 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
- 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
- Windshear or thunderstorm
- 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
- 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
The instrument-rated private pilot was on an instrument flight rules (IFR) cross-country flight; while en route, the pilot elected to divert to an intermediate airport to "check the weather." The pilot was subsequently provided a weather briefing that described a line of convective weather along the intended route of flight. The airplane departed about 45 minutes later and flew east along the south side of an east-west line of thunderstorms. The pilot was communicating with air traffic control, and when asked by the air traffic controller if he had onboard weather information, the pilot stated that he had NEXRAD. The airplane was equipped with satellite-delivered weather information service that was displayed in the cockpit, and it is likely that the pilot was referring to NEXRAD images provided by that system. The pilot requested and was granted permission to turn north in order to navigate through the line of storms toward his destination. Ground track and weather radar data revealed that the airplane penetrated a thunderstorm cell of strong intensity The pilot subsequently lost control of the airplane before it rapidly descended to ground impact.
The wreckage debris path was compact, and examination of the wreckage revealed extensive fragmentation and thermal damage. No preimpact mechanical malfunctions were noted that would have precluded normal operation of the airplane. The impact damage to the engine and propeller were consistent with the engine operating at a high power setting at the time of impact.
The satellite-delivered weather information likely being used by the pilot did not provide real-time weather radar images in the cockpit, with a delay between the time the weather was observed and when it was provided. It is likely that the pilot attempted to maneuver through the line of thunderstorms, but the time delay in the satellite-delivered weather data likely resulted in inadvertent penetration of a severe thunderstorm cell.
The investigation could not determine the color intensity of the precipitation being displayed to the pilot on cockpit avionics around the time of the accident. However, the most extreme color band that could have been shown would have been dark orange, which was classified as 55 dBZ. On the WSR-88D and satellite-delivered radar images, orange was classified as 40 dBZ. The WSR-88D Level 2 reflectivity product revealed that the weather reflectivity, around the accident location, ranged from 5 dBZ to 55 dBZ.
Postaccident toxicology testing revealed the presence of citalopram, an antidepressant medication, and ethanol. Citalopram is one of four medications that has been approved by the FAA for the treatment of depression. Personal medical records documented that the pilot's depression was well controlled with citalopram, and the pilot had no adverse effects from the medication. Therefore, there is no evidence that depression or the citalopram impaired the pilot's decision-making ability or his ability to safely operate the airplane. The ethanol detected was likely from postmortem production. Further, considering that the level of the ethanol was below a level that would be considered impairing, the ethanol detected did not impair the pilot nor contribute to the accident.
Probable cause
The pilot's decision to fly into a known area of adverse weather, which resulted in the airplane entering a severe thunderstorm and a subsequent loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA16FA006
- Event ID
- 20151010X62028
- Case number
- ERA16FA006
- 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: 34794769c272e83ee854f44ca0d9ec3495e46808b1c7e789743181413419ef5c; retrieved 2026-09-14T21:32:21.492Z.