Narrative:

Flight was in cruise at FL390 inbound to lax. Fmcs was programmed for civet 2 profile descent runway 25L approach. As aircraft neared descent point ATC cleared flight to FL350. The cruise page on FMC was selected and FL350 entered. Aircraft started descent further clrncs to FL310, FL290 and finally FL240 were issued and speed reductions to 280 KTS and 250 KTS were also issued. Aircraft then cleared for civet 2 profile descent. 8000 ft was selected on master control panel. This was the final altitude in the descent profile all other crossing altitudes were already programmed in the fmcs and therefore should have been met by the aircraft since the speed of 250 KTS was issued by ATC speed intervention was selected and aircraft descended. As aircraft neared 10000 ft I deselected speed intervention but instead of 250 KTS being selected the aircraft bug went to 320 KTS. I reselected speed intervention and 250 KTS. When aircraft leveled at 10000 ft near arnes I deselected speed intervention and speed remained at 250 KTS. About 3 mi from arnes the FMC speed bug suddenly slowed to 180 KTS. I called out speed 180 and reselected 250 KTS. As I was doing that the copilot noticed the aircraft suddenly nose over and start descending at 2000 FPM. He called out that we were still 3 mi from arnes and should be at 10000 ft. My attention was still fixed on the airspeed bug and it took me a few seconds to realize what was happening. About this time, lax approach control called and asked us if we knew we were descending early. I reached up and pressed, the altitude hold button stopping the descent at 9300 ft. ATC reclred us to maintain 9000 ft to arnes and then told us to continue the approach. I feel the reason for this altitude error was a problem in the FMC controller and also because we had selected 8000 ft in the altitude selector. If we had selected each crossing altitude in the profile we would not have descended early and would have a better picture of our position on the profile. Instead of having to deal with multiple problems we would only have had a speed problem to deal with.

Google
 

Original NASA ASRS Text

Title: ACR WDB ALTDEV OVERSHOT DURING DSCNT INTO LAX ON CIVET PROFILE TRYING VERY HARD TO ANALYZE AUTO APCH RESPONSE TO PRESENT PROFILE.

Narrative: FLT WAS IN CRUISE AT FL390 INBOUND TO LAX. FMCS WAS PROGRAMMED FOR CIVET 2 PROFILE DSCNT RWY 25L APCH. AS ACFT NEARED DSCNT POINT ATC CLRED FLT TO FL350. THE CRUISE PAGE ON FMC WAS SELECTED AND FL350 ENTERED. ACFT STARTED DSCNT FURTHER CLRNCS TO FL310, FL290 AND FINALLY FL240 WERE ISSUED AND SPD REDUCTIONS TO 280 KTS AND 250 KTS WERE ALSO ISSUED. ACFT THEN CLRED FOR CIVET 2 PROFILE DSCNT. 8000 FT WAS SELECTED ON MASTER CTL PANEL. THIS WAS THE FINAL ALT IN THE DSCNT PROFILE ALL OTHER XING ALTS WERE ALREADY PROGRAMMED IN THE FMCS AND THEREFORE SHOULD HAVE BEEN MET BY THE ACFT SINCE THE SPD OF 250 KTS WAS ISSUED BY ATC SPD INTERVENTION WAS SELECTED AND ACFT DSNDED. AS ACFT NEARED 10000 FT I DESELECTED SPD INTERVENTION BUT INSTEAD OF 250 KTS BEING SELECTED THE ACFT BUG WENT TO 320 KTS. I RESELECTED SPD INTERVENTION AND 250 KTS. WHEN ACFT LEVELED AT 10000 FT NEAR ARNES I DESELECTED SPD INTERVENTION AND SPD REMAINED AT 250 KTS. ABOUT 3 MI FROM ARNES THE FMC SPD BUG SUDDENLY SLOWED TO 180 KTS. I CALLED OUT SPD 180 AND RESELECTED 250 KTS. AS I WAS DOING THAT THE COPLT NOTICED THE ACFT SUDDENLY NOSE OVER AND START DSNDING AT 2000 FPM. HE CALLED OUT THAT WE WERE STILL 3 MI FROM ARNES AND SHOULD BE AT 10000 FT. MY ATTN WAS STILL FIXED ON THE AIRSPD BUG AND IT TOOK ME A FEW SECONDS TO REALIZE WHAT WAS HAPPENING. ABOUT THIS TIME, LAX APCH CTL CALLED AND ASKED US IF WE KNEW WE WERE DSNDING EARLY. I REACHED UP AND PRESSED, THE ALT HOLD BUTTON STOPPING THE DSCNT AT 9300 FT. ATC RECLRED US TO MAINTAIN 9000 FT TO ARNES AND THEN TOLD US TO CONTINUE THE APCH. I FEEL THE REASON FOR THIS ALT ERROR WAS A PROBLEM IN THE FMC CTLR AND ALSO BECAUSE WE HAD SELECTED 8000 FT IN THE ALT SELECTOR. IF WE HAD SELECTED EACH XING ALT IN THE PROFILE WE WOULD NOT HAVE DSNDED EARLY AND WOULD HAVE A BETTER PICTURE OF OUR POS ON THE PROFILE. INSTEAD OF HAVING TO DEAL WITH MULTIPLE PROBLEMS WE WOULD ONLY HAVE HAD A SPD PROBLEM TO DEAL WITH.

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.