UPS told federal investigators it relied on Boeing's maintenance guidance when it chose not to adopt enhanced inspection protocols for the aging MD-11 cargo jet that broke apart on takeoff from Louisville last November, killing 15 people and scattering wreckage across a half-mile stretch of industrial buildings south of the airport.
The disclosure, first reported by Fox Business, places Boeing squarely alongside UPS in the growing accountability debate over Flight 2976. It also sharpens a question regulators will have to answer: whether the manufacturer's recommended intervals for checking engine-pylon hardware on the decades-old trijet were dangerously out of step with the fleet's actual condition.
The stakes extend well beyond one company or one airframe. The MD-11 fleet, operated by UPS, FedEx, and Western Global Airlines, was grounded for months after the crash. The FAA and NTSB are now reexamining whether the inspection cycle that governed those planes left a known structural weak point unchecked for far too long.
UPS Flight 2976, a 34-year-old McDonnell Douglas MD-11F loaded with tens of thousands of gallons of jet fuel for the roughly 8.5-hour run to Honolulu, lifted off from Louisville Muhammad Ali International Airport at approximately 5:14 p.m. ET on November 4, 2025. Seconds later, the left engine and its pylon separated from the wing.
Video released months later by the NTSB captured the moment the engine tore free. The aircraft, unable to gain altitude, crashed onto the roof of the Kentucky Petroleum Recycling building just beyond the airport perimeter, triggering a massive fireball visible for miles. Debris and flames spread across the surrounding industrial zone.
Three crew members died: Capt. Richard Wartenberg, First Officer Lee Truitt, and International Relief Officer Capt. Dana Diamond. Twelve people on the ground were also killed, including a 3-year-old child. At least 11 others sustained injuries, some described by officials as "very significant."
Kentucky Gov. Andy Beshear addressed reporters that evening, urging residents to stay away from the site.
"Anybody who has seen the images, the video, knows how violent this crash is."
Beshear also confirmed that at least two employees at Grade A Auto Parts, a business near the crash site, were unaccounted for in the hours after impact. A shelter-in-place order covered all areas within five miles of the airport, as Just The News reported at the time.
The NTSB's preliminary findings zeroed in on a structural failure that former crash investigators said should alarm anyone familiar with the MD-11's history. Federal examiners found evidence of cracks in the left wing's engine mount, the hardware that holds the massive powerplant to the airframe.
Critically, the aircraft was not yet due for a detailed inspection of those engine-mount components. AP News reported that the plane still had nearly 7,000 more takeoff-and-landing cycles before the next scheduled check under the existing maintenance framework.
Former federal crash investigator Jeff Guzzetti told AP that UPS appeared to have followed the rules as written.
"It appears UPS was conducting this maintenance within the required time frame, but I'm sure the FAA is now going to ponder whether that time frame is adequate."
That observation cuts to the heart of the UPS defense. If the company followed Boeing's guidance and the FAA-approved intervals, the question shifts from whether UPS broke the rules to whether the rules themselves were broken. UPS has pointed to Boeing's maintenance recommendations as the basis for its decision not to adopt more aggressive inspection schedules that some operators had voluntarily embraced.
Former federal crash investigator Alan Diehl was blunter about the structural problem. "It is clear that engine pylon attachment failures are these aircraft's Achilles' heels," Diehl said.
The MD-11, a wide-body trijet derived from the DC-10, has a long and troubled history with engine-pylon separations. The design places one engine on each wing and a third at the base of the vertical tail. Pylon failures on the DC-10 contributed to some of the worst disasters in American aviation history, and the MD-11's structural lineage has kept that concern alive among safety analysts for decades.
The question facing regulators now is whether Boeing, as the successor to McDonnell Douglas and the entity responsible for continued airworthiness guidance, set inspection intervals that accounted for the realities of an aging fleet. A 34-year-old airframe accumulates fatigue in ways that a newer one does not. Whether Boeing's guidance adequately reflected that aging process is a central issue in the ongoing investigation.
The FAA's decision to ground all MD-11s operated by UPS, FedEx, and Western Global Airlines after the crash suggests regulators themselves recognized the potential for a fleet-wide problem, not an isolated failure on a single jet. The New York Post reported that the grounding lasted months while inspections and repairs were carried out across the remaining fleet.
Flight 2976 marked UPS's first fatal crash in more than 12 years. The company's previous fatal incidents occurred in Dubai in 2010 and in Birmingham, Alabama, in 2013, as the Washington Examiner noted. Both involved cargo operations. The Birmingham crash, which killed the two-person crew of a UPS Airbus A300, led to significant changes in pilot fatigue rules and approach procedures.
Louisville serves as UPS's global air hub, the nerve center of its overnight package-sorting operation. Hundreds of flights move through the facility each day, and the MD-11 has been a workhorse of the company's long-haul cargo network. The fleet's age, combined with the punishing cycle counts that come with daily freight operations, makes the inspection-interval question especially pointed.
The legal landscape around corporate liability in transportation disasters has drawn increasing attention in recent years. The Supreme Court unanimously ruled that crash victims can sue freight brokers that hired dangerous operators, a decision that expanded the reach of accountability beyond the party directly at the controls. The UPS case raises a parallel question: when a carrier follows the manufacturer's guidance and that guidance proves fatally inadequate, where does liability land?
The NTSB convened a hearing in Washington, D.C., to examine the crash, a step the board reserves for its most consequential investigations. The hearing's scope includes UPS's maintenance practices, Boeing's airworthiness directives, and the FAA's oversight of aging cargo fleets.
For the FAA, the crash presents an uncomfortable institutional question. The agency approved the inspection intervals that UPS followed. If those intervals left a known failure mode undetected on a 34-year-old airframe, the FAA's own certification process is implicated alongside Boeing's engineering and UPS's maintenance decisions.
Federal regulators have not been shy about holding airlines accountable for safety lapses in other contexts. The FAA recently proposed fines against American Airlines and Southwest over drug and alcohol testing failures, demonstrating a willingness to act when carriers fall short of safety mandates. But the UPS case is different in kind. Here, the carrier says it met the mandates. The mandates themselves may have been the problem.
Aviation disasters involving corporate operators often generate sprawling civil litigation alongside federal investigations. Families of victims in fatal crashes have pursued wrongful death claims running into the tens of millions, as seen in recent high-profile crash lawsuits against estates and operators. The 15 fatalities from Flight 2976, including a toddler and a dozen people who were simply at work in nearby buildings, guarantee that the civil exposure for UPS and potentially Boeing will be enormous.
Several critical questions remain unresolved. Investigators have not publicly confirmed whether the cracks found in the engine mount were the sole cause of the pylon separation or whether other factors, such as corrosion, improper repair history, or material defects, contributed. The NTSB has not issued a final probable-cause determination.
Authorities have also not said whether Boeing had internal data suggesting the existing inspection intervals were insufficient for high-cycle cargo operations. If such data existed and was not acted upon, the manufacturer's legal exposure would intensify dramatically.
The FAA has not announced whether it will permanently revise MD-11 inspection requirements or issue new airworthiness directives based on the fleet-wide checks conducted during the grounding. Those decisions will shape whether the remaining MD-11s continue flying cargo routes or face accelerated retirement.
Fatal aviation crashes involving aging aircraft and disputed maintenance responsibilities tend to produce years of litigation and regulatory revision. The Flight 2976 investigation is still in its early stages, and the final accounting of what went wrong, and who bears responsibility, could take years to resolve.
UPS's defense rests on a simple proposition: the company followed Boeing's guidance, and that guidance was endorsed by the FAA. If the inspection schedule was inadequate, UPS argues, the fault lies upstream with the manufacturer and the regulator, not the operator.
Boeing has not publicly responded to UPS's characterization. The manufacturer's silence leaves a gap that investigators and plaintiffs' attorneys will work to fill. Whether Boeing's maintenance recommendations reflected the best available engineering judgment or lagged behind what the aging fleet required is a factual question the NTSB hearing is designed to answer.
Fifteen people are dead because an engine fell off a cargo jet during takeoff. Someone set the rules that let cracks go undetected on a plane still thousands of cycles from its next check. The public deserves to know who wrote those rules, who approved them, and whether anyone raised a flag before Flight 2976 became the answer to a question that should have been asked years ago.
