Narrative:

Cleared to descend on seavu arrival for runway 25L; 'maintain 300 knots or greater.' prior to seavu; given runway assignment change to runway 24R. During approach briefing; first officer stated that he had installed; '24 right in route 2.' following runway assignment change; first officer selected route 2 and my map showed a parallel display for runway 25L. I told the first officer; 'that's not right; I still see runway 25.' after numerous unsuccessful attempts by the first officer to correct the situation; I told him to abandon the FMC and request a vector and descent for the ILS runway 24 right from ATC. Meanwhile; I was turning to intercept the runway 24 right localizer via raw data. First officer complied; ATC issued the vector; descent clearance and subsequent approach clearance. There was no significant deviation from the arrival and ATC did not indicate any conflicts or problems. We landed uneventfully. Contributing factors: first officer had in fact loaded the seavu arrival for runway 25 left on route 2; not runway 24 right. First officer stated that this was his seventh trip in 2 weeks and he was tired. Also; we had an early morning; east coast departure and it was approximately afternoon domicile time when he loaded the route 2 page. I glanced at the route 2 page; confirmed a seavu arrival; and also did not notice that it was for runway 25L and not runway 24R. Also; this was my seventh day out of eight flying; early domicile time; and suffered performance degradation due to onerous scheduling.supplemental information from acn 785189: contributing factors to this occurrence were: 1) while I checked route 1 prior to the top of descent; I omitted re-checking route 2. 2) last minute runway/transition change. 3) early body clock wake-up time. 4) this was my seventh (7TH) trip in a 2 week period with minimal time off.

Related reports:

Google
 

Original NASA ASRS Text

Title: A FATIGUED B757 CREW ON THE LAX SEAVU RWY 25L ARR WAS CHANGED TO RWY 24R BUT DUE TO A FMC PROGRAMMING ERROR NEEDED VECTORS TO THE ARPT.

Narrative: CLEARED TO DESCEND ON SEAVU ARRIVAL FOR RWY 25L; 'MAINTAIN 300 KNOTS OR GREATER.' PRIOR TO SEAVU; GIVEN RUNWAY ASSIGNMENT CHANGE TO RWY 24R. DURING APPROACH BRIEFING; FO STATED THAT HE HAD INSTALLED; '24 RIGHT IN ROUTE 2.' FOLLOWING RUNWAY ASSIGNMENT CHANGE; FO SELECTED ROUTE 2 AND MY MAP SHOWED A PARALLEL DISPLAY FOR RWY 25L. I TOLD THE FO; 'THAT'S NOT RIGHT; I STILL SEE RWY 25.' AFTER NUMEROUS UNSUCCESSFUL ATTEMPTS BY THE FO TO CORRECT THE SITUATION; I TOLD HIM TO ABANDON THE FMC AND REQUEST A VECTOR AND DESCENT FOR THE ILS RWY 24 RIGHT FROM ATC. MEANWHILE; I WAS TURNING TO INTERCEPT THE RWY 24 RIGHT LOCALIZER VIA RAW DATA. FO COMPLIED; ATC ISSUED THE VECTOR; DESCENT CLEARANCE AND SUBSEQUENT APPROACH CLEARANCE. THERE WAS NO SIGNIFICANT DEVIATION FROM THE ARRIVAL AND ATC DID NOT INDICATE ANY CONFLICTS OR PROBLEMS. WE LANDED UNEVENTFULLY. CONTRIBUTING FACTORS: FO HAD IN FACT LOADED THE SEAVU ARRIVAL FOR RWY 25 LEFT ON ROUTE 2; NOT RWY 24 RIGHT. FO STATED THAT THIS WAS HIS SEVENTH TRIP IN 2 WEEKS AND HE WAS TIRED. ALSO; WE HAD AN EARLY MORNING; EAST COAST DEPARTURE AND IT WAS APPROXIMATELY AFTERNOON DOMICILE TIME WHEN HE LOADED THE ROUTE 2 PAGE. I GLANCED AT THE ROUTE 2 PAGE; CONFIRMED A SEAVU ARRIVAL; AND ALSO DID NOT NOTICE THAT IT WAS FOR RWY 25L AND NOT RWY 24R. ALSO; THIS WAS MY SEVENTH DAY OUT OF EIGHT FLYING; EARLY DOMICILE TIME; AND SUFFERED PERFORMANCE DEGRADATION DUE TO ONEROUS SCHEDULING.SUPPLEMENTAL INFO FROM ACN 785189: CONTRIBUTING FACTORS TO THIS OCCURRENCE WERE: 1) WHILE I CHECKED ROUTE 1 PRIOR TO THE TOP OF DESCENT; I OMITTED RE-CHECKING ROUTE 2. 2) LAST MINUTE RUNWAY/TRANSITION CHANGE. 3) EARLY BODY CLOCK WAKE-UP TIME. 4) THIS WAS MY SEVENTH (7TH) TRIP IN A 2 WEEK PERIOD WITH MINIMAL TIME OFF.

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.