Slc controller described an unsafe condition when two same company aircraft with similar sounding fo...

Narrative:

Flight abcd and flight abgd taxied out for departure within minutes of each other at slc. I believe one was a CRJ900 and one was a CRJ200. I am reasonably sure that I used the right call sign but the flight strips were right next to each other in the bay and I apparently grabbed the wrong one. The aircraft got down to the end and the local controller departed the aircraft and it wasn't until after the aircraft tagged up that he/she realized that he/she had the wrong strip. It wasn't a dangerous situation this time; however it could have been because we routinely use visual separation between aircraft. It could have been a same route situation and we could have been expecting different routes and been applying visual. The similar sounding call signs and the darkness were the main culprits. I believe I would have caught the problem had it been daytime because I would have noticed the difference. Later on in the session there was another situation between flight acbd and flight adbc on the same departures respectively. We handled those without incident but it's another example of the problem we have with airline call signs. I also may have caught the first situation had I been a little less busy; the departure push was just starting; so when the original aircraft taxied; I wasn't busy; but I got busy just after that.

Original NASA ASRS Text

Title: SLC Controller described an unsafe condition when two same company aircraft with similar sounding four digit flight numbers were confused with regard to routing's issued.

Narrative: Flight ABCD and Flight ABGD taxied out for departure within minutes of each other at SLC. I believe one was a CRJ900 and one was a CRJ200. I am reasonably sure that I used the right call sign but the flight strips were right next to each other in the bay and I apparently grabbed the wrong one. The aircraft got down to the end and the Local Controller departed the aircraft and it wasn't until after the aircraft tagged up that he/she realized that he/she had the wrong strip. It wasn't a dangerous situation this time; however it could have been because we routinely use visual separation between aircraft. It could have been a same route situation and we could have been expecting different routes and been applying visual. The similar sounding call signs and the darkness were the main culprits. I believe I would have caught the problem had it been daytime because I would have noticed the difference. Later on in the session there was another situation between Flight ACBD and Flight ADBC on the same departures respectively. We handled those without incident but it's another example of the problem we have with airline call signs. I also may have caught the first situation had I been a little less busy; the departure push was just starting; so when the original aircraft taxied; I wasn't busy; but I got busy just after that.

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

Attributes
ACN	1068893
Time
Date	201302
Local Time Of Day	0001-0600
Place
Locale Reference	SLC.Airport
State Reference	UT
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Regional Jet 700 ER/LR (CRJ700)
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Slc controller described an unsafe condition when two same company aircraft with similar sounding four digit flight numbers were confused with regard to routing's issued.