Narrative:

Pc-12 on downwind to runway 20L at pdk at 5000 ft. BE36 on vector to ryy at 5000 ft. There were other aircraft in the immediate area which caused data tag overlap. I had already switched the BE36 to another frequency. The aircraft were in potential conflict, so I issued immediate descent to 4000 ft to the pc-12 and issued traffic 2 O'clock position, 5 mi at 5000 ft. The other controller issued a northwest heading to the BE36 and I then issued a right turn to 090 degrees on the pc-12 to obtain divergence. The data tag overlap contributed to the situation, plus the BE36 came over at 5000 ft wbound and I left him there instead of going to 4000 ft or 6000 ft which would have been correct for direction of flight.

Google
 

Original NASA ASRS Text

Title: A80 APCH CTLR EXPERIENCED POSSIBLE LOSS OF SEPARATION.

Narrative: PC-12 ON DOWNWIND TO RWY 20L AT PDK AT 5000 FT. BE36 ON VECTOR TO RYY AT 5000 FT. THERE WERE OTHER ACFT IN THE IMMEDIATE AREA WHICH CAUSED DATA TAG OVERLAP. I HAD ALREADY SWITCHED THE BE36 TO ANOTHER FREQ. THE ACFT WERE IN POTENTIAL CONFLICT, SO I ISSUED IMMEDIATE DSCNT TO 4000 FT TO THE PC-12 AND ISSUED TFC 2 O'CLOCK POS, 5 MI AT 5000 FT. THE OTHER CTLR ISSUED A NW HEADING TO THE BE36 AND I THEN ISSUED A R TURN TO 090 DEGS ON THE PC-12 TO OBTAIN DIVERGENCE. THE DATA TAG OVERLAP CONTRIBUTED TO THE SIT, PLUS THE BE36 CAME OVER AT 5000 FT WBOUND AND I LEFT HIM THERE INSTEAD OF GOING TO 4000 FT OR 6000 FT WHICH WOULD HAVE BEEN CORRECT FOR DIRECTION OF FLT.

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.