Full Breakdown
Duplicate Callsign Near Phoenix Averts Potential Mid-Air Collision
8/15/2026, 6:07:43 AM
Core Event
In the early hours of Friday, an air traffic controller at Phoenix Sky Harbor International Airport identified that two American Airlines Boeing 737-800s were operating under the identical flight number 2482. One aircraft was descending toward Phoenix from Chicago, while the other was departing Phoenix for Chicago. By distinguishing the aircraft as “American 2482 on arrival” and “American 2482 on departure,” the controller kept the planes vertically separated—approximately 2,000 feet—and horizontally about three miles apart, preventing a possible collision.
Background & Context
American Airlines typically uses the same flight number for the round-trip service between Chicago O’Hare (ORD) and Phoenix Sky Harbor (PHX). Normally the same aircraft completes both legs, eliminating any overlap. On this occasion the Chicago-to-Phoenix leg was delayed by weather, departing nearly two hours late on August 13. To keep the Phoenix-to-Chicago leg on schedule, the airline dispatched a second aircraft, resulting in both flights occupying the same airspace simultaneously—a rare operational scenario.
Data & Statistics
- Passengers: 295 total (122 on the inbound flight, 173 on the outbound flight).
- Altitude separation: The inbound aircraft was descending through 11,000 feet; the outbound aircraft was climbing toward 9,000 feet.
- Horizontal separation: About three miles at the closest point.
- Vertical separation maintained: Roughly 2,000 feet, within legal limits.
Official Statements & Responses
- The agency emphasized that required separation was always maintained.
- Aviation safety expert Steve Arroyo attributed the near-miss to a dispatch oversight, saying, “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.”
On-the-Ground Reports
Pilots on both flights later complimented the controller, describing the outcome as “good job” and expressing relief that the situation was resolved without incident.
Conflicting Reports & Gaps
Sources agree on the core facts, but minor discrepancies exist in the description of the aircraft’s exact altitudes and the terminology used for the frequency overlap. While some reports state the planes were on the same ATC frequency, others simply note that the controller differentiated them by appending “on arrival” or “on departure.” No definitive explanation has been provided regarding how the airline’s dispatch system failed to flag the duplicate callsign before the flights entered the same sector.
Verbatim Quotes
- “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
- “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,” — American Airlines
Why It Matters
The incident highlights the importance of robust dispatch checks and clear ATC communication when airlines reuse flight numbers for opposite legs. It also demonstrates the resilience of the air traffic control system, which can adapt quickly to unexpected procedural anomalies to preserve safety.
What’s Next
Both the FAA and American Airlines have launched investigations to determine how the duplicate callsign was assigned and to assess whether procedural changes are needed to prevent recurrence. Findings are expected to be released in forthcoming safety bulletins.
