By Key Facts
- Aircraft Type: Boeing 737-800
- Operator: American Airlines
- Location: Phoenix, Arizona, USA
- Date: 14 August (after midnight)
Two American Airlines Boeing 737-800 aircraft operating in opposite directions between Phoenix and Chicago were assigned the same callsign simultaneously on 14 August, forcing a Phoenix departure controller to step in and prevent the converging flights from losing safe separation.
What Happened Over Phoenix
Both aircraft were operating as AA2482 — a flight number that American Airlines applies to both the outbound Phoenix-to-Chicago sector and the inbound Chicago-to-Phoenix sector. The conflict developed just after midnight, approximately five minutes after the Chicago-bound aircraft lifted off from runway 7L.
After departure, the outbound crew reported climbing through 6,000 ft toward their assigned altitude of 9,000 ft. The controller recognised that the aircraft’s northbound track would intersect the path of the inbound service, which was descending from the northeast at around 12,000 ft.
To manage the conflict, the controller instructed the inbound flight — distinguished verbally as the aircraft “on the arrival” — to level off at 10,000 ft. The crew confirmed the instruction. The controller then queried the outbound crew directly, referencing their transponder code: “And there’s an American 2482 on a 0730 code, is that correct, on the departure?”
After the outbound crew confirmed their climb to 9,000 ft, the controller issued a traffic alert: “On the departure I need you to maintain 9,000, traffic one o’clock and 10 miles. [It’s] your company, same callsign, out of 11,800 descending to 10,000.”
The outbound crew responded: “Incredible — we’re looking, thank you.” The exchange was archived by LiveATC from air-ground radio communications.
American Airlines Boeing 737-800 Separation and Scheduling Factor
Publicly available ADS-B data indicates that the outbound American Airlines Boeing 737-800 passed behind and below the inbound aircraft, though the precise horizontal and vertical separation has not been independently verified. A 90-minute delay affecting the inbound Chicago-Phoenix flight appears to have contributed to the unusual positioning of the two services.
Identical callsigns for bidirectional services between the same city pair are not uncommon in U.S. airline operations. American’s AA1888 operates in both directions on the Dallas-Raleigh route, and Delta Air Lines’ DL2006 similarly covers Milwaukee-Minneapolis in both directions under the same flight number. However, the simultaneous presence of both directions in the same airspace at the same time — creating an active conflict — is a considerably rarer event.
In practice, airline scheduling is designed to prevent inbound and outbound legs of the same flight number from overlapping in time and geography. When delays push one leg off its planned slot, that buffer can erode. Controllers are trained to use transponder codes and positional language to distinguish aircraft when callsign ambiguity arises, as the Phoenix controller demonstrated here.
Aviation safety investigators and air traffic management bodies periodically review same-callsign conflicts as part of broader efforts to reduce the risk of confusion between flight crews and controllers. No formal incident filing has been publicly confirmed in connection with the 14 August event.
