 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Erj-190 flight crew reported two track deviations resulted when the FMS did not perform as expected.
| Attributes | |
| ACN | 1351139 |
| Time | |
| Date | 201604 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | LGA.Airport |
| State Reference | NY |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | EMB ERJ 190/195 ER/LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR HAARP3 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Not Flying |
| Person 2 | |
| Function | Pilot Flying First Officer |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
Issue with FMS malfunction on the HAARP3 RNAV arrival. FMS system missed bayse intersection by over 5 miles. I noticed that it was turning early and thought that it was 'smart turning' because of the winds. I did notice something different that day in the way the information was being displayed. It showed the aircraft not flying over bayse; it did make the 8;000 feet crossing restriction; however; the FMS was showing 2 active legs at the same time. It was showing basye and haarp as active legs. Upon arrival; ground control said for us to contact approach control on the phone. I spoke to [the] manager at lga approach control. I explained to him that we thought the FMS was compensating for the winds. [The manager] said that safety was not compromised; however; in the busy airspace over ny; 5 miles is way too much. I spoke to the mechanics in lga. Since we had received no caution or fault messages on the mcdu nor EICAS; they suggested to shut down the plane and restart it. They checked the database of both FMS and it was all correct.however; on the robuc 1 arrival in bos; it did the same thing. As we passed provi intersection; the aircraft turned towards winni and bypassed joody. As in lga; it showed two active way points in magenta. We ended up getting vectors to final. The FMS missed joody by 2.6 miles.I made an aircraft maintenance log (aml) entry with as much information as possible and spoke to the mechanic in bos that showed up to do a daily inspection.
Original NASA ASRS Text
Title: ERJ-190 flight crew reported two track deviations resulted when the FMS did not perform as expected.
Narrative: Issue with FMS malfunction on the HAARP3 RNAV Arrival. FMS system missed BAYSE intersection by over 5 miles. I noticed that it was turning early and thought that it was 'smart turning' because of the winds. I did notice something different that day in the way the information was being displayed. It showed the aircraft not flying over BAYSE; it did make the 8;000 feet crossing restriction; however; the FMS was showing 2 active legs at the same time. It was showing BASYE and HAARP as active legs. Upon arrival; Ground Control said for us to contact approach control on the phone. I spoke to [the] manager at LGA Approach Control. I explained to him that we thought the FMS was compensating for the winds. [The manager] said that safety was not compromised; however; in the busy airspace over NY; 5 miles is way too much. I spoke to the mechanics in LGA. Since we had received no caution or fault messages on the MCDU nor EICAS; they suggested to shut down the plane and restart it. They checked the database of both FMS and it was all correct.However; on the ROBUC 1 Arrival in BOS; it did the same thing. As we passed PROVI intersection; the aircraft turned towards WINNI and bypassed JOODY. As in LGA; it showed two active way points in magenta. We ended up getting vectors to final. The FMS missed JOODY by 2.6 miles.I made an Aircraft Maintenance Log (AML) entry with as much information as possible and spoke to the mechanic in BOS that showed up to do a daily inspection.
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.