“What options remain when the decision speed is already behind you?” That question is at the heart of the National Transportation Safety Board’s early findings into last week’s catastrophic crash of a UPS McDonnell Douglas MD-11F in Louisville, Kentucky, which killed 14 people, including all three pilots.
The CVR data indicates that, about 37 seconds after the crew called for takeoff thrust, a sustained bell started ringing in the cockpit and continued for 25 seconds until the end of the recording, believed to be with impact. According to NTSB board member Todd Inman, the bell was not an undifferentiated alarm tone but a chime repeating in a distinct pattern, consistent with certain aircraft warnings. Investigators have not definitely identified a cause yet, but Jeff Guzzetti, a former federal crash investigator, said, “It occurred at a point in the takeoff where they were likely past their decision speed to abort the takeoff.”
That decision speed, referred to as V1, is an important performance parameter in transport-category aircraft. Below V1, a rejected takeoff can be conducted within the available runway distance. Above it, the aircraft is committed to fly, even with an engine failure. The MD-11F calculates V1 before each departure based on weight, runway length, weather, and aircraft performance data. Once past V1, the crew’s only option is to continue the takeoff and attempt to handle the emergency airborne.
The MD-11’s No. 1 engine – mounted on the left wing – was already burning when the bell began sounding. Video from Atlanta airport CCTV and bystanders clearly shows the engine detaching during the takeoff roll. Inman confirmed the pylon, the structural assembly connecting the engine to the wing, was attached to the engine when it separated. That is an important detail because engine mounts are designed with frangible fuse pins that allow the mounting structure to separate under extreme load or vibration to protect against the engine tearing away critical wing structure. In this case, investigators will be investigating whether the separation sequence compromised the wing fuel tank – potentially intensifying the fire.
The MD-11 is powered by three General Electric CF6-80C2D1F turbofan engines. Although the CF6 family has a long service history, other variants have been involved in uncontained failures, including a 2016 Chicago incident in which a ruptured turbine disk punctured a fuel tank. The recovered fan blades and engine core components will be analysed by the NTSB powerplants group for signs of fatigue, foreign object damage or metallurgical anomalies.
The MD-11 has dual-loop detectors in each engine nacelle and Halon-based extinguishing bottles. The fire warning initiates both an aural alarm on the flight deck and visual indications that alert the crew to conduct the engine fire checklist: retard the thrust lever, shut off fuel, and discharge extinguishers. In this accident, the short duration from the beginning of the warning until impact indicates that the crew had little time to complete these steps before losing control.
Flight data reveals the aircraft reached around 210 mph, climbing only to around 100 ft above ground before descending into nearby businesses, striking Kentucky Petroleum Recycling and Grade A Auto Parts. The debris field extends for half a mile, and investigators have mapped it using LiDAR scanning to reconstruct the breakup sequence. Recovered near the runway were the left engine’s main assembly and multiple fan blade fragments.
The aircraft, which was built in 1991 and converted to a freighter, had undergone a heavy maintenance check in San Antonio between September and October. All maintenance records, including job cards and inspection sign-offs, are being reviewed. The NTSB has also requested a similar UPS MD-11 with the same engine configuration for comparative analysis and simulator runs to model cockpit scenarios matching the CVR timeline. As investigations continue, synchronising the multi-angle video evidence from phones, vehicle dashcams, and security cameras with flight data refines the sequence of events.
The CVR, along with the over 400 parameters available through the flight data recorder, will allow investigators to determine whether the fire began within the engine, the pylon structure, or the wing itself, and the speed at which it spread to structural failure. The investigation is in its early stages, with metallurgical testing, systems analysis, and human factors evaluation still to come. The CVR transcript will not be released until the bulk of factual reports are ready for the public docket, a process expected to take months.
