Phoenix controller averts collision between planes sharing same flight number

I've never seen two aircraft pretty much merge with the same call sign.
The Phoenix controller reflects on an incident that nearly became a catastrophe but was averted by his quick intervention.
Mark

How does something like this even happen? Two planes with the same number in the air at the same time?

Mimi

Weather delays the Chicago flight, so American pulls a spare plane from Phoenix to keep the schedule. Nobody in dispatch catches that both planes will be airborne simultaneously with the same call sign. It's a gap in the process.

Mark

And if the controller hadn't noticed?

Mimi

Both pilots might have thought the controller's altitude instructions applied to them. They could have ended up at the same height on converging paths. That's a collision.

Mark

So the controller's quick thinking was the only thing that prevented it?

Mimi

Not the only thing. The pilots could have asked for clarification. Visual separation helped. But yes—his experience and his decision to rename the planes on the radio, that was the critical move.

Mark

Has this happened before?

Mimi

An expert I read said he'd seen it maybe twice in forty years. It's rare enough that when it happens, people notice. But rare doesn't mean impossible.

Mark

What happens now?

Mimi

The FAA and American Airlines investigate. They look at dispatch procedures, at how flight plans get approved, at whether there are better safeguards. The system held this time. The question is whether they can make sure it holds next time.

  • Two American Airlines jets, both designated AA2482, were simultaneously airborne over Phoenix — one arriving from Chicago, one departing for it — creating a rare and dangerous case of identical call signs in converging airspace.
  • The risk was not merely logistical: if either pilot misheard a controller's instruction meant for the other aircraft, both planes could have ended up at the same altitude on a collision course.
  • A controller with 25 years of experience moved quickly, inventing verbal distinctions on the fly — 'the arrival' and 'the departure' — to keep both pilots oriented and vertically separated as their paths crossed.
  • The error traced back to dispatch, where a weather delay prompted American to deploy a second Phoenix aircraft without flagging that it would share a flight number with the delayed Chicago plane already in the air.
  • Both the FAA and American Airlines have opened investigations, with aviation experts noting that while the system's safeguards held this time, the incident exposes a gap that should have been caught long before the planes left the ground.

In the early hours of a Friday morning over Phoenix, two American Airlines jets bearing the same flight number converged in shared airspace — a quiet administrative error made suddenly consequential at altitude. A veteran air traffic controller, drawing on twenty-five years of experience, recognized the danger and separated the aircraft through precise, deliberate language before any harm could occur. The incident, born of a weather delay and a dispatch oversight, passed without injury but left behind a question that aviation safety has always carried: how many layers of human attention stand between routine and catastrophe?

Shortly after midnight on a Friday in Phoenix, a veteran air traffic controller found himself managing something he had never encountered in 25 years: two American Airlines jets, both called American 2482, converging through the same airspace. One was arriving from Chicago. The other was departing for it. Both carried identical call signs.

The danger was immediate and specific. If either pilot confused an instruction meant for the other aircraft, the planes could end up at the same altitude on a collision course. The controller responded with deliberate precision — renaming them in real time as "American 2482 on the arrival" and "American 2482 on the departure." He kept the arriving plane higher, instructed the departing flight to limit its climb, and ensured both crews had visual contact while still miles apart. When they passed safely, the arriving pilot radioed his thanks. The controller's reply was quiet: "It could have been disastrous, but I'm glad it worked out."

The mistake had originated in dispatch. American 2482 normally operates as a single aircraft shuttling between Chicago and Phoenix. When weather delayed the Chicago departure, American sent a second Phoenix-based plane to leave on schedule — without flagging that both aircraft would briefly share the same flight number in the same sky. Someone in dispatch, and the pilots who signed off on both flight plans, had missed it.

Aviation safety expert Steve Arroyo, who spent four decades with United Airlines, said he had seen this kind of error only a handful of times. "You can drop the ball," he said, "but it's nice to see that the system is resilient." Both the FAA and American Airlines announced investigations into how the duplicate call sign cleared every checkpoint before reaching the air. American's statement credited the diligence of its controllers and pilots for ensuring separation was maintained throughout.

The incident passed without injury, but it left a pointed question behind: the system held because one experienced person was paying close attention. The work now is to ensure that the error never makes it that far in the first place.

Shortly after midnight on a Friday in Phoenix, two American Airlines jets with identical call signs were heading toward each other through the same airspace. One was arriving from Chicago. The other was departing for the same city. Both were American 2482.

The controller working that sector that night had been directing air traffic for a quarter century. He had never encountered anything like it. When he realized what was happening—two planes, same number, converging flight paths—he understood the danger immediately. If both pilots misheard his instructions, if there was any confusion about which plane he was addressing, they could end up at the same altitude on a collision course.

He moved fast. The audio, later posted online, captures him establishing clarity through deliberate language. He began calling one "American 2482 on the arrival" and the other "American 2482 on the departure." The distinction was everything. He kept the arriving plane higher than the departing one, maintaining vertical separation as their routes crossed. He instructed the departing flight to limit its climb, preserving the gap between them. He ensured both pilots could see each other visually while they were still miles apart.

When the two aircraft had safely passed, the arriving pilot radioed his appreciation. The controller's response was measured: "It could have been disastrous, but I'm glad it worked out." Later, reflecting on the moment, he would say he had never seen two aircraft nearly merge under the same call sign in his entire career. That's pretty incredible, he said. And it was.

The error originated upstream, in the dispatch center. American 2482 is a round-trip route that normally operates with a single aircraft flying back and forth between Chicago and Phoenix. But on this day, weather had delayed the Chicago departure. Rather than wait, American deployed a second plane sitting in Phoenix to leave on schedule. The result: two aircraft with the same flight number briefly occupied the same airspace at the same time. Someone in dispatch, and the pilots who signed off on both flight plans, had missed it.

Steve Arroyo, an aviation safety expert who spent four decades with United Airlines—starting as a dispatcher before becoming a pilot—said he had seen this type of mistake only a handful of times in his career. "You can drop the ball, and that shouldn't happen," he said, "but it's nice to see that the system is resilient and we have all the safeguards." The safeguards, in this case, were a controller's experience and quick thinking, and the requirement that pilots maintain visual contact.

Both the Federal Aviation Administration and American Airlines announced they would investigate how the duplicate call sign slipped through. American's statement emphasized that "the diligence and professionalism of air traffic controllers and our pilots ensured required separation was always maintained and the issue was identified and addressed." The airline noted that both flights continued safely and without incident.

What could have been a catastrophe became instead a reminder of how aviation safety depends on layers of human attention—and how fragile those layers can be when one breaks. The system held because a controller was paying attention. The question now is whether the system can be redesigned so that someone in dispatch catches the error before it ever reaches the sky.

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.
— Phoenix air traffic controller
You can drop the ball, and that shouldn't happen, but it's nice to see that the system is resilient and we have all the safeguards.
— Steve Arroyo, aviation safety expert
Quer a matéria completa? Leia o original em 1News ↗
Fale Conosco FAQ