Altitude deviation altitude overshot in climb. Clearance interpretation.

Attributes
ACN	243169
Time
Date	199306
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : jst
State Reference	PA
Altitude	msl bound lower : 31000 msl bound upper : 32000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob tower : mkc
Operator	general aviation : corporate
Make Model Name	Light Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : atp
Experience	flight time last 90 days : 120 flight time total : 7500 flight time type : 2000
ASRS Report	243169
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	altitude deviation : overshoot non adherence : clearance 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
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

While climbing en route, using autoplt coupled to INS, the copilot went off frequency to talk with base operations. During this period a new altitude was assigned. Though I read back an altitude to the controller I did not remember to set the altitude alerter. When the copilot returned he noted the problem and asked me what should be set in the alerter. I said that I thought we were issued FL340, but that didn't sound right as a flight level and besides we were only filed for FL310. However, he had already set FL340 and by the time we talked through the problem we had already passed FL310 and the controller caught the error at FL320. We returned to FL310. We were told of no conflict with other traffic. I've attended a number of cockpit resource management courses and I guess this is a classic example of how important it is for both pilots to confirm clrncs immediately when they are received. If you wait too long there are just too many things going on that may confuse the issue. We have instituted a policy whereby after the PNF reads back an altitude clearance to ATC, he sets it in the alerter and the PF immediately confirms verbally. Even greater care must be taken when the radios are being used for 2 different frequencys.

Original NASA ASRS Text

Title: ALTDEV ALT OVERSHOT IN CLB. CLRNC INTERP.

Narrative: WHILE CLBING ENRTE, USING AUTOPLT COUPLED TO INS, THE COPLT WENT OFF FREQ TO TALK WITH BASE OPS. DURING THIS PERIOD A NEW ALT WAS ASSIGNED. THOUGH I READ BACK AN ALT TO THE CTLR I DID NOT REMEMBER TO SET THE ALT ALERTER. WHEN THE COPLT RETURNED HE NOTED THE PROB AND ASKED ME WHAT SHOULD BE SET IN THE ALERTER. I SAID THAT I THOUGHT WE WERE ISSUED FL340, BUT THAT DIDN'T SOUND RIGHT AS A FLT LEVEL AND BESIDES WE WERE ONLY FILED FOR FL310. HOWEVER, HE HAD ALREADY SET FL340 AND BY THE TIME WE TALKED THROUGH THE PROB WE HAD ALREADY PASSED FL310 AND THE CTLR CAUGHT THE ERROR AT FL320. WE RETURNED TO FL310. WE WERE TOLD OF NO CONFLICT WITH OTHER TFC. I'VE ATTENDED A NUMBER OF COCKPIT RESOURCE MGMNT COURSES AND I GUESS THIS IS A CLASSIC EXAMPLE OF HOW IMPORTANT IT IS FOR BOTH PLTS TO CONFIRM CLRNCS IMMEDIATELY WHEN THEY ARE RECEIVED. IF YOU WAIT TOO LONG THERE ARE JUST TOO MANY THINGS GOING ON THAT MAY CONFUSE THE ISSUE. WE HAVE INSTITUTED A POLICY WHEREBY AFTER THE PNF READS BACK AN ALT CLRNC TO ATC, HE SETS IT IN THE ALERTER AND THE PF IMMEDIATELY CONFIRMS VERBALLY. EVEN GREATER CARE MUST BE TAKEN WHEN THE RADIOS ARE BEING USED FOR 2 DIFFERENT FREQS.

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.