A B737 captain and two controllers involved describe a loss of separation incident between the B737 ...

Attributes
ACN	1303733
Time
Date	201510
Local Time Of Day	1801-2400
Place
Locale Reference	ZOA.ARTCC
State Reference	CA
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Vectors STAR DYAMD2
Flight Plan	IFR
Aircraft 2
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Handoff / Assist
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 4.0
Person 2
Function	Pilot Flying Captain
Experience	Flight Crew Last 90 Days 139 Flight Crew Type 4549
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy

Narrative:

A B737 was on a heading to follow the last aircraft in sequence to sfo. A crj-200 was in a climb to FL290 along with 10R for the climb and the B737. The plan was for the B737 to go last in the sequence of 4 aircraft to sfo. Upon checking the flight plan of the last aircraft I had planned to follow I noticed that the controller at R33 had not turned that aircraft towards the destination to help with the planned sequence. I inquired to make sure that I was indeed going last behind all other AC with the B737. R33 controller said that I was inacurrate with the assumption and that I should be going between the #3 and #4 aircraft. I immediately reacted to ensure proper sequencing for sfo and failed to reevaluate the climb and vector which was to insure initial seperation between the B737 and the crj-200. The turn to dyamd..DYAMD2..sfo for the B737 put him in conflict with the climbing crj-200. Additional turns were used in an attempt to ensure and reestablish standard separation.

Original NASA ASRS Text

Title: A B737 Captain and two Controllers involved describe a loss of separation incident between the B737 arriving and a CRJ200 departing SFO. A TCAS RA ultimately solves the conflict.

Narrative: A B737 was on a heading to follow the last aircraft in sequence to SFO. A CRJ-200 was in a climb to FL290 along with 10R for the climb and the B737. The plan was for the B737 to go last in the sequence of 4 aircraft to SFO. Upon checking the flight plan of the last aircraft I had planned to follow I noticed that the controller at R33 had not turned that aircraft towards the destination to help with the planned sequence. I inquired to make sure that I was indeed going LAST behind all other AC with the B737. R33 controller said that I was inacurrate with the assumption and that I should be going between the #3 and #4 aircraft. I immediately reacted to ensure proper sequencing for SFO and failed to reevaluate the climb and vector which was to insure initial seperation between the B737 and the CRJ-200. The turn to DYAMD..DYAMD2..SFO for the B737 put him in conflict with the climbing CRJ-200. Additional turns were used in an attempt to ensure and reestablish standard separation.

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.

A B737 captain and two controllers involved describe a loss of separation incident between the B737 arriving and a CRJ200 departing sfo. A TCAS RA ultimately solves the conflict.