Narrative:

On departure at approximately 14000 ft with the autoplt engaged; I noticed the control column cycling forward and aft once every 20 seconds. At first I thought it was because I was climbing out in perf. I disconnected perf and climbed using mach hold and EPR limit. This had no effect and the control column continued to cycle forward and aft once every 20-30 seconds. Upon reaching cruise altitude 33000 ft with the autoplt engaged; the control column continued to cycle forward and aft. I disconnected the autoplt and hand flew the aircraft and noticed the control column continued to cycle forward and aft. At this point; I had the first officer take the controls of the aircraft to see if he could feel and see what I was experiencing. He had the same indications and the same control column inputs as I did. At this point; we re-engaged the autoplt and referred to the QRH to see if there was anything related to this type of flight control 'abnormality.' there was nothing specific to what we were experiencing on our aircraft. I then contacted a maintenance tech via ACARS phone patch to see if there was any history or patterns of this particular type of flight control abnormality on this aircraft. I gave the maintenance tech the details of what we were experiencing and they informed me that I should consider landing as soon as practical. I was in total agreement because at this point I was already considering landing. I terminated the phone patch with maintenance and contacted dispatch to let them know that I would be diverting to either ZZZ1 or ZZZ2. He recommended ZZZ1 because it was about the same distance to ZZZ2; and ZZZ1 had opportunities for connecting passenger. I told the dispatcher that we were in the turn back to ZZZ1 and he asked me if I had declared an emergency. I told him at this point we had not declared an emergency but I would as soon as conditions permitted and I would relay everything through ATC. Once the aircraft was headed west bound; I declared an emergency with ATC for flight control malfunction. I felt that the situation was not getting any better and my experience with t-tailed aircraft told me that as you get lighter; these types of flight control problems get worse as the aircraft gets lighter. We made a normal en route descent and visual approach to landing. As we were in the descent; I received an ACARS message from maintenance telling me to try turning the mach trim switch to override. We did this in the descent but had no effect on the problem. Aircraft landing in ZZZ1 overweight with no problems. Emergency was terminated upon landing rollout. Callback conversation with reporter revealed the following information: captain reports that at least 2 issues were involved in this incident. One was faulty angle of attack (aoa) system and the second #2 vertical gyro. Ground maintenance discovered the aoa discrepancy and a flight test crew discovered the gyro. The angle of attack fault was attempting to activate the stall warning system which explains why the mach trim was partially activated. The #2 gyro was causing the autoplt to 'burp' at 30 second intervals as the gyro fluctuated. This crew was not interested in troubleshooting the problem in-flight because there were behaviors they did not understand and since the aircraft was controllable at the time they simply wanted to get on the ground and troubleshoot later. Supplemental information from acn 665189: the pfd would also jump about 5 degrees nose up then nose down. I also noticed the mach trim indicator was extended past the tip about a tenth of an inch and we were only flying mach .75 which seemed a little strange. Additionally; we disengaged the autoplt several times and the problem went away for the most part; however; there was a rumbling felt on the yoke which also concerned us. At that point; we became really concerned that we could have a stabilizer problem. Callback conversation with reporter acn 665189 revealed the following information: first officer reported that after 3 days of troubleshooting; maintenance discovered a rate gyro failure in the #2 (first officer's) flight control computer. The reporter stated that he has 9000 hours in type and has never experienced this before. They were truly concerned about the aircraft's condition. Reporter forwarded the maintenance department's analysis of the troubleshooting and flight testing accomplished in order to definitively solve this problem. The report's conclusion stated; 'and... This test crew said this isn't the first fcf they have flown for this very same condition on other MD80's... And the fix has always been the #1 or #2 vg. Good information for MD80 crews to know to switching to the auxiliary vg if they have ever have this condition.

Google
 

Original NASA ASRS Text

Title: AN MD80 OSCILLATED APPROX 5 DEGS AT 30 SECOND INTERVALS WITH THE AUTOPLT ENGAGED AND THE MACH TRIM SLIGHTLY ACTIVATED. THE CREW DECLARED AN EMER AND DIVERTED.

Narrative: ON DEP AT APPROX 14000 FT WITH THE AUTOPLT ENGAGED; I NOTICED THE CTL COLUMN CYCLING FORWARD AND AFT ONCE EVERY 20 SECONDS. AT FIRST I THOUGHT IT WAS BECAUSE I WAS CLBING OUT IN PERF. I DISCONNECTED PERF AND CLBED USING MACH HOLD AND EPR LIMIT. THIS HAD NO EFFECT AND THE CONTROL COLUMN CONTINUED TO CYCLE FORWARD AND AFT ONCE EVERY 20-30 SECONDS. UPON REACHING CRUISE ALT 33000 FT WITH THE AUTOPLT ENGAGED; THE CTL COLUMN CONTINUED TO CYCLE FORWARD AND AFT. I DISCONNECTED THE AUTOPLT AND HAND FLEW THE ACFT AND NOTICED THE CTL COLUMN CONTINUED TO CYCLE FORWARD AND AFT. AT THIS POINT; I HAD THE FO TAKE THE CTLS OF THE ACFT TO SEE IF HE COULD FEEL AND SEE WHAT I WAS EXPERIENCING. HE HAD THE SAME INDICATIONS AND THE SAME CTL COLUMN INPUTS AS I DID. AT THIS POINT; WE RE-ENGAGED THE AUTOPLT AND REFERRED TO THE QRH TO SEE IF THERE WAS ANYTHING RELATED TO THIS TYPE OF FLT CTL 'ABNORMALITY.' THERE WAS NOTHING SPECIFIC TO WHAT WE WERE EXPERIENCING ON OUR ACFT. I THEN CONTACTED A MAINT TECH VIA ACARS PHONE PATCH TO SEE IF THERE WAS ANY HISTORY OR PATTERNS OF THIS PARTICULAR TYPE OF FLT CTL ABNORMALITY ON THIS ACFT. I GAVE THE MAINT TECH THE DETAILS OF WHAT WE WERE EXPERIENCING AND THEY INFORMED ME THAT I SHOULD CONSIDER LNDG AS SOON AS PRACTICAL. I WAS IN TOTAL AGREEMENT BECAUSE AT THIS POINT I WAS ALREADY CONSIDERING LNDG. I TERMINATED THE PHONE PATCH WITH MAINT AND CONTACTED DISPATCH TO LET THEM KNOW THAT I WOULD BE DIVERTING TO EITHER ZZZ1 OR ZZZ2. HE RECOMMENDED ZZZ1 BECAUSE IT WAS ABOUT THE SAME DISTANCE TO ZZZ2; AND ZZZ1 HAD OPPORTUNITIES FOR CONNECTING PAX. I TOLD THE DISPATCHER THAT WE WERE IN THE TURN BACK TO ZZZ1 AND HE ASKED ME IF I HAD DECLARED AN EMER. I TOLD HIM AT THIS POINT WE HAD NOT DECLARED AN EMER BUT I WOULD AS SOON AS CONDITIONS PERMITTED AND I WOULD RELAY EVERYTHING THROUGH ATC. ONCE THE ACFT WAS HEADED W BOUND; I DECLARED AN EMER WITH ATC FOR FLT CTL MALFUNCTION. I FELT THAT THE SIT WAS NOT GETTING ANY BETTER AND MY EXPERIENCE WITH T-TAILED ACFT TOLD ME THAT AS YOU GET LIGHTER; THESE TYPES OF FLT CTL PROBS GET WORSE AS THE ACFT GETS LIGHTER. WE MADE A NORMAL ENRTE DSCNT AND VISUAL APCH TO LNDG. AS WE WERE IN THE DSCNT; I RECEIVED AN ACARS MESSAGE FROM MAINT TELLING ME TO TRY TURNING THE MACH TRIM SWITCH TO OVERRIDE. WE DID THIS IN THE DSCNT BUT HAD NO EFFECT ON THE PROB. ACFT LNDG IN ZZZ1 OVERWEIGHT WITH NO PROBS. EMER WAS TERMINATED UPON LNDG ROLLOUT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CAPT RPTS THAT AT LEAST 2 ISSUES WERE INVOLVED IN THIS INCIDENT. ONE WAS FAULTY ANGLE OF ATTACK (AOA) SYSTEM AND THE SECOND #2 VERTICAL GYRO. GND MAINT DISCOVERED THE AOA DISCREPANCY AND A FLT TEST CREW DISCOVERED THE GYRO. THE ANGLE OF ATTACK FAULT WAS ATTEMPTING TO ACTIVATE THE STALL WARNING SYSTEM WHICH EXPLAINS WHY THE MACH TRIM WAS PARTIALLY ACTIVATED. THE #2 GYRO WAS CAUSING THE AUTOPLT TO 'BURP' AT 30 SECOND INTERVALS AS THE GYRO FLUCTUATED. THIS CREW WAS NOT INTERESTED IN TROUBLESHOOTING THE PROB INFLT BECAUSE THERE WERE BEHAVIORS THEY DID NOT UNDERSTAND AND SINCE THE ACFT WAS CONTROLLABLE AT THE TIME THEY SIMPLY WANTED TO GET ON THE GND AND TROUBLESHOOT LATER. SUPPLEMENTAL INFO FROM ACN 665189: THE PFD WOULD ALSO JUMP ABOUT 5 DEGS NOSE UP THEN NOSE DOWN. I ALSO NOTICED THE MACH TRIM INDICATOR WAS EXTENDED PAST THE TIP ABOUT A TENTH OF AN INCH AND WE WERE ONLY FLYING MACH .75 WHICH SEEMED A LITTLE STRANGE. ADDITIONALLY; WE DISENGAGED THE AUTOPLT SEVERAL TIMES AND THE PROB WENT AWAY FOR THE MOST PART; HOWEVER; THERE WAS A RUMBLING FELT ON THE YOKE WHICH ALSO CONCERNED US. AT THAT POINT; WE BECAME REALLY CONCERNED THAT WE COULD HAVE A STABILIZER PROB. CALLBACK CONVERSATION WITH RPTR ACN 665189 REVEALED THE FOLLOWING INFO: FO RPTED THAT AFTER 3 DAYS OF TROUBLESHOOTING; MAINT DISCOVERED A RATE GYRO FAILURE IN THE #2 (FO'S) FLT CTL COMPUTER. THE RPTR STATED THAT HE HAS 9000 HRS IN TYPE AND HAS NEVER EXPERIENCED THIS BEFORE. THEY WERE TRULY CONCERNED ABOUT THE ACFT'S CONDITION. RPTR FORWARDED THE MAINT DEPT'S ANALYSIS OF THE TROUBLESHOOTING AND FLT TESTING ACCOMPLISHED IN ORDER TO DEFINITIVELY SOLVE THIS PROB. THE RPT'S CONCLUSION STATED; 'AND... THIS TEST CREW SAID THIS ISN'T THE FIRST FCF THEY HAVE FLOWN FOR THIS VERY SAME CONDITION ON OTHER MD80'S... AND THE FIX HAS ALWAYS BEEN THE #1 OR #2 VG. GOOD INFO FOR MD80 CREWS TO KNOW TO SWITCHING TO THE AUX VG IF THEY HAVE EVER HAVE THIS CONDITION.

Data retrieved from NASA's ASRS site as of January 2009 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.