Just prior to departure; sfo changed the departure runway to 28R so the crew reloaded the new FMS da...

Narrative:

Note: sfo recently changed some departure and arrival routings and names.ATC clearance was GNNRR1 departure. Tower cleared us to hold short rw 28L (we were anticipating takeoff on 28L - FMC was loaded for that runway). Tower switched runways on us at last second and gave us 28R. The FMC was changed to reflect 28R while takeoff data was pulled up and reviewed. All new data was loaded and we were cleared for takeoff 28R. LNAV/VNAV was engaged and we were flying the assigned SID (GNNRR1). Passing approximately FL200; ATC asked if we were flying to stins (the GNNRR1 routing consists of gnnrr-stins-amakr etc.). Shortly after ATC's call they gave us direct redwd; which we complied with. After we reviewed the SID and discussed ATC questioning us; we realized that we may have unintentionally left stins out of our clearance when tower gave us the new runway. Apparently when the runway was changed from 28L to 28R in the FMC; it created a discontinuity. Due to being rushed with the last second runway change; the discontinuity was closed (the correct procedure); but inadvertently deleted stins. There was limited time to cross check FMC work prior to takeoff. We think the FMC had us flying gnnrr-amakr instead of gnnrr-stins-amakr.recommended actions to avert the problem - sfo recently changed some departure/arrival plates. They are new to all crews and are not as familiar to us as the old plates. Tower changed the runway on us at the last second. We needed to slow down and carefully check/cross check data input to the FMC. This would have delayed our departure and possibly created spacing issues for ATC; but would have been the prudent thing to do.

Original NASA ASRS Text

Title: Just prior to departure; SFO changed the departure Runway to 28R so the crew reloaded the new FMS data and GNNRR 1 RNAV routing except for STINS. During climb; ZOA detected the error.

Narrative: Note: SFO recently changed some departure and arrival routings and names.ATC clearance was GNNRR1 departure. Tower cleared us to hold short RW 28L (we were anticipating takeoff on 28L - FMC was loaded for that runway). Tower switched runways on us at last second and gave us 28R. The FMC was changed to reflect 28R while Takeoff Data was pulled up and reviewed. All new data was loaded and we were cleared for takeoff 28R. LNAV/VNAV was engaged and we were flying the assigned SID (GNNRR1). Passing approximately FL200; ATC asked if we were flying to STINS (the GNNRR1 routing consists of GNNRR-STINS-AMAKR etc.). Shortly after ATC's call they gave us direct REDWD; which we complied with. After we reviewed the SID and discussed ATC questioning us; we realized that we may have unintentionally left STINS out of our clearance when Tower gave us the new runway. Apparently when the runway was changed from 28L to 28R in the FMC; it created a discontinuity. Due to being rushed with the last second runway change; the discontinuity was closed (the correct procedure); but inadvertently deleted STINS. There was limited time to cross check FMC work prior to takeoff. We think the FMC had us flying GNNRR-AMAKR instead of GNNRR-STINS-AMAKR.Recommended actions to avert the problem - SFO recently changed some departure/arrival plates. They are new to all crews and are not as familiar to us as the old plates. Tower changed the runway on us at the last second. We needed to slow down and carefully check/cross check data input to the FMC. This would have delayed our departure and possibly created spacing issues for ATC; but would have been the prudent thing to do.

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.

Attributes
ACN	1246559
Time
Date	201503
Local Time Of Day	1201-1800
Place
Locale Reference	ZOA.ARTCC
State Reference	CA
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Widebody Transport
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID GNNRR 1
Flight Plan	IFR
Person 1
Function	First Officer Pilot Not Flying
Experience	Flight Crew Last 90 Days 250 Flight Crew Total 5000 Flight Crew Type 2200
Person 2
Function	Pilot Flying First Officer
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 26000 Flight Crew Type 5000
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

Just prior to departure; sfo changed the departure runway to 28R so the crew reloaded the new FMS data and gnnrr 1 RNAV routing except for stins. During climb; ZOA detected the error.