ZSU controller described near loss of separation event during aircraft weather deviation maneuvers; ...

Attributes
ACN	850803
Time
Date	200909
Local Time Of Day	1201-1800
Place
Locale Reference	ZSU.ARTCC
State Reference	PR
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Make Model Name	Commercial Fixed Wing
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Person 1
Function	Coordinator Enroute Oceanic
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Military 0 Air Traffic Control Non Radar 2 Air Traffic Control Radar .4 Air Traffic Control Supervisory 0 Air Traffic Control Time Certified In Pos 1 (yrs) 2
Events
Anomaly	ATC Issue All Types

Narrative:

I was working D4 and got a call from commercial radio. They asked if the aircraft X could deviate because they were getting a call from the dispatcher. I looked at the radar and the aircraft turned on its own almost opposite direction with the aircraft Y. I tried to give commercial radio a clearance for aircraft Y but was not on commercial radio yet. Which I realized afterwards that if I would have given aircraft Y the clearance; it would of lost separation with another aircraft. However; I told commercial radio to disregard because aircraft X was on frequency and the radar controller turned aircraft X out of the way. The aircraft lost non radar separation but not radar separation. The problem is that aircraft X said to us afterwards that they asked numerous times to deviate and had no reply. Commercial radio said that they sent the messages to ZNY and not ZSU. This happens frequently that we do not get clearances; progresses; or requests for our aircraft in our airspace. This situation is preventable if we would have received the request from the pilot. Some of the progresses are ZNY's fault because they tell the pilots to go cpdlc and not to commercial radio.

Original NASA ASRS Text

Title: ZSU controller described near loss of separation event during aircraft weather deviation maneuvers; when communications between commercial radio and ZNY/ZSU faltered; requiring ZSU to utilize RADA procedures to secure separation.

Narrative: I was working D4 and got a call from commercial radio. They asked if the Aircraft X could deviate because they were getting a call from the dispatcher. I looked at the RADAR and the aircraft turned on its own almost opposite direction with the Aircraft Y. I tried to give commercial radio a clearance for Aircraft Y but was not on commercial radio yet. Which I realized afterwards that if I would have given Aircraft Y the clearance; it would of lost separation with another aircraft. However; I told commercial radio to disregard because Aircraft X was on frequency and the RADAR controller turned Aircraft X out of the way. The aircraft lost NON RADAR separation but not RADAR separation. The problem is that Aircraft X said to us afterwards that they asked numerous times to deviate and had no reply. commercial radio said that they sent the messages to ZNY and not ZSU. This happens frequently that we do not get clearances; progresses; or requests for our aircraft in our airspace. This situation is preventable if we would have received the request from the pilot. Some of the progresses are ZNY's fault because they tell the pilots to go CPDLC and not to commercial radio.

Data retrieved from NASA's ASRS site as of April 2012 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.

ZSU controller described near loss of separation event during aircraft weather deviation maneuvers; when communications between commercial radio and ZNY/ZSU faltered; requiring ZSU to utilize rada procedures to secure separation.