A LOW ALT ARTCC RADAR CTLR DOES NOT ENSURE CORRECT HDOF PROCS AND AN FK10'S COM IS XFERRED TO A HIGH ALT CTLR. THE NON IDENTED FK10 COMES IN CONFLICT WITH A DSNDING B757 PRIOR TO BEING RADAR IDENTED.

Narrative

I WAS WORKING R21 (DOMINION) WHICH IS A LOW SECTOR AT ZDC. RALEIGH APCH IS AT THE S SIDE OF THE SECTOR 12000 FT AND BELOW. RICHMOND IS AT THE NORTHERN BOUNDARY 9000 FT AND BELOW. ABOVE RALEIGH APCH; THIS SECTOR OWNS UP TO FL230. N OF RALEIGH'S BOUNDARY THIS SECTOR OWNS FL200 AND BELOW. TFC FOR THIS SECTOR IS RDU DEPS TO THE N. RICHMOND DEPS TO THE SW. RICHMOND LANDS FROM THE W AND S. ALSO; A VARIETY OF OTHER ACFT. ACFT Y DEPARTED RDU AND WAS HANDED OFF TO ME. THE SECTOR HAD MODERATE TFC AND I HAD JUST HANDLED MANY RDU DEPS. NORMAL PROC IS TO CLB JETS TO FL230 AND HAND THEM OFF TO SECTOR 20 (BLACKSTONE) FOR CLB. I CLBED ACFT Y TO FL230 AND ATTEMPTED TO HAND OFF THE ACFT TO SECTOR 20. APPARENTLY MY COMPUTER ENTRY WAS UNSUCCESSFUL. WHEN YOU HAND OFF AN ACFT; THE DATA BLOCK FLASHES AND WHEN THE HDOF IS ACCEPTED; THE DATA BLOCK IS CONSTANT WITH AN 'R' NEXT TO THE IDENT NUMBER IN THE DATA BLOCK. I LOOKED BACK AND NOTICED THE CONSTANT DATA BLOCK. THINKING SECTOR 20 HAD RADAR ON THE ACFT; I SWITCHED HIM TO SECTOR 20. 7 MINS LATER; A CONFLICT ALERT WENT OFF BTWN ACFT X AND ACFT Y BEING DSNDED TO DULLES. ACFT Y HAD CHKED ON WITH SECTOR 20; BUT SINCE THEY DID NOT SEE A DATA BLOCK; THE CTLR TOLD THE ACFT Y TO STAND BY. I WAS COMPLACENT IN MY ROUTINE AND SAW WHAT I EXPECTED TO SEE. WHEN I SAW THE CONSTANT DATA BLOCK FOR ACFT Y; I DID NOT THINK THAT MY HDOF ENTRY WAS UNSUCCESSFUL. I SIMPLY THOUGHT THE DATA BLOCK HAD FLASHED AND THE NEXT SECTOR TOOK THE HDOF. AN ACFT INCIDENT RESULTED IN ANOTHER CTLR'S AIRSPACE. SUPPLEMENTAL INFO FROM ACN 418876: DID NOT RECEIVED HDOF OR DATA BLOCK OF CLBING ACFT. SUPPLEMENTAL INFO FROM ACN 418822: ACFT WAS CLBED INTO MY AIRSPACE WITHOUT A HDOF.