Gulfstream Int'L Airlines Flight 427A
Short Brothers SD3-60 · Incident: airframe, component or system failure during initial climb
From Miami International Airport (MIA) to Orlando International Airport (MCO)
Event
- NTSB case
- MIA96IA146
- 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
- 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
- Airline
- 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
Short Brothers SD3-60
- Aircraft type
- Short Brothers SD3
- 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
- N826BE
- Operator
- Gulfstream Int'L Airlines
- Onboard fatalities
- Unknown
- Route
- From Miami International Airport (MIA)To Orlando International Airport (MCO), Orlando, FL
- 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 121: Air Carrier
- 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
- Initial climb
- First occurrenceThe 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
- Airframe, component or system 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
- Flt control syst, elevator trim/tab control › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The captain stated that the elevator trim worked fine during preflight inspection, and was set for takeoff. With the first officer flying the airplane after takeoff, while climbing through 300 feet, the elevator trim cable failed. The captain assisted the first officer, and the flight returned and landed uneventfully. Examination of the airplane revealed that an elevator trim cable failed due to fatigue about 18 inches forward of a turnbuckle and just aft of a pulley where a 45-degree change in direction occurred. The cable was required to be inspected every 1,460 days or 4,800 hours. At the time of the failure, the cable had accumulated 1,679.4 hours and 2,017 cycles, since last inspection 573 days earlier, and a total of 10,953.0 hours and 16,193 cycles, since new.
Probable cause
fatigue failure of a segment of the elevator trim cable.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA96IA146
- Event ID
- 20001208X06060
- Case number
- MIA96IA146
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: c58724cfeca1a06fe5b8e3d38640d606a1e1d8fd349509bdd54d2bb470441560; retrieved 2026-09-18T17:50:21.976Z.