Narrative:

As first officer; I was aware navigation routing from the originating city is notoriously inconsistent and previous experience consistently showed the dispatch release seldom matched the departure clearance routing from that city to any destination. It is very common for the release to issue BURRO2 and voice clearance to issue WILDCAT2 departure. Thus; when we received the non-standard routing to lax; I carefully manually entered routing; including J-104. (I did not enter a standard route and then modify it at any time.) but; clearance past tnp was BASET3; which indicated lax was landing east. I clarified clearance with delivery via voice; and wrote the clearance on my copy of release. This peculiarity was mentioned to the captain during the clearance briefing. All briefings were accomplished in accordance with fom standards. Route was confirmed; and both agreed since weather package showed lax landing west; we'd expect a new routing to seavu or other west arrival. However; BASET3 remained as route clearance arrival.once airborne abq center questioned our route at 20 NM west of gbn at fl 360. FMC showed gbn to tnp; and then baset 3. Abq directed us to messi intersection along J104; thus messi dct tnp. No other comment from abq center. Unsure how/why FMC dropped J104 from navigation routing. I personally loaded non-standard route and loaded J104; knowing inconsistencies were normal from our origination city. Both pilots discussed and reviewed departure routing and clearance. Yet; dispatch clearance was antiquated and failed to match current conditions at lax.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737-700 Flight Crew experienced a track deviation during a flight from TUS to LAX. The J104 airway between GBN and TNP had dropped out.

Narrative: As First Officer; I was aware NAV routing from the originating city is notoriously inconsistent and previous experience consistently showed the Dispatch Release seldom matched the departure clearance routing from that city to any destination. It is very common for the Release to issue BURRO2 and voice clearance to issue WILDCAT2 Departure. Thus; when we received the non-standard routing to LAX; I carefully manually entered routing; including J-104. (I did not enter a standard route and then modify it at any time.) But; clearance past TNP was BASET3; which indicated LAX was landing east. I clarified clearance with Delivery via voice; and wrote the clearance on my copy of Release. This peculiarity was mentioned to the Captain during the clearance briefing. All briefings were accomplished in accordance with FOM standards. Route was confirmed; and both agreed since weather package showed LAX landing west; we'd expect a new routing to SEAVU or other west arrival. However; BASET3 remained as route clearance arrival.Once airborne ABQ Center questioned our route at 20 NM west of GBN at FL 360. FMC showed GBN to TNP; and then BASET 3. ABQ directed us to MESSI intersection along J104; thus MESSI DCT TNP. No other comment from ABQ Center. Unsure how/why FMC dropped J104 from NAV routing. I personally loaded non-standard route and loaded J104; knowing inconsistencies were normal from our origination city. Both Pilots discussed and reviewed departure routing and clearance. Yet; Dispatch Clearance was antiquated and failed to match current conditions at LAX.

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