B737 flight crew reported after a cpdlc reroute was loaded; no runway transition was selected and a ...

Attributes
ACN	1453392
Time
Date	201706
Local Time Of Day	0601-1200
Place
Locale Reference	STL.Tower
State Reference	MO
Environment
Light	Daylight
Aircraft 1
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	SID JAHNY THREE
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 187 Flight Crew Type 400
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 242 Flight Crew Type 1700
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

At the gate we received a revised cpdlc clearance which I loaded from the clearance page. We reviewed the new route on the route page 2 and agreed it was correct. During the before push checklist we noticed the runway was not on the takeoff reference page; it was there earlier because we reviewed the departure procedure during the brief. I then re-input the runway and reloaded the takeoff data and we completed the checklist. The taxi out and takeoff were uneventful.after takeoff in the initial climb; somewhere around 1000 ft AGL the captain asked me to confirm we were on the correct departure path. We had confirmed LNAV and the FMA had the green LNAV; however; no magenta line was currently in view. As I was reviewing the chart and crosschecking the FMC data; ATC queried if we were headed to jahny or something similar. I believe I replied we were on the jahny departure; and after some congestion on the radio we were given direct map and continued without incident. During my review of the chart and our FMC data it appeared hefnr; dafus; and travs were not there and the LNAV was navigating to jahny. I'm not sure what caused this.I'm still unsure of our error but assume we missed a crosscheck somewhere during the cpdlc reroute. A more thorough review may have caught the error.

Original NASA ASRS Text

Title: B737 Flight Crew reported after a CPDLC reroute was loaded; no runway transition was selected and a track deviation occurred.

Narrative: At the gate we received a revised CPDLC clearance which I loaded from the Clearance page. We reviewed the new route on the Route page 2 and agreed it was correct. During the Before Push Checklist we noticed the runway was not on the takeoff reference page; it was there earlier because we reviewed the departure procedure during the brief. I then re-input the runway and reloaded the takeoff data and we completed the checklist. The taxi out and takeoff were uneventful.After takeoff in the initial climb; somewhere around 1000 ft AGL the Captain asked me to confirm we were on the correct departure path. We had confirmed LNAV and the FMA had the green LNAV; however; no magenta line was currently in view. As I was reviewing the chart and crosschecking the FMC data; ATC queried if we were headed to JAHNY or something similar. I believe I replied we were on the JAHNY Departure; and after some congestion on the radio we were given direct MAP and continued without incident. During my review of the chart and our FMC data it appeared HEFNR; DAFUS; and TRAVS were not there and the LNAV was navigating to JAHNY. I'm not sure what caused this.I'm still unsure of our error but assume we missed a crosscheck somewhere during the CPDLC reroute. A more thorough review may have caught the error.

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.

B737 flight crew reported after a cpdlc reroute was loaded; no runway transition was selected and a track deviation occurred.