Narrative:

While descending for landing at mdw, we were proceeding direct to cgt VOR. Later we were cleared to 'cross cgt at 10000 ft, maintain 6000 ft.' as PNF, I set 6000 ft into the altitude alerter for a second and then decided to set it to 10000 ft instead. I would reset it to 6000 ft when we passed cgt. The PF watched me do this. I felt he understood why the altitude alerter was set to 10000 ft and I continued my other duties. A few mins later, I was surprised to see us descending through 9500 ft. I put my hand on the yoke and said 'we need to maintain 10000 ft.' we climbed to 10000 ft direct to cgt and were not questioned by ATC. The reason for this altitude deviation was the PF setting 6000 ft in the alerter while I was involved with other duties. Our standard practice of always agreeing on the assigned altitude broke down. He thought we were cleared to 6000 ft. I may have reinforced that idea by first setting 6000 ft, then 10000 ft, but the PF failed to seek my concurrence before he reset it to 6000 ft. Contributing to this error is that we fly this route often and ZAU normally clears us to 6000 ft before reaching cgt VOR. This helps explain why the PF believed we were cleared to 6000 ft. I failed to emphasize the 10000 ft restr while setting it in the alerter. I assumed that the PF had heard ATC clearly and had heard my radio readback. We had both been on duty for about 13 hours when this incident occurred. I believe fatigue contributed to the false assumptions that we both made. It's certainly easier to be complacent about cockpit procedures when one is tired and looking forward to getting home.

Google
 

Original NASA ASRS Text

Title: A CPR FLC DSNDING A G1159 NEAR CGT FAILED TO LEVEL AT THE ALT AS ASSIGNED BY ATC.

Narrative: WHILE DSNDING FOR LNDG AT MDW, WE WERE PROCEEDING DIRECT TO CGT VOR. LATER WE WERE CLRED TO 'CROSS CGT AT 10000 FT, MAINTAIN 6000 FT.' AS PNF, I SET 6000 FT INTO THE ALT ALERTER FOR A SECOND AND THEN DECIDED TO SET IT TO 10000 FT INSTEAD. I WOULD RESET IT TO 6000 FT WHEN WE PASSED CGT. THE PF WATCHED ME DO THIS. I FELT HE UNDERSTOOD WHY THE ALT ALERTER WAS SET TO 10000 FT AND I CONTINUED MY OTHER DUTIES. A FEW MINS LATER, I WAS SURPRISED TO SEE US DSNDING THROUGH 9500 FT. I PUT MY HAND ON THE YOKE AND SAID 'WE NEED TO MAINTAIN 10000 FT.' WE CLBED TO 10000 FT DIRECT TO CGT AND WERE NOT QUESTIONED BY ATC. THE REASON FOR THIS ALTDEV WAS THE PF SETTING 6000 FT IN THE ALERTER WHILE I WAS INVOLVED WITH OTHER DUTIES. OUR STANDARD PRACTICE OF ALWAYS AGREEING ON THE ASSIGNED ALT BROKE DOWN. HE THOUGHT WE WERE CLRED TO 6000 FT. I MAY HAVE REINFORCED THAT IDEA BY FIRST SETTING 6000 FT, THEN 10000 FT, BUT THE PF FAILED TO SEEK MY CONCURRENCE BEFORE HE RESET IT TO 6000 FT. CONTRIBUTING TO THIS ERROR IS THAT WE FLY THIS RTE OFTEN AND ZAU NORMALLY CLRS US TO 6000 FT BEFORE REACHING CGT VOR. THIS HELPS EXPLAIN WHY THE PF BELIEVED WE WERE CLRED TO 6000 FT. I FAILED TO EMPHASIZE THE 10000 FT RESTR WHILE SETTING IT IN THE ALERTER. I ASSUMED THAT THE PF HAD HEARD ATC CLRLY AND HAD HEARD MY RADIO READBACK. WE HAD BOTH BEEN ON DUTY FOR ABOUT 13 HRS WHEN THIS INCIDENT OCCURRED. I BELIEVE FATIGUE CONTRIBUTED TO THE FALSE ASSUMPTIONS THAT WE BOTH MADE. IT'S CERTAINLY EASIER TO BE COMPLACENT ABOUT COCKPIT PROCS WHEN ONE IS TIRED AND LOOKING FORWARD TO GETTING HOME.

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.