Narrative:

At cruise FL290 we called ZJX and asked if FL290 would be our final. The controller responded that we could expect FL330 (our filed cruise was FL330). A short while later, we heard air carrier X cleared to FL330. We read back 'air carrier X departing FL290 for FL330.' we set the altitude alert to FL330 with the other pilot verifying the entry. We began our climb to FL330. Passing approximately FL310 we heard ZJX say that the clearance to FL330 was for air carrier Y. We then asked the controller what altitude air carrier X was to maintain, and his reply was FL290. We immediately began a descent to FL290 attaining a maximum altitude of FL313. No mention was made by the controller for us to descend to FL290. The TCASII looked clear of traffic in our vicinity. In our descent to FL290 we again verified our correct cruise altitude of FL290 with the controller and was told to maintain FL290, which we did. During all of this, there seemed to be a lot of confusion between us, the air traffic controller, and air carrier Y flight. Air carrier Y even seemed surprised to be told that he had been cleared to FL330. As we received a frequency change, I informed the controller that we had received the clearance to FL330 for air carrier X and read it back that way. The controller's reply was 'whatever.' I then informed the controller that his reply was not very professional. There was no conflict with any other aircraft during our deviation, just a lot of confusion. The controller could have helped all involved by taking charge and telling each aircraft where he wanted us since he was the only one who knew where each aircraft was to be. At no time was there any mention of similar sounding call signs on the same frequency nor did we hear air carrier Y flight talk on the frequency prior to the problem.

Google
 

Original NASA ASRS Text

Title: FLC OF AN MD88 WERE GIVEN CLRNC TO HIGHER CRUISE ALT, FOR WHICH THEY HAD FILED AND EXPECTED. HOWEVER, ARTCC CTLR INTERVENED DURING THEIR CLB AND SAID THAT THE CLRNC WAS FOR ANOTHER ACFT. THEY THEN LEARNED THAT THE OTHER ACFT HAD A SIMILAR SOUNDING CALL SIGN BUT THAT THE CTLR DID NOT USE THAT ATC PROC WHEN GIVING THE CLRNC.

Narrative: AT CRUISE FL290 WE CALLED ZJX AND ASKED IF FL290 WOULD BE OUR FINAL. THE CTLR RESPONDED THAT WE COULD EXPECT FL330 (OUR FILED CRUISE WAS FL330). A SHORT WHILE LATER, WE HEARD ACR X CLRED TO FL330. WE READ BACK 'ACR X DEPARTING FL290 FOR FL330.' WE SET THE ALT ALERT TO FL330 WITH THE OTHER PLT VERIFYING THE ENTRY. WE BEGAN OUR CLB TO FL330. PASSING APPROX FL310 WE HEARD ZJX SAY THAT THE CLRNC TO FL330 WAS FOR ACR Y. WE THEN ASKED THE CTLR WHAT ALT ACR X WAS TO MAINTAIN, AND HIS REPLY WAS FL290. WE IMMEDIATELY BEGAN A DSCNT TO FL290 ATTAINING A MAX ALT OF FL313. NO MENTION WAS MADE BY THE CTLR FOR US TO DSND TO FL290. THE TCASII LOOKED CLR OF TFC IN OUR VICINITY. IN OUR DSCNT TO FL290 WE AGAIN VERIFIED OUR CORRECT CRUISE ALT OF FL290 WITH THE CTLR AND WAS TOLD TO MAINTAIN FL290, WHICH WE DID. DURING ALL OF THIS, THERE SEEMED TO BE A LOT OF CONFUSION BTWN US, THE AIR TFC CTLR, AND ACR Y FLT. ACR Y EVEN SEEMED SURPRISED TO BE TOLD THAT HE HAD BEEN CLRED TO FL330. AS WE RECEIVED A FREQ CHANGE, I INFORMED THE CTLR THAT WE HAD RECEIVED THE CLRNC TO FL330 FOR ACR X AND READ IT BACK THAT WAY. THE CTLR'S REPLY WAS 'WHATEVER.' I THEN INFORMED THE CTLR THAT HIS REPLY WAS NOT VERY PROFESSIONAL. THERE WAS NO CONFLICT WITH ANY OTHER ACFT DURING OUR DEV, JUST A LOT OF CONFUSION. THE CTLR COULD HAVE HELPED ALL INVOLVED BY TAKING CHARGE AND TELLING EACH ACFT WHERE HE WANTED US SINCE HE WAS THE ONLY ONE WHO KNEW WHERE EACH ACFT WAS TO BE. AT NO TIME WAS THERE ANY MENTION OF SIMILAR SOUNDING CALL SIGNS ON THE SAME FREQ NOR DID WE HEAR ACR Y FLT TALK ON THE FREQ PRIOR TO THE PROB.

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.