An A320 flight crew; crossing staav at 12;000 MSL on the staav RNAV SID from las was reminded by ATC...

Narrative:

During the departure from las; climbing through 12;000 ft via the staav 5 RNAV; while crossing the staav waypoint; ATC asked if we were going to make the altitude restriction at tralr since it looked like we had missed the altitude restriction at staav. We replied that we did not show an altitude restriction at tralr. ATC replied that there was a 17;000 ft restriction at tralr and to contact the next controller on XXX.xx frequency. We checked in with the next controller and inquired an altitude restriction at tralr to which the controller replied that he did not show a restriction at tralr and standby. ATC again contacted us within a minute and verified there is no altitude restriction at tralr. At or above crossing restrictions on departures are not often difficult to comply with.a number of factors contributed to this event:- low climb rate due to the high gross weight of this flight- accelerating out of 10;000 ft- new procedure out of 10;000 ft afl not AGL;- the location of this crossing restriction of 13;000 ft- typically ATC gives a new altitude deleting the restriction- insufficient monitoring of the automation[the deviation could have been avoided by] improved monitoring of the:- at or above climb restrictions;- color changes (warnings) on the mcdu and pfd.

Original NASA ASRS Text

Title: An A320 flight crew; crossing STAAV at 12;000 MSL on the STAAV RNAV SID from LAS was reminded by ATC that the fix was required to have been crossed at 13;000 and asking if they intended to cross the next fix; TRALR; at 17;000. TRALR has no crossing restriction published on the chart.

Narrative: During the departure from LAS; climbing through 12;000 FT via the STAAV 5 RNAV; while crossing the STAAV waypoint; ATC asked if we were going to make the altitude restriction at TRALR since it looked like we had missed the altitude restriction at STAAV. We replied that we did not show an altitude restriction at TRALR. ATC replied that there was a 17;000 FT restriction at TRALR and to contact the next Controller on XXX.XX frequency. We checked in with the next Controller and inquired an altitude restriction at TRALR to which the Controller replied that he did not show a restriction at TRALR and standby. ATC again contacted us within a minute and verified there is no altitude restriction at TRALR. At or above crossing restrictions on departures are not often difficult to comply with.A number of factors contributed to this event:- Low climb rate due to the high gross weight of this flight- Accelerating out of 10;000 FT- New procedure out of 10;000 FT AFL not AGL;- The location of this crossing restriction of 13;000 FT- Typically ATC gives a new altitude deleting the restriction- Insufficient monitoring of the automation[The deviation could have been avoided by] improved monitoring of the:- At or above climb restrictions;- Color changes (warnings) on the MCDU and PFD.

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.

Attributes
ACN	1192479
Time
Date	201407
Local Time Of Day	0601-1200
Place
Locale Reference	LAS.Airport
State Reference	NV
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	A321
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID STAAV
Flight Plan	IFR
Person 1
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

An A320 flight crew; crossing staav at 12;000 MSL on the staav RNAV SID from las was reminded by ATC that the fix was required to have been crossed at 13;000 and asking if they intended to cross the next fix; tralr; at 17;000. Tralr has no crossing restriction published on the chart.