American Airlines Flights Clash Near Phoenix Due to Duplicate Flight Numbers

On the night of August 13 into the early hours of August 14, two American Airlines flights bearing the identical flight number AA2482 were airborne near Phoenix at the same time. Both flights were communicating with air traffic control (ATC) on the same frequency, which led to one plane mistakenly accepting a clearance intended for the other. This rare incident saw the two Boeing 737 aircraft cross paths at less than a mile apart horizontally, with a minimum vertical separation of 1,000 feet, thereby maintaining regulatory safe distance but narrowly avoiding a potential safety breach.

The flight inbound to Phoenix was delayed by approximately 90 minutes, and a different aircraft was then assigned for the return flight to Chicago, causing both flights to be active simultaneously using the same callsign. The outbound flight was issued a clearance to climb to 9,000 feet, which the inbound flight inadvertently accepted. Fortunately, vigilant controllers and flight crews identified the confusion, promptly halted the inbound flight’s climb at 10,000 feet and the outbound flight’s climb at 9,000 feet, maintaining safe separation between the two aircraft.

This event underscores a growing problem for major airlines like American, Delta, and United: they are running out of unique flight numbers. Flight numbers are typically composed of up to four digits, theoretically allowing for 9,999 unique identifiers, excluding zero. However, the actual operational complexities, including codeshare agreements and multiple segments, have pushed these airlines to reuse flight numbers in ways that risk operational confusion.

American Airlines’ Senior Vice President of Network Planning, Brian Znotins, has highlighted that the issue stems from the airline wanting to affix its flight numbers to more flights than the numbering system can accommodate. This includes flights operated by partner airlines and codeshare flights, such as those offered from Doha to cities in India and Pakistan, or those operated by Alaska Airlines but sold under American Airlines’ brand. This expansion complicates the numbering system dramatically.

To manage the constraints, American Airlines assigns the same flight number to flights that are not expected to be airborne simultaneously, such as ‘out and back’ operations like Chicago to Phoenix and back. However, when delays or schedule changes occur, like in this incident, such assumptions fail, leading to two aircraft using identical callsigns concurrently. Ideally, in such situations, the airline should alter the flight number of one flight before departure to prevent overlap within controlled airspace.

The technology systems underpinning airline operations, many of which date back to the 1960s, have made it extremely challenging to implement solutions like extending flight numbers to five digits or adding differentiating codes. Upgrading these systems would involve significant expense and extensive re-coordination with international aviation authorities such as IATA. Meanwhile, dispatch and operations teams must rely on procedural workarounds to avoid similar incidents.

Had the outbound flight’s callsign been adjusted before pushback, for example, to a variant such as ‘American 8248,’ it could have averted the confusion. Alternatively, controllers could have been pre-briefed about the two planes sharing the same number in the same region, allowing temporary reassignment of one flight’s callsign. The inability to swiftly enact these measures contributed to the communications close call reported in Phoenix airspace.

Despite no loss of safe separation or collision, this episode serves as a stark reminder that flight number exhaustion is no longer a theoretical issue; it is a practical safety concern. It also highlights the need for airlines and regulatory bodies to address legacy system limitations and modernize flight numbering schemes, particularly for carriers with extensive partner networks and codeshare arrangements.

For now, airlines, ATC agencies, and flight crews must be vigilant to such numbering overlaps, ensuring clear communication and rapid correction if conflicts arise. The experience near Phoenix demonstrated effective crew and controller coordination under pressure, but broader systemic and technological updates are needed to reduce future risks associated with duplicate flight numbers during simultaneous operations.