Narrative:

We were en route from dca to mco approximately 30 mins prior to landing when jax center ask us to descend from our cruise altitude to FL310. This was accomplished using the FMS and a VNAV descent. The aircraft smoothly descended to FL310 and leveled automatically. VNAV level was displayed on the flight mode annunciator. FL310 was also displayed in the altitude alert advisory window. A few mins later the flight attendant knocked at the door and I turned to let her in. At that moment the first officer said we are descending and he immediately pressed the altitude hold button. We descended about 100-150 ft before we returned to FL310. We did not deviation more than 150 ft and there was not a traffic conflict. This problem occurred because I had already entered crossing restrictions into the FMS that were displayed on the arrival we were using into mco. The FMS began a descent to meet these crossing restrictions with complete disregard for the altitude displayed in the altitude alert window. This is a software problem that has resulted in many altitude violations. I strongly suggest that a change be made to the software package. The FMS should look at the altitude in the altitude select window as it's primary reference and then other restrictions as secondary references. This would prevent the aircraft from automatically departing preselected altitudes.

Related reports:

Google
 

Original NASA ASRS Text

Title: ALTDEV ALT EXCURSION.

Narrative: WE WERE ENRTE FROM DCA TO MCO APPROX 30 MINS PRIOR TO LNDG WHEN JAX CENTER ASK US TO DSND FROM OUR CRUISE ALT TO FL310. THIS WAS ACCOMPLISHED USING THE FMS AND A VNAV DSCNT. THE ACFT SMOOTHLY DSNDED TO FL310 AND LEVELED AUTOMATICALLY. VNAV LEVEL WAS DISPLAYED ON THE FLT MODE ANNUNCIATOR. FL310 WAS ALSO DISPLAYED IN THE ALT ALERT ADVISORY WINDOW. A FEW MINS LATER THE FLT ATTENDANT KNOCKED AT THE DOOR AND I TURNED TO LET HER IN. AT THAT MOMENT THE FO SAID WE ARE DSNDING AND HE IMMEDIATELY PRESSED THE ALT HOLD BUTTON. WE DSNDED ABOUT 100-150 FT BEFORE WE RETURNED TO FL310. WE DID NOT DEV MORE THAN 150 FT AND THERE WAS NOT A TFC CONFLICT. THIS PROBLEM OCCURRED BECAUSE I HAD ALREADY ENTERED XING RESTRICTIONS INTO THE FMS THAT WERE DISPLAYED ON THE ARR WE WERE USING INTO MCO. THE FMS BEGAN A DSCNT TO MEET THESE XING RESTRICTIONS WITH COMPLETE DISREGARD FOR THE ALT DISPLAYED IN THE ALT ALERT WINDOW. THIS IS A SOFTWARE PROBLEM THAT HAS RESULTED IN MANY ALT VIOLATIONS. I STRONGLY SUGGEST THAT A CHANGE BE MADE TO THE SOFTWARE PACKAGE. THE FMS SHOULD LOOK AT THE ALT IN THE ALT SELECT WINDOW AS IT'S PRIMARY REF AND THEN OTHER RESTRICTIONS AS SECONDARY REFS. THIS WOULD PREVENT THE ACFT FROM AUTOMATICALLY DEPARTING PRESELECTED ALTS.

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.