Date: 201507
Local time of day: 1201-1800
Location: SFO.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Citation X (C750)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: While on the BDEGA ONE RNAV arrival we checked on with NORCAL approach and were told to expect the ILS 28L to SFO. Before checking on with NORCAL we briefed the ILS 28R as well as the RWY 28R transition since we were arriving from the north and we rarely land on 28L because of the proximity of [our destination on the field]. Shortly after CORKK intersection we were informed by ATC we weren't flying the correct transition for runway 28L and were promptly issued a vector. We soon realized our error of not switching the runways in the FMS.We should have switched the runway in the FMS right away. When we checked on with NORCAL the controller just said to expect runway 28R. Maybe in the future to avoid this again it would have been nice if he stated 'expect runway 28L; fly the runway 28L transition.'


Second narrative: While descending into SFO on the BDEGA1 RNAV arrival; we were passing the fix BDEGA when ATC assigned us runway 28L at SFO. We had anticipated 28R and put it in the FMS because that is the runway we usually use and it made sense for us to be assigned 28R because of our current position and our destination on the field. We mistakenly forgot to change the runway in the FMS and the automation flew the 28R transition instead of the 28L transition. ATC quickly caught the mistake and informed us that we were supposed to be on the 28L transition and assigned us a heading of 180 with which we promptly complied. After a few minutes of vectoring; ATC reassigned us to 28R and we proceeded to land without further incident.My mistake in not immediately switching the runway assignment in the FMS was a factor in this event. I was task saturated at the time making sure that the checklist was complete and everything in the cabin was set for landing. I don't think that NorCal should have assigned us the runway this late as we were just about 15 miles from the airport at the time we were assigned our runway for landing. Also; for NorCal to be switching runway assignments is a recipe for error. I would like them to assign runways well before we get close to the airport so the FMS can be set properly for landing ahead of time. In the future I will be more proactive in assuring and verifying that the assigned runway; along with the appropriate transition; is programmed and active in the FMS.


Synopsis: C750 flight crew arriving to SFO on the BDEGA1 and expecting Runway 28R is told to expect Runway 28L. However; the runway is not changed in the FMC and the aircraft turns on to the 28R transition. NCT detects the error and issues vectors. The crew eventually lands on Runway 28R.