Federal Express Flight 5080
McDonnell Douglas MD-11F · Accident: airframe, component or system failure on approach
From Suvarnabhumi Airport (BKK) to Subic Bay International Airport / Naval Air Station Cubi Point (SFS)
Event
- NTSB case
- DCA02MA042
- 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
- Accident
- 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
- 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
McDonnell Douglas MD-11F
- Aircraft type
- McDonnell Douglas MD-11
- 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
- N601FE
- Operator
- Federal Express
- Onboard fatalities
- Unknown
- Route
- From Suvarnabhumi Airport (BKK), BangkokTo Subic Bay International Airport / Naval Air Station Cubi Point (SFS), Subic Bay
- 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
- Substantial
Cause areas
- Flight control surfaces/attachments › Corroded
- Flight control, flap attachment › Separation
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
As the MD-11F airplane was on final approach to landing, the flight crew selected flaps 50 (full extension) and continued to approach the runway. About one minute later, the flight crew heard a loud bang and felt the airplane shudder. The airplane then began to roll to the left, and nearly full right control wheel input was required to counter the left roll. The flight crew performed a missed approach, declared an emergency, and diverted to another airport. During the landing, the airplane experienced a tailstrike. The flight control malfunction was initiated by the failure of the bolt assemblies securing the left inboard flap outboard hinge to the wing trailing edge. The lower outboard nut failed first due to stress corrosion cracking. The lower inboard bolt failure was initiated by fatigue and was completed by overload following the failure of the nut on the lower outboard bolt. The two upper bolts failed by overload following the failure of both lower bolt assemblies. The failure of all four bolt assemblies allowed the flap hinge to pull free from the wing trailing edge, drop and jam the left, inboard flap at the fully extended position. The separating flap hinge pulled the components of the left hand spoiler system from their original position resulting in the deployment of spoilers L1, L4, and L5. The deployment of three of the five left-hand spoilers caused the uncommanded left roll of the aircraft. Hydraulic system no. 3 was also damaged when the flap hinge separated allowing the hydraulic fluid to drain out of the system. Once the hydraulic quantity is depleted, the number three spoilers on each wing will not operate. According to Boeing engineers, the loss of the R3 spoiler would affect the ability of the right wing flight controls to counter the left roll of the aircraft. The airplane was originally used as a manufacturer flight test airplane. The impact of the flight-testing of the airplane to the overall fatigue life of the flap hinge bolts could not be determined. Prior to the accident, there were no requirements for the inspection of the flap hinge bolt assemblies on MD-11 aircraft. The manufacturer issued a service bulletin after the accident recommending inspection and/or replacement of the flap hinge, lower bolt assemblies. The bulletin recommends changing from alloy steel bolts and nuts to Inconel. Inconel is a nickel-based alloy that is highly resistant to general corrosion and stress corrosion cracking, which can occur in low alloy, high strength steel. The FAA issued an Airworthiness Directive mandating the Service Bulletin.
Probable cause
The failure of the lower outboard nut and bolt assembly of the left inboard flap's outboard hinge that resulted from stress corrosion cracking and fatigue. Factors contributing to the accident were the inadequate materials specification of the bolt, and inadequate inspection requirements for the assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA02MA042
- Event ID
- 20020718X01166
- Case number
- DCA02MA042
- 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. Values present in the bulk record are kept.
- The date is the UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: 875c21ac8a52be060019a165bb5e344a5c4bf90b8afd055017181d8ab8454fe8; retrieved 2026-09-18T16:02:23.314Z.