Narrative:

I was the captain and pilot flying [a flight] to den. Entering denver center; we were assigned several different arrival stars due to thunderstorms in the den area. Ultimately we were vectored southwest of den and assigned to descend via the crede 3 RNAV STAR. The crede 3 STAR was thoroughly briefed and 11;000 feet was inserted and confirmed in the MCP altitude window with VNAV path confirmed. As we approached the mogls fix (altitude on chart is at or above 13;000 feet); den approach vectored us off the STAR: they instructed us to turn 5 degrees right and descend to 11;000 feet for a left downwind to runway 16L. My first officer read back that exact clearance and I confirmed both the new heading and the same 11;000 feet altitude that was previously set. The controller did not challenge the altitude readback. In hindsight; I recognize there is a possibility that both my first officer and I heard and read back the wrong altitude; but neither of us think that is the case with this incident. Approximately one to two minutes later; the approach controller asked us to confirm that we were level at 13;000 feet MSL; and we responded that we were cleared to descend to 11;000 feet. Our approximate altitude at that time was 12;500 feet. He stated that our altitude clearance limit was 13;000 feet and instructed us to level off at 12;000 feet. From our perspective there was no additional impact on other aircraft such as TA or RA events. Once we got the altitude situation resolved; the remainder of the flight was normal and the aircraft landed uneventfully in den. Regarding the threat and error analysis; I did not feel like the radios were more congested or challenging than normal. Obviously; there was some sort of communication error between our flight crew and den approach. We understood and read back an 11;000 feet altitude assignment and the controller clearly thought he had assigned us a 13;000 feet MSL limit. I really don't know which party is at fault; but clearly communications were the root of the problem in this incident. Neither my first officer nor I had any question regarding our amended clearance. If I had any doubts about the correct assigned altitude; I would have requested a clarification. I do know that if we heard the clearance wrong; we also read back the same incorrect 11;000 feet limit. Please note the approach controller never corrected the altitude read back unless that call was potentially blocked by another aircraft. I have had to fill out very few reports; but I pledge to be a more aggressive listener on the radios in an effort to prevent these kind of issues.

Google
 

Original NASA ASRS Text

Title: B737NG Captain reported overshooting the assigned altitude on the CREDE 3 RNAV STAR into DEN after misinterpreting an ATC clearance.

Narrative: I was the Captain and Pilot Flying [a flight] to DEN. Entering Denver Center; we were assigned several different arrival STARS due to thunderstorms in the DEN area. Ultimately we were vectored southwest of DEN and assigned to descend via the CREDE 3 RNAV STAR. The CREDE 3 STAR was thoroughly briefed and 11;000 feet was inserted and confirmed in the MCP altitude window with VNAV PATH confirmed. As we approached the MOGLS fix (altitude on chart is at or above 13;000 feet); DEN Approach vectored us off the STAR: they instructed us to turn 5 degrees right and descend to 11;000 feet for a left downwind to Runway 16L. My First Officer read back that exact clearance and I confirmed both the new heading and the same 11;000 feet altitude that was previously set. The Controller did not challenge the altitude readback. In hindsight; I recognize there is a possibility that both my FO and I heard and read back the wrong altitude; but neither of us think that is the case with this incident. Approximately one to two minutes later; the Approach Controller asked us to confirm that we were level at 13;000 feet MSL; and we responded that we were cleared to descend to 11;000 feet. Our approximate altitude at that time was 12;500 feet. He stated that our altitude clearance limit was 13;000 feet and instructed us to level off at 12;000 feet. From our perspective there was no additional impact on other aircraft such as TA or RA events. Once we got the altitude situation resolved; the remainder of the flight was normal and the aircraft landed uneventfully in DEN. Regarding the threat and error analysis; I did not feel like the radios were more congested or challenging than normal. Obviously; there was some sort of communication error between our Flight Crew and DEN Approach. We understood and read back an 11;000 feet altitude assignment and the Controller clearly thought he had assigned us a 13;000 feet MSL limit. I really don't know which party is at fault; but clearly communications were the root of the problem in this incident. Neither my FO nor I had any question regarding our amended clearance. If I had any doubts about the correct assigned altitude; I would have requested a clarification. I do know that if we heard the clearance wrong; we also read back the same incorrect 11;000 feet limit. Please note the Approach Controller never corrected the altitude read back unless that call was potentially blocked by another aircraft. I have had to fill out very few reports; but I pledge to be a more aggressive listener on the radios in an effort to prevent these kind of issues.

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.