Narrative:

Atl approach vectored us onto a visual approach for runway 27L in atl with night VMC conditions. There was minimum separation between us and the 2 aircraft ahead of us. Aware of this, we were slowed to very near our final approach speed and the separation was still a concern to us. After switching to tower, fully configured and with clearance to land, we questioned the controller on our separation with the aircraft ahead. At this time the controller stated 'this isn't going to work' and instructed us to go around. I was flying the aircraft with the autoplt off and the go around was flown manually (automatic throttles disconnected). Published missed approach altitude ws 3500 ft and was briefed and set in mode control panel altitude window. In hindsight I realize the controller told us to climb to 3000 ft. I initiated the go around at approximately 1800 ft MSL and was instructed to turn left to 180 degrees. As we were raising gear, reconfiguring flaps, adding power, turning and climbing, the controller updated our heading to 120 degrees. The captain was making a PA to the passenger, and I reached up to update the heading bug and respond to the controller. I then noticed us climbing through 3500 ft (the published altitude). I immediately began to arrest the climb and descend back to 3000 ft. I believe we 'topped out' at 3800 ft. The controller then instructed us to maintain 3500 ft. There was no known conflict or remarks from the controller, we came back around for another visual and landing on runway 27L. We failed to aviate navigate and then communicate. The PA should have waited until level off and /or automation restored. Add to this a very light, pwrful aircraft with over 1200 ft to climb while turning, reconfiguring and talking and you have an altitude deviation. Prioritize and fly the airplane!

Related reports:

Google
 

Original NASA ASRS Text

Title: A B767-300 FLC OVERSHOOTS THEIR MISSED APCH ALT AFTER TWR ASSIGNS AN ALT FOR A MISSED APCH OTHER THAN THAT PUBLISHED AT ATL, GA.

Narrative: ATL APCH VECTORED US ONTO A VISUAL APCH FOR RWY 27L IN ATL WITH NIGHT VMC CONDITIONS. THERE WAS MINIMUM SEPARATION BETWEEN US AND THE 2 ACFT AHEAD OF US. AWARE OF THIS, WE WERE SLOWED TO VERY NEAR OUR FINAL APCH SPD AND THE SEPARATION WAS STILL A CONCERN TO US. AFTER SWITCHING TO TWR, FULLY CONFIGURED AND WITH CLRNC TO LAND, WE QUESTIONED THE CTLR ON OUR SEPARATION WITH THE ACFT AHEAD. AT THIS TIME THE CTLR STATED 'THIS ISN'T GOING TO WORK' AND INSTRUCTED US TO GAR. I WAS FLYING THE ACFT WITH THE AUTOPLT OFF AND THE GAR WAS FLOWN MANUALLY (AUTO THROTTLES DISCONNECTED). PUBLISHED MISSED APCH ALT WS 3500 FT AND WAS BRIEFED AND SET IN MODE CTL PANEL ALT WINDOW. IN HINDSIGHT I REALIZE THE CTLR TOLD US TO CLB TO 3000 FT. I INITIATED THE GAR AT APPROX 1800 FT MSL AND WAS INSTRUCTED TO TURN LEFT TO 180 DEGS. AS WE WERE RAISING GEAR, RECONFIGURING FLAPS, ADDING PWR, TURNING AND CLBING, THE CTLR UPDATED OUR HDG TO 120 DEGS. THE CAPT WAS MAKING A PA TO THE PAX, AND I REACHED UP TO UPDATE THE HDG BUG AND RESPOND TO THE CTLR. I THEN NOTICED US CLBING THROUGH 3500 FT (THE PUBLISHED ALT). I IMMEDIATELY BEGAN TO ARREST THE CLB AND DSND BACK TO 3000 FT. I BELIEVE WE 'TOPPED OUT' AT 3800 FT. THE CTLR THEN INSTRUCTED US TO MAINTAIN 3500 FT. THERE WAS NO KNOWN CONFLICT OR REMARKS FROM THE CTLR, WE CAME BACK AROUND FOR ANOTHER VISUAL AND LNDG ON RWY 27L. WE FAILED TO AVIATE NAVIGATE AND THEN COMMUNICATE. THE PA SHOULD HAVE WAITED UNTIL LEVEL OFF AND /OR AUTOMATION RESTORED. ADD TO THIS A VERY LIGHT, PWRFUL ACFT WITH OVER 1200 FT TO CLB WHILE TURNING, RECONFIGURING AND TALKING AND YOU HAVE AN ALT DEV. PRIORITIZE AND FLY THE AIRPLANE!

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.