Narrative:

Lft departure called to advise air carrier XXX had departed lft, but they could not depart him in the computer to activate flight plan. I took radar contact and then did a flight plan readout on air carrier XXX and discovered air carrier XXX was already being used by a flight from iah to slw. I then amended the lft air carrier XXX to air carrier xx and departed the aircraft and started a track on this aircraft. This is the third time this exact situation has occurred to me personally. The first time was about 6 months ago. The second 2 weeks ago, and then again now. I have talked with other controllers who have had this same situation also. One occurrence resulted in a system deviation as the flight plan for the active aircraft was removed from the system so the other flight plan could be activated. This action resulted in the data block being dropped from the scope of the controller and the aircraft violated the airspace of the next sector. Each time this situation has occurred, the airlines say their dispatcher is supposed to amend the call sign of the aircraft that is about to depart, but this requires a manual change be input into the computer system. This procedure has failed 3 times. My recommendation to resolve this situation is very simple -- on connecting flts, if you change airplanes, you change call signs. With all the numbers available to the acrs, this should not be a major fix.

Google
 

Original NASA ASRS Text

Title: LFT NOTIFIED ZHU OF DUPLICATE BEACON CODE OF DEPARTING E145. ZHU DETERMINES CALL SIGN STILL IN USE FROM ENRTE COMPANY E145.

Narrative: LFT DEP CALLED TO ADVISE ACR XXX HAD DEPARTED LFT, BUT THEY COULD NOT DEPART HIM IN THE COMPUTER TO ACTIVATE FLT PLAN. I TOOK RADAR CONTACT AND THEN DID A FLT PLAN READOUT ON ACR XXX AND DISCOVERED ACR XXX WAS ALREADY BEING USED BY A FLT FROM IAH TO SLW. I THEN AMENDED THE LFT ACR XXX TO ACR XX AND DEPARTED THE ACFT AND STARTED A TRACK ON THIS ACFT. THIS IS THE THIRD TIME THIS EXACT SIT HAS OCCURRED TO ME PERSONALLY. THE FIRST TIME WAS ABOUT 6 MONTHS AGO. THE SECOND 2 WKS AGO, AND THEN AGAIN NOW. I HAVE TALKED WITH OTHER CTLRS WHO HAVE HAD THIS SAME SIT ALSO. ONE OCCURRENCE RESULTED IN A SYS DEV AS THE FLT PLAN FOR THE ACTIVE ACFT WAS REMOVED FROM THE SYS SO THE OTHER FLT PLAN COULD BE ACTIVATED. THIS ACTION RESULTED IN THE DATA BLOCK BEING DROPPED FROM THE SCOPE OF THE CTLR AND THE ACFT VIOLATED THE AIRSPACE OF THE NEXT SECTOR. EACH TIME THIS SIT HAS OCCURRED, THE AIRLINES SAY THEIR DISPATCHER IS SUPPOSED TO AMEND THE CALL SIGN OF THE ACFT THAT IS ABOUT TO DEPART, BUT THIS REQUIRES A MANUAL CHANGE BE INPUT INTO THE COMPUTER SYS. THIS PROC HAS FAILED 3 TIMES. MY RECOMMENDATION TO RESOLVE THIS SIT IS VERY SIMPLE -- ON CONNECTING FLTS, IF YOU CHANGE AIRPLANES, YOU CHANGE CALL SIGNS. WITH ALL THE NUMBERS AVAILABLE TO THE ACRS, THIS SHOULD NOT BE A MAJOR FIX.

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.