ATC issues climb to en route A320, resulting in operational error.

Attributes
ACN	571558
Time
Date	200301
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : zau.artcc
State Reference	IL
Altitude	msl bound lower : 34000 msl bound upper : 35000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zau.artcc
Operator	common carrier : air carrier
Make Model Name	A320
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	cruise : enroute altitude change
Route In Use	enroute : direct
Flight Plan	IFR
Aircraft 2
Controlling Facilities	artcc : zau.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 : 150 flight time total : 20000 flight time type : 1500
ASRS Report	571558
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 160 flight time total : 15000 flight time type : 4500
ASRS Report	571155
Events
Anomaly	conflict : airborne critical non adherence : clearance non adherence : required legal separation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

Clearance was to 'climb to FL350, I need you there in 2 1/2 mins or less.' we acknowledged FL310 for FL350. I selected open climb and green DOT airspeed. Aircraft stopped climbing approximately at FL343. (1 min 45 seconds into climb) at that time, we tried to inform controller, but way too much frequency congestion to get in. At approximately 3 mins into climb, we were issued a right turn 330 degrees and then further right, 360 degrees. Once level at FL350, we were cleared direct bae. We informed controller bae wasn't on the flight plan, and then he issued a 270 degree heading. Nowhere were we aware of a loss in standard separation until about an hour later ATC requested me to contact them the next day. We spoke, and that is when I was informed of the controller's loss of separation. I asked if my cockpit was in error or the controller, and the answer was 'it was the controller's error in loss of standard separation due to non standard phraseology.' note: no TA or RA was issued by TCASII.

Original NASA ASRS Text

Title: ATC ISSUES CLB TO ENRTE A320, RESULTING IN OPERATIONAL ERROR.

Narrative: CLRNC WAS TO 'CLB TO FL350, I NEED YOU THERE IN 2 1/2 MINS OR LESS.' WE ACKNOWLEDGED FL310 FOR FL350. I SELECTED OPEN CLB AND GREEN DOT AIRSPD. ACFT STOPPED CLBING APPROX AT FL343. (1 MIN 45 SECONDS INTO CLB) AT THAT TIME, WE TRIED TO INFORM CTLR, BUT WAY TOO MUCH FREQ CONGESTION TO GET IN. AT APPROX 3 MINS INTO CLB, WE WERE ISSUED A R TURN 330 DEGS AND THEN FURTHER R, 360 DEGS. ONCE LEVEL AT FL350, WE WERE CLRED DIRECT BAE. WE INFORMED CTLR BAE WASN'T ON THE FLT PLAN, AND THEN HE ISSUED A 270 DEG HDG. NOWHERE WERE WE AWARE OF A LOSS IN STANDARD SEPARATION UNTIL ABOUT AN HR LATER ATC REQUESTED ME TO CONTACT THEM THE NEXT DAY. WE SPOKE, AND THAT IS WHEN I WAS INFORMED OF THE CTLR'S LOSS OF SEPARATION. I ASKED IF MY COCKPIT WAS IN ERROR OR THE CTLR, AND THE ANSWER WAS 'IT WAS THE CTLR'S ERROR IN LOSS OF STANDARD SEPARATION DUE TO NON STANDARD PHRASEOLOGY.' NOTE: NO TA OR RA WAS ISSUED BY TCASII.

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.