A B737-700 first officer set an incorrect altitude in the altitude window causing the crew to fly th...

Narrative:

It was day two of our two-day trip and the second leg that morning of four. We were running about ten minutes behind schedule due to the morning traffic for departures in XXX on our first leg. I was the first officer and the pilot flying for this leg. Even though I have been to sjc previously; it has only been maybe three or four times.we had a computer that was MEL'd which I had never seen before and which was an unexpected add to my workload. In hindsight I feel I may have been more focused on getting that information correct. Our clearance was to 'climb via the SID' which was the TECKY1 out of sjc; which neither the captain nor I had flown before. It seemed straight forward and I did a departure briefing as the pilot flying. On that departure there is an initial 'at or above' altitude followed by the hard 'at' altitude of 5;000 which is followed by another 'at or above' altitude. The final climb altitude is fl 190 which I had set in the MCP. When I briefed the departure I don't know if I just focused on the 'at or above' altitudes or was rushed; but I did not put the 5;000 hard altitude in the MCP.on the takeoff everything was normal. The captain checked on with norcal departure and stated we were climbing to fl 190 to which the controller responded but did not query us as to whether we were climbing via the SID. The captain later stated he assumed this meant we were climbing unrestricted to fl 190. Autopilot was engaged approximately 4;000 and then I went to engage VNAV and it would not engage. In hindsight I think this was due to the fact that we were already rapidly climbing to (or through) the hard altitude of 5;000 in the FMS departure; but at the time I couldn't figure out why it would not engage. At about the same time ATC asked us to just level off at our current altitude and I pressed the altitude hold mode on the MCP. The aircraft started a gradual level off at which time I think the captain realized what had happened and stated he was taking the controls and manually did the level off at approximately 6;000. We queried ATC whether they wanted us back to 5;000 and they said no; they would have a continuing climb to fl 190 in just a minute.

Original NASA ASRS Text

Title: A B737-700 First Officer set an incorrect altitude in the altitude window causing the crew to fly through an intermediate level off altitude while on the TECKY1 SID. The Captain also missed the mistake.

Narrative: It was day two of our two-day trip and the second leg that morning of four. We were running about ten minutes behind schedule due to the morning traffic for departures in XXX on our first leg. I was the First Officer and the Pilot Flying for this leg. Even though I have been to SJC previously; it has only been maybe three or four times.We had a computer that was MEL'd which I had never seen before and which was an unexpected add to my workload. In hindsight I feel I may have been more focused on getting that information correct. Our clearance was to 'climb via the SID' which was the TECKY1 out of SJC; which neither the Captain nor I had flown before. It seemed straight forward and I did a departure briefing as the Pilot Flying. On that departure there is an initial 'at or above' altitude followed by the hard 'at' altitude of 5;000 which is followed by another 'at or above' altitude. The final climb altitude is FL 190 which I had set in the MCP. When I briefed the departure I don't know if I just focused on the 'at or above' altitudes or was rushed; but I did not put the 5;000 hard altitude in the MCP.On the takeoff everything was normal. The Captain checked on with NorCal Departure and stated we were climbing to FL 190 to which the Controller responded but did not query us as to whether we were climbing via the SID. The captain later stated he assumed this meant we were climbing unrestricted to FL 190. Autopilot was engaged approximately 4;000 and then I went to engage VNAV and it would not engage. In hindsight I think this was due to the fact that we were already rapidly climbing to (or through) the hard altitude of 5;000 in the FMS departure; but at the time I couldn't figure out why it would not engage. At about the same time ATC asked us to just level off at our current altitude and I pressed the Altitude Hold mode on the MCP. The aircraft started a gradual level off at which time I think the Captain realized what had happened and stated he was taking the controls and manually did the level off at approximately 6;000. We queried ATC whether they wanted us back to 5;000 and they said no; they would have a continuing climb to FL 190 in just a minute.

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.

Attributes
ACN	1233573
Time
Date	201501
Place
Locale Reference	SJC.Airport
State Reference	CA
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Make Model Name	B737 Next Generation Undifferentiated
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID TECKY1
Flight Plan	IFR
Person 1
Function	First Officer Pilot Flying
Experience	Flight Crew Last 90 Days 148
Person 2
Function	Pilot Not Flying Captain
Experience	Flight Crew Last 90 Days 172
Events
Anomaly	Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Overshoot Deviation - Procedural Clearance Deviation - Procedural FAR Deviation - Procedural Published Material / Policy

A B737-700 first officer set an incorrect altitude in the altitude window causing the crew to fly through an intermediate level off altitude while on the TECKY1 SID. The captain also missed the mistake.