ACR X ENTERED ADJACENT CENTER AIRSPACE WITHOUT RADAR HDOF. OPDEV. ARTCC ARTCC INTERFAC COORD.

Narrative

ACR X WAS DIRECT CRL AT FL330 AND ENTERED CLEVELAND CENTER'S AIRSPACE WITHOUT A HDOF OR POINTOUT. FOR UNKNOWN REASONS WE WERE UNABLE TO INITIATE A HDOF TO CLEVELAND CENTER; I HAD THOUGHT MY MANUAL PERSON HAD EFFECTED A MANUAL HDOF AND THEREFORE I SHIPPED THE AIRPLANE TO THE DTW HIGH SECTOR. AT THE SECTOR I WAS WORKING (PMM HIGH) WE RELY ON THE AUTO HDOF SYS BECAUSE THE SECTOR IS SO BUSY; BUT FOR SOME REASON THIS FEATURE HAD BEEN INHIBITED (BY THE COMPUTER) FOR ACR X. SUPPLEMENTAL INFO FROM ACN 192820: I WAS PAGED TO THE SECTOR AND TOLD TO WORK THE 'D' POS AT PMM HIGH. THE FIRST THING I DID WAS TO TAKE A CALL FROM DETROIT HIGH SECTOR IN CLEVELAND CENTER ASKING US TO SHIP AN ACFT THEY WERE NOT TALKING TO. THE RADAR CTLR SHIPPED THE ACFT. IN THEN REMINDED THE RADAR CTLR TO SWITCH OTHER ACFT THAT WERE APCHING THE ZAU/ZCC BOUNDARY. VERY SHORTLY AFTER THE PECK HIGH (ZCC) CTLR ASKED OVER THE HOLLER LINE; IN THE BLIND; 'WHO IS THE ACR X IN MY AIRSPACE WITH NO HDOF?' THE RADAR MAN TOOK THE CALL ON THE LANDLINE TO COORDINATE WHILE I TRIED TO MAKE A HDOF VIA THE COMPUTER. THE FIRST 3 ATTEMPTS FAILED; THE FOURTH WORKED. I WAS AT THE SECTOR APPROX 2 MINS WHEN THE AIRSPACE VIOLATION WAS NOTED. A PANEL LATER DETERMINED THAT I ARRIVED AT THE SECTOR TOO LATE TO HAVE HAD ANY EFFECT ON THE OUTCOME AND SO HAD NO BLAME IN THE INCIDENT. THE RADAR CTLR STATED THAT HE THOUGHT THE COMPUTER HAD MADE AN AUTOMATED HDOF. IT WAS LATER DETERMINED THAT THE COMPUTER; FOR UNKNOWN REASONS; HAD INHIBITED THE HDOF.