Narrative:

Our flight was B727 talking to atl approach. We were on a 360 degree heading, base leg for runway 27L at 5000 ft. Approach said, 'you have B727 traffic at 2 O'clock, 5000 ft, good rate to 4000 ft.' we read back the clearance and descended at 1500 FPM. At about 4500 ft approach said, 'maintain 5000 ft.' we dished out at about 4300 ft and climbed back to 5000 ft. In the process we got a TA and the so established visual contact with a B767 at 4000 ft at 9 O'clock. Apparently, either we copied the clearance for B767 (which makes sense) or approach was confused and actually cleared us to 4000 ft. On the ground, I called approach control. The controller had already been relieved, but it was the supervisor's impression that we had copied the wrong clearance, but they wouldn't know till they listened to the tapes. At any rate, separation was not lost in that visual contact was maintained. This was a very busy time on the frequency with the additional complication of similar sounding call signs. In addition, we had another pilot on the jump seat, and we were all of the opinion that the controller had, in fact, cleared us 'good rate to 4000 ft.' supplemental information from acn 403585: on approach into atl, our flight was given a heading of 360 degrees. The response to the heading clipped the controller's call. The controller was queried and he directed a descent from 5000 ft to 4000 ft, and gives instructions to expedite the descent. At the same time, traffic was given -- a B727 at 2 O'clock. Passing 4500 ft in the descent to 4000 ft, the controller directed an immediate climb to 5000 ft and advised of B767 traffic, 3 NM at 10 O'clock. The B767 traffic was visually acquired at 10 O'clock, 2 NM away.

Related reports:

Google
 

Original NASA ASRS Text

Title: A DSNDING B727 CREW HAS A POTENTIAL CONFLICT WITH A DSNDING B767, BOTH BEING VECTORED INTO ATL. COM MIX UP IN SIMILAR SOUNDING ALPHA NUMERIC.

Narrative: OUR FLT WAS B727 TALKING TO ATL APCH. WE WERE ON A 360 DEG HDG, BASE LEG FOR RWY 27L AT 5000 FT. APCH SAID, 'YOU HAVE B727 TFC AT 2 O'CLOCK, 5000 FT, GOOD RATE TO 4000 FT.' WE READ BACK THE CLRNC AND DSNDED AT 1500 FPM. AT ABOUT 4500 FT APCH SAID, 'MAINTAIN 5000 FT.' WE DISHED OUT AT ABOUT 4300 FT AND CLBED BACK TO 5000 FT. IN THE PROCESS WE GOT A TA AND THE SO ESTABLISHED VISUAL CONTACT WITH A B767 AT 4000 FT AT 9 O'CLOCK. APPARENTLY, EITHER WE COPIED THE CLRNC FOR B767 (WHICH MAKES SENSE) OR APCH WAS CONFUSED AND ACTUALLY CLRED US TO 4000 FT. ON THE GND, I CALLED APCH CTL. THE CTLR HAD ALREADY BEEN RELIEVED, BUT IT WAS THE SUPVR'S IMPRESSION THAT WE HAD COPIED THE WRONG CLRNC, BUT THEY WOULDN'T KNOW TILL THEY LISTENED TO THE TAPES. AT ANY RATE, SEPARATION WAS NOT LOST IN THAT VISUAL CONTACT WAS MAINTAINED. THIS WAS A VERY BUSY TIME ON THE FREQ WITH THE ADDITIONAL COMPLICATION OF SIMILAR SOUNDING CALL SIGNS. IN ADDITION, WE HAD ANOTHER PLT ON THE JUMP SEAT, AND WE WERE ALL OF THE OPINION THAT THE CTLR HAD, IN FACT, CLRED US 'GOOD RATE TO 4000 FT.' SUPPLEMENTAL INFO FROM ACN 403585: ON APCH INTO ATL, OUR FLT WAS GIVEN A HDG OF 360 DEGS. THE RESPONSE TO THE HDG CLIPPED THE CTLR'S CALL. THE CTLR WAS QUERIED AND HE DIRECTED A DSCNT FROM 5000 FT TO 4000 FT, AND GIVES INSTRUCTIONS TO EXPEDITE THE DSCNT. AT THE SAME TIME, TFC WAS GIVEN -- A B727 AT 2 O'CLOCK. PASSING 4500 FT IN THE DSCNT TO 4000 FT, THE CTLR DIRECTED AN IMMEDIATE CLB TO 5000 FT AND ADVISED OF B767 TFC, 3 NM AT 10 O'CLOCK. THE B767 TFC WAS VISUALLY ACQUIRED AT 10 O'CLOCK, 2 NM AWAY.

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.