American Airlines Boeing 727-200 incident
Boeing 727-200 · Incident: airframe, component or system failure on approach
From OKC Will Rogers World Airport (OKC) to Dallas Fort Worth International Airport (DFW)
Event
- NTSB case
- FTW88IA165
- 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
Boeing 727-200
- Aircraft type
- Boeing 727
- 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
- N710AA
- Operator
- American Airlines
- Onboard fatalities
- Unknown
- Route
- From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo Dallas Fort Worth International Airport (DFW)
- 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
- Approach · VFR pattern final
- 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
- Minor
Cause areas
- Landing gear, normal retraction/extension assembly › Failure, total
- Landing gear, normal retraction/extension assembly › Fatigue
- Manufacturer › Acft/equip, inadequate design
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
ACFT RECEIVED MINOR DAMAGE WHEN THE PLT EXECUTED AN EMERGENCY GEAR UP LANDING FOLLOWING THE FAILURE OF THE MLG TO EXTEND USING NORMAL, ABNORMAL, AND MANUAL PROCEDURES. ACFT WAS LANDED WITH THE NLG EXTENDED AND THE MAINS RETRACTED. INVESTIGATION REVEALED THAT THE LEFT MLG DOOR ACTUATOR PIVOT TRUNNION UPPER SHAFT HAD FAILED AS A RESULT OF A FATIGUE FRACTURE. FOLLOWING THE FRACTURE, THE SEPARATED SHAFT HAD BECOME JAMMED BETWEEN THE TRUNNION AND THE ACTUATOR CLEVIS WHICH PREVENTED THE MANUAL DOOR UNLOCK MECHANISM FROM RELEASING. A REVIEW OF THE SERVICE DIFFICULTY HISTORY OF THE FAILED PART INDICATED THAT SEVERAL SIMILAR FAILURES HAD OCCURRED ON MANUFACTURED PARTS AND THAT A REDESIGNED PART WAS AVAILABLE FOR REPLACEMENT. THE OPERATOR HAD COMPLIED WITH ALL OF THE REQUIRED INSP'S.
Probable cause
FATIGUE FAILURE OF THE LEFT MAIN LANDING GEAR DOOR ACTUATOR PIVOT TRUNNION SHAFT WHICH SUBSEQUENTLY BECAME LODGED IN THE ACTUATOR CLEVIS PREVENTING THE DOOR UNLOCK MECHANISM FROM ACTUATING DURING GEAR EXTENSION.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW88IA165
- Event ID
- 20001213X26834
- Case number
- FTW88IA165
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1988-09-22.
- API snapshot SHA-256: bfa79e87baaa28c12dac70d1baba1f37dc44fdec72bb495ffc19018781c500cd; retrieved 2026-09-18T19:18:25.806Z.