Narrative:

We were filed for the civet arrival into lax. Approximately 5-10 mi from the civet intersection we were cleared via pdz 4 arrival followed shortly by 'cross civet at or above 14000 ft.' we were constantly given changes of arrs and/or runways at very close distances to lax with little or no notice. It is very common to get the civet arrival to runway 25L followed shortly thereafter by the mitts 1 to runway 24R. The captain and I discussed this possibility in our briefing and in fact had the mitts 1 loaded in route 2 on the FMC. As discussed above, we were very unexpectedly given the pdz 4 followed by 'cross civet at or above 10400 ft.' the captain entered this arrival while I looked for the commercial arrival plate. By the time the arrival was entered into the FMC and I discovered that civet is not on the pdz 4 arrival, we were approximately 2 mi past civet with a corresponding route discontinuity on the FMC. I told the captain to ask the controller what arrival he wanted us on, as civet was not on the pdz 4. The controller said 'the civet, the civet, you are 2 mi west of course, turn right heading 310 degrees and intercept runway 25L.' by this time the captain had pdz 4 and runway 24R programmed into the FMC and the runway 24R ILS frequency in the ILS raw data radio. By the time now we reshifted gears, found the approach plate, dialed in the frequency to runway 25L, and reprogrammed the FMC for the approach, the controller said 'you are cleared to bremr and the civet 4 arrival to runway 25L.' at this time we were a very short distance from bremr, perhaps 5 mi. The captain entered bremr into the FMC. I verified it and told him to execute it. I then reached up and engaged the LNAV on the MCP and verified it via the LNAV FMA annunciation on the ADI. Immediately after the LNAV engagement the autoplt began a left turn on course on the arrival as we were then over bremr. I then looked down to my arrival chart to see what our next altitude for descent was. The captain put the next altitude of 10000 ft for arnes into the altitude indicator window. When I looked up from the chart to verify that altitude, I noticed the airplane started a slow right turn back toward the heading bug that was not yet moved from the previous 310 degree heading set before. I immediately took the airplane away from the autoplt and hand flew the remainder of the approach and arrival. The controller who must have now been watching us very closely said that he now showed us north of course and to turn back left to intercept the runway 25L localizer. I have no idea nor does the captain how the airplane came out of LNAV and back into heading select. This deviation was caught very quickly and the airplane hand flown uneventfully for the remainder of the flight. As far as we know there was no traffic conflict or any other problem. Clearly the controller did not mean to give us the pdz 4 arrival, as he clearly stated he wanted us on the civet 4 when we asked him about the discrepancy of the clearance. I don't believe that the airplane was ever out of control or that it would have been better to hand fly it any earlier than I did. The reason I say this is that we were extremely busy constantly changing gears the entire time all this was going on. When the airplane flew straight ahead after crossing civet due to the route discontinuity it was doing exactly what I would have been doing if I were hand flying it as per our clearance. There was no where to go after civet because it was not on the pdz 4 arrival. The autoplt actually allowed us to get the charts out and figure out the mess that we found ourselves in. It is very difficult to have to totally shift gears in one of these airplanes when you have no idea a change is coming. I think that it may be easy for a controller looking at his screen to say 'I need spacing here, so let's move this guy to the runway,' when it isn't near that easy for a pilot who has to find the new arrival, new approach plate, figure the information presented on those plates, get down, slow down, etc. I don't think that the current method of 2 arrival changes and 3 runway changes which is not uncommon at all is conducive to safe flight operations. At an extremely busy airport, that has an extremely large amount of traffic and the busiest time of a flight, flcs are forced to be headsdown as they are forced to find new plates and digest the information presented on them. Then throw in just 1 small mistake -- be it controller or pilot -- and it is very easy to get behind an airplane quickly. At the very least, I do not believe that an arrival change should be allowed unless told by a previous controller to possibly expect that change further down the road. That way, as in this case, that procedure can be looked at and any discrepancies found (ie, civet not on pdz 4).

Google
 

Original NASA ASRS Text

Title: A B767 FLC IS OVERLOADED WITH ARR CHANGES AND SUFFERS A HDG TRACK DEV ON THE CIVET STAR E OF LAX, CA.

Narrative: WE WERE FILED FOR THE CIVET ARR INTO LAX. APPROX 5-10 MI FROM THE CIVET INTXN WE WERE CLRED VIA PDZ 4 ARR FOLLOWED SHORTLY BY 'CROSS CIVET AT OR ABOVE 14000 FT.' WE WERE CONSTANTLY GIVEN CHANGES OF ARRS AND/OR RWYS AT VERY CLOSE DISTANCES TO LAX WITH LITTLE OR NO NOTICE. IT IS VERY COMMON TO GET THE CIVET ARR TO RWY 25L FOLLOWED SHORTLY THEREAFTER BY THE MITTS 1 TO RWY 24R. THE CAPT AND I DISCUSSED THIS POSSIBILITY IN OUR BRIEFING AND IN FACT HAD THE MITTS 1 LOADED IN RTE 2 ON THE FMC. AS DISCUSSED ABOVE, WE WERE VERY UNEXPECTEDLY GIVEN THE PDZ 4 FOLLOWED BY 'CROSS CIVET AT OR ABOVE 10400 FT.' THE CAPT ENTERED THIS ARR WHILE I LOOKED FOR THE COMMERCIAL ARR PLATE. BY THE TIME THE ARR WAS ENTERED INTO THE FMC AND I DISCOVERED THAT CIVET IS NOT ON THE PDZ 4 ARR, WE WERE APPROX 2 MI PAST CIVET WITH A CORRESPONDING RTE DISCONTINUITY ON THE FMC. I TOLD THE CAPT TO ASK THE CTLR WHAT ARR HE WANTED US ON, AS CIVET WAS NOT ON THE PDZ 4. THE CTLR SAID 'THE CIVET, THE CIVET, YOU ARE 2 MI W OF COURSE, TURN R HDG 310 DEGS AND INTERCEPT RWY 25L.' BY THIS TIME THE CAPT HAD PDZ 4 AND RWY 24R PROGRAMMED INTO THE FMC AND THE RWY 24R ILS FREQ IN THE ILS RAW DATA RADIO. BY THE TIME NOW WE RESHIFTED GEARS, FOUND THE APCH PLATE, DIALED IN THE FREQ TO RWY 25L, AND REPROGRAMMED THE FMC FOR THE APCH, THE CTLR SAID 'YOU ARE CLRED TO BREMR AND THE CIVET 4 ARR TO RWY 25L.' AT THIS TIME WE WERE A VERY SHORT DISTANCE FROM BREMR, PERHAPS 5 MI. THE CAPT ENTERED BREMR INTO THE FMC. I VERIFIED IT AND TOLD HIM TO EXECUTE IT. I THEN REACHED UP AND ENGAGED THE LNAV ON THE MCP AND VERIFIED IT VIA THE LNAV FMA ANNUNCIATION ON THE ADI. IMMEDIATELY AFTER THE LNAV ENGAGEMENT THE AUTOPLT BEGAN A L TURN ON COURSE ON THE ARR AS WE WERE THEN OVER BREMR. I THEN LOOKED DOWN TO MY ARR CHART TO SEE WHAT OUR NEXT ALT FOR DSCNT WAS. THE CAPT PUT THE NEXT ALT OF 10000 FT FOR ARNES INTO THE ALT INDICATOR WINDOW. WHEN I LOOKED UP FROM THE CHART TO VERIFY THAT ALT, I NOTICED THE AIRPLANE STARTED A SLOW R TURN BACK TOWARD THE HDG BUG THAT WAS NOT YET MOVED FROM THE PREVIOUS 310 DEG HDG SET BEFORE. I IMMEDIATELY TOOK THE AIRPLANE AWAY FROM THE AUTOPLT AND HAND FLEW THE REMAINDER OF THE APCH AND ARR. THE CTLR WHO MUST HAVE NOW BEEN WATCHING US VERY CLOSELY SAID THAT HE NOW SHOWED US N OF COURSE AND TO TURN BACK L TO INTERCEPT THE RWY 25L LOC. I HAVE NO IDEA NOR DOES THE CAPT HOW THE AIRPLANE CAME OUT OF LNAV AND BACK INTO HDG SELECT. THIS DEV WAS CAUGHT VERY QUICKLY AND THE AIRPLANE HAND FLOWN UNEVENTFULLY FOR THE REMAINDER OF THE FLT. AS FAR AS WE KNOW THERE WAS NO TFC CONFLICT OR ANY OTHER PROB. CLRLY THE CTLR DID NOT MEAN TO GIVE US THE PDZ 4 ARR, AS HE CLRLY STATED HE WANTED US ON THE CIVET 4 WHEN WE ASKED HIM ABOUT THE DISCREPANCY OF THE CLRNC. I DON'T BELIEVE THAT THE AIRPLANE WAS EVER OUT OF CTL OR THAT IT WOULD HAVE BEEN BETTER TO HAND FLY IT ANY EARLIER THAN I DID. THE REASON I SAY THIS IS THAT WE WERE EXTREMELY BUSY CONSTANTLY CHANGING GEARS THE ENTIRE TIME ALL THIS WAS GOING ON. WHEN THE AIRPLANE FLEW STRAIGHT AHEAD AFTER XING CIVET DUE TO THE RTE DISCONTINUITY IT WAS DOING EXACTLY WHAT I WOULD HAVE BEEN DOING IF I WERE HAND FLYING IT AS PER OUR CLRNC. THERE WAS NO WHERE TO GO AFTER CIVET BECAUSE IT WAS NOT ON THE PDZ 4 ARR. THE AUTOPLT ACTUALLY ALLOWED US TO GET THE CHARTS OUT AND FIGURE OUT THE MESS THAT WE FOUND OURSELVES IN. IT IS VERY DIFFICULT TO HAVE TO TOTALLY SHIFT GEARS IN ONE OF THESE AIRPLANES WHEN YOU HAVE NO IDEA A CHANGE IS COMING. I THINK THAT IT MAY BE EASY FOR A CTLR LOOKING AT HIS SCREEN TO SAY 'I NEED SPACING HERE, SO LET'S MOVE THIS GUY TO THE RWY,' WHEN IT ISN'T NEAR THAT EASY FOR A PLT WHO HAS TO FIND THE NEW ARR, NEW APCH PLATE, FIGURE THE INFO PRESENTED ON THOSE PLATES, GET DOWN, SLOW DOWN, ETC. I DON'T THINK THAT THE CURRENT METHOD OF 2 ARR CHANGES AND 3 RWY CHANGES WHICH IS NOT UNCOMMON AT ALL IS CONDUCIVE TO SAFE FLT OPS. AT AN EXTREMELY BUSY ARPT, THAT HAS AN EXTREMELY LARGE AMOUNT OF TFC AND THE BUSIEST TIME OF A FLT, FLCS ARE FORCED TO BE HEADSDOWN AS THEY ARE FORCED TO FIND NEW PLATES AND DIGEST THE INFO PRESENTED ON THEM. THEN THROW IN JUST 1 SMALL MISTAKE -- BE IT CTLR OR PLT -- AND IT IS VERY EASY TO GET BEHIND AN AIRPLANE QUICKLY. AT THE VERY LEAST, I DO NOT BELIEVE THAT AN ARR CHANGE SHOULD BE ALLOWED UNLESS TOLD BY A PREVIOUS CTLR TO POSSIBLY EXPECT THAT CHANGE FURTHER DOWN THE ROAD. THAT WAY, AS IN THIS CASE, THAT PROC CAN BE LOOKED AT AND ANY DISCREPANCIES FOUND (IE, CIVET NOT ON PDZ 4).

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.