FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN24LA115 · Beech 400 A

14 Feb 2024 · Bentonville, AR, United States

Pdii Beech 400 A · Accident: flight control system malfunction/failure during takeoff

From an unrecorded airport to Concord-Padgett Regional Airport (KJQF)

Report a problem

Event

NTSB case
CEN24LA115
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
0 · 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 400 A

Aircraft type
Beechcraft 400
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
N95GK
Operator
Pdii
Onboard fatalities
Unknown
Route
From not recordedTo Concord-Padgett Regional Airport (KJQF), Concord, NC
Aircraft age
About 33 years (built 1991)
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
Takeoff
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
Flight control system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

During the takeoff the pilot pulled the airplane’s control yoke aft to rotate and the airplane lifted off the runway as normal. The nose of the airplane dropped, and the pilot applied additional backpressure on the yoke. The pilot reported he felt a “snap” followed by a lack of tension on the control yoke. The airplane pitched down and settled back on the runway. The pilot applied maximum braking and full thrust reverse; however, the airplane continued off the end of the runway. The pilot applied left rudder and brake to turn the airplane to avoid contacting a gas station. The landing gear collapsed during the turn, which resulted in substantial damage to the right wing when it struck the ground. A postaccident examination of the airplane revealed the elevator control cable was fractured at a pulley bracket near the aft portion of the fuselage where the cable transitioned from a horizontal to a vertical orientation. A metallurgical examination found nearly all the wires of the cable had rubbing damage to varying extents around the sides of the wires near the fracture. The upper guard pin exhibited wear, scratch marks, and gouges. The pulley contained several isolated wire fragments. The damage on the cable, upper guard pin on the pulley, and the pulley assembly was consistent with the cable having been improperly routed on the wrong side of the upper guard pin. Over time, the cable likely rubbed against the upper guard pin until the cable was sufficiently damaged to produce failure under normal operating loads. A review of the maintenance logbook entries found that the elevator cable was replaced about a year before the accident and that the airplane flew about 316.5 hours before the cable separated.

Probable cause

Improper rigging of the elevator cable over the upper guard pin, which resulted in a cable separation and loss of elevator control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN24LA115
Event ID
20240215193801
Case number
CEN24LA115
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: 05d454512605273aa1d8d98d45ef2d04dade9abb6312efa6e49ad18af7ffde32; retrieved 2026-09-16T18:30:59.718Z.