Narrative:

While stabilized with localizer and glideslope capture on ILS to runway 35L at den; with an aircraft on parallel approach to runway 35R; we received a TCAS resolution advisory (RA) warning. As pilot flying I disconnected autopilot and autothrottle and complied with 'adjust vertical speed' RA. I was unable to regain a stabilized approach; so I called for a missed approach to include the verbiage 'set missed approach altitude.' tower assigned an altitude to climb to which is the reason for this report. The pilot monitoring (pm) dialed (and he believes read back) 9;000 feet in the MCP. When climbing through approximately 8;000 feet MSL; the controller notified us he assigned 7;000 feet. The pm insisted we had been cleared to 9;000 feet. We were then assigned a departure frequency and received vectors back to runway 35L for a landing. When ATC declared we had climbed to the wrong altitude; I thought back and could not remember what clearance was given. I must have been task saturated with the missed approach and did not adequately focus on hearing the clearance. I am fairly confident I verified 9;000 feet in the MCP; but I was not aware this was possibly the wrong altitude. I recently watched the video about the low airspeed incident during a go-around and was in the 'yellow to red' trying to ensure I did the steps correctly which diverted attention from hearing the clearance consciously. Perhaps a preventive measure would be mentally 'chair-flying' the steps more often so it takes less mental capacity.

Google
 

Original NASA ASRS Text

Title: B737-700 flight crew receives a TCAS RA during a night IMC ILS caused by traffic on the parallel runway and complies with the RA command to reduce sink rate. This results in an unstabilized approach and a go-around. The missed approach altitude assigned by ATC is misunderstood by the First Officer resulting in an overshoot.

Narrative: While stabilized with Localizer and glideslope capture on ILS to Runway 35L at DEN; with an aircraft on parallel approach to Runway 35R; we received a TCAS Resolution Advisory (RA) warning. As pilot flying I disconnected autopilot and autothrottle and complied with 'Adjust Vertical Speed' RA. I was unable to regain a stabilized approach; so I called for a missed approach to include the verbiage 'Set Missed Approach Altitude.' Tower assigned an altitude to climb to which is the reason for this report. The pilot monitoring (PM) dialed (and he believes read back) 9;000 feet in the MCP. When climbing through approximately 8;000 feet MSL; the Controller notified us he assigned 7;000 feet. The PM insisted we had been cleared to 9;000 feet. We were then assigned a departure frequency and received vectors back to Runway 35L for a landing. When ATC declared we had climbed to the wrong altitude; I thought back and could not remember what clearance was given. I must have been task saturated with the missed approach and did not adequately focus on hearing the clearance. I am fairly confident I verified 9;000 feet in the MCP; but I was not aware this was possibly the wrong altitude. I recently watched the video about the low airspeed incident during a go-around and was in the 'Yellow to Red' trying to ensure I did the steps correctly which diverted attention from hearing the clearance consciously. Perhaps a preventive measure would be mentally 'chair-flying' the steps more often so it takes less mental capacity.

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.