37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1049148 |
Time | |
Date | 201211 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Flight Conditions | IMC |
Aircraft 1 | |
Make Model Name | MD-83 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Component | |
Aircraft Component | Navigational Equipment and Processing |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical |
Narrative:
Descending approximately 15 miles east of destination through 6;000 MSL the a/P [autopilot] and a/T [autothrottles] disconnected. Master caution 'yaw damp inoperative' and 'mach trim inoperative' messages illuminated on the eoap [electrical overhead annunciator panel]. Both nav displays showed map fail and both flight directors went out of view. Both fmas went to test mode and the a/P MCP went blank. The mcdus showed GNS [garmin navigation system] fail. The airspeed indicator and altimeter appeared unaffected. Airspeed was later cross referenced with a request to ATC for indicated groundspeed and appeared to be consistent with what was presented on the instrument. No groundspeed was available on cockpit instruments. I took manual control of the aircraft while the first officer searched the QRH for a relevant checklist. At this time ATC was giving vectors to avoid our destination's class B airspace and as we had not yet verified that we had good heading information. Given the procedure for referencing the stby compass; I elected to declare an emergency. As we descended below the cloud bases; familiar landmarks were referenced and we were able to ascertain that we had good heading information from the rmis. After a short discussion that it had to be coming from somewhere and given the lack of guidance from the QRH; we switched to dfgc [digital flight guidance computer] 2 and everything but the captain's FD [flight director] started working. Placing the F/D selector switch to 'both on 2' gave F/D indications on the captain's eadi [electronic attitude direction indicator]. We advised ATC that we had our instruments back and were vectored to the ILS. The approach and landing were uneventful. On the ground; reports were made to local maintenance and dispatch. Messages were left with the duty pilot and maintenance control.
Original NASA ASRS Text
Title: An MD-83 flight crew tangled with multiple Nav system failures as they descended near their destination. With assistance from ATC they were able to recover adequate navigation and attitude reference to complete their arrival.
Narrative: Descending approximately 15 miles east of destination through 6;000 MSL the A/P [Autopilot] and A/T [Autothrottles] disconnected. Master Caution 'Yaw Damp Inoperative' and 'Mach Trim Inoperative' messages illuminated on the EOAP [Electrical Overhead Annunciator Panel]. Both Nav Displays showed MAP FAIL and both Flight Directors went out of view. Both FMAs went to test mode and the A/P MCP went blank. The MCDUs showed GNS [Garmin Navigation System] FAIL. The Airspeed indicator and Altimeter appeared unaffected. Airspeed was later cross referenced with a request to ATC for indicated groundspeed and appeared to be consistent with what was presented on the instrument. No groundspeed was available on cockpit instruments. I took manual control of the aircraft while the First Officer searched the QRH for a relevant checklist. At this time ATC was giving vectors to avoid our destination's Class B airspace and as we had not yet verified that we had good heading information. Given the procedure for referencing the STBY Compass; I elected to declare an emergency. As we descended below the cloud bases; familiar landmarks were referenced and we were able to ascertain that we had good heading information from the RMIs. After a short discussion that it had to be coming from somewhere and given the lack of guidance from the QRH; we switched to DFGC [Digital Flight Guidance Computer] 2 and everything but the Captain's FD [Flight Director] started working. Placing the F/D selector switch to 'BOTH ON 2' gave F/D indications on the Captain's EADI [Electronic Attitude Direction Indicator]. We advised ATC that we had our instruments back and were vectored to the ILS. The approach and landing were uneventful. On the ground; reports were made to Local Maintenance and Dispatch. Messages were left with the Duty Pilot and Maintenance Control.
Data retrieved from NASA's ASRS site as of July 2013 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.