Air carrier large transport altitude deviation in response to wrong call sign.

Attributes
ACN	105525
Time
Date	198903
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : orf
State Reference	VA
Altitude	msl bound lower : 28000 msl bound upper : 31000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	cruise other
Route In Use	enroute airway : j209
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15000 flight time type : 9000
ASRS Report	105525
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : flight engineer pilot : instrument pilot : commercial
Experience	flight time last 90 days : 180 flight time total : 4400 flight time type : 2400
ASRS Report	105527
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : clearance other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	Pilot Deviation Operational Deviation other

Narrative:

We encountered chop at FL310 midway between norfolk and dixon on J209. I asked if there were any smooth altitudes and the controller said FL280 was smooth, 'air carrier X bci cleared to 280.' we called, 'out of 310 for 280.' at approximately FL283 the controller asked our altitude. We told him FL283 for FL280. He said he had cleared an air carrier Y flight # ending in 'I' to FL280. I asked him what altitude he wanted us at and he casually said, '280 is just fine, no problem.' all 3 of us questioned each other on the clearance we were given and we all agreed we were cleared to FL280. When we acknowledged the descent the only response from the controller was 'roger.' both us and air carrier Y could have called in simultaneously and with only a 'roger' we both could have thought it was for us. We do not know where the air carrier Y flight was and the controller didn't seem bothered one bit. A lot of acknowledgements are only 'roger,' and I believe this to be the case and problem here. Supplemental information from acn 105584: all pilots/controllers need to listen very carefully on today's congested frequencys.

Original NASA ASRS Text

Title: ACR LGT ALT DEVIATION IN RESPONSE TO WRONG CALL SIGN.

Narrative: WE ENCOUNTERED CHOP AT FL310 MIDWAY BTWN NORFOLK AND DIXON ON J209. I ASKED IF THERE WERE ANY SMOOTH ALTS AND THE CTLR SAID FL280 WAS SMOOTH, 'ACR X BCI CLRED TO 280.' WE CALLED, 'OUT OF 310 FOR 280.' AT APPROX FL283 THE CTLR ASKED OUR ALT. WE TOLD HIM FL283 FOR FL280. HE SAID HE HAD CLRED AN ACR Y FLT # ENDING IN 'I' TO FL280. I ASKED HIM WHAT ALT HE WANTED US AT AND HE CASUALLY SAID, '280 IS JUST FINE, NO PROB.' ALL 3 OF US QUESTIONED EACH OTHER ON THE CLRNC WE WERE GIVEN AND WE ALL AGREED WE WERE CLRED TO FL280. WHEN WE ACKNOWLEDGED THE DSCNT THE ONLY RESPONSE FROM THE CTLR WAS 'ROGER.' BOTH US AND ACR Y COULD HAVE CALLED IN SIMULTANEOUSLY AND WITH ONLY A 'ROGER' WE BOTH COULD HAVE THOUGHT IT WAS FOR US. WE DO NOT KNOW WHERE THE ACR Y FLT WAS AND THE CTLR DIDN'T SEEM BOTHERED ONE BIT. A LOT OF ACKNOWLEDGEMENTS ARE ONLY 'ROGER,' AND I BELIEVE THIS TO BE THE CASE AND PROB HERE. SUPPLEMENTAL INFO FROM ACN 105584: ALL PLTS/CTLRS NEED TO LISTEN VERY CAREFULLY ON TODAY'S CONGESTED FREQS.

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.