Date: 201809
Local time of day: 1201-1800
Location: SJC.Airport, CA
Light: Daylight
Aircraft: B737 Next Generation Undifferentiated
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class C SJC
ATC / advisory: Tower SJC
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Situational Awareness; Confusion
Second reporter function: Pilot Flying; First Officer
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Returned To Clearance
Contributing factors: Aircraft; Chart Or Publication; Human Factors
Primary problem: Ambiguous

Narrative: We received a different clearance than our filed route from ATC. Our revised route was SJC2 MOONY SJC BMRNG AF (as filed). Our filed route was LOUPE 4 BMRNG. We accepted the new route from CPDLC and auto loaded it into the FMC. We verified the route fixes together during the briefings. After departure; ATC queried us about making an early right turn on the departure after takeoff. At that point; we noticed on the SJC2 text that instructs to fly a 306 degree heading off of [Runway] 30R to 1.8 DME on the SJC VOR before making the right turn. We looked at the Route page and found the SJC2 SID was not there. We realized we had verified the fixes on the LEGS page on the ground but had not reviewed the Route page. When we auto loaded the route change from CPDLC; it put in the fixes but did not load the SID so the 1.8 DME delay turn was not in the FMC. We continued the fight uneventfully. We should have verified and briefed the new routing on both the Route page and the LEGS page. If we had done that; we could have trapped our error that the SJC2 SID did not get auto loaded from CPDLC.


Second narrative: While at the gate in KSJC; we received a reroute via the CPDLC. Our original flight plan had us on the LOUPE 4; while the new reroute had us fly SJC2 MOONY SJC then as filed. I auto loaded the new reroute via the CPDLC into the FMS. We briefed the LEGS page which showed all the correct fixes; but we forgot to look at the Route page as we were trying to stay on schedule. Had we looked at the Route page; we would have noticed that the SJC2 SID was never loaded into the flight plan. As a result; we missed the delayed turn on the departure instead of waiting until the 1.8 DME from the end of the runway; we turned sooner. I am not sure how much sooner we turned; but ATC brought it to our attention. The rest of our trip was without incident. As a side note; the next day flying; we got another reroute to ZZZ and the CPDLC left out the SID again. This time we recognized it immediately. Not sure why the auto reload through the CPDLC is leaving out the new SID when you hit the load prompt. Until this trip; I had never experienced this happening with the CPDLC. I need to be more careful in verifying new departures with subtle differences. Had I been more diligent and crosschecked the LEGS page as well as the route page; I believe we may have prevented this error.


Synopsis: B737 flight crew reported the CPDLC reroute did not load the new SID into the FMS flight plan and missed a delayed turn on the departure.