Narrative:

Captain loaded route into FMC during preflight using bur lax insert. I was distracted during preflight by several factors. I had left my ear pieces pouch at the layover hotel. Personal conflict with the first officer on the other flight leaving bur. ATIS information had departures on runway 33 and I was checking to make sure company takeoffs were authorized on that runway. I did not complete my usual x-chk of the route in the computer with the flight plan route. Departure was normal and we were given an early vector off of the departure route direct to gorman VOR. Approximately 10 mi from the gorman VOR, I x-chked the route out of gorman with the captain. Just as we recognized that the wrong route after gorman was in the FMC, ATC (ZLA) called and asked us to verify our route after gorman. (I discovered later that 2 company aircraft had flown the wrong route after gorman on preceding days.) we were given a vector heading followed by a clearance direct to the clovis VOR. New routing between familiar city pairs needs to be highlighted on the flight plan, emphasized by full clearance readback performance, and FMC route input should always be x-chked by both pilots with the flight plan. Supplemental information from acn 148913: during the cockpit setup for this flight a speed warning flag was noted. While the first officer attempted to contact company maintenance the captain entered the departure/destination (bur-sfo) in the FMC. The route that appeared was the expected route. Over gmn or shortly thereafter, ATC queried 'confirm you are filed over ehf, czn, mod.' west/O looking at the filed flight plan, the captain responded, 'negative we plan ave, bsr.' an entry of any 2 city pairs in our route system will produce a usable route, not necessarily the filed route.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACR MLG DEVIATION FROM CLRNC ROUTE. TRACK HEADING DEVIATION.

Narrative: CAPT LOADED RTE INTO FMC DURING PREFLT USING BUR LAX INSERT. I WAS DISTRACTED DURING PREFLT BY SEVERAL FACTORS. I HAD LEFT MY EAR PIECES POUCH AT THE LAYOVER HOTEL. PERSONAL CONFLICT WITH THE F/O ON THE OTHER FLT LEAVING BUR. ATIS INFO HAD DEPS ON RWY 33 AND I WAS CHKING TO MAKE SURE COMPANY TKOFS WERE AUTHORIZED ON THAT RWY. I DID NOT COMPLETE MY USUAL X-CHK OF THE RTE IN THE COMPUTER WITH THE FLT PLAN RTE. DEP WAS NORMAL AND WE WERE GIVEN AN EARLY VECTOR OFF OF THE DEP RTE DIRECT TO GORMAN VOR. APPROX 10 MI FROM THE GORMAN VOR, I X-CHKED THE RTE OUT OF GORMAN WITH THE CAPT. JUST AS WE RECOGNIZED THAT THE WRONG RTE AFTER GORMAN WAS IN THE FMC, ATC (ZLA) CALLED AND ASKED US TO VERIFY OUR RTE AFTER GORMAN. (I DISCOVERED LATER THAT 2 COMPANY ACFT HAD FLOWN THE WRONG RTE AFTER GORMAN ON PRECEDING DAYS.) WE WERE GIVEN A VECTOR HDG FOLLOWED BY A CLRNC DIRECT TO THE CLOVIS VOR. NEW RTING BTWN FAMILIAR CITY PAIRS NEEDS TO BE HIGHLIGHTED ON THE FLT PLAN, EMPHASIZED BY FULL CLRNC READBACK PERFORMANCE, AND FMC RTE INPUT SHOULD ALWAYS BE X-CHKED BY BOTH PLTS WITH THE FLT PLAN. SUPPLEMENTAL INFO FROM ACN 148913: DURING THE COCKPIT SETUP FOR THIS FLT A SPD WARNING FLAG WAS NOTED. WHILE THE F/O ATTEMPTED TO CONTACT COMPANY MAINT THE CAPT ENTERED THE DEP/DEST (BUR-SFO) IN THE FMC. THE RTE THAT APPEARED WAS THE EXPECTED RTE. OVER GMN OR SHORTLY THEREAFTER, ATC QUERIED 'CONFIRM YOU ARE FILED OVER EHF, CZN, MOD.' W/O LOOKING AT THE FILED FLT PLAN, THE CAPT RESPONDED, 'NEGATIVE WE PLAN AVE, BSR.' AN ENTRY OF ANY 2 CITY PAIRS IN OUR RTE SYS WILL PRODUCE A USABLE RTE, NOT NECESSARILY THE FILED RTE.

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.