A track deviation on the tragr RNAV 2 arrival to las, nv.

Attributes
ACN	572437
Time
Date	200301
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : las.airport
State Reference	NV
Altitude	msl single value : 8000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : l30.tracon
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : tragr
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 12500 flight time type : 2000
ASRS Report	572437
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 210 flight time total : 10500 flight time type : 7000
ASRS Report	572433
Events
Anomaly	non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	Company Aircraft Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Incorrect FMC programming. Programmed FMC in oak (aok.las.01) and selected runway 25L to get the entire route for the tragar arrival. I closed the route discontinuity between the arrival and runway, but did not look close enough to see that the fixes from tragr, then kimme were not listed. While we were on the arrival, we did not have the legs page up. We noticed the aircraft turn about 20 degrees left (which we knew was incorrect). It took us a few seconds to figure out what was going on. ATC noticed our turn and asked if we were headed to shand, we said yes, and ATC gave us a right turn to 130 degrees and gave us a phone number to call. On the ground we called company ATC specialist, who called back and said all was ok. I believe this problem was caused by a number of factors: 1) database in FMC was incorrect, problem was noted in flight release. 2) to quick to program FMC. 3) legs page was not displayed during arrival.

Original NASA ASRS Text

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

Narrative: INCORRECT FMC PROGRAMMING. PROGRAMMED FMC IN OAK (AOK.LAS.01) AND SELECTED RWY 25L TO GET THE ENTIRE RTE FOR THE TRAGAR ARR. I CLOSED THE RTE DISCONTINUITY BTWN THE ARR AND RWY, BUT DID NOT LOOK CLOSE ENOUGH TO SEE THAT THE FIXES FROM TRAGR, THEN KIMME WERE NOT LISTED. WHILE WE WERE ON THE ARR, WE DID NOT HAVE THE LEGS PAGE UP. WE NOTICED THE ACFT TURN ABOUT 20 DEGS L (WHICH WE KNEW WAS INCORRECT). IT TOOK US A FEW SECONDS TO FIGURE OUT WHAT WAS GOING ON. ATC NOTICED OUR TURN AND ASKED IF WE WERE HEADED TO SHAND, WE SAID YES, AND ATC GAVE US A R TURN TO 130 DEGS AND GAVE US A PHONE NUMBER TO CALL. ON THE GND WE CALLED COMPANY ATC SPECIALIST, WHO CALLED BACK AND SAID ALL WAS OK. I BELIEVE THIS PROB WAS CAUSED BY A NUMBER OF FACTORS: 1) DATABASE IN FMC WAS INCORRECT, PROB WAS NOTED IN FLT RELEASE. 2) TO QUICK TO PROGRAM FMC. 3) LEGS PAGE WAS NOT DISPLAYED DURING ARR.

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.