Narrative:

I was working when the sector that was working aircraft Y called me to tell me that they had attempted to point out aircraft Y to the adjacent ARTCC sector. The controller who was working aircraft Y then told me that the transferring controller had refused to accept the point out because he said he was giving me traffic at the same altitude. The traffic that controller was referencing was aircraft X. I believe that the controller who was working aircraft Y attempted to point the aircraft out so that the adjacent ARTCC controller could perhaps descend aircraft X below aircraft Y since aircraft X needed to start down anyway. The controller who was working aircraft Y informed me of the situation at which time I called the adjacent ARTCC controller and told the controller to put aircraft X on a 180 degree heading for the traffic.I don't believe that the control instruction that I issued was issued immediately as I did not notice the aircraft begin a turn for approximately 1 to 2 minutes. I believe that aircraft X checked on my frequency while I was calling the adjacent ARTCC controller to have them attempt to contact the aircraft. When I came off the landline I issued a descent to aircraft X for traffic. Approximately 20 seconds later aircraft X said they were descending in response to an RA at which time I believe I called the traffic. When the situation was resolved I issued clearance on course for aircraft X and as soon as possible notified management of the TCAS RA. Perhaps reiterate the importance of issuing control instructions in a timely manner especially when you have been made aware of traffic.

Google
 

Original NASA ASRS Text

Title: Center Controller reports of an adjacent sector's unwillingness to accept a point out due to a traffic conflict at the same altitude. Once the aircraft transitions into the Controller's sector; the Controller issues instructions to resolve the conflict; but it was too late and the flight crew complied with a TCAS RA.

Narrative: I was working when the sector that was working Aircraft Y called me to tell me that they had attempted to point out Aircraft Y to the adjacent ARTCC sector. The controller who was working Aircraft Y then told me that the transferring controller had refused to accept the point out because he said he was giving me traffic at the same altitude. The traffic that controller was referencing was Aircraft X. I believe that the controller who was working Aircraft Y attempted to point the aircraft out so that the adjacent ARTCC controller could perhaps descend Aircraft X below Aircraft Y since Aircraft X needed to start down anyway. The controller who was working Aircraft Y informed me of the situation at which time I called the adjacent ARTCC controller and told the controller to put Aircraft X on a 180 degree heading for the traffic.I don't believe that the control instruction that I issued was issued immediately as I did not notice the aircraft begin a turn for approximately 1 to 2 minutes. I believe that Aircraft X checked on my frequency while I was calling the adjacent ARTCC controller to have them attempt to contact the aircraft. When I came off the landline I issued a descent to Aircraft X for traffic. Approximately 20 seconds later Aircraft X said they were descending in response to an RA at which time I believe I called the traffic. When the situation was resolved I issued clearance on course for Aircraft X and as soon as possible notified management of the TCAS RA. Perhaps reiterate the importance of issuing control instructions in a timely manner especially when you have been made aware of traffic.

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.