Cherokee_Cruiser
Bronteroc
This is already how the system works. If the CA CA goes off, it is not just audible, both aircraft involved get a red CA (conflict alert) next to their data tag. The CA CA goes off all the time when visual separation is being applied. It is part of the aviation social contract, controller points out traffic, pilot says they have the traffic in sight, controller assumes the pilot does in fact have the traffic in sight. This controller did it twice. I could not say I would have done anything different, except maybe not using "no delay" and "immediate" in the same transmission to the AAL departure, but I digress. The gist of it is I would probably not have done anything different if I were the tower controller. I feel really bad for him and his family because the system failed him as well.
While I get that, I think it’s clear that the Blackhawk called out the wrong traffic in sight.
As for the controller:
“Do you have that CRJ in sight?”
Versus
“Pat 25, Traffic alert, danger close

Kidding for danger close. But I think a traffic call - especially the second one which was controllers tingly spider feeling - SHOULD be distance and clock direction.
Had the Blackhawk heard one half mile and 10’o clock, that might have forced them to think wait a minute, the guy we are looking at is much further than 1/2 mile, so who is this guy really close to us?
Could have made all the difference.