What we know about the UPS MD-11 crash in Louisville
The gist: A UPS McDonnell Douglas MD-11 freighter bound from Louisville to Honolulu crashed shortly after takeoff on the evening of November 4, 2025, after a large plume of fire appeared near the left wing during the takeoff roll and the left engine separated from the wing. The NTSB is in the fact-gathering phase and has explicitly declined to speculate on cause, but its briefings establish a sequence: an apparently normal takeoff, a repeating cockpit bell about 37 seconds after takeoff thrust was called, roughly 25 more seconds of crew efforts to control the aircraft, and impact with structures and terrain off airport property.
What's going on
The aircraft and the flight. The airplane was a McDonnell Douglas MD-11, later altered to an MD-11F freighter, manufactured in 1991 with tail number N259UP, and now handled by Boeing following its merger with McDonnell Douglas [1]. It was traveling from Louisville, Kentucky to Honolulu, Hawaii with three people on board [2]. Board member Todd Inman, briefing for the NTSB, said a fully loaded freighter headed to Honolulu would carry "a large amount of fuel,"[3] which fed the post-accident fire response [4].
The sequence. After the crew was cleared for takeoff, "a large plume of fire in the area of the left wing occurred during the takeoff roll"[2]. The plane lifted off and gained enough altitude to clear the fence at the end of runway 17R, then struck structures and terrain off airport property, and a post-impact fire covered almost half a mile [2]. Airport CCTV showed the left engine detaching from the wing during the takeoff roll [5]. Inman later said investigators believe the engine photographed on the ground is the left engine, and that it is on the airfield, not off airport property [6].
The recorders. The cockpit voice recorder and flight data recorder were located on the first day, showing heat damage but no intrusion [7]. A recorder specialist flew them overnight to the NTSB laboratory in Washington, where both were successfully downloaded [8][9]. The FDR held about 63 hours of data over 24 flights, including the accident flight, with about 420 parameters including altitude, airspeed, engine information and system statuses [10]. The CVR contained two hours and four minutes of "good quality digital recorded audio"[11].
What the CVR shows. Crew completed standard checklists and briefings, and the takeoff roll was "uneventful through the different speed call outs"[11]. About 37 seconds after the crew called for takeoff thrust, "a repeating bell was heard on the CVR, which persisted until the end of the recording 25 seconds later,"[12] during which the crew "engaged in efforts to attempt to control the aircraft before the crash"[12]. Inman stressed he was "not using the word alarm,"[13] and that the bell could reflect "a mixture of several different things"[13] pending FDR analysis [14]. Investigators believe the end of the recording was the final point of impact, though FDR data could add factors [14].
Altitude and speed. Preliminary FAA ADS-B data put the aircraft's last reported point at 475 feet of GPS altitude, traveling 183 knots, at 5:13:32 p.m. Eastern on the night of the accident [15]. Inman later clarified that under how ADS-B data is reported, this equates to approximately 100 feet above ground level, and said it is being checked against FDR data still being validated [16][17].
The engine and pylon. A FOD walk on runway 17R found multiple pieces of engine fan blades along with the main component of the number one (left) engine, all moved to a secured location [18][8]. The bulk of the left engine pylon was still attached to the left engine when the engine separated from the wing, and both are undergoing further examination [19]. Inman clarified the pylon was attached at the time it disengaged, though impact damage may have occurred afterward, and said the area "needs to be an area of focus"[20] based on video evidence [21].
What investigators have ruled out or pushed back on. UPS told the NTSB the flight was not delayed and no maintenance was done immediately before it, a claim investigators will independently verify [22][23]. On reports the crew's originally assigned aircraft was swapped for a maintenance issue, Inman said "we've not gotten any specific information on it,"[24] and that scheduling records and CCTV would be checked [25]. Asked about airworthiness directives, Inman said he was not aware of any and that it would be unlikely none existed for an aircraft flying that long, but "at this point, we have not seen anything that's said we need to hone in on a specific area"[26]. He said nothing so far warranted an urgent safety recommendation [27][28]. On the government shutdown, he said SDF Tower appeared to be at its proper complement and no ATC working group had been formed [29][30].
What's next. The aircraft had been in San Antonio, Texas for about six weeks for what Inman called a heavy check; investigators are pulling those records and will review maintenance from that period to the date of the flight [31][32][33]. Job cards have been provided, UPS is supplying an exemplar aircraft with the same engine type, and the operations team will use on-site MD-11 simulators [34][20]. CVR and FDR groups will convene at NTSB headquarters; the CVR transcript will be made public only when a majority of other factual reports are placed in the public docket, several months away [12][19]. The NTSB named as parties the FAA, UPS, the Independent Pilots Association, the Teamsters, Boeing and GE Aircraft Engines [35][36]. Inman said the on-scene briefing was the final one, with updates to come from Washington [17].
Why it matters
The investigation's central puzzle is compressed into about a minute of flight. The crew's checklists and speed callouts were normal, then a bell began and never stopped before the recording ended 25 seconds later [11][12]. Because the left engine separated during the takeoff roll and its pylon came off with it, the attachment area is where investigators say the evidence points — Inman called it "one aspect" of the investigation but one where "we know we have some form of cause of issue or concern"[37] [21]. The NTSB's metallurgical analysts in Washington will examine that hardware [21].
The stakes extend beyond the three people on board. The crash killed and injured people on the ground and left others missing, and Inman described the NTSB's family assistance work and its coordination with local authorities on recovery [38][39][40]. The debris field's location among businesses — with similar metals and alloys complicating the sorting of aircraft parts — has kept the site active, with spot fires still flaring in compressed paper products days later [41][42][43].
There is also an operational dimension. Inman noted the Louisville hub handles "life-saving drugs, postal products, food, supplements"[44] moving through every night, and that the investigation could slow important products, which is why teams worked to map the scene and hand back runways while preserving evidence [45]. And because the MD-11 fleet is old and heavily used, the NTSB is verifying that every age- and cycle-based check was performed, with the option of recommending different checks [27].
What's still unclear
- What the bell meant. Inman declined to call it an alarm and said the FDR's 400-plus data sets are needed to distinguish among possible alarms [13][14].
- Why the engine separated. The pylon finding focuses attention on the attachment area, but no cause has been stated [21][37].
- The San Antonio heavy check. Investigators are still gathering records from the six-week visit; nothing has been concluded [31][33].
- The crew-swap reports. The NTSB had no specific information and planned to check scheduling and CCTV [24].
- Final altitude and speed. The 475-foot ADS-B figure is preliminary and still being reconciled with FDR data [16][17].
- Whether any recommendation will follow. Inman said nothing so far rises to an urgent finding, but the NTSB has not determined probable cause and will not do so on scene [46][27].
The NTSB's stated posture is that it walks in "with no premise," analyzing facts before drawing conclusions [47]. Until the FDR and CVR groups report, the public record consists of a sequence and a piece of hardware — not a cause.
Written with AI (Memex) from 47 cited source passages. Every quotation was checked word-for-word against the sources: 13 of 13 verified.