A quick-thinking air traffic controller at Phoenix Sky Harbor International Airport averted a potential disaster late Thursday night after two American Airlines jets ended up sharing the same flight number and radio frequency, one landing, the other taking off.
The incident unfolded just after midnight when American Airlines Flight 2482, arriving from Chicago O'Hare International Airport, converged with a second aircraft also designated Flight 2482 that was departing Phoenix for Chicago. Both planes were on the same radio frequency at the same time, a scenario that could have led to catastrophic confusion in the cockpit and on the ground.
A veteran controller recognized the conflict and began differentiating the two jets in his radio calls, addressing one as "American 2482 arriving" and the other as "American 2482 departing." The Federal Aviation Administration said required separation between the aircraft was maintained throughout, and both flights continued without incident. The FAA is now investigating how the duplicate call sign situation occurred.
Dispatch audio captured by ATC.com revealed the controller's reaction once the danger had passed. As CBS News reported, the controller told the pilots:
"I've been working air traffic for 25 years. I've never seen two aircraft pretty much merge with the same call sign. That's pretty incredible."
He followed up with a blunter assessment:
"It could have been disastrous, but I'm glad it all worked out."
That a controller with a quarter-century of experience had never encountered the situation speaks to how unusual, and how dangerous, the mix-up was. In aviation, a flight number is more than a booking reference. It is the primary identifier controllers use to issue altitude, speed, and heading instructions. Two aircraft sharing that identifier on the same frequency means a command meant for one plane could be followed by the other.
American Airlines told CBS News the chain of errors began with a weather delay. The original Flight 2482 from Chicago was running late. Rather than make passengers in Phoenix wait, the airline brought in a substitute aircraft and dispatched it to Chicago, but kept the same flight number, 2482.
The result: two planes airborne at the same time under identical call signs. The delayed inbound jet from Chicago arrived at Phoenix Sky Harbor just as the replacement aircraft was departing the same airport for Chicago.
Aviation safety expert Steve Arroyo told the Associated Press that someone in the airline's dispatch center likely failed to catch that both planes would be airborne simultaneously with identical flight numbers. That is a basic scheduling safeguard, and it did not work.
American Airlines issued a statement saying it is "reviewing the details related to two American flights with the same callsign." The airline credited the controller and its own pilots for the safe outcome:
"The diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed. Both flights continued safely and without incident."
The FAA confirmed that the two planes maintained required separation for the duration of the event. But confirming a safe outcome is not the same as confirming a safe process. The agency said it is investigating.
Several questions remain unanswered. The FAA has not specified whether the separation it referenced was lateral, vertical, or both. The agency has not said whether its investigation is limited to this single incident or part of a broader review of call sign assignment procedures. And American Airlines has not explained at what point in its dispatch process the duplicate was allowed to persist, whether it was a human error, a scheduling-software failure, or something else entirely.
What is clear is that the system designed to prevent exactly this kind of overlap failed. The airline's own internal controls did not flag the conflict before two jets were in the air. The only thing standing between a routine Thursday night and a potential catastrophe was one controller who caught the problem in real time and improvised a fix.
Passengers on both flights likely had no idea anything unusual happened. They landed or took off, collected their bags or stowed them, and went on with their evenings. The controller went back to his scope.
That is how aviation safety is supposed to work, layers of redundancy catching mistakes before they become disasters. But when the first layer fails, everything depends on the person behind the radar screen. This time, that person delivered. The question American Airlines and the FAA owe the flying public is why it came down to one controller's vigilance in the first place.
