Narrative:

On the landr 3 arrival into den we were at FL280 with a clearance to cross landr at 17000 ft. At our top of descent ATC gave us a descent to FL260. I understood that to mean descend now to FL260 the on to cross landr at 17000 ft. The MCP altitude alert was not reset to FL260. The first officer gave the correct call of 'out of FL270 for FL260.' I questioned that, still thinking we were cleared to 17000 ft and that we were high on the descent. Approaching FL260 the first officer said 'we are only cleared to FL260' and I began to level. We went through FL260 down to FL255 and then back to FL260. We asked the controller to confirm our altitude and were told FL260. My perception was we were high on the descent and needed to get down. I focused on that instead of the real clearance to FL260. The altitude alert on the MCP always needs to be set to your assigned altitude! Supplemental information from acn 526353: the captain reset the MCP to 17000 ft and ensured 17000 ft and 250 KIAS at landr were in the FMC. At our top of descent ATC amended our altitude to maintain FL260. I accepted the clearance and read it back to ATC. At this time I noticed the captain initiating a 3100 FPM descent for our 2000 ft altitude change and all prior to resetting the MCP altitude. I pointed to 17000 ft set in the window and tried to clarify that the clearance was only to FL260 and that it should be reset. By this point I was calling 'FL270 for FL260.' we were rapidly approaching FL260 so I became adamant that the clearance was FL260. To this the captain replied that we were to expedite through FL260 down to 17000 ft. I put my hands on the controls to stop the descent and insisted the clearance had changed. I verified the altitude and we regained a positive rate of climb back to FL260 by FL255. There were no TCAS advisories associated with this event. Complete crew situational awareness, double check MCP prior to initiating any altitude change, ATC monitoring descents for possible separation conflicts and verifying with flight crew.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDC AMENDS DESCENT ALT, WHICH BECOMES A QUESTION WITH THE CAPT INVOLVING AN ALT OVERSHOOT AND CONFLICT WITH OTHER TFC.

Narrative: ON THE LANDR 3 ARRIVAL INTO DEN WE WERE AT FL280 WITH A CLRNC TO CROSS LANDR AT 17000 FT. AT OUR TOP OF DESCENT ATC GAVE US A DESCENT TO FL260. I UNDERSTOOD THAT TO MEAN DESCEND NOW TO FL260 THE ON TO CROSS LANDR AT 17000 FT. THE MCP ALT ALERT WAS NOT RESET TO FL260. THE FO GAVE THE CORRECT CALL OF 'OUT OF FL270 FOR FL260.' I QUESTIONED THAT, STILL THINKING WE WERE CLRED TO 17000 FT AND THAT WE WERE HIGH ON THE DESCENT. APCHING FL260 THE FO SAID 'WE ARE ONLY CLRED TO FL260' AND I BEGAN TO LEVEL. WE WENT THROUGH FL260 DOWN TO FL255 AND THEN BACK TO FL260. WE ASKED THE CTLR TO CONFIRM OUR ALT AND WERE TOLD FL260. MY PERCEPTION WAS WE WERE HIGH ON THE DESCENT AND NEEDED TO GET DOWN. I FOCUSED ON THAT INSTEAD OF THE REAL CLRNC TO FL260. THE ALT ALERT ON THE MCP ALWAYS NEEDS TO BE SET TO YOUR ASSIGNED ALT! SUPPLEMENTAL INFO FROM ACN 526353: THE CAPT RESET THE MCP TO 17000 FT AND ENSURED 17000 FT AND 250 KIAS AT LANDR WERE IN THE FMC. AT OUR TOP OF DESCENT ATC AMENDED OUR ALT TO MAINTAIN FL260. I ACCEPTED THE CLRNC AND READ IT BACK TO ATC. AT THIS TIME I NOTICED THE CAPT INITIATING A 3100 FPM DESCENT FOR OUR 2000 FT ALT CHANGE AND ALL PRIOR TO RESETTING THE MCP ALT. I POINTED TO 17000 FT SET IN THE WINDOW AND TRIED TO CLARIFY THAT THE CLRNC WAS ONLY TO FL260 AND THAT IT SHOULD BE RESET. BY THIS POINT I WAS CALLING 'FL270 FOR FL260.' WE WERE RAPIDLY APCHING FL260 SO I BECAME ADAMANT THAT THE CLRNC WAS FL260. TO THIS THE CAPT REPLIED THAT WE WERE TO EXPEDITE THROUGH FL260 DOWN TO 17000 FT. I PUT MY HANDS ON THE CTLS TO STOP THE DESCENT AND INSISTED THE CLRNC HAD CHANGED. I VERIFIED THE ALT AND WE REGAINED A POSITIVE RATE OF CLIMB BACK TO FL260 BY FL255. THERE WERE NO TCAS ADVISORIES ASSOCIATED WITH THIS EVENT. COMPLETE CREW SITUATIONAL AWARENESS, DOUBLE CHECK MCP PRIOR TO INITIATING ANY ALT CHANGE, ATC MONITORING DESCENTS FOR POSSIBLE SEPARATION CONFLICTS AND VERIFYING WITH FLT CREW.

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.