Narrative:

Aircraft X was direct to camrn to cross 40 miles southeast of camrn at FL140. W-107 had gone active and my radar assist secured a point out through the warning area for aircraft X direct to camrn descending to FL090.when aircraft X was approximately 10 miles from the boundary of sectors 86 and 66 the conflict alert started to flash with aircraft X and the [a flight of three.] the [flight of three were] turned directly into the aircraft X that I was working.when I recognized the conflict I told aircraft X to turn left for traffic; no response was received. I called a traffic alert for aircraft X. My RA told me that [one controller] wanted me to stop aircraft X at FL180. I told aircraft X to maintain FL180. Aircraft X responded that he was responding to a TCAS resolution advisory. I did everything that I could.as for the aircraft Y; he was never in my airspace. The first time that I recall seeing this limited data block was when the aircraft Y was at FL190 heading eastbound already off the aircraft X's right side. At that point the aircraft X was already descending down and was out of FL189. Upon watching the falcon playback it appears that aircraft Y turns off his transponder. At that point there was absolutely no way for me to be able to even know he was there until the aircraft Y turns his transponder back on.after this second conflict cleared I was told by my RA; who was told by sector 66 to put aircraft X on a heading of 010. I did this and transferred communications to sector 66 as they wanted to talk to him.[the other controller] should protect for point outs when they accept point outs from us. If they are unable to do so then they need to advise us during coordination so that a mutually agreeable solution can be determined.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZNY Center Controllers reported about a problem with a restricted area due to traffic in and out of it that caused airborne conflicts with multiple aircraft.

Narrative: Aircraft X was direct to CAMRN to cross 40 miles southeast of CAMRN at FL140. W-107 had gone active and my Radar Assist secured a point out through the warning area for Aircraft X direct to CAMRN descending to FL090.When Aircraft X was approximately 10 miles from the boundary of sectors 86 and 66 the conflict alert started to flash with Aircraft X and the [a flight of three.] The [flight of three were] turned directly into the Aircraft X that I was working.When I recognized the conflict I told Aircraft X to turn left for traffic; no response was received. I called a traffic alert for Aircraft X. My RA told me that [one controller] wanted me to stop Aircraft X at FL180. I told Aircraft X to maintain FL180. Aircraft X responded that he was responding to a TCAS Resolution Advisory. I did everything that I could.As for the Aircraft Y; he was never in my airspace. The first time that I recall seeing this limited data block was when the Aircraft Y was at FL190 heading eastbound already off the Aircraft X's right side. At that point the Aircraft X was already descending down and was out of FL189. Upon watching the Falcon playback it appears that Aircraft Y turns off his transponder. At that point there was absolutely no way for me to be able to even know he was there until the Aircraft Y turns his transponder back on.After this second conflict cleared I was told by my RA; who was told by sector 66 to put Aircraft X on a heading of 010. I did this and transferred communications to sector 66 as they wanted to talk to him.[The other Controller] should protect for point outs when they accept point outs from us. If they are unable to do so then they need to advise us during coordination so that a mutually agreeable solution can be determined.

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.