Narrative:

We received a revised route clearance via cpdlc. As with all revised routes via cpdlc; the free text section of the message states that there is a revised route; but not what the new route should be. We followed company procedures by selecting the load prompt in the cpdlc message with both pilots present and watched the revised route populate into the FMC. Everything worked as advertised. The problem; however; is that we as pilots are unable to verify that the route loaded into the FMC is what ATC actually wants us to fly. We are expected to assume that the route loaded correctly. We verify every other input to the FMC; but not the new route we are expected to fly? At some point this will lead to an aircraft flying an incorrect route and a loss of separation or worse. Our only option is to call clearance delivery on the radio and verify verbally what route they intended us to fly. That is what we did on this flight. However; it is not an improvement from our previous system and is prone to error if a pilot forgets to call and verify; or simply trusts the system as our company procedures say to do. In its current form; the cpdlc system is a step backwards from pre departure clearance. And the procedures developed for route verification leave pilots and passengers exposed to potentially deadly mistakes. Immediately require all companies using cpdlc institute a procedural change requiring pilots to call clearance delivery and verbally verify that the new route loaded into the FMC is the route that ATC intends them to fly. Change the cpdlc software so the message sent to the aircraft includes both the loadable new route and text displaying the new route to permit pilot verification of the FMC route.

Google
 

Original NASA ASRS Text

Title: B737-800 First Officer reported confusion regarding CPDLC clearance messages.

Narrative: We received a revised route clearance via CPDLC. As with all revised routes via CPDLC; the free text section of the message states that there is a revised route; but not what the new route should be. We followed Company procedures by selecting the load prompt in the CPDLC message with both pilots present and watched the revised route populate into the FMC. Everything worked as advertised. The problem; however; is that we as pilots are unable to verify that the route loaded into the FMC is what ATC actually wants us to fly. We are expected to ASSUME that the route loaded correctly. We verify every other input to the FMC; but not the new route we are expected to fly? At some point this will lead to an aircraft flying an incorrect route and a loss of separation or worse. Our only option is to call Clearance Delivery on the radio and verify verbally what route they intended us to fly. That is what we did on this flight. However; it is not an improvement from our previous system and is prone to error if a pilot forgets to call and verify; or simply trusts the system as our Company procedures say to do. In its current form; the CPDLC system is a step backwards from PDC. And the procedures developed for route verification leave pilots and passengers exposed to potentially deadly mistakes. Immediately require all Companies using CPDLC institute a procedural change requiring pilots to call Clearance Delivery and verbally verify that the new route loaded into the FMC is the route that ATC intends them to fly. Change the CPDLC software so the message sent to the aircraft includes both the loadable new route and text displaying the new route to permit pilot verification of the FMC route.

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.