A B737-300 flight crew deviate from arrival track at las following a late runway change.

Attributes
ACN	770735
Time
Date	200801
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : las.airport
State Reference	NV
Altitude	msl single value : 12000
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
Route In Use	arrival star : grnpa
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 308 flight time type : 9833
ASRS Report	770735
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 215 flight time type : 10000
ASRS Report	770739
Events
Anomaly	aircraft equipment problem : less severe non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance flight crew : returned to intended or assigned course
Supplementary
Problem Areas	Flight Crew Human Performance Aircraft
Primary Problem	Flight Crew Human Performance

Narrative:

We were on arrival into las vegas and had made the restr of luxor at 12000 ft and 250 knots. We were told to descend via the arrival for runway 19L. The LNAV was set up for runway 25L and several points on the arrival had been deleted because we don't use them for runway 25. I reselected the arrival and inadvertently selected the wrong point to go to. Neither one of us caught the error and when the aircraft began a turn; it appeared to be turning in the right direction. I then proceeded to change the runway in the LNAV to runway 19L and when I looked up; we were still in a turn. Checking the LNAV I saw the error and was in the process of turning back to course when approach control intervened and directed us to turn to heading 180 immediately. We were already in a turn in that direction and completed the turn to prescribed heading (180). Since we were off the STAR; she then gave us a descent to 10000 ft and handed us off to another controller who vectored us to runway 19L. Landing was uneventful. Better coordination of LNAV inputs particularly since this was a -300. The error would have been readily recognized in a -700 because the map presentation would have looked incorrect. Coordinate the input/verify/select.

Original NASA ASRS Text

Title: A B737-300 FLT CREW DEVIATE FROM ARR TRACK AT LAS FOLLOWING A LATE RWY CHANGE.

Narrative: WE WERE ON ARR INTO LAS VEGAS AND HAD MADE THE RESTR OF LUXOR AT 12000 FT AND 250 KNOTS. WE WERE TOLD TO DSND VIA THE ARR FOR RWY 19L. THE LNAV WAS SET UP FOR RWY 25L AND SEVERAL POINTS ON THE ARR HAD BEEN DELETED BECAUSE WE DON'T USE THEM FOR RWY 25. I RESELECTED THE ARR AND INADVERTENTLY SELECTED THE WRONG POINT TO GO TO. NEITHER ONE OF US CAUGHT THE ERROR AND WHEN THE ACFT BEGAN A TURN; IT APPEARED TO BE TURNING IN THE RIGHT DIRECTION. I THEN PROCEEDED TO CHANGE THE RWY IN THE LNAV TO RWY 19L AND WHEN I LOOKED UP; WE WERE STILL IN A TURN. CHKING THE LNAV I SAW THE ERROR AND WAS IN THE PROCESS OF TURNING BACK TO COURSE WHEN APCH CTL INTERVENED AND DIRECTED US TO TURN TO HDG 180 IMMEDIATELY. WE WERE ALREADY IN A TURN IN THAT DIRECTION AND COMPLETED THE TURN TO PRESCRIBED HDG (180). SINCE WE WERE OFF THE STAR; SHE THEN GAVE US A DSCNT TO 10000 FT AND HANDED US OFF TO ANOTHER CTLR WHO VECTORED US TO RWY 19L. LNDG WAS UNEVENTFUL. BETTER COORD OF LNAV INPUTS PARTICULARLY SINCE THIS WAS A -300. THE ERROR WOULD HAVE BEEN READILY RECOGNIZED IN A -700 BECAUSE THE MAP PRESENTATION WOULD HAVE LOOKED INCORRECT. COORDINATE THE INPUT/VERIFY/SELECT.

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