An apparent loss of previously programmed fixes on the skebr RNAV 2 arrival to las, nv.

Attributes
ACN	572373
Time
Date	200301
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	navaid : dag.vortac
State Reference	CA
Altitude	msl single value : 13000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : l30.tracon tower : phx.tower
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 375 flight time total : 14000 flight time type : 2600
ASRS Report	572373
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended or assigned course
Consequence	other
Supplementary
Problem Areas	Aircraft Company Flight Crew Human Performance
Primary Problem	Aircraft

Narrative:

Course deviation on the ground in lax, I programmed FMC for route and arrival to runway 35L in las skebr RNAV 2 arrival. I verified route prior to pushback. Upon arrival into las airspace, we were cleared to cross clarr intersection at 13000 ft. We were later given the clearance 'fly the skebr arrival except maintain 13000 ft.' I remained on the FMC descent page for my descent profile to cross clarr at 13000 ft and 250 KTS. After crossing clarr intersection, the aircraft began a right turn, something both the captain and I immediately realized was not what we should be doing. I started typing in the next fix (skebr) and the captain notified ATC that we were correcting back to the left. We were given a vector heading for spacing, and later told to go direct bld VOR. When I reprogrammed the FMC, I noticed that we were going from clarr intersection directly to shand intersection. Somewhere between lax and las, the arrival fixes after clarr dropped out?! Both the captain and I had verified that the arrival fixes were programmed in the box both prior to pushback and also en route.

Original NASA ASRS Text

Title: AN APPARENT LOSS OF PREVIOUSLY PROGRAMMED FIXES ON THE SKEBR RNAV 2 ARR TO LAS, NV.

Narrative: COURSE DEVIATION ON THE GND IN LAX, I PROGRAMMED FMC FOR RTE AND ARR TO RWY 35L IN LAS SKEBR RNAV 2 ARR. I VERIFIED RTE PRIOR TO PUSHBACK. UPON ARR INTO LAS AIRSPACE, WE WERE CLRED TO CROSS CLARR INTXN AT 13000 FT. WE WERE LATER GIVEN THE CLRNC 'FLY THE SKEBR ARR EXCEPT MAINTAIN 13000 FT.' I REMAINED ON THE FMC DSCNT PAGE FOR MY DSCNT PROFILE TO CROSS CLARR AT 13000 FT AND 250 KTS. AFTER XING CLARR INTXN, THE ACFT BEGAN A R TURN, SOMETHING BOTH THE CAPT AND I IMMEDIATELY REALIZED WAS NOT WHAT WE SHOULD BE DOING. I STARTED TYPING IN THE NEXT FIX (SKEBR) AND THE CAPT NOTIFIED ATC THAT WE WERE CORRECTING BACK TO THE L. WE WERE GIVEN A VECTOR HDG FOR SPACING, AND LATER TOLD TO GO DIRECT BLD VOR. WHEN I REPROGRAMMED THE FMC, I NOTICED THAT WE WERE GOING FROM CLARR INTXN DIRECTLY TO SHAND INTXN. SOMEWHERE BTWN LAX AND LAS, THE ARR FIXES AFTER CLARR DROPPED OUT?! BOTH THE CAPT AND I HAD VERIFIED THAT THE ARR FIXES WERE PROGRAMMED IN THE BOX BOTH PRIOR TO PUSHBACK AND ALSO ENRTE.

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.