Narrative:

During preflight; I tried to retrieve the clearance via controller pilot data link communication (cpdlc) on the aircraft during preflight. The dispatch paperwork stated the aircraft was cpdlc capable. We could not establish ATC comm link. Shortly thereafter; I attempted to retrieve the clearance via pre-departure clearance (pre departure clearance). The clearance came back via pre departure clearance and was matched up with what had been manually input in to the route page on the FMC. During our preflight briefing; the flight plan was verified between the dispatch paperwork and the route programmed in the FMC. As the aircraft was being pushed back from the gate; a clearance was received from the cpdlc even while there was no indication on the engine instrument display screen of an ATC data link with the letters 'ATC'. The clearance was as filed and it was accepted. While in cruise at 34;000 with indianapolis center; a controller queried as to where we were going? We stated that we were proceeding direct to butler VOR (bum). The controller responded by asking who had cleared us to butler instead of centralia (enl). We stated that bum was the next fix on our flight plan. The controller asked who had cleared us to bum and we again stated it was the next fix on clearance. He then issued the clearance to proceed direct to bum. We queried if there was an issue that we should be concerned about and the controller stated that he was only trying to determine if a prior controller had issued the clearance to proceed to bum and not enl. The controller then stated that if there was an issue; we would be advised by the next controller; and then handed us off to the next sector controller. We never heard anything regarding the incident upon being handed off to the next sector.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 First Officer reported a track deviation occurred when there was apparently a routing change that was not reflected in the Pre-Departure Clearance or Controller Pilot Data Link Communication.

Narrative: During preflight; I tried to retrieve the clearance via Controller Pilot Data Link Communication (CPDLC) on the aircraft during preflight. The Dispatch paperwork stated the aircraft was CPDLC capable. We could not establish ATC COMM link. Shortly thereafter; I attempted to retrieve the clearance via Pre-Departure Clearance (PDC). The clearance came back via PDC and was matched up with what had been manually input in to the Route page on the FMC. During our preflight briefing; the flight plan was verified between the Dispatch paperwork and the route programmed in the FMC. As the aircraft was being pushed back from the gate; a clearance was received from the CPDLC even while there was no indication on the engine instrument display screen of an ATC data link with the letters 'ATC'. The clearance was as filed and it was accepted. While in cruise at 34;000 with Indianapolis Center; a Controller queried as to where we were going? We stated that we were proceeding direct to BUTLER VOR (BUM). The Controller responded by asking who had cleared us to Butler instead of CENTRALIA (ENL). We stated that BUM was the next fix on our flight plan. The Controller asked who had cleared us to BUM and we again stated it was the next fix on clearance. He then issued the clearance to proceed direct to BUM. We queried if there was an issue that we should be concerned about and the Controller stated that he was only trying to determine if a prior Controller had issued the clearance to proceed to BUM and not ENL. The Controller then stated that if there was an issue; we would be advised by the next Controller; and then handed us off to the next sector Controller. We never heard anything regarding the incident upon being handed off to the next sector.

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.