CEN21LA107 · Hawker Beechcraft Corp G58
Hawker Beechcraft Corp G58 · Accident: loss of engine power (partial) en route
From Jonesboro Municipal Airport (JBR) to Conway Regional Airport (CXW)
Event
- NTSB case
- CEN21LA107
- 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
Hawker Beechcraft Corp G58
- Aircraft type
- Beechcraft 58
- 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
- N325GC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jonesboro Municipal Airport (JBR), Jonesboro, ARTo Conway Regional Airport (CXW), Conway, AR
- Aircraft age
- About 14 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 engine power (partial)
- 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 power plant
- Not determined › Not determined
- Personnel issues › Action/decision
- Personnel issues › Physical
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot and passenger departed in the airplane for a business flight. After departure, the airplane flew southwest, climbed to about 2,300 ft above mean sea level, and started to descend. The flight continued to track southwest then it turned right to the northwest. The airplane’s flight track was lost about 10 minutes after takeoff at a location consistent with the accident site.
A pilot who took off behind the accident airplane reported that the runup and takeoff appeared normal. Several witnesses reported hearing and seeing the airplane prior to the accident. They described the airplane as flying low and the engines as not “sounding good” and that they were making “popping” noises.” One witness stated that it sounded like one engine was operating and the other engine was “sputtering”, before both engines quit.
A witness near the accident site reported that it sounded like one engine was operating and that the other engine alternately sounded as if it was making a “sputtering” sound and operating normally. Shortly after, it sounded like the engines quit. He said the airplane flew parallel to the high-tension powerlines at an altitude of an aerial application airplane. Another witness near the accident site, observed the airplane fly over his location about 1,000 ft agl, traveling east to west. He said the engines were “popping and sputtering” and making a “backfiring noise.”
Postaccident examination of the airframe revealed no anomalies. Blade A of the left propeller was separated from overstress while blade B and C were straight and unremarkable, and the leading edges were unremarkable. The left propeller was against the start lock and at approximately 18° of pitch at impact, consistent with a loss of engine power to the left engine.
An examination of the engines revealed all the fuel lines were thermally damaged. The left fuel servo screen was found to be about halfway obstructed and contaminated with an unknown black debris. Postaccident testing of the debris revealed similarities with materials used in aircraft fuel system components, particularly with hoses. It is likely the debris on the screen was soot from the postimpact fire and it could not be determined where and when the polymer signatures originated from.
Based on the available evidence, it is likely the left engine lost power while in flight. The witnesses reported hearing noises consistent with an engine misfiring and it likely was losing power; however, the reason for the loss of engine power could not be determined. Based on the flight track, it is likely the pilot attempted to perform a forced landing with one engine inoperative.
Given the variety of levels of ethanol and the absence of any in the pilot’s liver, it is most likely that the identified ethanol is from postmortem production rather than ingestion. The pilot’s previous use of cocaine (which often leads to withdrawal effects) and his simultaneous use of a large amount of butalbital and a small amount of temazepam were likely significantly impairing at the time of the accident and likely contributed to his inability to respond appropriately to the left engine’s loss of power.
Probable cause
A loss of left engine power for undetermined reasons, which resulted in an emergency descent with one engine inoperative and inadvertent collision with transmission lines. Contributing to the accident was the pilot’s inability to respond appropriately to the emergency due to impairment from his previous use of cocaine and multiple other impairing drugs.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN21LA107
- Event ID
- 20210104102486
- Case number
- CEN21LA107
- 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, cause areas. 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: b2f81cd828c1686d7d2bffda889acf9bc0862657e7fd35618e6b3c227948111f; retrieved 2026-09-15T07:24:07.629Z.