L30 controller and commercial flight crew voiced concern regarding continued confusion reference the...

Attributes
ACN	948387
Time
Date	201105
Local Time Of Day	0001-0600
Place
Locale Reference	L30.TRACON
State Reference	NV
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	SID SHEAD7
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Person 2
Function	First Officer
Experience	Flight Crew Last 90 Days 169
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

A B737 called up on the Shead7 departure climbing to 7;000. The departure itself states to climb to FL190 with clearly stated restrictions along the way. The first restriction being roppr at 7;000; approaching mddog the B737 asked for higher and I said negative expect higher in 8-9 miles because he should have crossed mddog at 9;000. Once I saw he was still at 7;000 I climbed him to 11;000 to get him climbing above the MVA which is 10;000 and keep him below the inbound traffic descending to 12;000 and gave him a traffic alert. I informed the pilot via the departure he should have been climbing to FL190 via the departure and he stated he was issued 7;000 and no higher. Recommendation; since the new procedures of climbing all aircraft to FL190 on departure with restrictions has been implemented a couple months ago many pilots have made this mistake. Many different altitudes have been stated on departure. An effort needs to be made on the controllers and pilots part to get a uniform altitude report on initial call up.

Original NASA ASRS Text

Title: L30 Controller and commercial flight crew voiced concern regarding continued confusion reference the altitude assignments and crossing restrictions on several LAS RNAV SIDs.

Narrative: A B737 called up on the Shead7 departure climbing to 7;000. The departure itself states to climb to FL190 with clearly stated restrictions along the way. The first restriction being ROPPR at 7;000; approaching MDDOG the B737 asked for higher and I said negative expect higher in 8-9 miles because he should have crossed MDDOG at 9;000. Once I saw he was still at 7;000 I climbed him to 11;000 to get him climbing above the MVA which is 10;000 and keep him below the inbound traffic descending to 12;000 and gave him a traffic alert. I informed the pilot via the departure he should have been climbing to FL190 via the departure and he stated he was issued 7;000 and no higher. Recommendation; since the new procedures of climbing all aircraft to FL190 on departure with restrictions has been implemented a couple months ago many pilots have made this mistake. Many different altitudes have been stated on departure. An effort needs to be made on the controllers and pilots part to get a uniform altitude report on initial call up.

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

L30 controller and commercial flight crew voiced concern regarding continued confusion reference the altitude assignments and crossing restrictions on several las RNAV sids.