Narrative:

During preflight checklist I told the first officer that I had updated the route in the ONS to the revised clearance. After passing roberts I noticed that the frequency in the selector looked like it might be stl instead of the route we had been revised to. We were about 20-25 NM out of roberts at that time. I had him start back to the revised route. At that time center also noticed our error and questioned our route. The first officer had missed the change on the pre departure clearance. Probably because the route line was as we had filed with the exception below. Something should draw our attention to the revision and the filed routing should not be given first if it is revised. As my first officer said -- not an excuse -- just a suggestion that might prevent this error from happening to someone else in the future.

Related reports:

Google
 

Original NASA ASRS Text

Title: MD80S ACFT IN CRUISE. FLC HAD MISSED THE ROUTING CHANGE ON THE PDC AND WERE OFF COURSE WHEN CTLR QUESTIONED THEIR ROUTING.

Narrative: DURING PREFLT CHKLIST I TOLD THE FO THAT I HAD UPDATED THE RTE IN THE ONS TO THE REVISED CLRNC. AFTER PASSING ROBERTS I NOTICED THAT THE FREQ IN THE SELECTOR LOOKED LIKE IT MIGHT BE STL INSTEAD OF THE RTE WE HAD BEEN REVISED TO. WE WERE ABOUT 20-25 NM OUT OF ROBERTS AT THAT TIME. I HAD HIM START BACK TO THE REVISED RTE. AT THAT TIME CTR ALSO NOTICED OUR ERROR AND QUESTIONED OUR RTE. THE FO HAD MISSED THE CHANGE ON THE PDC. PROBABLY BECAUSE THE RTE LINE WAS AS WE HAD FILED WITH THE EXCEPTION BELOW. SOMETHING SHOULD DRAW OUR ATTN TO THE REVISION AND THE FILED ROUTING SHOULD NOT BE GIVEN FIRST IF IT IS REVISED. AS MY FO SAID -- NOT AN EXCUSE -- JUST A SUGGESTION THAT MIGHT PREVENT THIS ERROR FROM HAPPENING TO SOMEONE ELSE IN THE FUTURE.

Data retrieved from NASA's ASRS site as of July 2007 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.