Narrative:

While on a vector we were initially cleared to 14000 ft MSL. During descent, we were reclred to maintain 17000 ft MSL. Unable to receive cos ATIS, there was a discussion about correct altimeter setting at FL180. Approaching 17000 ft, we received a traffic alert from TCASII and went outside to look for traffic. We then received TCASII command to climb and disconnected autoplt and flew the TCASII until 'clear of traffic.' the crew had been on duty over 11 hours and fatigue was a contributing factor (long night flying back side of clock). When I looked back in cockpit, I thought I remembered seeing 16500 ft in the altimeter. The copilot was sure (since he was flying) that 'altitude select' was selected on autoplt. Since we recovered quickly at about 17300 ft and re-leveled at 17000 ft MSL, we reported our action to the controller. The other aircraft also reported receiving a TCASII alert. Factors that may have contributed: 1) flight duty had started at XA30 local the night before. Route of flight was cos-las 35 min ground time, then las-oak 2 1/2 hour ground tie, then oak-las 45 min ground time, then las-cos to arrive at approximately XL30. 2) confusion at altimeter setting at FL180 diminishing the effect of the 1000 ft to go call. 3) first night of week being most difficult new crew and tired. If the altitude was busted, it may have been in the range of 400-500 ft. It is possible the autoplt was still leveling at 17000 ft. The only other possibility could be wrong altimeter settings.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B727 CREW OVERSHOT ASSIGNED ALT DURING DSCNT, CAUSING A TCASII TA.

Narrative: WHILE ON A VECTOR WE WERE INITIALLY CLRED TO 14000 FT MSL. DURING DSCNT, WE WERE RECLRED TO MAINTAIN 17000 FT MSL. UNABLE TO RECEIVE COS ATIS, THERE WAS A DISCUSSION ABOUT CORRECT ALTIMETER SETTING AT FL180. APCHING 17000 FT, WE RECEIVED A TFC ALERT FROM TCASII AND WENT OUTSIDE TO LOOK FOR TFC. WE THEN RECEIVED TCASII COMMAND TO CLB AND DISCONNECTED AUTOPLT AND FLEW THE TCASII UNTIL 'CLR OF TFC.' THE CREW HAD BEEN ON DUTY OVER 11 HRS AND FATIGUE WAS A CONTRIBUTING FACTOR (LONG NIGHT FLYING BACK SIDE OF CLOCK). WHEN I LOOKED BACK IN COCKPIT, I THOUGHT I REMEMBERED SEEING 16500 FT IN THE ALTIMETER. THE COPLT WAS SURE (SINCE HE WAS FLYING) THAT 'ALT SELECT' WAS SELECTED ON AUTOPLT. SINCE WE RECOVERED QUICKLY AT ABOUT 17300 FT AND RE-LEVELED AT 17000 FT MSL, WE RPTED OUR ACTION TO THE CTLR. THE OTHER ACFT ALSO RPTED RECEIVING A TCASII ALERT. FACTORS THAT MAY HAVE CONTRIBUTED: 1) FLT DUTY HAD STARTED AT XA30 LCL THE NIGHT BEFORE. RTE OF FLT WAS COS-LAS 35 MIN GND TIME, THEN LAS-OAK 2 1/2 HR GND TIE, THEN OAK-LAS 45 MIN GND TIME, THEN LAS-COS TO ARRIVE AT APPROX XL30. 2) CONFUSION AT ALTIMETER SETTING AT FL180 DIMINISHING THE EFFECT OF THE 1000 FT TO GO CALL. 3) FIRST NIGHT OF WK BEING MOST DIFFICULT NEW CREW AND TIRED. IF THE ALT WAS BUSTED, IT MAY HAVE BEEN IN THE RANGE OF 400-500 FT. IT IS POSSIBLE THE AUTOPLT WAS STILL LEVELING AT 17000 FT. THE ONLY OTHER POSSIBILITY COULD BE WRONG ALTIMETER SETTINGS.

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.