Narrative:

We were with new york approach, ewr sector, heading northeast and descending to 3000 ft, on vectors to runway 22L at ewr. 3000 ft is what I heard, read back, and set in the altitude alerter. We (first officer was PF) were descending through 3700 ft when the very busy and harried-sounding controller exclaimed that we should be at 5000 ft. We immediately climbed to 5000 ft, and responded that we had heard, read back, and set 3000 ft. Upon reaching 5000 ft, the controller then had to give us an immediate turn to 360 degrees because of an MD80 at 5000 ft. We were aircraft X, other aircraft call sign is unknown. Contributing to this incident: evening rush in new york area, controller task saturation, similar sounding call signs, no TCASII on our aircraft.

Google
 

Original NASA ASRS Text

Title: ACR DC8-7 FLC APPARENTLY ACKNOWLEDGES ALT DSCNT CLRNC FOR WRONG ACFT. APCH CTLR CHALLENGES DC8-77'S DSCNT AND ISSUES OTHER CTL INSTRUCTIONS. FLC CLBS AND COMES IN POSSIBLE CONFLICT WITH OTHER ACFT.

Narrative: WE WERE WITH NEW YORK APCH, EWR SECTOR, HDG NE AND DSNDING TO 3000 FT, ON VECTORS TO RWY 22L AT EWR. 3000 FT IS WHAT I HEARD, READ BACK, AND SET IN THE ALT ALERTER. WE (FO WAS PF) WERE DSNDING THROUGH 3700 FT WHEN THE VERY BUSY AND HARRIED-SOUNDING CTLR EXCLAIMED THAT WE SHOULD BE AT 5000 FT. WE IMMEDIATELY CLBED TO 5000 FT, AND RESPONDED THAT WE HAD HEARD, READ BACK, AND SET 3000 FT. UPON REACHING 5000 FT, THE CTLR THEN HAD TO GIVE US AN IMMEDIATE TURN TO 360 DEGS BECAUSE OF AN MD80 AT 5000 FT. WE WERE ACFT X, OTHER ACFT CALL SIGN IS UNKNOWN. CONTRIBUTING TO THIS INCIDENT: EVENING RUSH IN NEW YORK AREA, CTLR TASK SATURATION, SIMILAR SOUNDING CALL SIGNS, NO TCASII ON OUR ACFT.

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.