37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1314223 |
Time | |
Date | 201511 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | MD-80 Series (DC-9-80) Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Total 22000 |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Track / Heading All Types |
Narrative:
While cruising at FL320 our first indication of any problems to come was a 'horizon' light on the FMA. We looked at both attitude indicators; noting they appeared normal for now and after a few minutes the first officer (first officer) attitude indicator was tilting down 5-10 degrees while the capt.'s appeared normal. We looked in the QRH for guidance. After a few more minutes a 'heading' light appeared on the FMA's. We compared both compasses and found to be satisfactory. Next I noticed on the capt.'s pfd a 'rnp' message appeared. I told the first officer that we were not receiving any VOR's/DME's. The first officer dialed in [a] VOR to check our position which was showing ok at this point. The aircraft started turning toward ZZZ which was our clearance; but we noticed it was turning too early and went into heading hold. ATC told us it was 9 miles too early. We asked for vectors which we received. While in that turn I noticed that the FMS DME was off and was counting down at a very rapid rate. The first officer told me his navigational display showed an 800 knot tailwind. While on vectors; heading what ATC gave us (about a 235 heading) ATC asked again what our heading was and required another 10 degrees left to go where he needed us. ATC corrected us a few more times. I now realized that our heading system wasn't working correctly. Again asked for vectors. Soon our flight displays went away as well as we lost the autopilot and auto throttles. First officer kept hand flying. Requested lower because of rvsm airspace. ATC gave us FL280 and we descended to it. Now I tried to figure out just what we really had. Notified dispatch of situation and asked about any other airport with better weather with what reaming gas we had. Told dispatch our intentions.... Requested vectors to [destination]. Notified ATC as well of all malfunctions we saw. Notified #1 flight attenendats (flight attendant) and told her of our situation. Working with ATC...I was able to test the #1 VOR system at several points to verify its accuracy. It appeared to work ok but at this time wasn't sure of anything regarding the air crafts navigation equipment. We then noticed that the FMA's were out along with the flight directors. Eventually we shut off the flight directors. They became more of a distraction than help. The first officer told me about a message in the FMS system that said 'platform failure 2' and within a few minutes of clearing; another message 'platform failure 1' was in the FMS message box. Next went the map feature on the nd's. This entire time there were no flags anywhere. Eventually the message mcdu popped up on the pfd. Again looked in the QRH. Tried ACARS as well for ATIS but didn't work.not one of these multiple events happened simultaneously. They failed one at a time just adding to the complication of this flight. Descent was uneventful with the help from ATC. We were vectored all the way to final until we broke out underneath the clouds at about 2300. The #1 ILS appeared to work correctly and a visual approach; with raw data only; continued until touchdown. At about 800 AGL the ground prox equipment sounded off with 'whoop whoop pull up' until I turned it off so it would not distract us during landing.
Original NASA ASRS Text
Title: MD-80 Captain reported sequential loss of flight and navigational instruments; autopilot; autothrottles; ACARS; and FMS Platforms while in cruise at FL320 and during subsequent descent. Aircraft landed in visual conditions with assistance from ATC.
Narrative: While cruising at FL320 our first indication of any problems to come was a 'HORIZON' light on the FMA. We looked at both attitude indicators; noting they appeared normal for now and after a few minutes the First Officer (FO) attitude indicator was tilting down 5-10 degrees while the Capt.'s appeared normal. We looked in the QRH for guidance. After a few more minutes a 'HEADING' light appeared on the FMA'S. We compared both compasses and found to be satisfactory. Next I noticed on the Capt.'s PFD a 'RNP' message appeared. I told the First Officer that we were not receiving any VOR's/DME's. The FO dialed in [a] VOR to check our position which was showing OK at this point. The aircraft started turning toward ZZZ which was our clearance; but we noticed it was turning too early and went into Heading Hold. ATC told us it was 9 miles too early. We asked for vectors which we received. While in that turn I noticed that the FMS DME was off and was counting down at a very rapid rate. The FO told me his Navigational Display showed an 800 knot tailwind. While on vectors; heading what ATC gave us (about a 235 heading) ATC asked again what our heading was and required another 10 degrees left to go where he needed us. ATC corrected us a few more times. I now realized that our heading system wasn't working correctly. Again asked for vectors. Soon our Flight Displays went away as well as we lost the Autopilot and Auto throttles. FO kept hand flying. Requested lower because of RVSM airspace. ATC gave us FL280 and we descended to it. Now I tried to figure out just what we really had. Notified dispatch of situation and asked about any other airport with better weather with what reaming gas we had. Told Dispatch our intentions.... Requested vectors to [destination]. Notified ATC as well of all malfunctions we saw. Notified #1 Flight Attenendats (FA) and told her of our situation. Working with ATC...I was able to test the #1 VOR system at several points to verify its accuracy. It appeared to work OK but at this time wasn't sure of anything regarding the Air Crafts navigation equipment. We then noticed that the FMA's were out along with the flight directors. Eventually we shut off the flight directors. They became more of a distraction than help. The F/O told me about a message in the FMS system that said 'PLATFORM FAILURE 2' and within a few minutes of clearing; another message 'PLATFORM FAILURE 1' was in the FMS message box. Next went the MAP feature on the ND's. This entire time there were NO flags anywhere. Eventually the message MCDU popped up on the PFD. Again looked in the QRH. Tried ACARS as well for ATIS but didn't work.Not one of these multiple events happened simultaneously. They failed one at a time just adding to the complication of this flight. Descent was uneventful with the help from ATC. We were vectored all the way to final until we broke out underneath the clouds at about 2300. The #1 ILS appeared to work correctly and a visual approach; with raw data only; continued until touchdown. At about 800 AGL the Ground Prox equipment sounded off with 'whoop whoop pull up' until I turned it off so it would not distract us during landing.
Data retrieved from NASA's ASRS site 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.