Altitude deviation altitude overshot in climb.

Attributes
ACN	216672
Time
Date	199207
Day	Mon
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : dbq
State Reference	IA
Altitude	msl bound lower : 28000 msl bound upper : 29400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zau tower : atl
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 235 flight time total : 12000 flight time type : 235
ASRS Report	216672
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : instrument pilot : flight engineer pilot : commercial
Experience	flight time last 90 days : 35 flight time total : 2100 flight time type : 35
ASRS Report	216665
Events
Anomaly	altitude deviation : excursion from assigned altitude conflict : airborne less severe non adherence : clearance non adherence : required legal separation other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance flight crew : returned to intended course or assigned course other
Consequence	Other
Miss Distance	horizontal : 0 vertical : 1600
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Error

Narrative:

During climb out flight from chicago to minneapolis was cleared by ZAU on frequency 132.72 to FL310. After passing FL292, center cleared flight back to FL280 because of crossing traffic at FL310. The controller inquired if we were back at FL280 and the first officer replied we were back into a descent passing FL294. The first officer told the controller we had been cleared to FL310, read it back and the controller's response was that he had just taken over the position and did not know what the previous controller cleared us to, but he showed that we should be at FL280. When asked if there was a conflict, he stated we passed below traffic at FL310 by 1600 ft. He later thanked us for our descent back to FL280. No further discussion.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT IN CLB.

Narrative: DURING CLBOUT FLT FROM CHICAGO TO MINNEAPOLIS WAS CLRED BY ZAU ON FREQ 132.72 TO FL310. AFTER PASSING FL292, CTR CLRED FLT BACK TO FL280 BECAUSE OF XING TFC AT FL310. THE CTLR INQUIRED IF WE WERE BACK AT FL280 AND THE FO REPLIED WE WERE BACK INTO A DSCNT PASSING FL294. THE FO TOLD THE CTLR WE HAD BEEN CLRED TO FL310, READ IT BACK AND THE CTLR'S RESPONSE WAS THAT HE HAD JUST TAKEN OVER THE POS AND DID NOT KNOW WHAT THE PREVIOUS CTLR CLRED US TO, BUT HE SHOWED THAT WE SHOULD BE AT FL280. WHEN ASKED IF THERE WAS A CONFLICT, HE STATED WE PASSED BELOW TFC AT FL310 BY 1600 FT. HE LATER THANKED US FOR OUR DSCNT BACK TO FL280. NO FURTHER DISCUSSION.

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.