Narrative:

Flight ewr-mco. Took off ewr and was level at 6000 ft being handled by new york departure control. I was PNF. Both I and the captain thought we heard our controller clear us to 16000 ft. I acknowledged the clearance with a full readback and the captain confirmed the altitude and began a climb. As we passed through about 6500 ft, our controller told us to maintain 6000 ft. The captain immediately stopped our climb and returned to 6000 ft. I asked the controller if we were not cleared to 16000 ft and he said no, it was for another aircraft. Our flight number was agg and there were at least 3 other flts on the same frequency whose number ended in G, or gg. Air carrier bjogg, air carrier aogg, and air carrier bohg, if I remember correctly. I believe we heard and responded to air carrier B0GG's clearance to 16000 ft. Unfortunately, the controller did not catch our error when I read back the clearance. This was the first leg of a pairing. Both I and the captain were well rested. We had not flown together before, but our rapport and CRM were excellent. We both believe we heard our own flight number agg 'cleared to 16000 ft.' obviously without the tapes we cannot be sure it was our error and not the controller's. I believe the main causes of this error are: 1) too many similar call signs on the same frequency. 2) controller too busy to catch incorrect readback. 3) high workload for both air crew and controller in congested airspace. Corrective actions indicate a need for slower rates of speech, more vigilance when dealing with similar call signs on congested frequencys, and increased attention paid to readbacks by controllers. Also standard reading of flight numbers. Supplemental information from acn 478558: contacted controller on landline. Traffic separation was not compromised. Other factors: very early wake-up for an early show with less than normal sleep, thus not as alert for mistakes.

Related reports:

Google
 

Original NASA ASRS Text

Title: AN MD80 FLC ACCEPTS THE CLRNC MEANT FOR ANOTHER ACR FLT HAVING A SIMILAR SOUNDING CALL SIGN WHEN 7 MI N OF COL, NJ.

Narrative: FLT EWR-MCO. TOOK OFF EWR AND WAS LEVEL AT 6000 FT BEING HANDLED BY NEW YORK DEP CTL. I WAS PNF. BOTH I AND THE CAPT THOUGHT WE HEARD OUR CTLR CLR US TO 16000 FT. I ACKNOWLEDGED THE CLRNC WITH A FULL READBACK AND THE CAPT CONFIRMED THE ALT AND BEGAN A CLB. AS WE PASSED THROUGH ABOUT 6500 FT, OUR CTLR TOLD US TO MAINTAIN 6000 FT. THE CAPT IMMEDIATELY STOPPED OUR CLB AND RETURNED TO 6000 FT. I ASKED THE CTLR IF WE WERE NOT CLRED TO 16000 FT AND HE SAID NO, IT WAS FOR ANOTHER ACFT. OUR FLT NUMBER WAS AGG AND THERE WERE AT LEAST 3 OTHER FLTS ON THE SAME FREQ WHOSE NUMBER ENDED IN G, OR GG. ACR BJOGG, ACR AOGG, AND ACR BOHG, IF I REMEMBER CORRECTLY. I BELIEVE WE HEARD AND RESPONDED TO ACR B0GG'S CLRNC TO 16000 FT. UNFORTUNATELY, THE CTLR DID NOT CATCH OUR ERROR WHEN I READ BACK THE CLRNC. THIS WAS THE FIRST LEG OF A PAIRING. BOTH I AND THE CAPT WERE WELL RESTED. WE HAD NOT FLOWN TOGETHER BEFORE, BUT OUR RAPPORT AND CRM WERE EXCELLENT. WE BOTH BELIEVE WE HEARD OUR OWN FLT NUMBER AGG 'CLRED TO 16000 FT.' OBVIOUSLY WITHOUT THE TAPES WE CANNOT BE SURE IT WAS OUR ERROR AND NOT THE CTLR'S. I BELIEVE THE MAIN CAUSES OF THIS ERROR ARE: 1) TOO MANY SIMILAR CALL SIGNS ON THE SAME FREQ. 2) CTLR TOO BUSY TO CATCH INCORRECT READBACK. 3) HIGH WORKLOAD FOR BOTH AIR CREW AND CTLR IN CONGESTED AIRSPACE. CORRECTIVE ACTIONS INDICATE A NEED FOR SLOWER RATES OF SPEECH, MORE VIGILANCE WHEN DEALING WITH SIMILAR CALL SIGNS ON CONGESTED FREQS, AND INCREASED ATTN PAID TO READBACKS BY CTLRS. ALSO STANDARD READING OF FLT NUMBERS. SUPPLEMENTAL INFO FROM ACN 478558: CONTACTED CTLR ON LANDLINE. TFC SEPARATION WAS NOT COMPROMISED. OTHER FACTORS: VERY EARLY WAKE-UP FOR AN EARLY SHOW WITH LESS THAN NORMAL SLEEP, THUS NOT AS ALERT FOR MISTAKES.

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.