Narrative:

Somewhere outside civet we were cleared and I read back the civet 5 arrival runway 25R. Somewhere after civet we were told to switch to frequency 128.5. I knew this was wrong. When we checked in the controller asked if we were going to runway 24R. I said no; we were cleared for runway 25R. The controller said change to runway 24R; frequency 108.5 and cleared for that runway. We did; no further incident. This happens way too often; and way too late in the arrival phase. We had an FMC that was slow to respond to our inputs; and on more than one occasion gave the message 'single FMC operation' and 're-syncing other FMC.' this compounds to the problem; as there are way too many intxns and step-down fixes to comply with in a logical manner when the FMC is slow and approach gives you last second changes to comply with.

Google
 

Original NASA ASRS Text

Title: B767-200 FLT CREW HAS CLRNC CHANGE IN CLOSE DURING CIVET ARR TO LAX.

Narrative: SOMEWHERE OUTSIDE CIVET WE WERE CLRED AND I READ BACK THE CIVET 5 ARR RWY 25R. SOMEWHERE AFTER CIVET WE WERE TOLD TO SWITCH TO FREQ 128.5. I KNEW THIS WAS WRONG. WHEN WE CHKED IN THE CTLR ASKED IF WE WERE GOING TO RWY 24R. I SAID NO; WE WERE CLRED FOR RWY 25R. THE CTLR SAID CHANGE TO RWY 24R; FREQ 108.5 AND CLRED FOR THAT RWY. WE DID; NO FURTHER INCIDENT. THIS HAPPENS WAY TOO OFTEN; AND WAY TOO LATE IN THE ARR PHASE. WE HAD AN FMC THAT WAS SLOW TO RESPOND TO OUR INPUTS; AND ON MORE THAN ONE OCCASION GAVE THE MESSAGE 'SINGLE FMC OP' AND 'RE-SYNCING OTHER FMC.' THIS COMPOUNDS TO THE PROB; AS THERE ARE WAY TOO MANY INTXNS AND STEP-DOWN FIXES TO COMPLY WITH IN A LOGICAL MANNER WHEN THE FMC IS SLOW AND APCH GIVES YOU LAST SECOND CHANGES TO COMPLY WITH.

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.