Narrative:

At FL370 while in clear, daylight, smooth conditions, the aircraft began a smooth climb. The captain noticed it first, called it to my attention (I was looking at another MD11 below us). I disconnected the autoplt and returned to FL370. We had been at FL370 for about 6 hours (flight was lax-nrt) and the only FMS input was for a descent to cross a fix inbound to nrt. The only glareshield (autoflt) input was a heading change. The captain saw FL370 still in altitude window during this excursion. We were descending back to FL370 when tokyo asked if we were avoiding WX. We said no, we were returning to FL370. No conflict arose and nothing further was said. Remainder of flight uneventful. The mechanic in nrt ran a diagnostic on the autoflt/FMS/glareshield and found only a spurious speed input to FMS descent. He felt it had nothing to do with this event. I have heard of only 1 other such type excursion and have been on this aircraft for 6 yrs. I am upset that I do not know how or why it occurred or how to prevent it from recurring. I will visit with our MD11 type manager next week to research this matter. I would be most appreciative if you have any information on what might have caused this. Callback conversation with reporter revealed the following information: the reporter stated the aircraft began a slow smooth gentle climb from FL370 to FL378 when the deviation was discovered. The reporter said at no time did the altitude alert sound and the altitude select still read FL370. The reporter stated the report was written up and tokyo maintenance did a comprehensive test of the autoflt, FMS and glareshield components and found nothing that would cause the altitude deviation. The reporter said the outbound captain who had extensive MD11 experience was advised of the event and commented it had happened once before. The reporter has 6 yrs flying the MD11 with no previous experience of altitude deviation from the flight control computer. The reporter stated a visit was made to air carrier MD11 flight manager to request information on previous autoplt altitude hold reports on the MD11 but none were in the maintenance history.

Google
 

Original NASA ASRS Text

Title: AN MD11 IN CRUISE AT FL370 WITH AUTOPLT IN ALT HOLD MODE BEGAN A SMOOTH GENTLE CLB TO FL378 WITH NO ALT ALERT WARNING. ALT SELECT STILL INDICATED FL370.

Narrative: AT FL370 WHILE IN CLR, DAYLIGHT, SMOOTH CONDITIONS, THE ACFT BEGAN A SMOOTH CLB. THE CAPT NOTICED IT FIRST, CALLED IT TO MY ATTN (I WAS LOOKING AT ANOTHER MD11 BELOW US). I DISCONNECTED THE AUTOPLT AND RETURNED TO FL370. WE HAD BEEN AT FL370 FOR ABOUT 6 HRS (FLT WAS LAX-NRT) AND THE ONLY FMS INPUT WAS FOR A DSCNT TO CROSS A FIX INBOUND TO NRT. THE ONLY GLARESHIELD (AUTOFLT) INPUT WAS A HDG CHANGE. THE CAPT SAW FL370 STILL IN ALT WINDOW DURING THIS EXCURSION. WE WERE DSNDING BACK TO FL370 WHEN TOKYO ASKED IF WE WERE AVOIDING WX. WE SAID NO, WE WERE RETURNING TO FL370. NO CONFLICT AROSE AND NOTHING FURTHER WAS SAID. REMAINDER OF FLT UNEVENTFUL. THE MECH IN NRT RAN A DIAGNOSTIC ON THE AUTOFLT/FMS/GLARESHIELD AND FOUND ONLY A SPURIOUS SPD INPUT TO FMS DSCNT. HE FELT IT HAD NOTHING TO DO WITH THIS EVENT. I HAVE HEARD OF ONLY 1 OTHER SUCH TYPE EXCURSION AND HAVE BEEN ON THIS ACFT FOR 6 YRS. I AM UPSET THAT I DO NOT KNOW HOW OR WHY IT OCCURRED OR HOW TO PREVENT IT FROM RECURRING. I WILL VISIT WITH OUR MD11 TYPE MGR NEXT WEEK TO RESEARCH THIS MATTER. I WOULD BE MOST APPRECIATIVE IF YOU HAVE ANY INFO ON WHAT MIGHT HAVE CAUSED THIS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR STATED THE ACFT BEGAN A SLOW SMOOTH GENTLE CLB FROM FL370 TO FL378 WHEN THE DEV WAS DISCOVERED. THE RPTR SAID AT NO TIME DID THE ALT ALERT SOUND AND THE ALT SELECT STILL READ FL370. THE RPTR STATED THE RPT WAS WRITTEN UP AND TOKYO MAINT DID A COMPREHENSIVE TEST OF THE AUTOFLT, FMS AND GLARESHIELD COMPONENTS AND FOUND NOTHING THAT WOULD CAUSE THE ALTDEV. THE RPTR SAID THE OUTBOUND CAPT WHO HAD EXTENSIVE MD11 EXPERIENCE WAS ADVISED OF THE EVENT AND COMMENTED IT HAD HAPPENED ONCE BEFORE. THE RPTR HAS 6 YRS FLYING THE MD11 WITH NO PREVIOUS EXPERIENCE OF ALTDEV FROM THE FLT CTL COMPUTER. THE RPTR STATED A VISIT WAS MADE TO ACR MD11 FLT MGR TO REQUEST INFO ON PREVIOUS AUTOPLT ALT HOLD RPTS ON THE MD11 BUT NONE WERE IN THE MAINT HISTORY.

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.