Full Breakdown
UPS MD-11 Crash Highlights Flaws in Engine-Mount Inspection Regime
5/21/2026, 4:12:39 AM
Incident Overview
On 4 November 2025 a United Parcel Service (UPS) cargo MD-11 crashed while accelerating for take-off at Louisville’s Muhammad Ali International Airport. The left engine and its pylon separated from the wing, causing the aircraft to strike the runway and explode. All three pilots and 12 people on the ground were killed; 23 others were injured. Investigators identified failure of a steel bearing and metal sheath within the engine-mount assembly as the initiating event.
Inspection Schedule History and Boeing’s Request
The MD-11’s engine-mount bearings sit deep near the pylons and require engine removal for visual inspection. The Federal Aviation Administration (FAA) originally mandated detailed inspections every 19,900 take-off/landing cycles. In 2015 Boeing petitioned to extend the interval to 29,260 cycles, citing data that pre-dated the aircraft’s 1980s certification and did not incorporate seven documented bearing-failure incidents on the same model. The FAA approved the request after a one-month review without requesting additional testing or information.
Key Stakeholders and Their Roles
- Boeing – Manufacturer that submitted the extended-interval proposal and supplied service letters on bearing issues.
- FAA – Regulator that authorized the schedule change and later approved Boeing’s corrective plan for bearing replacement every 4,000 cycles.
- NTSB – Investigative body conducting the crash inquiry, releasing video evidence and over 2,000 pages of documents.
- UPS – Operator of the crashed aircraft.
- Greg Raiff – Owner of Elevate Aviation Group, representing airline-maintenance perspectives.
- Jennifer Homendy – NTSB Chairwoman.
- Jeff Guzzetti – Aviation-safety expert.
- Justin Konopaske – Boeing’s Director of Airframe Service Engineering.
Data on Bearing Failures and Cycle Limits
- The crashed aircraft had accumulated 21,043 cycles, exceeding the original 19,900-cycle inspection point but still below the relaxed 29,260-cycle threshold.
- Seven bearing-failure reports existed before the original limit; three additional failures occurred after the schedule was extended, all before the crash.
- Documented problems from 2002-2009 occurred between 6,058 and 13,650 cycles.
- Only one other engine-separation accident involving a similar model occurred decades earlier, attributed to improper maintenance rather than bearing failure.
Official Statements & Responses
NTSB Chairwoman Homendy criticized the FAA for not demanding further data or testing when Boeing sought the interval extension, noting that Boeing had already issued service letters on the issue. Boeing’s Konopaske acknowledged that transparency was essential and that the company could not confirm whether bearing failures were considered in the 2015 discussion. Safety analyst Guzzetti emphasized that safety is a shared responsibility among airline, manufacturer, and regulator. Raiff asserted that operators follow federally approved maintenance programs and are not expected to redesign inspection schedules. The FAA, after reviewing Boeing’s corrective plan, authorized regular bearing replacement every 4,000 cycles and cleared FedEx to resume MD-11 operations.
Criticism & Opposition
Critics argue that the FAA’s reliance on outdated data and a brief review process allowed a known defect to persist unchecked. Boeing’s failure to fully disclose bearing-failure histories to regulators is cited as a breach of industry transparency norms. The relaxed inspection interval is viewed as prioritizing operational efficiency over safety, especially given the difficulty of detecting bearing wear without engine removal.
Impact and Future Safeguards
The crash has prompted a reassessment of inspection intervals for aging aircraft. Boeing’s new plan mandates spherical-bearing replacement after every 4,000 cycles, a substantially shorter interval than the previously approved 29,260 cycles. The FAA’s endorsement of this plan aims to prevent recurrence. The NTSB’s ongoing investigation, expected to culminate in a final report by late 2026 or early 2027, will likely shape future regulatory guidance for legacy airframes.
Conflicting Reports & Gaps
Sources differ on the exact number of pre-crash bearing failures: seven were reported before the original limit, while three occurred after the interval change, but detailed failure descriptions remain undisclosed. Additionally, the NTSB has not yet released its final findings, leaving open questions about other contributing factors beyond the bearing defect.
Verbatim Quotes
- “Safety is a shared responsibility between the airline, the manufacturer, and the regulator. And the NTSB is attempting to parse out the roles and responsibilities of each of those three entities,” — Jeff Guzzetti, Aviation-Safety Expert
- “I’m confused on why you wouldn’t ask for more information, more testing, and why you would just accept information that Boeing provided in the late 80s during certification, 30 years earlier basically,” — Jennifer Homendy, NTSB Chairwoman
- “I would not expect UPS or any other operator to do it unless it’s specifically on the manufacturer’s design maintenance programs,” — Greg Raiff, Elevate Aviation Group Owner
- “I believe transparency is critical in that process. I don’t know what the engineers were considering or how they were considering, or if they considered those bearing failures in that discussion, I can’t say,” — Justin Konopaske, Boeing Director of Airframe Service Engineering
What’s Next
The FAA will monitor compliance with the 4,000-cycle bearing-replacement schedule across all MD-11 operators. FedEx has resumed flights under the new regime. The NTSB’s final report, anticipated by late 2026 or early 2027, will detail additional safety recommendations and may prompt broader regulatory reforms for legacy cargo aircraft.
