Date: 201501
Location: SJC.Airport, CA
Flight conditions: Mixed
Weather elements / visibility: 3
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class C SJC; Class E NCT
ATC / advisory: TRACON NCT
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Human factors: Confusion; Time Pressure; Communication Breakdown; Workload; Training / Qualification
Second reporter function: Pilot Not Flying; Captain
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

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.


Second narrative: Although a deprature briefing was accomplished the wrong altitude in the window was not caught and VNAV was not selected after takeoff prior to 5000 feet.


Synopsis: 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.