Narrative:

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'.

Google
 

Original NASA ASRS Text

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

Narrative: 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'.

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.