A B737-300 flight crew has traffic conflict during departure.

Attributes
ACN	557560
Time
Date	200208
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phx.airport
State Reference	AZ
Altitude	msl single value : 10500
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
Flight Phase	climbout : vacating altitude
Route In Use	departure sid : tfd 1
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : flight engineer pilot : cfi
Experience	flight time last 90 days : 275 flight time total : 7500 flight time type : 2500
ASRS Report	557560
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	aircraft equipment : tcas other controllerb
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departing phx on the stanfield 1 SID. Radar idented by departure control and assigned 250 KTS and FL210. Acknowledged clearance, turned right at 4 DME to heading of 190 degrees to await expected vectors. Acknowledged 2 radio checks from departure controller. Approximately 5 mi after making turn to 190 degree heading, we were commanded to make immediate climbing left turn (we were climbing at this time 250 KTS as previously cleared). We saw crossing traffic on TCASII and through visual confirmation, but never received a TA or an RA from the equipment. We were informed that we had been issued a clearance for heading of 080 degrees for our climb 'numerous time.' we had been on the published departure approximately 5 mins, and no such instructions were heard. If we were on the wrong heading, I would have thought that the controller would have corrected our heading (if wrong) at the time he requested a radio check.

Original NASA ASRS Text

Title: A B737-300 FLC HAS TFC CONFLICT DURING DEP.

Narrative: DEPARTING PHX ON THE STANFIELD 1 SID. RADAR IDENTED BY DEP CTL AND ASSIGNED 250 KTS AND FL210. ACKNOWLEDGED CLRNC, TURNED R AT 4 DME TO HDG OF 190 DEGS TO AWAIT EXPECTED VECTORS. ACKNOWLEDGED 2 RADIO CHKS FROM DEP CTLR. APPROX 5 MI AFTER MAKING TURN TO 190 DEG HDG, WE WERE COMMANDED TO MAKE IMMEDIATE CLBING L TURN (WE WERE CLBING AT THIS TIME 250 KTS AS PREVIOUSLY CLRED). WE SAW XING TFC ON TCASII AND THROUGH VISUAL CONFIRMATION, BUT NEVER RECEIVED A TA OR AN RA FROM THE EQUIP. WE WERE INFORMED THAT WE HAD BEEN ISSUED A CLRNC FOR HDG OF 080 DEGS FOR OUR CLB 'NUMEROUS TIME.' WE HAD BEEN ON THE PUBLISHED DEP APPROX 5 MINS, AND NO SUCH INSTRUCTIONS WERE HEARD. IF WE WERE ON THE WRONG HDG, I WOULD HAVE THOUGHT THAT THE CTLR WOULD HAVE CORRECTED OUR HDG (IF WRONG) AT THE TIME HE REQUESTED A RADIO CHK.

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.