ERA13IA114 · Cessna 560XL
NetJets Aviation Cessna 560XL · Incident: flight control system malfunction/failure en route
From Treasure Coast International Airport (FPR) to DeKalb Peachtree Airport (PDK)
Event
- NTSB case
- ERA13IA114
- 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
- N662QS
- Operator
- NetJets Aviation
- Onboard fatalities
- Unknown
- Route
- From Treasure Coast International Airport (FPR), Fort Pierce, FLTo DeKalb Peachtree Airport (PDK), Atlanta, GA
- 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 Subpart K: Fractional
- 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 · climb to 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
- None
Cause areas
- Environmental issues › Physical environment
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight departed uneventfully and was climbing to their planned cruise altitude. As the airplane climbed through FL350 at a rate of 1,000 feet per minute (fpm) and with the autopilot engaged, the airplane pitched nose-down and entered a 400-fpm descent. The flight crew then disconnected the autopilot, assumed manual control of the airplane, and leveled at FL350. Both crewmembers noted that "excessive" force was required to change the pitch of the airplane, and subsequently notified air traffic control of the situation. The crew then requested a descent, and noted that both trim and manual elevator control inputs would result in an exaggerated pitch response from the airplane. Upon descending through FL180, the crew felt that something "broke loose" and the elevator controls began to respond normally. The crew subsequently re-engaged the autopilot and continued to the planned destination uneventfully.
Post-incident examination of the airplane revealed that several of the fuselage bilge drain holes were partially or totally obstructed, allowing water to accumulate within the bilge and in areas adjacent to elevator control cables and pulleys. Several of the pulleys exhibited evidence of saturation with moisture, and two of the pulleys' bearings had seized completely and displayed evidence that the control cable had subsequently worn their grooves. Additionally, seals designed to limit the entry of moisture within the tail area were not trimmed according to the published installation procedure. As a result of the findings of the investigation, the airframe manufacturer and operator each implemented a revised inspection and cleaning program to ensure the proper drainage of moisture from the tailcone and fuselage bilge areas.
Probable cause
An accumulation of debris in the airplane’s bilge drain holes that prevented accumulated moisture from properly draining; the accumulated moisture subsequently froze around the elevator control components, which resulted in the flight control stiffness. Contributing to the accident was maintenance personnel’s improper installation of seals in the airplane’s tailcone, which allowed water to enter the tailcone.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13IA114
- Event ID
- 20130114X25958
- Case number
- ERA13IA114
- 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, damage. 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: c83888e6df0cf1598b592d4a88dc50e5b5cf0e56c04abccd688132ee5b9342d7; retrieved 2026-09-15T20:44:35.193Z.