Narrative:

We were on a pre departure clearance clearance from den via the BAYLR1 RNAV SID. The pre departure clearance clearly stated the altitude clearance limit of 10;000 feet MSL. We reviewed the SID and noted it had a limit of FL230 with various lower altitude hold downs. We then agreed to set the first hard altitude of 10;000 feet MSL in the altitude alerter window. We were cleared for takeoff; RNAV to dugme and the baylr SID. Dugme had an altitude constraint to cross at 10;000 feet MSL. I was pilot flying and I made a normal takeoff. The captain checked in with denver departure and reported climbing out of 7;500 feet for FL230 with the restrictions. He then cleared us to FL230 without restrictions and turned us off the SID with a left turn to 260 degrees in order to climb off track above slower traffic ahead. At around 16;000 feet MSL he re-cleared us direct baylr intersection and switched us to another departure frequency. The new controller further cleared us to FL260 and then asked us why we were above 10;000 feet. Incredulously; the captain replied because we were cleared to FL230 on initial contact. The departure controller then went on a litany of minutiae explaining that you only get 10;000 feet out of denver. That was a hard altitude. Period.when we were issued an RNAV departure; we checked the plate for altitude limits and then set the first restriction. This being a brand new RNAV SID; they (ATC) should have noted that our initial check-in was in error. We stated climbing to FL230 with restrictions. They just acknowledged it and took out the restrictions. I do fully admit that our pre departure clearance stated maintain 10;000 feet; but I (we) got wrapped up in the RNAV SID clearance limit instead.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-700 flight crew departing westbound from DEN was given a PDC including the BAYLR RNAV SID which includes multiple altitude constraints as well as a clearance to maintain 10;000 feet MSL. After takeoff; confusion as to their cleared altitude resulted.

Narrative: We were on a PDC clearance from DEN via the BAYLR1 RNAV SID. The PDC clearly stated the altitude clearance limit of 10;000 feet MSL. We reviewed the SID and noted it had a limit of FL230 with various lower altitude hold downs. We then agreed to set the first hard altitude of 10;000 feet MSL in the Altitude Alerter window. We were cleared for takeoff; RNAV to DUGME and the BAYLR SID. DUGME had an altitude constraint to cross at 10;000 feet MSL. I was Pilot Flying and I made a normal takeoff. The Captain checked in with Denver Departure and reported climbing out of 7;500 feet for FL230 with the restrictions. He then cleared us to FL230 without restrictions and turned us off the SID with a left turn to 260 degrees in order to climb off track above slower traffic ahead. At around 16;000 feet MSL he re-cleared us direct BAYLR intersection and switched us to another Departure frequency. The new Controller further cleared us to FL260 and then asked us why we were above 10;000 feet. Incredulously; the Captain replied because we were cleared to FL230 on initial contact. The Departure Controller then went on a litany of minutiae explaining that you only get 10;000 feet out of Denver. That was a hard altitude. Period.When we were issued an RNAV departure; we checked the plate for altitude limits and then set the first restriction. This being a brand new RNAV SID; they (ATC) should have noted that our initial check-in was in error. We stated climbing to FL230 with restrictions. They just acknowledged it and took out the restrictions. I do fully admit that our PDC stated maintain 10;000 feet; but I (we) got wrapped up in the RNAV SID clearance limit instead.

Data retrieved from NASA's ASRS site as of July 2013 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.