A UPS cargo plane aborted its landing at Louisville Muhammad Ali International Airport after air traffic controllers detected another aircraft moving past a hold-short line on the runway.
The incident occurred around 12:10 a.m. Local time on Tuesday, April 14, when UPS Flight 1303 was approximately 125 feet above ground on approach to runway 17. Controllers instructed the Labcorp aircraft to hold short, but it moved slightly beyond the designated markings, triggering tower alarms.
Air traffic control then ordered the UPS plane to execute a go-around maneuver. Audio obtained by CBS News captures a controller asking the Labcorp pilot, “What are you doing?” to which the pilot replied, “Sorry for that.”
FlightRadar24 data confirmed the Labcorp plane never entered the runway, and the FAA stated that required separation between the two aircraft was maintained throughout the event.
UPS said in a statement that its pilot followed standard procedures and that there was no operational impact from the incident. The FAA echoed this, confirming no contact occurred between the planes.
The near miss comes roughly five months after a fatal UPS cargo plane crash during takeoff at the same airport in November 2025, which killed 14 people, including three crew members.
That earlier crash involved a UPS Boeing 767 that departed runway 17L and crashed in a nearby field, prompting ongoing scrutiny of safety procedures at Louisville’s airport.
Since then, the FAA has increased monitoring of ground movements and communications at the facility, particularly during low-visibility night operations.
Controllers at Louisville routinely manage high volumes of cargo traffic, with UPS operating one of its largest air hubs at the airport, handling hundreds of flights nightly.
The Labcorp aircraft involved in the April incident was conducting a routine medical transport flight, according to flight tracking data and company flight patterns.
While no regulatory violations have been formally cited, the FAA typically reviews such incidents to assess whether procedural gaps or communication breakdowns contributed to the risk.
Air traffic control transcripts from the event are under standard review, though no disciplinary actions have been announced as of this reporting.
The incident adds to a growing list of runway incursions and near misses reported at U.S. Airports over the past year, raising concerns about workload, staffing, and technology gaps in tower operations.
Experts note that while technology like surface movement radar and automated alerts has reduced risks, human factors — including fatigue, workload, and communication clarity — remain central to preventing runway conflicts.
The FAA has not issued any immediate changes to procedures at Louisville following the April incident, but it continues to evaluate data from similar events nationwide.
For now, both UPS and Labcorp have resumed normal operations, and no flight delays or cancellations were attributed to the go-around.
Was anyone injured in the incident?
No injuries were reported. The FAA confirmed that required separation was maintained and the aircraft did not build contact.
Why did the UPS pilot abort the landing?
The UPS plane was instructed to go around after air traffic control detected the Labcorp aircraft moving past the hold-short line, triggering a potential conflict on the runway.
Is this related to the fatal UPS crash at Louisville last year?
Both incidents occurred at the same airport and involved UPS cargo flights, but investigators have not linked them causally. The April event was a runway incursion; the November crash occurred during takeoff and is still under NTSB review.
