Similar a/north result in clearance to descent acknowledged by wrong aircraft.

Attributes
ACN	89932
Time
Date	198806
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : pie
State Reference	FL
Altitude	msl bound lower : 29000 msl bound upper : 31000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zjx
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other descent other
Route In Use	enroute airway : j43
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 230 flight time total : 6500 flight time type : 980
ASRS Report	89932
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : commercial pilot : instrument pilot : atp
Experience	flight time last 90 days : 220 flight time total : 11000
ASRS Report	89945
Events
Anomaly	altitude deviation : excursion from assigned altitude other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

Jax center called our flight number, 'company abc descent to FL290.' we were cruising at FL330. I responded 'roger out of 330 to 290, company abc.' the captain was flying the aircraft and began to descend to 29000'. I informed the captain that I would be off frequency to set the tpa ATIS. I was copying the ATIS when I felt the aircraft begin to level off, so I looked up and asked the captain what was the matter? He said the controller questioned what altitude were we descending to. He (captain) replied that it was to our cleared altitude of FL290. The controller told him that the clearance had been given to company abd, not company abc. At this point company abd who had not replied to company abc clearance replied they were level FL330. We were then cleared down to FL270 and company abd cleared to F290. This was going on (the conversation) as I was on the other frequency. Why didn't the controller correct our reply to his clearance when we replied company abc down to FL290? This would have averted any altitude infringement or miscom. There was no evasive action nor any other traffic reported in our area.

Original NASA ASRS Text

Title: SIMILAR A/N RESULT IN CLRNC TO DESCENT ACKNOWLEDGED BY WRONG ACFT.

Narrative: JAX CENTER CALLED OUR FLT NUMBER, 'COMPANY ABC DSCNT TO FL290.' WE WERE CRUISING AT FL330. I RESPONDED 'ROGER OUT OF 330 TO 290, COMPANY ABC.' THE CAPT WAS FLYING THE ACFT AND BEGAN TO DSND TO 29000'. I INFORMED THE CAPT THAT I WOULD BE OFF FREQ TO SET THE TPA ATIS. I WAS COPYING THE ATIS WHEN I FELT THE ACFT BEGIN TO LEVEL OFF, SO I LOOKED UP AND ASKED THE CAPT WHAT WAS THE MATTER? HE SAID THE CTLR QUESTIONED WHAT ALT WERE WE DSNDING TO. HE (CAPT) REPLIED THAT IT WAS TO OUR CLRED ALT OF FL290. THE CTLR TOLD HIM THAT THE CLRNC HAD BEEN GIVEN TO COMPANY ABD, NOT COMPANY ABC. AT THIS POINT COMPANY ABD WHO HAD NOT REPLIED TO COMPANY ABC CLRNC REPLIED THEY WERE LEVEL FL330. WE WERE THEN CLRED DOWN TO FL270 AND COMPANY ABD CLRED TO F290. THIS WAS GOING ON (THE CONVERSATION) AS I WAS ON THE OTHER FREQ. WHY DIDN'T THE CTLR CORRECT OUR REPLY TO HIS CLRNC WHEN WE REPLIED COMPANY ABC DOWN TO FL290? THIS WOULD HAVE AVERTED ANY ALT INFRINGEMENT OR MISCOM. THERE WAS NO EVASIVE ACTION NOR ANY OTHER TFC RPTED IN OUR AREA.

Data retrieved from NASA's ASRS site as of August 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.