Narrative:

We had multiple issues/threats occur in a short period of time during our arrival into kden. To start with the approach briefing was delayed due to ACARS not working; which required the first officer to get the ATIS manually and then retrieve the landing data. We had briefed for the ILS and then got the RNAV (rnp) Z runway 17R. After loading the RNAV and dealing with a discontinuity issue and rebriefing the approach; we were asked to hold 280 knots on the arrival until advised. We were approaching harum and the aircraft wanted to slow to 250 knots as published. I used speed intervention to hold 280 knots while I entered 280 knots for harum on the legs page. When I closed the speed window I expected the speed to stay at 280; but it started to decelerate to 250. I opened the window again and dialed 280 in the window and then entered 280 on the descent page for descent speed and closed the window expecting the speed to stay at 280. It again started to slow to 250 knots; and again I had to use speed intervention to maintain 280 knots. When the altitude intervention button is pushed; the VNAV path mode changed to VNAV speed mode which resulted in an idle descent. I was aware that we were descending approximately 2500 fpm when less than 1000 fpm was needed to cross harum at 13;000 feet. I had previously set 11;000 feet in the MCP altitude window because we were cleared to descend via the arrival. My mistake was selecting vertical speed mode and reducing our descent rate to 900 fpm to make a smoother descent to cross harum at 13;000 feet; and then forgetting to reset the altitude window from 11;000 feet to 13;000 feet. Our descent continued through 13;000 feet to about 12;600 feet when ATC advised us to return to 13;000 feet. I've been doing this for a while and am aware of the error that I made. I don't believe these issues/threats are that difficult to deal with and have dealt with them successfully many times in the past. I would like to think that this was just a fluke due to the fact that multiple threats hit in a short period of time.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-700 Captain reported overshooting a cleared altitude on arrival into DEN.

Narrative: We had multiple issues/threats occur in a short period of time during our arrival into KDEN. To start with the Approach Briefing was delayed due to ACARS not working; which required the First Officer to get the ATIS manually and then retrieve the landing data. We had briefed for the ILS and then got the RNAV (RNP) Z Runway 17R. After loading the RNAV and dealing with a discontinuity issue and rebriefing the approach; we were asked to hold 280 knots on the arrival until advised. We were approaching HARUM and the aircraft wanted to slow to 250 knots as published. I used Speed Intervention to hold 280 knots while I entered 280 knots for HARUM on the LEGS page. When I closed the speed window I expected the speed to stay at 280; but it started to decelerate to 250. I opened the window again and dialed 280 in the window and then entered 280 on the Descent page for descent speed and closed the window expecting the speed to stay at 280. It again started to slow to 250 knots; and again I had to use Speed Intervention to maintain 280 knots. When the Altitude Intervention button is pushed; the VNAV PATH mode changed to VNAV Speed mode which resulted in an idle descent. I was aware that we were descending approximately 2500 fpm when less than 1000 fpm was needed to cross HARUM at 13;000 feet. I had previously set 11;000 feet in the MCP altitude window because we were cleared to descend via the arrival. My mistake was selecting Vertical Speed mode and reducing our descent rate to 900 fpm to make a smoother descent to cross HARUM at 13;000 feet; and then forgetting to reset the altitude window from 11;000 feet to 13;000 feet. Our descent continued through 13;000 feet to about 12;600 feet when ATC advised us to return to 13;000 feet. I've been doing this for a while and am aware of the error that I made. I don't believe these issues/threats are that difficult to deal with and have dealt with them successfully many times in the past. I would like to think that this was just a fluke due to the fact that multiple threats hit in a short period of time.

Data retrieved from NASA's ASRS site 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.