Narrative:

ZMA called with a confirmation on foreign mlt Y who was at FL370. I had head on traffic so I asked if he was able FL390, ZMA indicated that they had traffic at FL390. I then approved FL350. I proceeded to check all the non radar bays in which the aircraft would to traversing, there was no conflict. Later on sju called on a confirmation on air carrier X who was at FL350. I then approved FL350. What I did not realize was that the strips where not posted when I checked on aircraft Y. I was then relieved by another controller. I did not have a chance to check over what I had done. The controller that relieved me took it for granted that they were not in conflict. And did not check over the situation. Elwod is not a compulsory reporting point, and this is why the other controller never saw the situation. One hour later we were informed of the conflict by one of the pilots. We have no computerized conflict probe in the north atlantic non radar, and I stress non radar region. In this day and age there should be no reason why we have to control the same way our grand parents were controling non radar. Odaps has been promised for yrs but has still not made its way to ZNY. Supplemental information from acn 101231: this was a near midair collision while at cruise altitude (FL350) on amber 300 northbound near elwod intersection on a flight from sju to jfk in ny. The WX was clear and smooth just before sunset. We felt a bump like jetwash, then looked around and saw an aircraft off our right side at our altitude going away from us. No evasive action was taken because we did not see him until after we went through his wake. He was headed northeast bound in level flight. I had just plotted our position south of elwod at XA59. On reporting the incident to ny oceanic control they admitted they had a foreign air force widebody transport en route to bermuda on blue 646 at FL350 and his estimate for elwod would be xx, the same as our estimate.

Related reports:

Google
 

Original NASA ASRS Text

Title: LESS THAN STANDARD SEPARATION BETWEEN ACR AND FOREIGN MIL TRANSPORT. OPERATIONAL ERROR.

Narrative: ZMA CALLED WITH A CONFIRMATION ON FOREIGN MLT Y WHO WAS AT FL370. I HAD HEAD ON TFC SO I ASKED IF HE WAS ABLE FL390, ZMA INDICATED THAT THEY HAD TFC AT FL390. I THEN APPROVED FL350. I PROCEEDED TO CHK ALL THE NON RADAR BAYS IN WHICH THE ACFT WOULD TO TRAVERSING, THERE WAS NO CONFLICT. LATER ON SJU CALLED ON A CONFIRMATION ON ACR X WHO WAS AT FL350. I THEN APPROVED FL350. WHAT I DID NOT REALIZE WAS THAT THE STRIPS WHERE NOT POSTED WHEN I CHKED ON ACFT Y. I WAS THEN RELIEVED BY ANOTHER CTLR. I DID NOT HAVE A CHANCE TO CHK OVER WHAT I HAD DONE. THE CTLR THAT RELIEVED ME TOOK IT FOR GRANTED THAT THEY WERE NOT IN CONFLICT. AND DID NOT CHK OVER THE SITUATION. ELWOD IS NOT A COMPULSORY RPTING POINT, AND THIS IS WHY THE OTHER CTLR NEVER SAW THE SITUATION. ONE HR LATER WE WERE INFORMED OF THE CONFLICT BY ONE OF THE PLTS. WE HAVE NO COMPUTERIZED CONFLICT PROBE IN THE NORTH ATLANTIC NON RADAR, AND I STRESS NON RADAR REGION. IN THIS DAY AND AGE THERE SHOULD BE NO REASON WHY WE HAVE TO CONTROL THE SAME WAY OUR GRAND PARENTS WERE CTLING NON RADAR. ODAPS HAS BEEN PROMISED FOR YRS BUT HAS STILL NOT MADE ITS WAY TO ZNY. SUPPLEMENTAL INFO FROM ACN 101231: THIS WAS A NMAC WHILE AT CRUISE ALT (FL350) ON AMBER 300 NBOUND NEAR ELWOD INTXN ON A FLT FROM SJU TO JFK IN NY. THE WX WAS CLEAR AND SMOOTH JUST BEFORE SUNSET. WE FELT A BUMP LIKE JETWASH, THEN LOOKED AROUND AND SAW AN ACFT OFF OUR RIGHT SIDE AT OUR ALT GOING AWAY FROM US. NO EVASIVE ACTION WAS TAKEN BECAUSE WE DID NOT SEE HIM UNTIL AFTER WE WENT THROUGH HIS WAKE. HE WAS HEADED NE BOUND IN LEVEL FLT. I HAD JUST PLOTTED OUR POS S OF ELWOD AT XA59. ON RPTING THE INCIDENT TO NY OCEANIC CTL THEY ADMITTED THEY HAD A FOREIGN AIR FORCE WDB ENRTE TO BERMUDA ON BLUE 646 AT FL350 AND HIS ESTIMATE FOR ELWOD WOULD BE XX, THE SAME AS OUR ESTIMATE.

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