MD82 CREW HAD AIRFRAME VIBRATION; AURAL STALL WARNING ACTIVATION; AND MACH INDICATION FLUCTUATION.

2000-01 · NASA ASRS report 462010

Date: 2000-01 · Aircraft: MD-82 · Phase: cruise

Anomalies: aircraft-equipment-problem-critical|inflight-event-encounter-loss-of-aircraft-control|other-airframe-vibration-mach-indication-aural-stall-warning

Synopsis

MD82 CREW HAD AIRFRAME VIBRATION; AURAL STALL WARNING ACTIVATION; AND MACH INDICATION FLUCTUATION.

Narrative

THE FOLLOWING DETAILS AN INCIDENT ON JAN/XA/00; WHILE ENRTE FROM FORT MEYERS; FL; TO DETROIT; MI. AT THE TIME OF THE INCIDENT; THE ACFT HAD BEEN OPERATING AT FL350 FOR APPROX 10-15 MINS AND WAS APPROX 100 MI N OF ATLANTA; GA; ON AN ATC ASSIGNED VECTOR TO VOLUNTEER VOR (KNOXVILLE; TN). THE SIC WAS THE PF; WITH THE ACFT ON AUTOPLT AND AUTOTHROTTLE. TIME OF THE INCIDENT WAS NOT NOTED. ACFT WT WAS APPROX 136000 LBS. WHILE IN LEVEL FLT AT FL350; WE BECAME AWARE OF A HIGH FREQ VIBRATION; WHICH WAS FIRST THOUGHT TO BE CAUSED BY TURB. THE VIBRATION WAS UNUSUAL; IN THAT IT WAS RAPID 'STACCATO' IN NATURE AND SEEMED TO GROW IN MAGNITUDE AT A REGULAR RATE. THE ONLY TIME I HAD FELT A SIMILAR VIBRATION WAS DURING A MACH BUFFET DEMONSTRATION IN A B737 SIMULATOR. I FELT THAT THE VIBRATION MIGHT HAVE BEEN CAUSED BY MACH BUFFET; CTL FLUTTER; OR A STRUCTURAL PROB. THE VIBRATION WAS INCREASING IN SEVERITY AND I TOLD THE SIC TO REDUCE SPD. THE SIC DISCONNECTED THE AUTOTHROTTLES AND MADE A PWR REDUCTION WHICH HAD NO EFFECT. THE VIBRATION CONTINUED TO GET WORSE AND I ORDERED A SECOND PWR REDUCTION. AT SOME TIME DURING THIS SCENARIO; THE SIC DISCONNECTED THE AUTOPLT AND HAND FLEW THE ACFT. HE LATER STATED THAT WHEN HE DISCONNECTED THE AUTOPLT; THE ACFT WAS 'IN TRIM' AND STILL MAINTAINING ALT. A SHORT TIME LATER; THE STALL WARNING ACTUATED. THE SIC ADVANCED THE PWR LEVERS AND I BACKED HIM UP TO FIREWALL PWR. THE STALL WARNING PERSISTED. I TOLD THE SIC TO LOWER THE NOSE AND WE STARTED A DSCNT. AT APPROX FL340 THE STALL WARNING CEASED; BUT WHEN THE SIC ATTEMPTED TO LEVEL THE ACFT; THE STALL WARNING SOUNDED AGAIN. WE CONTINUED THE DSCNT AND THE STALL WARNING TERMINATED. I ADVISED ATC THAT WE HAD LEFT FL350 AS A RESULT OF A STALL WARNING AND REQUESTED FL310. THE COCKPIT WAS VERY NOISY AND I WAS UNABLE TO HEAR THE CTLR'S READBACK. I MADE THE ADVISORY/REQUEST AGAIN AND WAS ISSUED FL310. WE CONTINUED THE DSCNT TO FL310 WITHOUT FURTHER INCIDENT OR QUERY FROM ATC. AT NO TIME WERE THERE ANY OTHER INDICATIONS THAT THE ACFT WAS IN A STALL OR APCH TO STALL SIT; OTHER THAN THE ACTUATION OF THE STALL WARNING SYS. THE SIC STATED THAT THE ACFT RESPONDED NORMALLY TO BOTH PITCH AND ROLL COMMANDS AT ALL TIMES DURING THE INCIDENT. HOWEVER; AT FL310; WE OBSERVED RAPID CHANGES IN MACH NUMBER WITH NO CHANGES IN PWR OR INDICATED AIRSPD. AT ONE TIME; THE MACH CHANGED FROM .754 TO .770 IN LESS THAN 4 SECONDS. IN ANOTHER EXCURSION; THE MACH WAS SEEN TO MOVE FROM .754 TO .776 IN ABOUT 10 SECONDS. BASED ON THE SIC'S DESCRIPTION OF CTL RESPONSE; THE ACFT'S STABILITY AND IN-TRIM CONDITION AT THE TIME OF THE STALL WARNING EVENT; AND THE NOTED MALFUNCTIONS OF THE MACH SPD INDICATING SYS; WE BELIEVED THE STALL WARNING TO BE A FALSE INDICATION. AFTER REVIEWING THE QRH; CHAPTER 13 (AIRSPD/MACH INDICATIONS UNRELIABLE); I DETERMINED THAT WE COULD SAFELY CONTINUE THE FLT TO THE DEST USING INDICATED AIRSPD ONLY. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: CREW WAS FLYING AN MD82 ACFT. A NEW PLT; WITH APPROX 100 HRS IN TYPE; DESCRIBED MACH BUFFET. THIS CAME ON SO INTENSELY THAT HE WAS UNSURE WHAT IT WAS. PWR REDUCTION DID NOT SEEM TO HELP. THE MD82 HAS AN AURAL 'STALL' VOICE WARNING SYS. THIS IS WHAT ACTIVATED ALONG WITH A STALL WARNING ANNUNCIATOR LIGHT. AT NO TIME WAS THE STICK SHAKER SYS ACTIVATED. THEY ENCOUNTERED A SECONDARY STALL WARNING AFTER DSNDING ONLY 1000 FT. MAINT CHKED THE ENTIRE AIRFRAME FOR POSSIBLE SOURCES OF VIBRATION; AND NOTHING WAS FOUND. BOTH MACH METERS VARIED IN UNISON. THE MACH; AIR DATA SYS WERE CHKED IN DETAIL; AND NOTHING WAS FOUND.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.