Narrative:

Air carrier X flight abac called to secure a release time to destination. The FD/GC1 controller used the correct call sign; but used air carrier X's flight abdc call sign in the following coordination with ZZZ center. In subsequent communications with flight abac; the correct call sign was used; but the flight progress strip for flight abdc was marked and used. Flight abac's plan was sent via pre departure clearance. Flight abdc's flight plan was also sent pre departure clearance. The wrong strip was used when flight abac called and requested his release; then again when he requested push; and later when he requested taxi. At some point; flight abac's plan was removed from the system by the FD/GC1 controller because he thought it was a duplicate. It wasn't a duplicate; but in fact flight abdc's flight plan that the controller was looking at. He stated that he looked at the exact same routing; but didn't notice that they were different call signs. Even though the strip that was being passed to LC1 was flight abdc's; the FD/GC1 continued using the call sign flight abac. I was monitoring this operation from the flm desk; because the controller was working the positions combined and fairly newly certified. The call sign was consistent in all transmissions except for the ZZZ center coordination and I did not catch that discrepancy. I was not hovering over the controller and checking each strip he passed because; from where I was observing; he had everything under control and was using the correct call sign. I have recommended to the controller that he pay extra attention to the information that is in front of him; that he use the information on the strip to confirm what the pilot is saying and to check for similar sounding call signs. I also recommended to him that he use extreme caution when removing any strip. I suggested that he pause and process all of the information in front of him for each action.

Related reports:

Google
 

Original NASA ASRS Text

Title: Tower Supervisor described a confused IFR clearance issuance event when the FD Controller continued to confuse a similar sounding air carrier call sign and then inadvertently removed an active IFR strip in the process.

Narrative: Air Carrier X Flight ABAC called to secure a release time to destination. The FD/GC1 Controller used the correct call sign; but used Air Carrier X's Flight ABDC call sign in the following coordination with ZZZ Center. In subsequent communications with Flight ABAC; the correct call sign was used; but the flight progress strip for Flight ABDC was marked and used. Flight ABAC's plan was sent via PDC. Flight ABDC's flight plan was also sent PDC. The wrong strip was used when Flight ABAC called and requested his release; then again when he requested push; and later when he requested taxi. At some point; Flight ABAC's plan was removed from the system by the FD/GC1 Controller because he thought it was a duplicate. It wasn't a duplicate; but in fact Flight ABDC's flight plan that the Controller was looking at. He stated that he looked at the exact same routing; but didn't notice that they were different call signs. Even though the strip that was being passed to LC1 was Flight ABDC's; the FD/GC1 continued using the call sign Flight ABAC. I was monitoring this operation from the FLM desk; because the Controller was working the positions combined and fairly newly certified. The call sign was consistent in all transmissions except for the ZZZ Center coordination and I did not catch that discrepancy. I was not hovering over the Controller and checking each strip he passed because; from where I was observing; he had everything under control and was using the correct call sign. I have recommended to the Controller that he pay extra attention to the information that is in front of him; that he use the information on the strip to confirm what the pilot is saying and to check for similar sounding call signs. I also recommended to him that he use extreme caution when removing any strip. I suggested that he pause and process all of the information in front of him for each action.

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