Narrative:

Air carrier flight abc departed jackson, ms, en route to mdw. Level cruise flight. Had the autoplt flying LNAV routing that showed mem J29 pxv, when our actual routing from our dispatch (and the route given to us by clearance delivery in jan) was mem J35 fam. Autoplt joined J29 and shortly thereafter the ZME controller advised us we were supposed to be on J35. We turned left to join the airway, reprogrammed the CDU for proper routing and continued to destination. No traffic conflicts were advised by ZME, and none on TCASII. I should have studied the complete route in the CDU and compared with the filed routing. Supplemental information from acn 392524: flight from jackson, ms, to mdw, il. Flight plan filed by company dispatch (jan direct sqs J35 capital.motif arrival) differed from standard company route stored in aircraft FMS (jan direct sqs J35 mem J29 pxv direct tth direct bvt.BVT2 arrival). Captain was flying, autoplt engaged, LNAV mode selected. I (first officer) was 'backing up' navigation on VOR (J35 course inbound to mem). Just prior to mem, flight attendant came in cockpit to take coffee orders. She returned with coffee, started asking about company's hiring requirements, as her brother is wanting to apply. Aircraft makes slight right turn to intercept J29 over mem (instead of staying on J35, as filed). Approximately 10 DME north of mem, center controller asks if we're turning to intercept J35, shows us east of course. Captain realizes wrong turn by FMS/LNAV. He selects heading mode, turns for J35 intercept. Soon after, controller gives us frequency change. New controller gives us direct cap. Rest of flight uneventful. Contributing factors: distraction by flight attendant's service, questions during approach to and overflt of mem VOR. Had arrived early at jan on previous leg. Had not received release with dispatch filed flight plan information yet when FMS loaded with canned company route. Didn't have it to compare the two. Should have compared prior to pushback once release paperwork was brought to cockpit.

Google
 

Original NASA ASRS Text

Title: A B737-300 FLYING IN ZME AIRSPACE FOLLOWS THE WRONG AIRWAY. FLT PLAN WAS NEVER CHKED AGAINST CLRNC RECEIVED.

Narrative: ACR FLT ABC DEPARTED JACKSON, MS, ENRTE TO MDW. LEVEL CRUISE FLT. HAD THE AUTOPLT FLYING LNAV ROUTING THAT SHOWED MEM J29 PXV, WHEN OUR ACTUAL ROUTING FROM OUR DISPATCH (AND THE RTE GIVEN TO US BY CLRNC DELIVERY IN JAN) WAS MEM J35 FAM. AUTOPLT JOINED J29 AND SHORTLY THEREAFTER THE ZME CTLR ADVISED US WE WERE SUPPOSED TO BE ON J35. WE TURNED L TO JOIN THE AIRWAY, REPROGRAMMED THE CDU FOR PROPER ROUTING AND CONTINUED TO DEST. NO TFC CONFLICTS WERE ADVISED BY ZME, AND NONE ON TCASII. I SHOULD HAVE STUDIED THE COMPLETE RTE IN THE CDU AND COMPARED WITH THE FILED ROUTING. SUPPLEMENTAL INFO FROM ACN 392524: FLT FROM JACKSON, MS, TO MDW, IL. FLT PLAN FILED BY COMPANY DISPATCH (JAN DIRECT SQS J35 CAPITAL.MOTIF ARR) DIFFERED FROM STANDARD COMPANY RTE STORED IN ACFT FMS (JAN DIRECT SQS J35 MEM J29 PXV DIRECT TTH DIRECT BVT.BVT2 ARR). CAPT WAS FLYING, AUTOPLT ENGAGED, LNAV MODE SELECTED. I (FO) WAS 'BACKING UP' NAV ON VOR (J35 COURSE INBOUND TO MEM). JUST PRIOR TO MEM, FLT ATTENDANT CAME IN COCKPIT TO TAKE COFFEE ORDERS. SHE RETURNED WITH COFFEE, STARTED ASKING ABOUT COMPANY'S HIRING REQUIREMENTS, AS HER BROTHER IS WANTING TO APPLY. ACFT MAKES SLIGHT R TURN TO INTERCEPT J29 OVER MEM (INSTEAD OF STAYING ON J35, AS FILED). APPROX 10 DME N OF MEM, CTR CTLR ASKS IF WE'RE TURNING TO INTERCEPT J35, SHOWS US E OF COURSE. CAPT REALIZES WRONG TURN BY FMS/LNAV. HE SELECTS HDG MODE, TURNS FOR J35 INTERCEPT. SOON AFTER, CTLR GIVES US FREQ CHANGE. NEW CTLR GIVES US DIRECT CAP. REST OF FLT UNEVENTFUL. CONTRIBUTING FACTORS: DISTR BY FLT ATTENDANT'S SVC, QUESTIONS DURING APCH TO AND OVERFLT OF MEM VOR. HAD ARRIVED EARLY AT JAN ON PREVIOUS LEG. HAD NOT RECEIVED RELEASE WITH DISPATCH FILED FLT PLAN INFO YET WHEN FMS LOADED WITH CANNED COMPANY RTE. DIDN'T HAVE IT TO COMPARE THE TWO. SHOULD HAVE COMPARED PRIOR TO PUSHBACK ONCE RELEASE PAPERWORK WAS BROUGHT TO COCKPIT.

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.