Narrative:

At the time of the possible loss of separation, I was providing training to a developmental. We were initially working north atlantic sectors gemini and mercury combined, but we decided to split the sectors due to heavy traffic volume. While we were splitting the sectors, moncton center called (late) with an estimate that was approximately 20 mins from the boundary. I hand-copied the estimate on aircraft Y as no flight details were in our system. I did not notice that aircraft Y, with routing jebby -- 4300N/05000W was potential traffic for aircraft X with routing 4200N/06000W 4300N/05500W 4400N/05000W. These flts crossed at approximately 5500W. Once aircraft Y was typed into the system, the data block appeared on the odaps display 'flashing' with aircraft X indicting that a conflict alert existed. Based upon flight strip times/estimates, the 2 aircraft would have only had about 1 or 2 mins crossing time at 5500W at the same altitude (FL350). Therefore, as soon as the conflict was detected I climbed aircraft X to FL360 and called moncton center to see if they were still in radio contact with aircraft Y. Moncton said they switched aircraft Y to commercial radio so I requested control and subsequently descended aircraft Y to FL340. Aircraft X reported level at FL360 and aircraft Y at FL340 prior to the point where their rtes of flight crossed. However, I do not know if moncton center had aircraft Y in radar coverage (where only 5 mi lateral separation would be required) when the flts were at the same altitude. And, since I am uncertain whether the flts had 60 NM lateral separation (non-radar, mnps) at the time vertical separation was established and or 10 mins converging at 5500W, I wanted to report this incident as a possible loss of separation. This incident may have been a non-event. Neither aircraft reported traffic (on TCAS) and no action, evasive or otherwise, was taken by the pilots.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZNY CTLR CONCERNED WITH POSSIBLE OPERROR AT FL350 IN NON-RADAR CTLR.

Narrative: AT THE TIME OF THE POSSIBLE LOSS OF SEPARATION, I WAS PROVIDING TRAINING TO A DEVELOPMENTAL. WE WERE INITIALLY WORKING NORTH ATLANTIC SECTORS GEMINI AND MERCURY COMBINED, BUT WE DECIDED TO SPLIT THE SECTORS DUE TO HVY TFC VOLUME. WHILE WE WERE SPLITTING THE SECTORS, MONCTON CTR CALLED (LATE) WITH AN ESTIMATE THAT WAS APPROX 20 MINS FROM THE BOUNDARY. I HAND-COPIED THE ESTIMATE ON ACFT Y AS NO FLT DETAILS WERE IN OUR SYS. I DID NOT NOTICE THAT ACFT Y, WITH ROUTING JEBBY -- 4300N/05000W WAS POTENTIAL TFC FOR ACFT X WITH ROUTING 4200N/06000W 4300N/05500W 4400N/05000W. THESE FLTS CROSSED AT APPROX 5500W. ONCE ACFT Y WAS TYPED INTO THE SYS, THE DATA BLOCK APPEARED ON THE ODAPS DISPLAY 'FLASHING' WITH ACFT X INDICTING THAT A CONFLICT ALERT EXISTED. BASED UPON FLT STRIP TIMES/ESTIMATES, THE 2 ACFT WOULD HAVE ONLY HAD ABOUT 1 OR 2 MINS XING TIME AT 5500W AT THE SAME ALT (FL350). THEREFORE, AS SOON AS THE CONFLICT WAS DETECTED I CLBED ACFT X TO FL360 AND CALLED MONCTON CTR TO SEE IF THEY WERE STILL IN RADIO CONTACT WITH ACFT Y. MONCTON SAID THEY SWITCHED ACFT Y TO COMMERCIAL RADIO SO I REQUESTED CTL AND SUBSEQUENTLY DSNDED ACFT Y TO FL340. ACFT X RPTED LEVEL AT FL360 AND ACFT Y AT FL340 PRIOR TO THE POINT WHERE THEIR RTES OF FLT CROSSED. HOWEVER, I DO NOT KNOW IF MONCTON CTR HAD ACFT Y IN RADAR COVERAGE (WHERE ONLY 5 MI LATERAL SEPARATION WOULD BE REQUIRED) WHEN THE FLTS WERE AT THE SAME ALT. AND, SINCE I AM UNCERTAIN WHETHER THE FLTS HAD 60 NM LATERAL SEPARATION (NON-RADAR, MNPS) AT THE TIME VERT SEPARATION WAS ESTABLISHED AND OR 10 MINS CONVERGING AT 5500W, I WANTED TO RPT THIS INCIDENT AS A POSSIBLE LOSS OF SEPARATION. THIS INCIDENT MAY HAVE BEEN A NON-EVENT. NEITHER ACFT RPTED TFC (ON TCAS) AND NO ACTION, EVASIVE OR OTHERWISE, WAS TAKEN BY THE PLTS.

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