Narrative:

At initial contact with ft worth center, we were cleared from 17000 ft to FL250. We had just departed a WX holding pattern over amarillo VOR and were returning to dfw. Autoplt and autothrottles were previously engaged. As the PNF, I set the altitude window to FL250 and the captain acknowledged '250.' I then got busy working on the divert and setting up for the short leg to dfw. I glanced at the altimeter as we were approaching FL250 and called 'altitude!' to the pilot. He immediately disconnected the autoplt and pushed the nose over. The altimeter reached FL255 before starting down. Coincident with returning to level flight at FL250 the controller asked 'say altitude?' and we responded FL250. As we leveled off, I noted that the altitude set window was set at FL200 instead of FL250. Contributing factors were an extremely busy divert, 3 fast radio changes in the climb, icing, turbulence, IMC and night. We had been on approach to amarillo. When it was broken off and we were given holding instructions. We held until we hit 'bingo' fuel for dfw. We requested clearance to dfw. Amarillo approach gave us an initial climb and vector and handed us over to ZAB who climbed us to 17000 ft and turned us over to ZFW. Human factors: the captain was trying to coordination with company dispatch while climbing out. Dispatch instructed him to return to amarillo, shoot the approach and if unable to land to divert lubbock. I was hearing bits of the conversation and trying to simultaneously prepare for all contingencies. Bottom line: 1 pilot should have been strictly flying the aircraft and talking to center while the other pilot coordinated with company. I don't know how the altitude set got from 250 to 200 and why we didn't get a warning when the aircraft climbed above FL200. Corrective action: 1 pilot should be solely involved in flying or monitoring the aircraft performance.

Google
 

Original NASA ASRS Text

Title: FLC OF AN MLG OVERSHOT ALT DUE TO DISTR IN COORDINATING WX DIVERT WITH COMPANY.

Narrative: AT INITIAL CONTACT WITH FT WORTH CTR, WE WERE CLRED FROM 17000 FT TO FL250. WE HAD JUST DEPARTED A WX HOLDING PATTERN OVER AMARILLO VOR AND WERE RETURNING TO DFW. AUTOPLT AND AUTOTHROTTLES WERE PREVIOUSLY ENGAGED. AS THE PNF, I SET THE ALT WINDOW TO FL250 AND THE CAPT ACKNOWLEDGED '250.' I THEN GOT BUSY WORKING ON THE DIVERT AND SETTING UP FOR THE SHORT LEG TO DFW. I GLANCED AT THE ALTIMETER AS WE WERE APCHING FL250 AND CALLED 'ALT!' TO THE PLT. HE IMMEDIATELY DISCONNECTED THE AUTOPLT AND PUSHED THE NOSE OVER. THE ALTIMETER REACHED FL255 BEFORE STARTING DOWN. COINCIDENT WITH RETURNING TO LEVEL FLT AT FL250 THE CTLR ASKED 'SAY ALT?' AND WE RESPONDED FL250. AS WE LEVELED OFF, I NOTED THAT THE ALT SET WINDOW WAS SET AT FL200 INSTEAD OF FL250. CONTRIBUTING FACTORS WERE AN EXTREMELY BUSY DIVERT, 3 FAST RADIO CHANGES IN THE CLB, ICING, TURB, IMC AND NIGHT. WE HAD BEEN ON APCH TO AMARILLO. WHEN IT WAS BROKEN OFF AND WE WERE GIVEN HOLDING INSTRUCTIONS. WE HELD UNTIL WE HIT 'BINGO' FUEL FOR DFW. WE REQUESTED CLRNC TO DFW. AMARILLO APCH GAVE US AN INITIAL CLB AND VECTOR AND HANDED US OVER TO ZAB WHO CLBED US TO 17000 FT AND TURNED US OVER TO ZFW. HUMAN FACTORS: THE CAPT WAS TRYING TO COORD WITH COMPANY DISPATCH WHILE CLBING OUT. DISPATCH INSTRUCTED HIM TO RETURN TO AMARILLO, SHOOT THE APCH AND IF UNABLE TO LAND TO DIVERT LUBBOCK. I WAS HEARING BITS OF THE CONVERSATION AND TRYING TO SIMULTANEOUSLY PREPARE FOR ALL CONTINGENCIES. BOTTOM LINE: 1 PLT SHOULD HAVE BEEN STRICTLY FLYING THE ACFT AND TALKING TO CTR WHILE THE OTHER PLT COORDINATED WITH COMPANY. I DON'T KNOW HOW THE ALT SET GOT FROM 250 TO 200 AND WHY WE DIDN'T GET A WARNING WHEN THE ACFT CLBED ABOVE FL200. CORRECTIVE ACTION: 1 PLT SHOULD BE SOLELY INVOLVED IN FLYING OR MONITORING THE ACFT PERFORMANCE.

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.