An air carrier flight crew downloaded an oceanic clearance via cpdlc at the gate then uploaded the r...

Narrative:

During preparation for departure; first officer obtained the clearance through cpdlc (controller pilot data link communications). The following was received through ATC uplink: cleared to rbv via route clearance direct to swann N3909.0w0761 direct bross N3911.4w0755 J42 rbv N4012.1w07429. +Load new route to rbv+ after rbv cleared to ZZZZ as filed; JCOBY3.swann; climb via SID; expect FL310 10 min aft dp; dp frq see SID. First officer (first officer) and myself reviewed the revised clearance; accepted it and he loaded it into the FMC via the load FMC prompt. He then added JCOBY3.swann departure into the FMC. We reviewed the FMC to see that it followed the revised clearance. The only difference from the original FMC route upload was that from rignz; the route was jcoby direct swann instead of jcoby; griim; sooki; swann. Since the revised clearance stated direct swann; we agreed that the FMC route was correct. First officer then briefed captain about the revised clearance. Captain was the pilot flying for this segment. On departure from runway 30; we were initially given runway heading; then a turn to 030 and then direct rignz and resume departure. After confirming direct rignz; LNAV was engaged. After climbing above 10;000 ft; captain engaged the ap. As we continued to climb toward swann (probably around 15000 ft); dulles departure asked where we were heading and first officer replied direct swann. ATC then gave us a heading to the right and said we were supposed to be on the published departure. First officer replied that the revised cpdlc clearance we loaded on the ground was direct swann. ATC admitted that it was confusing and many aircrew have made the same mistake. His wording was 'we have taken this to the national level' regarding this confusion. He said our deviation was no problem and gave us direct swann. The rest of the flight afterward was uneventful.

Original NASA ASRS Text

Title: An air carrier flight crew downloaded an oceanic clearance via CPDLC at the gate then uploaded the route into the FMC. After takeoff; ATC issued a vector and notified the crew two waypoints had been missed.

Narrative: During preparation for departure; First Officer obtained the clearance through CPDLC (Controller Pilot Data Link Communications). The following was received through ATC uplink: CLEARED TO RBV VIA ROUTE CLEARANCE DIRECT TO SWANN N3909.0W0761 DIRECT BROSS N3911.4W0755 J42 RBV N4012.1W07429. +LOAD NEW RTE TO RBV+ AFTER RBV CLEARED TO ZZZZ AS FILED; JCOBY3.SWANN; CLIMB VIA SID; EXPECT FL310 10 MIN AFT DP; DP FRQ SEE SID. FO (First Officer) and myself reviewed the revised clearance; accepted it and he loaded it into the FMC via the LOAD FMC prompt. He then added JCOBY3.SWANN departure into the FMC. We reviewed the FMC to see that it followed the revised clearance. The only difference from the original FMC route upload was that from RIGNZ; the route was JCOBY direct SWANN instead of JCOBY; GRIIM; SOOKI; SWANN. Since the revised clearance stated DIRECT SWANN; we agreed that the FMC route was correct. FO then briefed CAPT about the revised clearance. CAPT was the pilot flying for this segment. On departure from Runway 30; we were initially given runway heading; then a turn to 030 and then direct RIGNZ and resume departure. After confirming direct RIGNZ; LNAV was engaged. After climbing above 10;000 ft; CAPT engaged the AP. As we continued to climb toward SWANN (probably around 15000 ft); Dulles Departure asked where we were heading and FO replied direct SWANN. ATC then gave us a heading to the right and said we were supposed to be on the published departure. FO replied that the revised CPDLC clearance we loaded on the ground was direct SWANN. ATC admitted that it was confusing and many aircrew have made the same mistake. His wording was 'we have taken this to the national level' regarding this confusion. He said our deviation was no problem and gave us direct SWANN. The rest of the flight afterward was uneventful.

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	1404536
Time
Date	201611
Local Time Of Day	1201-1800
Place
Locale Reference	PCT.TRACON
State Reference	VA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Oceanic
Flight Plan	IFR
Component
Aircraft Component	Navigational Equipment and Processing
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 150 Flight Crew Total 8395 Flight Crew Type 682
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 200 Flight Crew Total 14369 Flight Crew Type 50
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

An air carrier flight crew downloaded an oceanic clearance via cpdlc at the gate then uploaded the route into the FMC. After takeoff; ATC issued a vector and notified the crew two waypoints had been missed.