B737NG flight crew reported receiving a revised clearance prior to departure via cpdlc then attempti...

Attributes
ACN	1381890
Time
Date	201608
Local Time Of Day	1201-1800
Place
Locale Reference	PHL.Airport
State Reference	PA
Environment
Light	Daylight
Aircraft 1
Make Model Name	B737 Next Generation Undifferentiated
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID PHL1
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 165 Flight Crew Type 100
Person 2
Function	Captain Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 163 Flight Crew Type 8000
Events
Anomaly	Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

Narrative:

First time getting a revised route via fans controller pilot data link communications (cpdlc) talked it over [with] the captain; we made the FMC match the new text on the route pages. After the discussion with the captain we agreed the route matched the clearance. After takeoff on the departure (heading 268 to 5000) phl departure cleared us to pottstown (ptw) the captain typed in pbs and executed. I was in the process of verifying that was the correct point. ATC asked if we were headed to ptw and gave us a heading as we reentered ptw and started LNAV to ptw. ATC went over our clearance with us verified it nothing else was stated by the ATC. The captain and I climbed with no further issues we went to our efb to look into the efb bull about cpdlc issues. We manually entered what we thought the route change was instead of loading it from the page. Understand the fans cpdlc procedures and take time to understand the procedure. Slow down and talk about things before. Also take the time to call clearance delivery to verify what the clearance was.

Original NASA ASRS Text

Title: B737NG flight crew reported receiving a revised clearance prior to departure via CPDLC then attempting to enter the revision into the FMC manually. Thinking only the SID had changed other revisions are omitted resulting in a track deviation.

Narrative: First time getting a revised route via FANS Controller Pilot Data Link Communications (CPDLC) talked it over [with] the Captain; we made the FMC match the new text on the route pages. After the discussion with the Captain we agreed the route matched the clearance. After takeoff on the departure (heading 268 to 5000) PHL departure cleared us to Pottstown (PTW) the Captain typed in PBS and executed. I was in the process of verifying that was the correct point. ATC asked if we were headed to PTW and gave us a heading as we reentered PTW and started LNAV to PTW. ATC went over our clearance with us verified it nothing else was stated by the ATC. The Captain and I climbed with no further issues we went to our EFB to look into the EFB Bull about CPDLC issues. We manually entered what we thought the route change was instead of loading it from the page. Understand the FANS CPDLC procedures and take time to understand the procedure. Slow down and talk about things before. Also take the time to call Clearance Delivery to verify what the clearance was.

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.

B737NG flight crew reported receiving a revised clearance prior to departure via cpdlc then attempting to enter the revision into the FMC manually. Thinking only the SID had changed other revisions are omitted resulting in a track deviation.