Columbia Aircraft Mfg LC41 550FG accident near Gurdon, Arkansas, January 5, 2017
On January 5, 2017 at about 6:39 pm local time, a 2007 Columbia Aircraft Mfg LC41 550FG, registered N972JK, was destroyed in an accident during enroute near Gurdon, Arkansas. 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 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.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 5, 2017 · about 6:39 pm local time
- Place
- Gurdon, Arkansas · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Columbia Aircraft Mfg LC41 550FG 550FG, built 2007 · all LC41 550FGs on the register
- Registration
- N972JK · no longer on the register · serial 41800
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
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
- Emergency descent initiated during enroute
- Loss of control in flight during enroute defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 250 hours in all; 100 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: fatal
Pilot-Rated Passenger
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 450 hours in all; 10 in this make and model
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: rgt
- Injury: fatal
The aircraft
- Airframe total time: 418 hours
- Last inspection: annual inspection, June 2, 2016; 93 hours since
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor TSIO-550-C (piston); 418 hours total
- Fire on the ground
The flight
- Departed from: TKI Mckinney TX at 5:45 pm
- Destination: 1A5 Franklin NC
- Flight plan: VFR then IFR
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 360° at 7 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 2,400 ft; clear
- Temperature: 37°F (3°C), dew point 28°F (-2°C)
- Altimeter: 30.01 inHg
- Observation at 4:56 pm from ADF, 15 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
22 documents, released by the NTSB on November 8, 2018. 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.
