ACR Y SAME ALT ASSIGNED HAD LTSS FROM ACR X ON OCEANIC RTE. SYS ERROR.

Narrative

ACR X WAS PASSED TO MID CTR AND PASSED FL330; BUT HE WAS PASSED AT FL290 PRIOR TO THIS. WHEN THE PREVIOUS CTLR PASSED FL330 ON ACR X; THIS CONFLICTED WITH ACR Y AT FL330. WHEN I SIGNED ON; THE INCIDENT HAD ALREADY OCCURRED. MID CTR (MERIDA CTR) CALLED AND REQUESTED THAT ACR X BE DSNDED TO FL290. I COULD NOT BECAUSE OF OPPOSITE DIRECTION NON-RADAR TFC AT FL310. WE TRIED TO COORDINATE WITH HOLDING; THEN I ASKED IF ACR Y COULD TAKE FL370. THE MID (MERIDA CTR) CTLR SAID HE WAS AT FL370. I ASKED AGAIN; AND THE CTLR SAID SHOW ACR Y AT FL370. WE COORDINATED FL370 WITH ZMA. MID NEVER CLBED THE ACR Y TO FL370. THIS ACFT GOT TOO CLOSE TO ACR X AND ANOTHER ACFT LATER WITH ZHU AND ZMA. ALL EVENTS OCCURRED IN NON-RADAR CONDITIONS. WITH RADAR; FDIO; AND DIRECT PLT-TO-CTLR COM; THIS DEV WOULD NOT HAVE OCCURRED. SUPPLEMENTAL INFORMATION FROM ACN 248387: 2 SCHEDULED ACRS WERE BOTH AT FL330 CONVERGING AT MARTE INTXN. THE NON-RADAR CTLR ASKED MID CTR TO MOVE ONE OF THE ACFT TO FL370 AND WAS TOLD THAT THE ACFT WOULD BE AT FL370. WE LATER FOUND OUT THE ACFT WAS STILL AT FL330. THIS PUT THE ACFT IN CONFLICT WITH 2 OTHER ACRS. DUE TO LACK OF COM WE ARE NOT IN DIRECT GND-TO-AIR COMS WITH THE ACFT. IF WE HAD COMS WITH THE ACFT FLYING THROUGH THE GULF OF MEXICO; SITS LIKE THIS COULD BE FIXED FASTER. SUPPLEMENTAL INFORMATION FROM ACN 248385: TFC IN THE GULF OF MEXICO HAS INCREASED BY OVER 15 PERCENT EACH YR FOR THE LAST SEVERAL YRS. THE RADIO COVERAGE IN THIS AREA IS VERY POOR AND RADAR COVERAGE IS NON-EXISTENT FOR MOST OF THE GULF OF MEXICO. BECAUSE OF THE EQUIP SHORTAGES; THE WORKLOAD FOR OCEANIC CTLRS AT ZHU IS VERY HVY. ACR X SEBOUND CONFLICTED WITH ACR Y NEBOUND (LESS THAN 15 MINS; NON-RADAR OCEANIC SEPARATION).