Date: 201510
Local time of day: 1801-2400
Location: ZOA.ARTCC, CA
Flight conditions: VMC
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Second aircraft: Regional Jet 200 ER/LR (CRJ200)
Reporter organization: Government
Reporter function: Handoff / Assist
Human factors: Confusion; Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

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.


Second narrative: FL260 approaching RUSME; ATC instructed us to maintain present heading (heading 310) for separation. With the autopilot still engaged; I selected HDG SEL. We flew on this heading for several minutes. ATC then cleared us direct to DYAMD. DYAMD was selected on the legs page and LNAV engaged. The airplane had completed the turn and we were proceeding directly to DYAMD. We were then give ATC direction to turn right 30 degrees but as I was in the turn I received a climb RA. I immediately disengaged the autopilot and auto throttles and began a climb to follow the RA. I climb 600 ft above our assigned altitude to FL266. Once we received the clear of conflict I reengaged the autopilot and auto throttles and descended back to our assigned altitude of FL260. We advised ATC of the RA and asked for a phone number to contact Oakland Center. The flight ended without further incidents. In SFO I called Oakland Center and spoke to a supervisor who apologized for ATC turning us too early. He told me steps were being taken to deal with the problem.


Synopsis: 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.