CLT TRACON Controller described controller airspace deviation event when air carrier responded to multiple clearances issued to another similar sounding call sign aircraft; reporter contending flight crews were also partially responsible for event.

Date: 2009-06 · Aircraft: B737-400 · Phase: descent

Anomalies: atc-issue-all-types

Synopsis

CLT TRACON Controller described controller airspace deviation event when air carrier responded to multiple clearances issued to another similar sounding call sign aircraft; reporter contending flight crews were also partially responsible for event.

Narrative

Aircraft ABCD was an arrival to CLT. The aircraft initially check in on my frequency as a result of taking a frequency change for another aircraft. I informed Aircraft ABCD that he had taken the clearance for Aircraft ABCE and sent them back to the center. Later after I received a hand off on ABCD he again took a frequency change for ABCE who I was handing off to the final controller. I immediately stated that the instruction was to ABCD. In spite of the correction aircraft ABCD switched to the final controller. The final controller had taken a hand-off on aircraft ABCE and mistakenly assumed the aircraft checking in was the aircraft he took a hand-off on. The final controller issued a descent clearance to ABCD because of his error. The result was an airspace deviation for the controller. Given that this was the second time in 15 minutes that ABCD took a clearance for a different aircraft I feel the pilot of ABCD should have been given a deviation. The manager on duty would not file a deviation nor would he bring this to the attention of the company. There is no doubt that ATC was at fault in that we issued a clearance to the wrong aircraft. However there is no doubt that the pilot of ABCD was the true cause of the situation.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.