FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA15IA008 · Cessna S550 CITATION I

4 Oct 2014 · Tampa, FL, United States

Gulf Atlantic Airways Cessna S550 CITATION I · Incident: flight control system malfunction/failure during takeoff

From Tampa International Airport (TPA) to Gainesville Regional Airport (GNV)

Report a problem

Event

NTSB case
ERA15IA008
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 S550 CITATION I

Aircraft type
Cessna 550
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
N550AJ
Onboard fatalities
Unknown
Route
From Tampa International Airport (TPA), Tampa, FLTo Gainesville Regional Airport (GNV), Gainesville, FL
Aircraft age
About 27 years (built 1987)
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
None

Cause areas

  • Aircraft › Aircraft systems
  • 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

The airline transport pilot and commercial-rated copilot, who was the pilot flying, were conducting a positioning flight. The copilot reported that, during takeoff when the airplane was at 400 ft, he retracted the flaps and turned right for the published departure procedure. He noted that, during the turn, the controls were stiff, and he was feeling pushback. Both pilots then began pushing on the control yoke, and the copilot tried to use both the electric and manual pitch trim to reduce the control forces without success. He then engaged the trim disconnect and pulled the pitch trim circuit breaker, but the secondary pitch trim was still frozen. He again attempted to use the manual pitch trim without success. The copilot subsequently declared an emergency with air traffic control, returned to the airport, and landed uneventfully.

During postincident troubleshooting of the pitch trim system anomaly, the left screw of the left elevator trim tab actuator was removed, cleaned, regreased, and then reinstalled. Subsequently, the primary and secondary sprockets were found separated from the left internal screw, which was fractured due to overstress; no evidence of a preexisting fracture was noted. The two actuator shaft assemblies were examined, and both assemblies were missing flat roller bearings. Maintenance records indicated that the actuator was newly installed over 24 years, or 6,560 flight hours, before the accident and had not been disassembled since that time. Given that fresh grease was found in the actuator in an area that normal maintenance is not performed, it is likely that undocumented maintenance was conducted on the actuator at some point and that the missing bearings were not reinstalled at that time.

The maintenance records also revealed that the pitch trim actuator was last lubricated as part of a phase 2 inspection about 1 year 7 months, or 197 flight hours, before the accident, which was within limits; the process did not require the removal of the left internal screw from the actuator housing. Although postincident troubleshooting precluded the determination of the amount and condition of the grease on the left internal screw, it is likely that maintenance personnel did not adequately lubricate the left elevator trim tab actuator during this inspection. Therefore, it is likely that excessive play caused by the missing bearings, which resulted in wear, and the inadequate lubrication of the left elevator trim tab actuator caused the overstress fracture of the left internal screw and the subsequent failure of the pitch trim system.

Probable cause

The lack of flat roller bearings in the two elevator trim tab actuators and maintenance personnel’s inadequate lubrication of the left elevator trim tab actuator, both of which resulted in the overstress fracture of the left internal screw and subsequent in-flight failure of the pitch trim system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA15IA008
Event ID
20141006X40044
Case number
ERA15IA008
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, 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: 5c038f869e0f2617ede75317f8c43751cf9d94474f48d0a32cbd4b3623587f07; retrieved 2026-09-16T01:49:54.692Z.