\n<\/p>\n
Two American Airlines Boeing 737-800s were airborne in the same sector near Phoenix Sky Harbor International Airport (PHX) under the callsign \u201cAmerican 2482\u201d shortly after midnight on August 14, 2026, a duplication the Federal Aviation Administration (FAA) is now investigating. One aircraft was arriving from Chicago O\u2019Hare International Airport (ORD), the other had just departed Phoenix for the same airport.<\/p>\n
Flightradar24 data shows the arriving flight descending through 11,000 feet while the departure was climbing toward 9,000 feet when the crews and the controller working the sector identified the duplication. The FAA said required separation was maintained throughout, and neither aircraft has been reported as receiving a collision avoidance resolution advisory.<\/p>\n
\nJust after midnight, a pair of American Airlines flights with the same call sign were on the same frequency near Phoenix. Call sign confusion has resulted in previous incidents, but thankfully ATC and the pilots were able to resolve the situation. https:\/\/t.co\/YwuuMx2e9S<\/a> pic.twitter.com\/61a0tf4x9k<\/a><\/p>\n
\u2014 Flightradar24 (@flightradar24) August 14, 2026<\/a><\/p><\/blockquote>\n
<\/center><\/p>\n
How two American 2482 ended up airborne at once<\/h2>\n
American Airlines uses flight number 2482 in both directions on the Chicago to Phoenix route, normally with a single aircraft turning around at Phoenix. The inbound leg was delayed by weather and landed at 12:13 a.m. local time against a scheduled arrival of 10:43 p.m. Rather than hold the return service, the carrier assigned a second 737-800 already at Phoenix, which departed at 11:58 p.m. Both aircraft were airborne under the same identifier at the same time, on the same frequency.<\/p>\n
Where a duplication is anticipated, the second flight is normally refiled under a different number before pushback, or a letter is appended to the callsign. Neither step was taken.<\/p>\n
Controller uses altitude to separate identical callsigns<\/h2>\n
Once the conflict became apparent, the controller began addressing the aircraft as \u201cAmerican 2482 on the arrival\u201d and \u201cAmerican 2482 on the departure,\u201d restricted the departing jet to 9,000 feet, kept the arrival above it, and passed traffic advisories to both crews as the tracks converged. Both reported the other aircraft in sight.<\/p>\n
On frequency, the controller told the crews he had not seen two aircraft merge under the same callsign in 25 years of working traffic, adding that it could have been disastrous.<\/p>\n
American Airlines said it was reviewing the circumstances and credited controllers and its own crews with maintaining separation.<\/p>\n
A known risk without a systematic US fix<\/h2>\n
Callsign similarity and duplication have been a standing concern for regulators and air navigation service providers, with alphanumeric callsigns promoted as one mitigation. US carriers have not adopted them systematically.<\/p>\n
The investigation adds to a run of FAA reviews of US traffic events this year, including a rejected takeoff at Miami International Airport<\/a> in June 2026 after a business jet entered an active runway, and a Black Hawk crossing in front of a United Airlines 737-800<\/a> near Santa Ana in March 2026. The agency is running those reviews while still working through a shortfall of certified controllers<\/a> across the national airspace system.<\/p>\n<\/p><\/div>\n