Narrative:

Air carrier X departed pie airport northbound to tay, ZJX airspace. Approximately 10 mi north of pie, the automatic-acquire full data block went into coast status, and the target reacquired with a full data block of air carrier Y. I was not working air carrier Y, nor did I know who air carrier Y was. Approximately 10 mins later, I got a call from cdk jax sector with a manual handoff on air carrier Y, a clamp arrival to srq. The 2 aircraft flight progress strips indicated different beacon codes. At the time it occurred I was moderately to very busy and desperately needed altitude information on air carrier X due to crossing traffic situation. Safety was definitely compromised.

Google
 

Original NASA ASRS Text

Title: COMPUTER TRACKING PROB CAUSES DATA BLOCK TO DROP ON 1 ACFT, THEN REACQUIRE AS ANOTHER ACFT.

Narrative: ACR X DEPARTED PIE ARPT NBOUND TO TAY, ZJX AIRSPACE. APPROX 10 MI N OF PIE, THE AUTO-ACQUIRE FULL DATA BLOCK WENT INTO COAST STATUS, AND THE TARGET REACQUIRED WITH A FULL DATA BLOCK OF ACR Y. I WAS NOT WORKING ACR Y, NOR DID I KNOW WHO ACR Y WAS. APPROX 10 MINS LATER, I GOT A CALL FROM CDK JAX SECTOR WITH A MANUAL HDOF ON ACR Y, A CLAMP ARR TO SRQ. THE 2 ACFT FLT PROGRESS STRIPS INDICATED DIFFERENT BEACON CODES. AT THE TIME IT OCCURRED I WAS MODERATELY TO VERY BUSY AND DESPERATELY NEEDED ALT INFO ON ACR X DUE TO XING TFC SIT. SAFETY WAS DEFINITELY COMPROMISED.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.