Narrative:

On the ground in oak, the first officer programmed the CDU for our flight. While he programmed the route, I monitored his key strokes. He put in our route OAKLAS01 then activated and executed the route. Then he paged through the route on the route page to ensure the programmed route matched the flight plan. Then he went to the arrival page and assured the tragr 2 to runway 25L was active, and it was. Then he went to the legs page and paged through the entire route. When he got to the tragr 2 section of the arrival, the route went from tragr intersection with a discontinuity and then to the shand intersection. The discontinuity was cleaned up and we were both satisfied that the route was correctly entered. Once we were on the arrival, we of course passed the tragr intersection and went directly to the shand intersection. ATC noticed our off-course trend and asked where we were going. Consulting the legs page, we noticed our mistake and made a course correction direct to ipumy intersection and the remainder of the tragr 2 arrival. Once on the ground, the first officer reprogrammed the computer for the same route. It was then that we realized our mistake. The new database dropped the last 3 intxns on the tragr 2 arrival and we assumed that the entire arrival was in the stored company route. The company route should include all of the fixes on the arrival. If all of the intxns are not included in the stored route, then a note on the dispatch release should be mandatory. Supplemental information from acn 572541: a company NOTAM stated 'FMC database inaccuracies', but failed to mention the possibility of missing fixes. In the future, I will verify the route via the legs pages, also any NOTAMS should include more detail or a note to contact dispatch to verify the problem.

Related reports:

Google
 

Original NASA ASRS Text

Title: A TRACK DEV ON THE TRAGR 2 ARR TO LAS, NV.

Narrative: ON THE GND IN OAK, THE FO PROGRAMMED THE CDU FOR OUR FLT. WHILE HE PROGRAMMED THE RTE, I MONITORED HIS KEY STROKES. HE PUT IN OUR RTE OAKLAS01 THEN ACTIVATED AND EXECUTED THE RTE. THEN HE PAGED THROUGH THE RTE ON THE RTE PAGE TO ENSURE THE PROGRAMMED RTE MATCHED THE FLT PLAN. THEN HE WENT TO THE ARR PAGE AND ASSURED THE TRAGR 2 TO RWY 25L WAS ACTIVE, AND IT WAS. THEN HE WENT TO THE LEGS PAGE AND PAGED THROUGH THE ENTIRE RTE. WHEN HE GOT TO THE TRAGR 2 SECTION OF THE ARR, THE RTE WENT FROM TRAGR INTXN WITH A DISCONTINUITY AND THEN TO THE SHAND INTXN. THE DISCONTINUITY WAS CLEANED UP AND WE WERE BOTH SATISFIED THAT THE RTE WAS CORRECTLY ENTERED. ONCE WE WERE ON THE ARR, WE OF COURSE PASSED THE TRAGR INTXN AND WENT DIRECTLY TO THE SHAND INTXN. ATC NOTICED OUR OFF-COURSE TREND AND ASKED WHERE WE WERE GOING. CONSULTING THE LEGS PAGE, WE NOTICED OUR MISTAKE AND MADE A COURSE CORRECTION DIRECT TO IPUMY INTXN AND THE REMAINDER OF THE TRAGR 2 ARR. ONCE ON THE GND, THE FO REPROGRAMMED THE COMPUTER FOR THE SAME RTE. IT WAS THEN THAT WE REALIZED OUR MISTAKE. THE NEW DATABASE DROPPED THE LAST 3 INTXNS ON THE TRAGR 2 ARR AND WE ASSUMED THAT THE ENTIRE ARR WAS IN THE STORED COMPANY RTE. THE COMPANY RTE SHOULD INCLUDE ALL OF THE FIXES ON THE ARR. IF ALL OF THE INTXNS ARE NOT INCLUDED IN THE STORED RTE, THEN A NOTE ON THE DISPATCH RELEASE SHOULD BE MANDATORY. SUPPLEMENTAL INFO FROM ACN 572541: A COMPANY NOTAM STATED 'FMC DATABASE INACCURACIES', BUT FAILED TO MENTION THE POSSIBILITY OF MISSING FIXES. IN THE FUTURE, I WILL VERIFY THE RTE VIA THE LEGS PAGES, ALSO ANY NOTAMS SHOULD INCLUDE MORE DETAIL OR A NOTE TO CONTACT DISPATCH TO VERIFY THE PROB.

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.