Narrative:

Having just arrived ZZZ from the west we were both aware of impending thunderstorms and WX that lay east of the valley running north to south. I noted our filed routing along the maxxo 1 and was in complete agreement that was the safest flight plan option by way of a published route considering the impending WX. I concluded to myself that this was good flight planning as things were unfolding. Again; the filed route per our release was the maxxo 1 and the same was reflected on the pre departure clearance. The route was entered into the FMC; crosschecked; and briefed per SOP just as it appeared to me. Consequently; what wasn't noted and apparently missed was the revised segment portion on the pre departure clearance strip which does appear along with our filed routing. I am more than aware that any filed flight plan is subject to revision irregardless of the fact that it may not; at the time of departure; provide the safest passage reference WX. Despite the fact; and very simply put; the revised segment escaped my review. Following our departure ATC queried us regarding our routing. I placed a call to ZZZ TRACON as soon as I arrived at destination. The human factors as referenced above could very easily have been a contributing factor. I don't recall any particulars that occurred during boarding but interruptions are certainly no less frequent than ever. I have experienced no difficulties to date complying with our 'save fuel' initiatives; ie; single engine taxi outbound and inbound but it undoubtedly increases workload during shorter taxi times and distances. I question whether or not a more standardized display of flight information would or might be helpful. I miss the old system while at the same time I enjoy the conveniences of the ACARS. In any event; I hope my comments prove helpful and until I am instructed otherwise by procedure; I am about revising my personal technique and methodology to preclude the re-occurrence of any similar type of event.

Google
 

Original NASA ASRS Text

Title: ACR FLT CREW FAILS TO NOTE REVISED SEGMENT OF PDC CLRNC MESSAGE. FLY FILED SID VICE SID BY WHICH CLEARED IN THE REVISED SEGMENT.

Narrative: HAVING JUST ARRIVED ZZZ FROM THE WEST WE WERE BOTH AWARE OF IMPENDING TSTMS AND WX THAT LAY EAST OF THE VALLEY RUNNING NORTH TO SOUTH. I NOTED OUR FILED ROUTING ALONG THE MAXXO 1 AND WAS IN COMPLETE AGREEMENT THAT WAS THE SAFEST FLIGHT PLAN OPTION BY WAY OF A PUBLISHED ROUTE CONSIDERING THE IMPENDING WX. I CONCLUDED TO MYSELF THAT THIS WAS GOOD FLIGHT PLANNING AS THINGS WERE UNFOLDING. AGAIN; THE FILED ROUTE PER OUR RELEASE WAS THE MAXXO 1 AND THE SAME WAS REFLECTED ON THE PDC. THE ROUTE WAS ENTERED INTO THE FMC; CROSSCHECKED; AND BRIEFED PER SOP JUST AS IT APPEARED TO ME. CONSEQUENTLY; WHAT WASN'T NOTED AND APPARENTLY MISSED WAS THE REVISED SEGMENT PORTION ON THE PDC STRIP WHICH DOES APPEAR ALONG WITH OUR FILED ROUTING. I AM MORE THAN AWARE THAT ANY FILED FLIGHT PLAN IS SUBJECT TO REVISION IRREGARDLESS OF THE FACT THAT IT MAY NOT; AT THE TIME OF DEPARTURE; PROVIDE THE SAFEST PASSAGE REFERENCE WX. DESPITE THE FACT; AND VERY SIMPLY PUT; THE REVISED SEGMENT ESCAPED MY REVIEW. FOLLOWING OUR DEPARTURE ATC QUERIED US REGARDING OUR ROUTING. I PLACED A CALL TO ZZZ TRACON AS SOON AS I ARRIVED AT DEST. THE HUMAN FACTORS AS REFERENCED ABOVE COULD VERY EASILY HAVE BEEN A CONTRIBUTING FACTOR. I DON'T RECALL ANY PARTICULARS THAT OCCURRED DURING BOARDING BUT INTERRUPTIONS ARE CERTAINLY NO LESS FREQUENT THAN EVER. I HAVE EXPERIENCED NO DIFFICULTIES TO DATE COMPLYING WITH OUR 'SAVE FUEL' INITIATIVES; IE; SINGLE ENGINE TAXI OUTBOUND AND INBOUND BUT IT UNDOUBTEDLY INCREASES WORKLOAD DURING SHORTER TAXI TIMES AND DISTANCES. I QUESTION WHETHER OR NOT A MORE STANDARDIZED DISPLAY OF FLIGHT INFO WOULD OR MIGHT BE HELPFUL. I MISS THE OLD SYSTEM WHILE AT THE SAME TIME I ENJOY THE CONVENIENCES OF THE ACARS. IN ANY EVENT; I HOPE MY COMMENTS PROVE HELPFUL AND UNTIL I AM INSTRUCTED OTHERWISE BY PROCEDURE; I AM ABOUT REVISING MY PERSONAL TECHNIQUE AND METHODOLOGY TO PRECLUDE THE RE-OCCURRENCE OF ANY SIMILAR TYPE OF EVENT.

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