ACFT DSCNT THROUGH OCCUPIED ALT HAD LTSS FROM ACR X. SYS ERROR.

Narrative

WE HAD TAKEN A POINT OUT FROM NEW YORK CENTER ON ACR X NWBOUND AT 9000 FT. WE WERE BUSY RESOLVING CONFLICTS INVOLVING ACFT IN OTHER PARTS OF THE SECTOR; AND ANOTHER ACFT HAD BEEN INFORMED OF 'RADAR CONTACT LOST' IN THE SECTOR. WE ACCEPTED A HDOF ON AN ACFT Y NEBOUND AT 10000 FT. AT SOME POINT THE LIMITED DATA BLOCK WAS DROPPED ON THE POINT OUT. AT LEAST 6 MINS ELAPSED BTWN THE TIME OF THE POINT OUT AND THE TIME I DSNDED ACFT Y EBOUND ACFT TO 8000 FOR DSCNT INTO SWF. THE CONFLICT ALERT WENT OFF AFTER THE 2 ACFT HAD PASSED EACH OTHER. THIS WAS THE FIRST I HAD SEEN OF THE DATA BLOCK OF ACR X AT 9000 FT. WHAT HAD HAPPENED WAS THAT THE ACR X WE HAD TAKEN THE POINT OUT ON WAS NOT FLAT-TRACKED. THE ACFT WAS FLYING DIRECT TO RKA; BUT WAS STILL IN THE COMPUTER AS GOING AROUND OUR SECTOR. THIS CAUSED THE ACR X DATA BLOCK TO BE DROPPED WHEN THE HDOF TO ANOTHER SECTOR IN BOSTON CENTER WAS INITIATED. ALL THAT REMAINED WAS THE CORRELATED TARGET. THIS IS A DANGEROUS SITUATION. SOMETHING SHOULD BE DONE SO THAT THE ENTIRE DATA BLOCK ISN'T JUST DROPPED OFF THE SCOPE. THIS SAME SITUATION IS PROBABLY VERY COMMON. IT JUST GOES UNNOTICED UNTIL SOMETHING LIKE THIS HAPPENS.