Narrative:

Location: near mzv, en route, wbound departures from ord were ATC delayed due to severe WX west of chicago. While waiting in line for takeoff, we received an ATC rerte from ord clearance delivery, to use the cdr 'swap route' ORDLAX0W. The first officer and I referenced our ord 20-7K pages and agreed that the routing read kord mzv lmn J64 civet civet//klax. Both pages were dated aug/xa/01 and both of our commercial manuals are current through revision 14, dated jul/xa/01. We loaded the route into the FMC. As workload permitted, we notified dispatch of the rerte via ACARS. Approximately 25 mins after takeoff, following the standard departure vectors from ZAU, we were cleared present position direct dsm, on course. We acknowledged the clearance, and prepared to modify the FMC routing. During this time we noted that dsm was not part of our filed route, and we brought this to the attention of ZAU, asking for clarification. ZAU replied that dsm was indeed on our route and that we had been reclred via ORDLAX0W, and he proceeded to read that routing -- kord iow dsm J10 obh J100 bce J60 hec J64 civet civet//klax. However, that routing corresponded to ORDLAX2W in our commercial chart. We pointed this out to center, and several exchanges were unable to resolve the reason for our discrepancies. Eventually, we were reclred to fly the routing that we had loaded according to our ORDLAX0W. Shortly thereafter, we received an updated routing via ACARS from dispatch. That routing matched the ...0W routing (the one that showed in our book as ...2W) as described by ZAU. We sent an ACARS message to dispatch explaining our exchange with ZAU and noted our discrepancy with his routing, and updated him as to the route we were flying. The rest of the flight was uneventful. We have still not been able to resolve the cause of the mismatched swap route descriptions. Update to routing after jul/xa/01 -- that captain and first officer have not yet received. ATC and dispatch on different revision cycle than crew members. Both captain and first officer made same filing error in commercial manuals. We did note that some swap rtes from ord and dfw had been changed via NOTAM, but not the ones we were flying. Possible fix to add additional xchk -- 'change standard phraseology from ATC to (for example) air carrier cleared to lax via ORDLAX0W over mzv -- rest of route remains unchanged.' including the first fix in the clearance might provide a quick, easy way for the crew to insure that the routings actually match in description as well as number.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B757 CREW FOUND A DISCREPANCY BTWN THE SWAP ROUTING RECEIVED FROM ATC AND THAT CONTAINED IN THEIR COMMERCIAL MANUALS.

Narrative: LOCATION: NEAR MZV, ENRTE, WBOUND DEPS FROM ORD WERE ATC DELAYED DUE TO SEVERE WX W OF CHICAGO. WHILE WAITING IN LINE FOR TKOF, WE RECEIVED AN ATC RERTE FROM ORD CLRNC DELIVERY, TO USE THE CDR 'SWAP RTE' ORDLAX0W. THE FO AND I REFED OUR ORD 20-7K PAGES AND AGREED THAT THE ROUTING READ KORD MZV LMN J64 CIVET CIVET//KLAX. BOTH PAGES WERE DATED AUG/XA/01 AND BOTH OF OUR COMMERCIAL MANUALS ARE CURRENT THROUGH REVISION 14, DATED JUL/XA/01. WE LOADED THE RTE INTO THE FMC. AS WORKLOAD PERMITTED, WE NOTIFIED DISPATCH OF THE RERTE VIA ACARS. APPROX 25 MINS AFTER TKOF, FOLLOWING THE STANDARD DEP VECTORS FROM ZAU, WE WERE CLRED PRESENT POS DIRECT DSM, ON COURSE. WE ACKNOWLEDGED THE CLRNC, AND PREPARED TO MODIFY THE FMC ROUTING. DURING THIS TIME WE NOTED THAT DSM WAS NOT PART OF OUR FILED RTE, AND WE BROUGHT THIS TO THE ATTN OF ZAU, ASKING FOR CLARIFICATION. ZAU REPLIED THAT DSM WAS INDEED ON OUR RTE AND THAT WE HAD BEEN RECLRED VIA ORDLAX0W, AND HE PROCEEDED TO READ THAT ROUTING -- KORD IOW DSM J10 OBH J100 BCE J60 HEC J64 CIVET CIVET//KLAX. HOWEVER, THAT ROUTING CORRESPONDED TO ORDLAX2W IN OUR COMMERCIAL CHART. WE POINTED THIS OUT TO CTR, AND SEVERAL EXCHANGES WERE UNABLE TO RESOLVE THE REASON FOR OUR DISCREPANCIES. EVENTUALLY, WE WERE RECLRED TO FLY THE ROUTING THAT WE HAD LOADED ACCORDING TO OUR ORDLAX0W. SHORTLY THEREAFTER, WE RECEIVED AN UPDATED ROUTING VIA ACARS FROM DISPATCH. THAT ROUTING MATCHED THE ...0W ROUTING (THE ONE THAT SHOWED IN OUR BOOK AS ...2W) AS DESCRIBED BY ZAU. WE SENT AN ACARS MESSAGE TO DISPATCH EXPLAINING OUR EXCHANGE WITH ZAU AND NOTED OUR DISCREPANCY WITH HIS ROUTING, AND UPDATED HIM AS TO THE RTE WE WERE FLYING. THE REST OF THE FLT WAS UNEVENTFUL. WE HAVE STILL NOT BEEN ABLE TO RESOLVE THE CAUSE OF THE MISMATCHED SWAP RTE DESCRIPTIONS. UPDATE TO ROUTING AFTER JUL/XA/01 -- THAT CAPT AND FO HAVE NOT YET RECEIVED. ATC AND DISPATCH ON DIFFERENT REVISION CYCLE THAN CREW MEMBERS. BOTH CAPT AND FO MADE SAME FILING ERROR IN COMMERCIAL MANUALS. WE DID NOTE THAT SOME SWAP RTES FROM ORD AND DFW HAD BEEN CHANGED VIA NOTAM, BUT NOT THE ONES WE WERE FLYING. POSSIBLE FIX TO ADD ADDITIONAL XCHK -- 'CHANGE STANDARD PHRASEOLOGY FROM ATC TO (FOR EXAMPLE) ACR CLRED TO LAX VIA ORDLAX0W OVER MZV -- REST OF RTE REMAINS UNCHANGED.' INCLUDING THE FIRST FIX IN THE CLRNC MIGHT PROVIDE A QUICK, EASY WAY FOR THE CREW TO INSURE THAT THE ROUTINGS ACTUALLY MATCH IN DESCRIPTION AS WELL AS NUMBER.

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.