 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A319 flight crew had both navigation displays fail on the arrival. The flight crew manually flew the arrival and landed without incident.
| Attributes | |
| ACN | 1702346 |
| Time | |
| Date | 201911 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | ZZZZ.ARTCC |
| State Reference | FO |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR ZZZZ |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | PFD |
| Person 1 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Experience | Flight Crew Last 90 Days 188 Flight Crew Total 17335 Flight Crew Type 529 |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Altitude Overshoot Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Descending via STAR zzzzzx to ZZZZ; VMC conditions; FCU set to sel speed 250 kts; navigation; des; confirmed by FMA's. Just prior to fix ZZZZZ1 approximately 10;000 feet; both captain and first officer nd displays went blank for a few seconds. When displays came back on; it took a few seconds for the map functions to return and for us to figure out that the FCU had reverted out of navigation into heading mode. I manually placed us on a corrective heading and rearmed navigation mode which then engaged and started to track correctly to the RNAV course. We then started cross checking and observed that not only had the navigation mode reverted; but the descent mode had reverted out of managed descent with constraint protections into vertical speed mode; 1800 FPM descending. We caught this at approximately 8;000 feet; shortly after passing fix ZZZZZ1; which has a crossing constraint of 9;000 feet. I disengaged the ap; hand flew and started a level off correction. The next fix was ZZZZZ2 with a constraint of 7;000 feet. We manually set 7;000 feet in the FCU; and set the remaining STAR and app fixes crossing altitudes and air speeds manually. I hand flew the remainder of the STAR and LNAV app runway xx in VMC conditions to an uneventful landing.
Original NASA ASRS Text
Title: A319 flight crew had both navigation displays fail on the arrival. The flight crew manually flew the arrival and landed without incident.
Narrative: Descending via STAR ZZZZZX to ZZZZ; VMC conditions; FCU set to SEL SPD 250 kts; NAV; DES; confirmed by FMA's. Just prior to fix ZZZZZ1 approximately 10;000 feet; both Captain and First Officer ND displays went blank for a few seconds. When displays came back on; it took a few seconds for the map functions to return and for us to figure out that the FCU had reverted out of NAV into HDG mode. I manually placed us on a corrective HDG and rearmed NAV mode which then engaged and started to track correctly to the RNAV course. We then started cross checking and observed that not only had the NAV mode reverted; but the descent mode had reverted out of managed descent with constraint protections into Vertical Speed mode; 1800 FPM descending. We caught this at approximately 8;000 feet; shortly after passing fix ZZZZZ1; which has a crossing constraint of 9;000 feet. I disengaged the AP; hand flew and started a level off correction. The next fix was ZZZZZ2 with a constraint of 7;000 feet. We manually set 7;000 feet in the FCU; and set the remaining STAR and APP fixes crossing altitudes and air speeds manually. I hand flew the remainder of the STAR and LNAV App RWY XX in VMC conditions to an uneventful 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.