37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1000658 |
Time | |
Date | 201203 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Regional Jet 200 ER/LR (CRJ200) |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Component | |
Aircraft Component | AHRS/ND |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Critical Deviation - Speed All Types Deviation - Track / Heading All Types |
Narrative:
We were 1;000 ft above level off for the 12;000 ft restriction on the arrival. Off flags appeared in the captain's ADI and HSI; accompanied by a master caution; autopilot disconnect and EFIS comp messages. I immediately assumed manual control referencing pfd 2. I leveled off at 12;000 ft and cross checked the standby instruments and outside references. They seemed okay initially. The first officer noticed that there was an YD1 inoperative message and reset that. There were also roll and heading comparator flags in PFD2. I maintained wings level briefly to see if the AHRS1 would in flight align. The first officer noted a 30 degree anomaly between both heading systems and the standby compass. I confirmed this; took the radios and called for the EFIS comp mon checklist. After what seemed like more than a minute AHRS1 in flight aligned. There was still an EFIS comp message with roll and heading comparator flags in both pfd's. The frequency was congested and the situation dynamic so I did not call ATC right away. I noticed that we were slightly right of course and made a shallow left turn to intercept course. I continued to fly cross cockpit and noticed that ADI2 showed level flight while the aircraft was in nearly 10 degrees of right bank. This was confirmed with a careful cross check of the standby ADI and outside references. It seemed unbelievable to me but in fact it was true. Because of this discrepancy; I elected to not call for the QRH procedure for AHRS1 failure. This would only send this incorrect roll information to ADI1. Approach queried us about our speed. At this point I remembered that the last controller had assigned 300 KTS. I reported our actual speed of 250 KTS and added power. I also advised approach that our primary attitude and heading instruments had failed and that we were on the standby systems. I requested radar vectors. ATC issued an altitude change to the jet coming up behind us. He promptly complied. ATC assigned several incremental heading changes to put us on downwind. Once we were wings level on downwind we accurately adjusted both heading systems to the standby compass. After a minute of wings level flight on downwind both ai's also crosschecked wings level with the standby ADI and outside references. I switched to FD2 and engaged the autopilot. We monitored the systems closely. The remainder of the flight was uneventful. Maintenance found no discrepancy but the subsequent flight experienced a loss of PFD1 at 300 ft on final approach. That one cleared at touchdown and resulted in replacement of AHRS1. The autopilot and pilot flying's instruments shutting off just before level off with several messages to sort through. A marked difference between the remaining instruments; I think we all did our best under the circumstances. In 30 years as a pilot this is the first 'dual ADI failure' I have had; if you can call it that. I am not sure why AD2 was off slightly but the equipment proved its ability to in flight align. The only thing I would bring up is that the QRH is incomplete. It does not include the in flight alignment procedure described in the prm. Good luck making that happen. In the mean time I hope the detailed info in this report of a successful in flight alignment will be shared with my fellow rj pilots.
Original NASA ASRS Text
Title: A CRJ200 Captain reported a dual AHRS failure during descent including the EFIS COMP message; ADI and HSI OFF flags. The EFIS COMP MON Checklist was completed and the system reset before landing; but failed on the next flight and AHRS 1 was replaced.
Narrative: We were 1;000 FT above level off for the 12;000 FT restriction on the arrival. OFF flags appeared in the Captain's ADI and HSI; accompanied by a Master Caution; autopilot disconnect and EFIS COMP messages. I immediately assumed manual control referencing PFD 2. I leveled off at 12;000 FT and cross checked the standby instruments and outside references. They seemed okay initially. The First Officer noticed that there was an YD1 INOP message and reset that. There were also roll and heading comparator flags in PFD2. I maintained wings level briefly to see if the AHRS1 would in flight align. The First Officer noted a 30 degree anomaly between both heading systems and the standby compass. I confirmed this; took the radios and called for the EFIS COMP MON checklist. After what seemed like more than a minute AHRS1 in flight aligned. There was still an EFIS COMP message with roll and heading comparator flags in both PFD's. The frequency was congested and the situation dynamic so I did not call ATC right away. I noticed that we were slightly right of course and made a shallow left turn to intercept course. I continued to fly cross cockpit and noticed that ADI2 showed level flight while the aircraft was in nearly 10 degrees of right bank. This was confirmed with a careful cross check of the standby ADI and outside references. It seemed unbelievable to me but in fact it was true. Because of this discrepancy; I elected to not call for the QRH procedure for AHRS1 failure. This would only send this incorrect roll information to ADI1. Approach queried us about our speed. At this point I remembered that the last controller had assigned 300 KTS. I reported our actual speed of 250 KTS and added power. I also advised Approach that our primary attitude and heading instruments had failed and that we were on the standby systems. I requested radar vectors. ATC issued an altitude change to the jet coming up behind us. He promptly complied. ATC assigned several incremental heading changes to put us on downwind. Once we were wings level on downwind we accurately adjusted both heading systems to the standby compass. After a minute of wings level flight on downwind both AI's also crosschecked wings level with the standby ADI and outside references. I switched to FD2 and engaged the autopilot. We monitored the systems closely. The remainder of the flight was uneventful. Maintenance found no discrepancy but the subsequent flight experienced a loss of PFD1 at 300 FT on final approach. That one cleared at touchdown and resulted in replacement of AHRS1. The autopilot and pilot flying's instruments shutting off just before level off with several messages to sort through. A marked difference between the remaining instruments; I think we all did our best under the circumstances. In 30 years as a pilot this is the first 'dual ADI failure' I have had; if you can call it that. I am not sure why AD2 was off slightly but the equipment proved its ability to in flight align. The only thing I would bring up is that the QRH is incomplete. It does not include the in flight alignment procedure described in the PRM. Good luck making that happen. In the mean time I hope the detailed info in this report of a successful in flight alignment will be shared with my fellow RJ pilots.
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.