Narrative:

Air carrier X was on a high base on the west side of ZZZ centerline to runway 16R; air carrier Y was on an east side downwind for runway 16R at 5;000 feet and air carrier Z was on the runway 16L localizer at 5;000 feet. I had not noticed the similar sounding call signs yet so I was grouping my numbers. I told air carrier X to fly heading 130 and join the localizer to 16R and I heard the read back (not noticing that it was air carrier Y responding); then I told air carrier Z to descend to 4;000 feet. Since I had not heard that air carrier Y took air carrier X's heading; I didn't correct the read back. I then noticed air carrier Y's data tag begin to move west. I told air carrier Y to fly heading 340 and called traffic because now air carrier Y was in conflict with air carrier Z. Air carrier Y said he had air carrier Z in [sight]; I told air carrier Y to maintain visual separation; caution wake turbulence and fly heading 340. Air carrier Y told me he was responding to a TCAS. Air carrier Z was descending; as instructed; when I called traffic. From what I can remember; air carrier Z was descending out of 4;500 feet when traffic was called. During the relief briefing; when I was taking the position; I was informed that the fused radar had 2 very bad stitching jumps; upwards of 1/2 mile each. During my session; I noticed 1 very bad stitching problem and I can confirm it appeared the air carrier jumped about 1/2 mile to the west then corrected. When air carrier Y's tag went west; my first thought was that it was a stitching problem but when it didn't correct is when I took action. The airlines need to ensure similar sounding call signs don't arrive into the same sector at the same time and the stitching problem with fusion needs to be investigated. Fused radar has had stitching problems all along but tonight; a 1/2 mile jump is just unsafe.

Google
 

Original NASA ASRS Text

Title: Approach Controller reports of similar sounding call signs problem along with a stitching issue related to fusion radar.

Narrative: Air Carrier X was on a high base on the west side of ZZZ centerline to Runway 16R; Air Carrier Y was on an east side downwind for Runway 16R at 5;000 feet and Air Carrier Z was on the Runway 16L localizer at 5;000 feet. I had not noticed the similar sounding call signs yet so I was grouping my numbers. I told Air Carrier X to fly heading 130 and join the localizer to 16R and I heard the read back (not noticing that it was Air Carrier Y responding); then I told Air Carrier Z to descend to 4;000 feet. Since I had not heard that Air Carrier Y took Air Carrier X's heading; I didn't correct the read back. I then noticed Air Carrier Y's data tag begin to move west. I told Air Carrier Y to fly heading 340 and called traffic because now Air Carrier Y was in conflict with Air Carrier Z. Air Carrier Y said he had Air Carrier Z in [sight]; I told Air Carrier Y to maintain visual separation; caution wake turbulence and fly heading 340. Air Carrier Y told me he was responding to a TCAS. Air Carrier Z was descending; as instructed; when I called traffic. From what I can remember; Air Carrier Z was descending out of 4;500 feet when traffic was called. During the relief briefing; when I was taking the position; I was informed that the fused radar had 2 very bad stitching jumps; upwards of 1/2 mile each. During my session; I noticed 1 very bad stitching problem and I can confirm it appeared the Air Carrier jumped about 1/2 mile to the west then corrected. When Air Carrier Y's tag went west; my first thought was that it was a stitching problem but when it didn't correct is when I took action. The airlines need to ensure similar sounding call signs don't arrive into the same sector at the same time and the stitching problem with fusion needs to be investigated. Fused radar has had stitching problems all along but tonight; a 1/2 mile jump is just unsafe.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.