CEN12IA554 · Cessna 560XL
Elliott Aviation Flight Services Cessna 560XL · Incident: flight control system malfunction/failure en route
From Flying Cloud Airport (FCM) to Arlington Municipal Airport (GKY)
Event
- NTSB case
- CEN12IA554
- 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
- Incident
- 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
- 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
Cessna 560XL
- Aircraft type
- Cessna 560
- 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
- N108EK
- Operator
- Elliott Aviation Flight Services
- Onboard fatalities
- Unknown
- Route
- From Flying Cloud Airport (FCM), Minneapolis, MNTo Arlington Municipal Airport (GKY), Arlington, TX
- Aircraft age
- Not recorded
- 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
- 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
- Minor
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight crewmembers reported that, after about 10 minutes of cruise flight at 40,000 ft pressure altitude, they observed an autopilot pitch trim mistrim annunciation and an associated master caution indication. As they began to reference the applicable checklist, the autopilot automatically disengaged, the airplane suddenly pitched down, and the airspeed increased to about 30 knots over the redline. The flight crew regained control of the airplane and then leveled it at 33,000 ft pressure altitude. The flight crew subsequently landed the airplane without further incident. The autopilot was not used after the temporary loss of airplane control; however, the electric pitch trim was used after passing through 10,000 ft mean sea level, and it functioned normally. A postincident examination of the autopilot, pitch trim systems, and horizontal stabilizer did not reveal any anomalies consistent with a loss of control.
Probable cause
A temporary loss of control during cruise flight for reasons that could not be determined because postincident examination of the autopilot, pitch trim systems, and horizontal stabilizer revealed no anomalies consistent with a loss of control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12IA554
- Event ID
- 20120820X02558
- Case number
- CEN12IA554
- 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: 68cbc0e3743e7954b0a8e0bec839f5c81fd6cb5a5ddbb19859a4eb810491f065; retrieved 2026-09-15T19:25:36.321Z.