Date: 201507
Local time of day: 0001-0600
Location: SFO.Airport, CA
Flight conditions: IMC
Aircraft: B747 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class B SFO
ATC / advisory: TRACON NCT
Aircraft component: FMS/FMC
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Human-Machine Interface; Situational Awareness
Second reporter function: Captain; Pilot Flying
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 Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented; Flight Crew Returned To Clearance
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Flew the GNNRR TWO RNAV DEPARTURE out of SFO. On departure the ATC controller asked us if we were proceeding to STINS intersection. We were going from GNNRR to AMAKR and didn't have STINS on the RTE page or the legs page. The Captain entered the SID while loading the FMC and told us that there was no transition when he selected the SID and that he deleted the discontinuity between GNNRR and AMAKR. He briefed us when he did this and none of us caught that STINS wasn't in the database when the SID was selected.


Second narrative: While performing duties as the PF; and while climbing out on departure from KSFO; NORCAL Departure queried [Air Carrier X] whether or not we were flying the GNNRR2 RNAV DEP SID. Checking our FMC and position; when we're flying the prescribed departure on a leg that inscribed a direct route from GNNRR to AMAKR. Our PDC CLNC was KSFO GNNRR2 AMAKR LINUZ….. In the process of loading the FMC; there was no opportunity to select an AMAKR transition. The GNNRR2 RNAV DEP was selected and a discontinuity between GNNRR and AMAKR was closed during the course of the FMC preflight. SOP checks of the PDC and verification of the FMC routing was completed; but the PDC was misinterpreted as a clearance from GNNRR direct to AMAKR. NORCAL's inquiry caused a closer review of the departure procedure; and showed an intervening fix; STINS; between GNNRR and AMAKR for which we had not accounted for in correctly programming the departure into the FMC; but instead were flying directly from GNNRR to AMAKR. NORCAL indicated some confusion in seeing our routing and indicated that this was not an unusually occurrence. They were at a loss in understanding why they were often seeing this happen. NORCAL did not indicate that there was any traffic conflict nor was there any need for us to alter our course. We continued direct to AMAKR; soon discovering our departure error. No further action was initiated or taken. Once level at cruising altitude; a discussion ensued in a classic TEM/CRM manner amongst all crew members.


Synopsis: B747 flight crew describe a track deviation during the GNNRR2 RNAV Departure from SFO. The Captain had entered the procedure in the FMC but had not selected the AMAKR transition and just closed the route discontinuity; eliminating STINS.