FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA058 · Beech 35-C33

7 Dec 2023 · Pulaski, TN, United States

Beech 35-C33 · Accident: loss of control in flight en route

From Knoxville Downtown Island Airport (DKX) to Saline County Regional Airport (SUZ)

Report a problem

Event

NTSB case
ERA24FA058
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

Beech 35-C33

Aircraft type
Beechcraft 35
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
N5891J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Knoxville Downtown Island Airport (DKX), Knoxville, TNTo Saline County Regional Airport (SUZ), Benton, AR
Aircraft age
About 58 years (built 1965)
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 · cruise
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

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

NTSB narrative

After departure on a 430-nautical mile (nm) cross-country flight, initial controller-pilot communications and headings were unremarkable. However, as the airplane climbed through 6,500 ft mean sea level (msl) and became established enroute, a performance study of ADS-B data showed that the airplane’s altitude and airspeed began to vary as the airplane repeatedly descended and climbed with fluctuating airspeeds. These oscillations became increasingly more severe over about 25 minutes, with altitude deviations up to 1,500 ft and significant fluctuations in airspeed. An air traffic controller advised the pilot that the airplane was left of course; although the pilot acknowledged the controller, the deviations continued to worsen and the pilot stopped responding to radio calls. Faint emergency transmissions were later received from the pilot and passenger as the airplane continued to descend. During the final portion of the flight, the airplane exceeded a descent rate of 10,000 ft per minute with a groundspeed of about 228 knots before terrain impact. The increasing altitude and heading deviations, loss of communication, and rapid uncontrolled descent were consistent with a loss of airplane control. Flight instructors who had flown with the pilot before the accident indicated that she routinely demonstrated poor manual aircraft handling and struggled with cockpit automation, including autopilot and trim use. The pilot’s training history showed that she had demonstrated difficulty maintaining situational awareness, suggesting the high-performance airplane she had purchased about 1.5 years before the accident was beyond her level of pilot proficiency, something explicitly noted by one of the instructors who had flown with her. Postaccident examination of the airplane wreckage did not reveal evidence of any anomalies or mechanical irregularities that would have precluded normal operation, though the degree of fragmentation and fire damage precluded a complete evaluation of the airplane’s flight controls and autopilot system. Given the airplane’s heading was stable during the initial portion of the flight, it is likely that the pilot had been using the autopilot. Based on the pilot’s reported misunderstanding of that system, including, but not limited to the autopilot’s pitch inputs and the requirement for manual pitch trim application, it is possible that the pilot inadvertently mis-trimmed the airplane, which resulted in oscillations that were exacerbated by the pilot’s application of force on the control yoke. These kinds of pilot-induced oscillations can occur when manual yoke or pitch trim inputs are in conflict with the autopilot's pitch control inputs, leading to delayed, or out-of-sync, corrections, rather than a smooth, constant altitude hold. The airplane’s vertical profile as evidenced by the ADS-B data, was consistent with these kinds of pilot-induced oscillations. As the oscillations became stronger, the pilot may have ultimately been unable to control the airplane’s pitch, even with the autopilot disengaged, resulting in the loss of airplane control. Toxicology results indicated that the pilot had used a combination of medications that may be used to treat conditions such as anxiety and depression, which may have performance-impairing effects. However, no details about any associated underlying conditions were available from reviewed records. Additionally, the medications trazodone, alprazolam, and buspirone may cause psychomotor and cognitive impairment such as slowed reaction time, diminished situational awareness, and sedation. However, due to the extent of the pilot’s injuries, measurement of drug levels was limited to tissue specimens only, preventing reliable comparison to antemortem reference ranges in blood. Overall, the pilot may have been experiencing impairing effects of medication use or an associated underlying condition at the time of the accident, and such effects may have diminished her ability to render effective control inputs. However, available medical and circumstantial evidence was insufficient to establish whether such effects contributed to the accident, particularly given the pilot’s demonstrated baseline proficiency in the high-performance airplane.

Probable cause

The pilot’s failure to maintain airplane control, which resulted in pilot-induced oscillations and a subsequent loss of control and impact with terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA058
Event ID
20231207193491
Case number
ERA24FA058
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, 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: ee6a7c3c7bcd9e73cdeaee84e49d51acd1f7ffec5fbb27416852c216e13fd940; retrieved 2026-09-15T08:08:58.258Z.