Date: 201512
Local time of day: 0601-1200
Location: S56.TRACON, UT
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B SLC
ATC / advisory: TRACON S56
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Captain Pilot Monitoring (PM); First Officer (FO) pilot flying. Discussed LEETZ4 departure and the crossing and speed restrictions for departure. PDC was climb via SID maintain 10;000 feet. Approaching ZEETA intersection ATC issued 'delete speed climb to FL230'. At this time of clearance we were very close to the ZEETA fix. I looked down at the SID plate knowing that 10;000 feet was still set in the altitude window. While I looked at the plate the FO reset the altitude to 230 without saying that had been done. When I looked up the plane was going past 10;000 feet prior to ZEETA intersection. I told the FO he still had to comply with the altitude restrictions and was only cleared to deviate charted speed restrictions. Plane leveled off at 10;300 feet in which ATC then cleared us direct to AINTT intersection; and we continued climb to FL230.I really feel that our company procedure as to who sets the altitude contributed to this possible deviation. In this case had the PM been responsible for setting the altitude; I would have made the comment of 'we're cleared to FL230 but I'm leaving 10;000 set till we cross the fix...' The departure was briefed very explicitly due to the number of restrictions associated with it. Plus the revised clearance was issued so close to the fix that the FO was distracted by the revised clearance and did not completely understand what the instructions were; and how it pertained to the SID. Of course when I went heads down for less than 30 seconds to double check; is when the altitude was reset on the DFGS...by then it was too late as we were in such close proximity of the fix.Contributing factors:FO misunderstanding the ATC clearance. ATC re-issue of clearance to close to the fix not giving crew enough time to coordinate the new restrictions. Failure of communication regarding of re-setting the altitude in the DFGS. PM not being responsible for re-setting the revised altitude.


Second narrative: Departed SLC on the LEETZ4 SID. 10;000 feet Max Crossing Restriction at ZEETA. Prior to reaching ZEETA with 10;000 feet set in Altitude Window; received a Departure Control radio call 'Ignore Speed Restrictions and Climb to FL230.' I was the Pilot Flying; I set FL230 in the Altitude Window and rolled the IAS to 250 knots. We passed over ZEETA intersection at 10;300 feet.QUESTION: Did I make a mistake by crossing ZEETA above the 10;000 feet Crossing Restriction?


Synopsis: Air carrier flight crew reported climbing through a crossing restriction departing SLC when the flying pilot became confused about the specifics of the clearance.