Narrative:

We received the pre departure clearance to the MMUGS1 departure; which is a 'new procedure at this airport'. We planned on a [runway] 26L takeoff. The departure was briefed; to include an incorrect initial altitude of 5;000 ft as posted in the 'initial climb' section at botll. We missed the 'maintain 4;000 ft' as posted in the 'routing' section of the SID. We were assigned [runway] 26L for departure. During taxi to [runway] 26L we were subsequently assigned [runway] 26R for departure. We checked to see if there were any different departure instructions for a 26R vice 26L departure and there were none. We were cleared to line up and wait [runway] 26R. [When cleared for takeoff] we were cleared for a left turn to ttaps (which is not part of the MUGGS1 departure from [runways] 26L/right; but is on the departure routing from [runways] 15L/right) so it was not in our FMC routing. Once airborne I heading-selected toward ttaps and entered ttaps into the FMC and executed it. LNAV was selected and executed. I missed noticing the 'at or below 4;000 ft' notation on the SID at ttaps (which would have protected us with regard to the 4;000 ft restriction). The entire time we were in the left turn to ttaps we were entering the new routing; accelerating; cleaning up the airplane and switching to and checking in with departure; so we were very busy. As we were climbing above 4;000 ft on our way to 5;000 ft; for the crossing restriction at botll; the departure controller queried us our altitude; I replied with our current altitude and that were climbing to 5;000 ft and he responded that we shouldn't be that high; but that it was not a problem and to climb and maintain 16;000 ft. The problems were: we saw the 'cross botll at or below 5;000 ft' in the 'initial climb' box and interpreted that as the initial altitude and we didn't notice the 'maintain 4;000 ft' that was buried in the 'routing' box. We received 'with our takeoff clearance' instructions for a left turn to a fix that was not on the departure routing for the runway of departure via the SID. I think it would be helpful if the actual 'initial altitude' was in the 'initial climb' box rather than for it to be hidden in the 'routing' box. [There are] different locations for the 'maintain XXXX' altitude restrictions for all the different sids out of houston. There is no consistency at all. There really should be a standard; and prominent' location for all initial altitude restrictions for all sids. Emboldening the maintain XXXX ft' would also help.

Google
 

Original NASA ASRS Text

Title: The flight crew of a B767-300 cleared for takeoff from Runway 26R and cleared to fly the MMUGS RNAV SID from IAH failed to note the fine print restriction to 'maintain 4;000 FT' in the ROUTING section of the SID text; which is illogically located below the INITIAL CLIMB box. As a result; they were climbing to cross BOTLL at or below 5;000 as directed by the chart graphic; and the directives in the INITIAL CLIMB text box when ATC advised they had flown through their cleared altitude.

Narrative: We received the PDC to the MMUGS1 departure; which is a 'New procedure at this airport'. We planned on a [Runway] 26L takeoff. The departure was briefed; to include an incorrect initial altitude of 5;000 FT as posted in the 'INITIAL CLIMB' section at BOTLL. We missed the 'MAINTAIN 4;000 FT' as posted in the 'ROUTING' section of the SID. We were assigned [Runway] 26L for departure. During taxi to [Runway] 26L we were subsequently assigned [Runway] 26R for departure. We checked to see if there were any different departure instructions for a 26R vice 26L departure and there were none. We were cleared to line up and wait [Runway] 26R. [When cleared for takeoff] we were cleared for a left turn to TTAPS (which is not part of the MUGGS1 departure from [runways] 26L/R; but is on the departure routing from [runways] 15L/R) so it was not in our FMC routing. Once airborne I heading-selected toward TTAPS and entered TTAPS into the FMC and executed it. LNAV was selected and executed. I missed noticing the 'At or below 4;000 FT' notation on the SID at TTAPS (which would have protected us with regard to the 4;000 FT restriction). The entire time we were in the left turn to TTAPS we were entering the new routing; accelerating; cleaning up the airplane and switching to and checking in with Departure; so we were very busy. As we were climbing above 4;000 FT on our way to 5;000 FT; for the crossing restriction at BOTLL; the Departure Controller queried us our altitude; I replied with our current altitude and that were climbing to 5;000 FT and he responded that we shouldn't be that high; but that it was not a problem and to climb and maintain 16;000 FT. The problems were: We saw the 'cross BOTLL at or below 5;000 FT' in the 'INITIAL CLIMB' box and interpreted that as the initial altitude and we didn't notice the 'MAINTAIN 4;000 FT' that was buried in the 'ROUTING' box. We received 'with our takeoff clearance' instructions for a left turn to a fix that was not on the departure routing for the runway of departure via the SID. I think it would be helpful if the actual 'initial altitude' was in the 'INITIAL CLIMB' box rather than for it to be hidden in the 'ROUTING' box. [THERE ARE] DIFFERENT LOCATIONS FOR THE 'MAINTAIN XXXX' altitude restrictions for all the different SIDs out of Houston. There is no consistency at all. There really should be a standard; and prominent' location for all initial altitude restrictions for ALL SIDs. Emboldening the MAINTAIN XXXX FT' would also help.

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.