B737-300 dispute with departure controller phx over crossing altitudes not depicted on new SID.

Attributes
ACN	440690
Time
Date	199906
Day	Sun
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	msl bound lower : 7000 msl bound upper : 15000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : p50.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : dryht1
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : multi engine pilot : instrument pilot : flight engineer pilot : atp pilot : commercial
Experience	flight time last 90 days : 120 flight time total : 20500 flight time type : 10000
ASRS Report	440690
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 20 flight time total : 8000 flight time type : 20
ASRS Report	440858
Events
Anomaly	altitude deviation : crossing restriction not met altitude deviation : excursion from assigned altitude non adherence : clearance non adherence : published procedure
Independent Detector	atc equipment other atc equipment : radar other controllera other flight crewa other flight crewb
Resolutory Action	controller : issued advisory controller : issued new clearance flight crew : became reoriented
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Chart Or Publication
Primary Problem	Chart Or Publication

Narrative:

First officer called for clearance, received dryht.1-dryht-ach, as filed, maintain at or below 300 ft until 10 mi west, then climb and maintain 7000 ft. He responded by acknowledging the so only, as per phx procedures. I heard the clearance and copied it the same as him. The dryht.1 is relatively new to phx (departure procedure) and has no published altitudes. It has a turn to 190 degrees at 4 DME east of pxr VOR for vectors takeoff east. While clearance seemed different, the 3000 ft and 7000 ft were normal phx departure altitude and so I complied, even though our route would (eventually) be east. After 3 calls to departure control to check in (he was very busy), controller gave us 100 degree heading and asked if we were climbing to 15000 ft. We responded that no, we hadn't been given 15000 ft. Controller said it was published on the dryht.1. (There are no published altitudes on this departure.) I reiterated our clearance to him. He then cleared us to climb and maintain 15000 ft and go direct bayta intersection.

Original NASA ASRS Text

Title: B737-300 DISPUTE WITH DEP CTLR PHX OVER XING ALTS NOT DEPICTED ON NEW SID.

Narrative: FO CALLED FOR CLRNC, RECEIVED DRYHT.1-DRYHT-ACH, AS FILED, MAINTAIN AT OR BELOW 300 FT UNTIL 10 MI W, THEN CLB AND MAINTAIN 7000 FT. HE RESPONDED BY ACKNOWLEDGING THE SO ONLY, AS PER PHX PROCS. I HEARD THE CLRNC AND COPIED IT THE SAME AS HIM. THE DRYHT.1 IS RELATIVELY NEW TO PHX (DEP PROC) AND HAS NO PUBLISHED ALTS. IT HAS A TURN TO 190 DEGS AT 4 DME E OF PXR VOR FOR VECTORS TKOF E. WHILE CLRNC SEEMED DIFFERENT, THE 3000 FT AND 7000 FT WERE NORMAL PHX DEP ALT AND SO I COMPLIED, EVEN THOUGH OUR RTE WOULD (EVENTUALLY) BE E. AFTER 3 CALLS TO DEP CTL TO CHK IN (HE WAS VERY BUSY), CTLR GAVE US 100 DEG HDG AND ASKED IF WE WERE CLBING TO 15000 FT. WE RESPONDED THAT NO, WE HADN'T BEEN GIVEN 15000 FT. CTLR SAID IT WAS PUBLISHED ON THE DRYHT.1. (THERE ARE NO PUBLISHED ALTS ON THIS DEP.) I REITERATED OUR CLRNC TO HIM. HE THEN CLRED US TO CLB AND MAINTAIN 15000 FT AND GO DIRECT BAYTA INTXN.

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