A pilot received confusing instructions from the center controller. The pilots delayed complying wit...

Narrative:

On a flight we were level at 27;000 feet when we received the following transmission from center. '(Aircraft X) climb and maintain flight level 290; correction (different call sign)descend and maintain flight level 280.' both of us in the cockpit hesitated to initiate the climb and concurred that his 'correction' may be wanting us to disregard his first instruction. There was then 10-15 seconds of radio chatter before we could confirm our climb to 29;000 feet. The controller confirmed the climb; and we began climbing immediately. Another controller (trainer/supervisor?) came on to ask us if we were climbing. We confirmed that we were. The controller then stressed we needed to climb at best rate to 29;000 feet in a given amount of time. We were easily able to comply with that request. I believe the only way to resolve this problem was for the controller to use the term 'break' in between his two separate commands to two separate aircraft. I believe we did the right thing in delaying our climb; as his phraseology made us believe there was a conflict with the climb. A quick scan of our TCAS showed that as a possibility. Instead; it sounds as though they needed us to climb as soon as possible. I do not believe any separation issues occurred. We were able to meet the controller's climb requirement well before the timed duration he gave us.

Original NASA ASRS Text

Title: A pilot received confusing instructions from the Center controller. The pilots delayed complying with the instruction until they were able to verify the instruction with the Controller.

Narrative: On a flight we were level at 27;000 feet when we received the following transmission from Center. '(Aircraft X) climb and maintain flight level 290; Correction (Different Call Sign)descend and maintain Flight level 280.' Both of us in the cockpit hesitated to initiate the climb and concurred that his 'correction' may be wanting us to disregard his first instruction. There was then 10-15 seconds of radio chatter before we could confirm our climb to 29;000 feet. The Controller confirmed the climb; and we began climbing immediately. Another controller (Trainer/Supervisor?) came on to ask us if we were climbing. We confirmed that we were. The controller then stressed we needed to climb at best rate to 29;000 feet in a given amount of time. We were easily able to comply with that request. I believe the only way to resolve this problem was for the controller to use the term 'Break' in between his two separate commands to two separate aircraft. I believe we did the right thing in delaying our climb; as his phraseology made us believe there was a conflict with the climb. A quick scan of our TCAS showed that as a possibility. Instead; it sounds as though they needed us to climb ASAP. I do not believe any separation issues occurred. We were able to meet the controller's climb requirement well before the timed duration he gave us.

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

Attributes
ACN	1352520
Time
Date	201605
Local Time Of Day	1201-1800
Place
Locale Reference	ZOB.ARTCC
State Reference	OH
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Make Model Name	Beechjet 400
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Direct
Flight Plan	IFR
Person 1
Function	First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor
Experience	Flight Crew Last 90 Days 75 Flight Crew Total 2650 Flight Crew Type 1600
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance

A pilot received confusing instructions from the center controller. The pilots delayed complying with the instruction until they were able to verify the instruction with the controller.