IMPROPER ARTCC INTRAFAC COORD. ACR X CLB THROUGH OCCUPIED ALT; HAD LTSS FROM ACR Y. SYS ERROR.

Narrative

I WAS WORKING CMH RADAR AND HAD HANDED OFF AND SWITCHED ACR Y. THE DATA BLOCK WAS DROPPED AFTER HE LEFT MY AIRSPACE. THE LTL CTLR FLASHED ACR X CLBING TO 15000 FT AND I TOOK THE HDOF. JUST AFTER THE HDOF; ACR Z WAS FLASHED CLBING TO FL190 (OUT OF 14000 FT). THE LTL CTLR ADVISED ACR X REQUESTED 17000 FT AND WAS MY CTL REF 'THE ACR.' WHEN ACR X WAS CLR OF ACR Z I ISSUED THE ACR X CLBING TO 17000 FT. AFTER AEDP; I LEARNED THAT ACR X WAS THE TFC HE INTENDED. THE LIMITED DATA BLOCK ON ACR Y WAS COVERED BY THE DATA BLOCK ON ACR X. I THOUGHT THE ACR Y WAS LONG GONE AND GOT NO PVD FROM LTL. THE ERROR HAPPENED 17 MI ON LTL'S SIDE OF THE SECTOR BOUNDARY. SAME COMPANY WAS COMING FROM ANOTHER SECTOR; BUT I THOUGHT LTL HAD A POINTOUT ON HIM BECAUSE OF THE DEVS. AS IT TURNED OUT; ACR Y WAS THE ONLY SAME COMPANY ON HIS SCOPE; HENCE 'YOUR CTL REF THE ACR.' ACR Z WAS THE ONLY SAME COMPANY ACR ON MY SCOPE. SUPPLEMENTAL INFO FROM ACN 302061: ACR X LEVEL AT 15000 FT REQUESTED 17000 FT. TFC WAS CALLED (ACR Y AT 16000 FT). ACR X WAS TOLD HIGHER WAS AVAILABLE CLRING TFC. I SPOKE TO THE RECEIVING CTLR AND STATED THAT ACR X WANTED HIGHER AND WAS HIS CTL CLRING ACR Y. THE OTHER CTLR THOUGHT THE REF WAS TO A DIFFERENT SAME COMPANY ACFT. PROPER COORD WOULD PROBABLY HAVE PREVENTED THIS.