Narrative:

We had just leveled off from a step climb from FL330 to FL350. The first officer was busy with the plotting chart and I was busy with an ACARS message. The first officer noticed the aircraft passing FL355 and that FL360 was set in the altitude controller on the flight control panel. I arrested the climb using the vertical speed wheel, reset FL350 in the altitude controller, and selected the init page on my mcdu. The altitude blocks on the mcdu init page were all dashes. Maximum altitude reached during the deviation was FL356. All normal procedures were followed during the step climb and we are convinced the aircraft entered an uncommanded climb through some type of FMS fault. There were no altitude warnings leaving FL350. We advised zan of the deviation. Both of us are new to 2 pilot transports. If both of us had not been distraction with other chores we would probably have noticed the deviation sooner. In the future I will be certain that even in cruise flight the PF will be just that, and all other duties will be delegated to the PNF. Supplemental information from acn 375055: after re-establishing FL350 we noticed on the flight plan init page that there were dashes in the cruise level field. After using normal procedures (ie, altitude restr of cleared altitude in altitude window) in the climb, we confirmed passing FL340 for FL350 and got the altitude aural message. We leveled at FL350 and shortly thereafter the deviation occurred with no altitude warning upon leaving FL350. I am convinced the FMS had some sort of fault. Had there not been the distrs at that time we probably would have caught it sooner.

Google
 

Original NASA ASRS Text

Title: AN ACR MD11 FLC HAD THE ACFT LEAVE ITS ASSIGNED ALT AND START A CLB. NEITHER PLT NOTICED THE BEGINNING OF THIS PHENOMENON AND THE ALT ALERT DID NOT SOUND. THE FO NOTICED THE CLB AS THE ACFT PASSED FL355 AND THE FLC THEN RETURNED TO FL350 AND ADVISED THE ARTCC CTLR OF THE DEV. THE FLC IS CONVINCED THAT THIS WAS AN FMC MALFUNCTION, BUT ADMIT THAT THEY BOTH WERE UNDULY DISTR BY ROUTINE TASKS.

Narrative: WE HAD JUST LEVELED OFF FROM A STEP CLB FROM FL330 TO FL350. THE FO WAS BUSY WITH THE PLOTTING CHART AND I WAS BUSY WITH AN ACARS MESSAGE. THE FO NOTICED THE ACFT PASSING FL355 AND THAT FL360 WAS SET IN THE ALT CTLR ON THE FLT CTL PANEL. I ARRESTED THE CLB USING THE VERT SPD WHEEL, RESET FL350 IN THE ALT CTLR, AND SELECTED THE INIT PAGE ON MY MCDU. THE ALT BLOCKS ON THE MCDU INIT PAGE WERE ALL DASHES. MAX ALT REACHED DURING THE DEV WAS FL356. ALL NORMAL PROCS WERE FOLLOWED DURING THE STEP CLB AND WE ARE CONVINCED THE ACFT ENTERED AN UNCOMMANDED CLB THROUGH SOME TYPE OF FMS FAULT. THERE WERE NO ALT WARNINGS LEAVING FL350. WE ADVISED ZAN OF THE DEV. BOTH OF US ARE NEW TO 2 PLT TRANSPORTS. IF BOTH OF US HAD NOT BEEN DISTR WITH OTHER CHORES WE WOULD PROBABLY HAVE NOTICED THE DEV SOONER. IN THE FUTURE I WILL BE CERTAIN THAT EVEN IN CRUISE FLT THE PF WILL BE JUST THAT, AND ALL OTHER DUTIES WILL BE DELEGATED TO THE PNF. SUPPLEMENTAL INFO FROM ACN 375055: AFTER RE-ESTABLISHING FL350 WE NOTICED ON THE FLT PLAN INIT PAGE THAT THERE WERE DASHES IN THE CRUISE LEVEL FIELD. AFTER USING NORMAL PROCS (IE, ALT RESTR OF CLRED ALT IN ALT WINDOW) IN THE CLB, WE CONFIRMED PASSING FL340 FOR FL350 AND GOT THE ALT AURAL MESSAGE. WE LEVELED AT FL350 AND SHORTLY THEREAFTER THE DEV OCCURRED WITH NO ALT WARNING UPON LEAVING FL350. I AM CONVINCED THE FMS HAD SOME SORT OF FAULT. HAD THERE NOT BEEN THE DISTRS AT THAT TIME WE PROBABLY WOULD HAVE CAUGHT IT SOONER.

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.