Narrative:

We were on final approach to cle; behind flight abcd (third digit is the only difference; and a 5 is pretty similar looking to a 2 besides that). The last few ATC sectors had warned us of the similar call signs; including the tower controller. By the time tower told us I quipped with him that this was pretty normal for us by now; it has been going on for so long. I have to admit to getting used to it and it may even help me pay more attention to ATC. After flight abcd landed ahead of us the tower controller; whom we had already had the conversation about the call signs; said 'flight abgd turn left and cross runway 24L and contact ground on the other side.' I informed him that we were unable to comply as we were still on final. The controller made the correction and re-issued the instruction to the other flight. As I admitted above; I've gotten quite used to the similar call signs in cle. I estimate 75%-90% of my flights in and out of there have at least one other flight number with only one digit difference to my own. I feel that each one is a safety concern; even the ones where nothing happens. However it is simply unreasonable for me to write a report for all of them. This event stands out to me because it highlights the safety risk from a controller error perspective. In this case it was slightly humorous as we were given taxi instructions in flight; but the fact is all of these similar call signs convene in congested terminal airspace; where an incorrectly addressed heading or altitude instruction could have serious consequences. I know that ATC has to deal with similar call signs all the time and not just from us; and getting all of their transmissions right is part of their job; and paying attention and questioning any perceived errors is part of ours; but to increase the risk of errors by introducing so many threats into our collective workload seems a little foolish to me.

Google
 

Original NASA ASRS Text

Title: Air Carrier operating at CLE voiced concern regarding his company's frequent use of four digit similar sounding flight numbers; all operating in the same time frame.

Narrative: We were on final approach to CLE; behind Flight ABCD (third digit is the only difference; and a 5 is pretty similar looking to a 2 besides that). The last few ATC sectors had warned us of the similar call signs; including the Tower Controller. By the time Tower told us I quipped with him that this was pretty normal for us by now; it has been going on for so long. I have to admit to getting used to it and it may even help me pay more attention to ATC. After Flight ABCD landed ahead of us the Tower Controller; whom we had already had the conversation about the call signs; said 'Flight ABGD turn left and cross Runway 24L and contact ground on the other side.' I informed him that we were unable to comply as we were still on final. The Controller made the correction and re-issued the instruction to the other flight. As I admitted above; I've gotten quite used to the similar call signs in CLE. I estimate 75%-90% of my flights in and out of there have at least one other flight number with only one digit difference to my own. I feel that each one is a safety concern; even the ones where nothing happens. However it is simply unreasonable for me to write a report for all of them. This event stands out to me because it highlights the safety risk from a Controller error perspective. In this case it was slightly humorous as we were given taxi instructions in flight; but the fact is all of these similar call signs convene in congested terminal airspace; where an incorrectly addressed heading or altitude instruction could have serious consequences. I know that ATC has to deal with similar call signs all the time and not just from us; and getting all of their transmissions right is part of their job; and paying attention and questioning any perceived errors is part of ours; but to increase the risk of errors by introducing so many threats into our collective workload seems a little foolish to me.

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.