FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN17FA071 · Columbia Aircraft MFG LC41 550FG

5 Jan 2017 · Gurdon, AR, United States

Columbia Aircraft MFG LC41 550FG · Accident: loss of control in flight en route

From McKinney National Airport (TKI) to Macon County Airport (1A5)

Report a problem

Event

NTSB case
CEN17FA071
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
N972JK
Operator
Unknown
Onboard fatalities
Unknown
Route
From McKinney National Airport (TKI), McKinney, TXTo Macon County Airport (1A5), Franklin, NC
Aircraft age
About 10 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
Loss of control in flight
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The private pilot and pilot-rated passenger were conducting a cross-country flight in the airplane. The pilot's communications with air traffic control (ATC) were unremarkable until the pilot requested an instrument flight rules (IFR) clearance to climb to 25,000 ft mean sea level (msl) to do an "equipment test"; at that time, the airplane was at a cruise level of 17,500 ft msl. The controller granted the pilot's request, and radar showed that the airplane climbed to 25,000 ft, where it remained for about 3 minutes and 25 seconds. The pilot then requested to descend to 17,500 ft, and the airplane started to descend before the controller could issue a clearance. The controller then cleared the pilot to descend to 19,000 ft and asked the pilot if everything was alright. The pilot responded that the airplane was experiencing an "equipment issue" and requested to cancel the IFR clearance. The controller cleared the pilot to descend and maintain 17,000 ft and asked if he needed assistance. The pilot responded that he was "okay for now." About 1 minute later, the pilot declared an emergency. the controller requested the pilot to state the nature of the emergency, but the pilot's response was unintelligible. The controller attempted to contact the airplane without success. Radar data showed that the airplane descended more than 17,000 ft in 2 minutes 12 seconds, and radar contact with the airplane was lost when the airplane descended to an altitude of about 3,100 feet.

The airplane impacted terrain in an almost-vertical nose-down orientation, and a postimpact fire ensued. The recovered airframe pieces were examined, but, due to the severe airframe fragmentation, flight control continuity could only be established from the rudder surface to overload separations on the control cables leading to the cockpit. One of the two speedbrake modules was found deployed. The airplane's fuel, environmental , anti-icing, and oxygen systems and cockpit gauges and instruments could not be examined due to severe impact and fire damage. Examinations of the engine, propeller, and turbochargers revealed no anomalies that would have precluded normal operation, and propeller signatures were consistent with low power at the time of impact.

According to weather information, the airplane was most likely not in clouds during the descent from 25,000 to about 6,000 ft, so airplane icing was not likely. The airplane would likely have been in clouds below 6,000 ft, but the airplane likely remained in visual meteorological conditions during that part of the descent and entered instrument meteorological condition immediately before impacting the terrain. The pilot radioed that the airplane was having "an equipment issue," but, due to the severe impact and postcrash fire damage to the airplane's systems, neither the specific equipment issue nor the reason why the airplane descended rapidly could be determined.

The pilot had evidence of use of amphetamine. However, because the blood results are from heart blood and amphetamine undergoes significant post mortem redistribution which may increase central levels (such as heart levels) by 3-8 times, the blood level cannot be used to determine whether the pilot was using the drug medicinally or abusing it. Similarly, the urine drug level of 7 could have been the result of either medicinal use or abuse. While it is likely that the pilot had some psychoactive effects from his use of amphetamine at the time of the accident, whether or not it was impairing could not be determined from this investigation. The pilot rated passenger's toxicology testing demonstrated evidence of previous use of marijuana. However, no active/parent THC was identified in brain. Since THC is stored in brain and can remain there for long periods, this indicates the pilot rated passenger's use of THC was likely several days before. It is therefore unlikely that the pilot rated passenger was impaired by his use of marijuana during the flight. Overall, it is unlikely the pilot rated passenger was impaired by his use of marijuana at some point prior to the accident. The investigation was unable to determine if the pilot's use of amphetamine was medicinal or misuse and was unable to determine from the available information whether its likely psychoactive effects, present during the flight, were impairing.

Probable cause

The loss of control in flight for reasons that could not be determined because of the severe impact and postcrash fire damage to the airplane and the lack of information about the airplane emergency that the pilot was experiencing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17FA071
Event ID
20170105X74726
Case number
CEN17FA071
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, coordinates. 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: aea5d58351b65785de69de5148178ff35183896c682f2783c20354e482759913; retrieved 2026-09-14T22:05:33.050Z.