ARTCC RADAR CTLR ATTEMPTED TO RESOLVE OPPOSITE DIRECTION CONFLICTION BTWN 2 ACFT ON A516. MANUAL RADAR CTLR HAD APPROVED WRONG ALT FOR DIRECTION CLB; WITHOUT ENSURING COMPLETE COORD WITH CTLR. RADAR CTLR UNSUCCESSFULLY ATTEMPTED TO RESOLVE CONFLICT WHEN ACFT WERE WITHIN RADAR COVERAGE.

Narrative

I WAS WORKING RADAR FULLY COMBINED. ACR #1 CALLED ON INITIAL CONTACT. I UNDERSTOOD THE CALL SIGN ONLY. HE WAS RPTING A FIX NOT IN MY AIRSPACE. I GAVE HIM SQUAWK CODE AND ASKED FOR LATITUDE 22 DEGS/LONGITUDE 60 DEGS BOUNDARY ESTIMATE; HIS EXIT FIX; RTE OF FLT (MILOK INTXN; A516; PJM LATITUDE 22 DEGS/LONGITUDE 60 DEGS). I DO RECALL TELLING THE PLT I DID NOT UNDERSTAND ALL OF HIS XMISSION. ACR #2 RTE (PJM A516 MILOK-SBOUND CLBING TO FL350) WAS LEVEL AT TIME OF INCIDENT. I NOTICED ACR #1 TAG AT ABOUT THE SAME TIME OF TCASII RA. DATA BLOCK HAD FL330; AT ALT; WITH MODE C AT FL350 AND CLBING. I CALLED TFC TO ACR #2 ON VERY EXPANDED RANGE. TARGETS WERE SEPARATED; BUT VERY CLOSE. BOTH ACFT HAD BEEN CLRED ONE BY ME; ACR #2 TO MAINTAIN FL350 ON A316; OPPOSITE DIRECTION; ACR #1 WRONG FOR DIRECTION. INITIAL RESPONSE WAS A FOREIGN FACILITY DEV. I'M NOT SURE. FL350 WAS APPROVED BY NON-RADAR CTLR FOR ACR #1 ENTERING SJU AIRSPACE. AT TIME OF INCIDENT; I REALIZED OUR ACFT; ACR #2; WAS NOT COORDINATED EITHER. ATTEMPTED TO CONTACT SVMI; BUT VERY HARD. A LANGUAGE BARRIER WAS A FACTOR. BY THE TIME I WAS ABLE TO ASSESS THE SIT; IT WAS OVER. I WAS PROVIDING TRANSITIONAL CLB/DSND SEPARATION ON 2 ACFT OFF A SATELLITE ARPT; BQN; AT APPROX TIME OF TAG ON ACR #1; LANGUAGE BARRIER; LATE COORD; OR NO COORD; WRONG ALT FOR DIRECTION OF FLT; LATE TAG; INEFFICIENT SCAN ON MY PART; ALL CONTRIBUTED TO BREAKDOWN OF SAFETY.