Narrative:

I was working the local control 1 position with air carrier X; an E170 in position and hold on runway 18R when air carrier X; with same call sign; an E170; checked in on an 8 mi final for runway 18R. This is the second time in a week that I have seen air carrier X have duplicate call signs overlap on different flight plans. The coordination and keyboard entries required to take care of this situation are definitely not needed during a busy departure push that we have at mem during the afternoon. I am going to inform FAA management of this situation in hopes that may contact air carrier X and inform them to change the call signs. For example; if an air carrier has an air carrier Y overlapping; they will change the departure's call sign to air carrier ya.

Google
 

Original NASA ASRS Text

Title: MEM CTLR DESCRIBED DATA BLOCK ANOMALY; CAUSING UNNECESSARY DISTRACTIONS.

Narrative: I WAS WORKING THE LCL CTL 1 POS WITH ACR X; AN E170 IN POS AND HOLD ON RWY 18R WHEN ACR X; WITH SAME CALL SIGN; AN E170; CHKED IN ON AN 8 MI FINAL FOR RWY 18R. THIS IS THE SECOND TIME IN A WK THAT I HAVE SEEN ACR X HAVE DUPLICATE CALL SIGNS OVERLAP ON DIFFERENT FLT PLANS. THE COORD AND KEYBOARD ENTRIES REQUIRED TO TAKE CARE OF THIS SITUATION ARE DEFINITELY NOT NEEDED DURING A BUSY DEP PUSH THAT WE HAVE AT MEM DURING THE AFTERNOON. I AM GOING TO INFORM FAA MGMNT OF THIS SITUATION IN HOPES THAT MAY CONTACT ACR X AND INFORM THEM TO CHANGE THE CALL SIGNS. FOR EXAMPLE; IF AN ACR HAS AN ACR Y OVERLAPPING; THEY WILL CHANGE THE DEP'S CALL SIGN TO ACR YA.

Data retrieved from NASA's ASRS site as of May 2009 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.