B757 flight crew experienced confusion as to what altitude was issued by ZID controller during busy ...

Attributes
ACN	667287
Time
Date	200508
Place
Locale Reference	navaid : iiu.vortac
State Reference	KY
Altitude	msl single value : 26000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zid.artcc
Operator	common carrier : air carrier
Make Model Name	B757 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : initial
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zid.artcc
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
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 : 10000 flight time type : 2000
ASRS Report	667287
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	flight crew : took precautionary avoidance action
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

We were level at FL250; speed reduced to 280 KIAS with ZID. My copilot asked ZID if we could have normal speed. ZID replied; 'you have traffic crossing ahead; climb to FL260.' copilot replied; and said 'what did that have to do with the speed?' we set FL260 and climbed. At about leveloff; ZID said; 'air carrier X; confirm altitude as FL250.' copilot replied; 'what?' center promptly got into a long conversation with another aircraft. Thinking that maybe he meant to say crossing aircraft at FL260; I returned to FL250. We spent the next 4 or 5 mins trying to get ZID to confirm what altitude he wanted us at. Between his constant talking to other aircraft; having other aircraft step on our xmissions and center being off frequency and not answering; this was a very tense time for me! ZID eventually said 'maintain FL250.' he said nothing else about the incident and again started a busy conversation with another aircraft. We then got a frequency change and never got to discuss it with the controller. A very disturbing day! This is unfortunately common; where center is too busy to talk to us and correct a problem. As far as I know; no conflict. No TCAS alert.

Original NASA ASRS Text

Title: B757 FLT CREW EXPERIENCED CONFUSION AS TO WHAT ALT WAS ISSUED BY ZID CTLR DURING BUSY TFC PERIOD.

Narrative: WE WERE LEVEL AT FL250; SPD REDUCED TO 280 KIAS WITH ZID. MY COPLT ASKED ZID IF WE COULD HAVE NORMAL SPD. ZID REPLIED; 'YOU HAVE TFC XING AHEAD; CLB TO FL260.' COPLT REPLIED; AND SAID 'WHAT DID THAT HAVE TO DO WITH THE SPD?' WE SET FL260 AND CLBED. AT ABOUT LEVELOFF; ZID SAID; 'ACR X; CONFIRM ALT AS FL250.' COPLT REPLIED; 'WHAT?' CTR PROMPTLY GOT INTO A LONG CONVERSATION WITH ANOTHER ACFT. THINKING THAT MAYBE HE MEANT TO SAY XING ACFT AT FL260; I RETURNED TO FL250. WE SPENT THE NEXT 4 OR 5 MINS TRYING TO GET ZID TO CONFIRM WHAT ALT HE WANTED US AT. BTWN HIS CONSTANT TALKING TO OTHER ACFT; HAVING OTHER ACFT STEP ON OUR XMISSIONS AND CTR BEING OFF FREQ AND NOT ANSWERING; THIS WAS A VERY TENSE TIME FOR ME! ZID EVENTUALLY SAID 'MAINTAIN FL250.' HE SAID NOTHING ELSE ABOUT THE INCIDENT AND AGAIN STARTED A BUSY CONVERSATION WITH ANOTHER ACFT. WE THEN GOT A FREQ CHANGE AND NEVER GOT TO DISCUSS IT WITH THE CTLR. A VERY DISTURBING DAY! THIS IS UNFORTUNATELY COMMON; WHERE CTR IS TOO BUSY TO TALK TO US AND CORRECT A PROB. AS FAR AS I KNOW; NO CONFLICT. NO TCAS ALERT.

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

B757 flight crew experienced confusion as to what altitude was issued by ZID controller during busy traffic period.