B737-700 flight crew is issued a runway change during civet 5 arrival to lax and has a track/heading...

Attributes
ACN	733115
Time
Date	200703
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lax.airport
State Reference	CA
Altitude	msl single value : 15000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	common carrier : air carrier
Make Model Name	B737-700
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	arrival star : civet
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 225 flight time type : 10000
ASRS Report	733115
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Experience	flight time last 90 days : 223 flight time type : 4000
ASRS Report	733112
Events
Anomaly	non adherence : published procedure non adherence : clearance other spatial deviation
Independent Detector	other flight crewa other flight crewb
Resolutory Action	flight crew : returned to intended or assigned course
Supplementary
Problem Areas	ATC Human Performance Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

On approach into lax; we experienced a course deviation error while flying the civet arrival. Just after rustt on the arrival; we were given a runway change to runway 25R. This event occurred during a high workload phase of flight. As the PF I selected the departure/arrival page on the CDU and inadvertently selected the las arrs instead of lax. As I was also preoccupied with making the next crossing restr; I asked the captain (PNF) to take a look at the CDU and correct the mistake. At some point; the modification was executed and we no longer had the arrival or runway for lax. I went to heading select while the captain quickly reloaded the lax arrival and runway. We were approximately .5 miles north of eddso when the route was available. We corrected the course error and complied with all the crossing restrs. Shortly after shell on the approach; runway 24R became available and we were cleared for the visual and landing on runway 24R. During high workloads it is critical to have both pilots involved with programming route changes. It might be best to have PNF make the FMC changes; but in all cases; FMC route modes should be verified before the execute key is pressed.

Original NASA ASRS Text

Title: B737-700 FLT CREW IS ISSUED A RWY CHANGE DURING CIVET 5 ARR TO LAX AND HAS A TRACK/HEADING DEVIATION.

Narrative: ON APCH INTO LAX; WE EXPERIENCED A COURSE DEV ERROR WHILE FLYING THE CIVET ARR. JUST AFTER RUSTT ON THE ARR; WE WERE GIVEN A RWY CHANGE TO RWY 25R. THIS EVENT OCCURRED DURING A HIGH WORKLOAD PHASE OF FLT. AS THE PF I SELECTED THE DEP/ARR PAGE ON THE CDU AND INADVERTENTLY SELECTED THE LAS ARRS INSTEAD OF LAX. AS I WAS ALSO PREOCCUPIED WITH MAKING THE NEXT CROSSING RESTR; I ASKED THE CAPT (PNF) TO TAKE A LOOK AT THE CDU AND CORRECT THE MISTAKE. AT SOME POINT; THE MODIFICATION WAS EXECUTED AND WE NO LONGER HAD THE ARR OR RWY FOR LAX. I WENT TO HEADING SELECT WHILE THE CAPT QUICKLY RELOADED THE LAX ARR AND RWY. WE WERE APPROX .5 MILES N OF EDDSO WHEN THE RTE WAS AVAILABLE. WE CORRECTED THE COURSE ERROR AND COMPLIED WITH ALL THE CROSSING RESTRS. SHORTLY AFTER SHELL ON THE APCH; RWY 24R BECAME AVAILABLE AND WE WERE CLRED FOR THE VISUAL AND LNDG ON RWY 24R. DURING HIGH WORKLOADS IT IS CRITICAL TO HAVE BOTH PLTS INVOLVED WITH PROGRAMMING RTE CHANGES. IT MIGHT BE BEST TO HAVE PNF MAKE THE FMC CHANGES; BUT IN ALL CASES; FMC RTE MODES SHOULD BE VERIFIED BEFORE THE EXECUTE KEY IS PRESSED.

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

B737-700 flight crew is issued a runway change during civet 5 arrival to lax and has a track/heading deviation.