Narrative:

I leveled out at 6000 ft instead of 5000 ft as assigned in ATC clearance. I honestly don't know if I misread the ACARS clearance and misdialed the initial altitude or if I was distraction while setting up and 6000 ft was left from prior leg. At any rate, 6000 ft was mistakenly set and not challenged later. This was an IOE trip after finishing training. I may have been too focused on proper programming of FMC and not enough on basics. Also, a short taxi/high workload taxi out helped to keep us from catching a basic error. Long and short is -- all basic clearance information must be doublechked and confirmed every time. Supplemental information from acn 411744: during climb out the student, first officer in training, set 6000 ft in the altitude window. The student had been on a similar FMC aircraft that had EFIS. On climb out from dca, while level at 6000 ft, the controller asked about our assigned altitude. Due to previous incorrect lateral navigation entries, cockpit attention was diverted from altitude readings/checks normally accomplished. Busy, short taxi path involving high workload during briefing. Radio confusion about crossing runway 33. Glare on altitude window LCD readout, making it difficult to read. Short taxi route, teaching environment during high workload. Tower rushing our aircraft to fill an 'arrival slot' for our departure resulting in checklists being accomplished quickly. ACARS departure information being located well behind the pilot's normal field of vision and requiring information to be read sideways. Student's incorrect entry (later corrected) in the lateral data navigation base requiring several corrective entries by both pilot and diverting attention during climb out. Recommendations: study feasibility of ACARS data being placed/repeated to pilot's normal field of vision.

Google
 

Original NASA ASRS Text

Title: A CLBING B737-300 OVERSHOT ITS ASSIGNED ALT OF 5000 FT BY 1000 FT. FO WAS IN TRAINING.

Narrative: I LEVELED OUT AT 6000 FT INSTEAD OF 5000 FT AS ASSIGNED IN ATC CLRNC. I HONESTLY DON'T KNOW IF I MISREAD THE ACARS CLRNC AND MISDIALED THE INITIAL ALT OR IF I WAS DISTR WHILE SETTING UP AND 6000 FT WAS LEFT FROM PRIOR LEG. AT ANY RATE, 6000 FT WAS MISTAKENLY SET AND NOT CHALLENGED LATER. THIS WAS AN IOE TRIP AFTER FINISHING TRAINING. I MAY HAVE BEEN TOO FOCUSED ON PROPER PROGRAMMING OF FMC AND NOT ENOUGH ON BASICS. ALSO, A SHORT TAXI/HIGH WORKLOAD TAXI OUT HELPED TO KEEP US FROM CATCHING A BASIC ERROR. LONG AND SHORT IS -- ALL BASIC CLRNC INFO MUST BE DOUBLECHKED AND CONFIRMED EVERY TIME. SUPPLEMENTAL INFO FROM ACN 411744: DURING CLBOUT THE STUDENT, FO IN TRAINING, SET 6000 FT IN THE ALT WINDOW. THE STUDENT HAD BEEN ON A SIMILAR FMC ACFT THAT HAD EFIS. ON CLBOUT FROM DCA, WHILE LEVEL AT 6000 FT, THE CTLR ASKED ABOUT OUR ASSIGNED ALT. DUE TO PREVIOUS INCORRECT LATERAL NAV ENTRIES, COCKPIT ATTN WAS DIVERTED FROM ALT READINGS/CHKS NORMALLY ACCOMPLISHED. BUSY, SHORT TAXI PATH INVOLVING HIGH WORKLOAD DURING BRIEFING. RADIO CONFUSION ABOUT XING RWY 33. GLARE ON ALT WINDOW LCD READOUT, MAKING IT DIFFICULT TO READ. SHORT TAXI RTE, TEACHING ENVIRONMENT DURING HIGH WORKLOAD. TWR RUSHING OUR ACFT TO FILL AN 'ARR SLOT' FOR OUR DEP RESULTING IN CHKLISTS BEING ACCOMPLISHED QUICKLY. ACARS DEP INFO BEING LOCATED WELL BEHIND THE PLT'S NORMAL FIELD OF VISION AND REQUIRING INFO TO BE READ SIDEWAYS. STUDENT'S INCORRECT ENTRY (LATER CORRECTED) IN THE LATERAL DATA NAV BASE REQUIRING SEVERAL CORRECTIVE ENTRIES BY BOTH PLT AND DIVERTING ATTN DURING CLBOUT. RECOMMENDATIONS: STUDY FEASIBILITY OF ACARS DATA BEING PLACED/REPEATED TO PLT'S NORMAL FIELD OF VISION.

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.