Narrative:

Our filed plan was: pdx..btg J189 ave.SADDE6.lax. The actual clearance contained a revised segment 'J189 lmt.' we programmed the FMC as J189 lmt direct ave SADDE6. At approximately 40 NM north of lin, ZOA asked if we were going direct to linden. We said no, direct avenal. Controller asked if prior frequency cleared us direct avenal. We believed after lmt we were cleared to avenal as per our pre-departure clearance. The controller cleared us direct avenal at this point. If ATC intended us to fly the originally filed route, I don't understand the purpose of the revised segment in the pre-departure clearance. There was no traffic conflict.

Google
 

Original NASA ASRS Text

Title: ACR HAS TRACK DEV NEAR LINDEN, CA, AFTER THEY LOADED AN APPARENT ROUTING CHANGE INCORRECTLY INTO THE FMC.

Narrative: OUR FILED PLAN WAS: PDX..BTG J189 AVE.SADDE6.LAX. THE ACTUAL CLRNC CONTAINED A REVISED SEGMENT 'J189 LMT.' WE PROGRAMMED THE FMC AS J189 LMT DIRECT AVE SADDE6. AT APPROX 40 NM N OF LIN, ZOA ASKED IF WE WERE GOING DIRECT TO LINDEN. WE SAID NO, DIRECT AVENAL. CTLR ASKED IF PRIOR FREQ CLRED US DIRECT AVENAL. WE BELIEVED AFTER LMT WE WERE CLRED TO AVENAL AS PER OUR PRE-DEP CLRNC. THE CTLR CLRED US DIRECT AVENAL AT THIS POINT. IF ATC INTENDED US TO FLY THE ORIGINALLY FILED RTE, I DON'T UNDERSTAND THE PURPOSE OF THE REVISED SEGMENT IN THE PRE-DEP CLRNC. THERE WAS NO TFC CONFLICT.

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.