ACR-HVT CROSSED THE ROUTE OF AN ACR-WDB AT THE SAME ALT WITH LESS THAN STANDARD SEPARATION.

Narrative

THE 2 ACFT INVOLVED WERE ASSIGNED THE SAME ALT W/O HAVING THE REQUIRED SEP FOR XING TRACKS (15 MINS). THE PROB WAS DISCOVERED WHEN THE ACFT; TRANSITING FROM NON RADAR TO RADAR ENVIRONMENT; WERE OBSERVED BY THE CTLR. AT THIS TIME THE ACFT HAD PASSED EACH OTHER; THEREFORE NO ACTION WAS TAKEN NOR WAS EVASIVE ACTION REQUIRED. FACTORS CONTRIBUTING TO THIS ERROR WERE; LACK OF AUTOMATED FLT DATA PROCESSING ON ONE OF THE ACFT; CTLR FATIGUE AND SECTOR OVERLOAD. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING: ONE OF THE ACFT; A WDB; WAS NBOUND ON A22 AT FL350. THE OTHER ACFT WAS WBOUND ON A RANDOM ROUTE AT FL350. RPTR STATED THAT HE SIMPLY MISSED THE SIGNIFICANCE OF BOTH ACFT IN CONFLICT AT THE SAME ALT. IN HIS RPT HE STATED THAT A CONTRIBUTING FACTOR WAS CTLR WORKLOAD. HIS ESTIMATE OF TFC FIGURES IN THE SECTOR WAS 40 ACFT. FATIGUE WAS ALSO MENTIONED AS A FACTOR. RPTR WAS WORKING HIS SIXTH DAY WHICH IS COMMON; WITH 10 HRS A DAY NOT UNCOMMON. THE PRIMARY CAUSE OF THIS CONFLICT WAS HIS FAILURE TO SEE THE PENDING CONFLICT IN TIME TO DSND ONE OF THE ACFT.