UPS Cargo Jet Aborts Landing at Louisville After Another Aircraft Enters Runway Path

A UPS cargo plane was forced to abort its landing at Louisville Muhammad Ali International Airport early Tuesday after another aircraft came dangerously close to its intended runway, prompting an audible reaction from the flight crew captured on air traffic control audio. The Federal Aviation Administration confirmed the incident occurred around 12:10 a.m. local time and has opened an investigation.

According to preliminary information released by the FAA, the UPS flight was on final approach to Louisville Muhammad Ali International Airport when the flight crew observed another aircraft encroaching on the runway path. The pilot initiated a go-around — a standard but consequential maneuver in which an approaching aircraft aborts its landing, applies takeoff power, and climbs back to a safe altitude to attempt another approach. Cockpit-to-tower audio from the moment reportedly included an alarmed crew question, “What are you doing?” directed at the other traffic, underscoring how quickly the situation escalated.

Louisville is a uniquely high-volume cargo environment. The airport serves as the site of UPS Worldport, the delivery giant’s sprawling global air hub that processes an average of 2 million packages per day and as many as 4 million during peak holiday periods. Hundreds of widebody freighter departures and arrivals funnel through the airfield during overnight hours, making the window between midnight and 4 a.m. among the busiest in North American aviation. That concentration of heavy aircraft operating in darkness heightens both the complexity of air traffic control coordination and the consequences of any ground or runway conflict.

Investigators will likely examine controller instructions, pilot readbacks, aircraft position data, and airport surface movement logs to determine how the two aircraft came into conflict. Go-arounds themselves are considered routine safety procedures rather than emergencies, but the circumstances that trigger them — particularly when another aircraft is involved — often become the focus of regulatory scrutiny. Depending on findings, the incident could be classified under one of the FAA’s runway incursion severity categories, ranging from Category D (minimal risk) to Category A (a serious incident in which a collision was narrowly avoided). No injuries or damage have been reported.