Flight crew misread SID.

Attributes
ACN	141780
Time
Date	199004
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : phx
State Reference	AZ
Altitude	msl bound lower : 5000 msl bound upper : 5000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : phx tracon : n90
Operator	common carrier : air carrier
Make Model Name	Large Transport, Low Wing, 3 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	departure sid : sid
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : commercial pilot : atp pilot : instrument
Experience	flight time last 90 days : 50 flight time total : 22000 flight time type : 500
ASRS Report	141780
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllera
Resolutory Action	other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On the drake three departure from phoenix with captain flying, turned to 030 degree after reaching srp 1 DME, to intercept 330 degree right. (Takeoff from runway 8R.) flew thru radial and immediately turned further left to intercept. According to departure (see attachment) we should have remained on 030 degree heading for vectors to 330 degree radial. No conflict resulted. When queried by departure, we immediately began to follow vectors without further incident. On the pre-departure briefing, the captain read aloud the runway 8R, drake three departure narrative in the upper right corner of the page. The crew responded by observing that a tight turn would be required to 'intercept' the 330 degree radial. We obviously overlooked the little word 'vector' and did not notice the note at the bottom of the page saying 'expect vectors'. I suggest the narrative be rewritten to place a period after '030 degree'. Then, starting a new sentence, substitute the word 'expect' for the word 'for'. Thus to read 'turn left heading 030 degree, expect vectors to salt river R330', etc.

Original NASA ASRS Text

Title: FLT CREW MISREAD SID.

Narrative: ON THE DRAKE THREE DEP FROM PHOENIX WITH CAPT FLYING, TURNED TO 030 DEG AFTER REACHING SRP 1 DME, TO INTERCEPT 330 DEG R. (TKOF FROM RWY 8R.) FLEW THRU RADIAL AND IMMEDIATELY TURNED FURTHER LEFT TO INTERCEPT. ACCORDING TO DEP (SEE ATTACHMENT) WE SHOULD HAVE REMAINED ON 030 DEG HDG FOR VECTORS TO 330 DEG RADIAL. NO CONFLICT RESULTED. WHEN QUERIED BY DEP, WE IMMEDIATELY BEGAN TO FOLLOW VECTORS WITHOUT FURTHER INCIDENT. ON THE PRE-DEP BRIEFING, THE CAPT READ ALOUD THE RWY 8R, DRAKE THREE DEP NARRATIVE IN THE UPPER RIGHT CORNER OF THE PAGE. THE CREW RESPONDED BY OBSERVING THAT A TIGHT TURN WOULD BE REQUIRED TO 'INTERCEPT' THE 330 DEG RADIAL. WE OBVIOUSLY OVERLOOKED THE LITTLE WORD 'VECTOR' AND DID NOT NOTICE THE NOTE AT THE BOTTOM OF THE PAGE SAYING 'EXPECT VECTORS'. I SUGGEST THE NARRATIVE BE REWRITTEN TO PLACE A PERIOD AFTER '030 DEG'. THEN, STARTING A NEW SENTENCE, SUBSTITUTE THE WORD 'EXPECT' FOR THE WORD 'FOR'. THUS TO READ 'TURN LEFT HDG 030 DEG, EXPECT VECTORS TO SALT RIVER R330', ETC.

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.