Flight Crew Air Transport Pilot (ATP)
Flight Crew Last 90 Days 204; Flight Crew Type 560
Situational Awareness
Deviation - Altitude Crossing Restriction Not Met; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Human Factors; Procedure
BUR was apparently one of the SoCal airports that got new RNAV procedures and this was the first day they were in use. Upon departing Runway 15 we were cleared relatively early in the flight to 'climb and maintain' into the low flight levels. I do not recall the exact altitude; but it must have been 210 or 230. Because of the unrestricted climb the Captain (I was still hand-flying; FD in LNAV/VNAV mode) took out the 'at or below FL190' altitude restriction at JETHK. A few minutes later ATC amended our clearance to climb and maintain 15;000 feet due to crossing traffic.After we got the handoff the next Controller cleared us to climb via except maintain 230. At that point we did not remember to reinsert the restriction at JETHK and we must have climbed through 190 before reaching the fix. I am not aware of a traffic conflict; but the Controller issued a 'friendly reminder' that the restriction on the new procedure is due to crossing arrival traffic and therefore important to comply with in the future.Of course the main fault is with us as the flying crew; but the ATC clearance switching between 'climb and maintain' and 'climb via' seems to set one up for the mistake we made. The problem for us was that there was a significant amount of time between taking out the crossing restriction in the FMC and being switched back to the climb via clearance. Neither one of us remembered to recheck the programmed procedure. We were both wondering how to change our automation technique to prevent this error. I will try in the future to avoid making changes in FMC and using Level Change for an unrestricted climb and VNAV for 'climb via'.
We departed BUR and were climbing on the SLAPP 1 SID. Today was the first day this RNAV SID was used. When I checked in with SoCal Departure they cleared us to 'climb and maintain' either FL210 or FL230 (can't remember exactly which one it was). Since it was a 'climb and maintain' clearance and there is a lower altitude restriction at JETHK of FL190B; I deleted the altitude restriction after my First Officer verified it.Shortly thereafter ATC told us to stop our climb at 15;000 feet for traffic. After passing the traffic and then being handed off to another Controller; we were now told to 'climb via the SID except maintain FL230'. That led to some confusion in itself because the top altitude is FL230. We continued our climb with LNAV/VNAV engaged. Several minutes later ATC told us to stop our climb at FL210 which we did.Just prior to being handed off to the next Controller; we were told that in the future we are expected to cross JETHK at or below FL190. He said it was not a problem and that ATC was trying to figure out these SIDs as well.This error occurred because we were first given a 'climb and maintain' clearance to an altitude limit that was higher than the JETHK restriction. We were later revised to a 'climb via' clearance. We could have climbed the aircraft in LVL CHG mode and left the altitude restrictions in the FMC until we were sure they were not an issue and I should have been more diligent in catching the change in the clearance. Later the same day; we flew another roundtrip through BUR and were given the same clearance change as we climbed on the SLAPP1 SID. We recognized the issue the second time. This is definitely a 'gotcha' and I hope they change their procedure.
B737 flight crew reported being cleared initially to climb via the SLAPP1 to maintain FL210 then told to climb and maintain FL230 and the crossing restriction (JETHK of FL 190B) is removed. After a level off at 15;000 for traffic the crew is recleared to climb via; but the crossing restriction is not reentered.