Narrative:

On flight from ewr our FMS treated newel intersection as a flyover waypoint. We were assigned newel J60 psb and the FMS did not lead the turn prior to newel. When I programmed the EWR2 departure off 22R at the gate the FMS put in newel sax newel. I tried deleting the first newel intersection; but the FMS would not allow that. I deleted the second newel and the sax intersection and then manually entered the sax intersection prior to newel. At no point was newel showing as a flyover waypoint in the FMS. Once airborne new york departure gave us direct to newel intersection. We entered that and the aircraft headed to newel as normal. I was the nonflying pilot; so it wasn't until we were right at newel that I noticed the FMS did not lead the turn to join J60. The FMS did not show newel as a flyover waypoint; but it treated it as such. As the FMS turned the aircraft right over newel; ATC asked if we were in the turn to join J60. I told them we were proceeding to gynts intersection from newel. Once on the ground [at destination] I put the FMS to ewr and re-entered the EWR2 departure off 22R to make sure I hadn't missed the FMS designating newel as a flyover point. This is not the first time I have seen this kind of anomaly where the FMS randomly treats a point as a flyover waypoint without any indication of it in the FMS. The honeywell FMS in the ERJ145 has some quirks that appear to be increasing and creates a large threat. Even when it does work the concern is when it will do something unusual. Never trust the FMS.

Related reports:

Google
 

Original NASA ASRS Text

Title: EMB-145 Captain reported ATC clearance deviation due to malfunctioning FMS providing inaccurate navigation information.

Narrative: On flight from EWR our FMS treated NEWEL intersection as a flyover waypoint. We were assigned NEWEL J60 PSB and the FMS did not lead the turn prior to NEWEL. When I programmed the EWR2 Departure off 22R at the gate the FMS put in NEWEL SAX NEWEL. I tried deleting the first NEWEL intersection; but the FMS would not allow that. I deleted the second NEWEL and the SAX intersection and then manually entered the SAX intersection prior to NEWEL. At no point was NEWEL showing as a flyover waypoint in the FMS. Once airborne New York Departure gave us direct to NEWEL intersection. We entered that and the aircraft headed to NEWEL as normal. I was the nonflying pilot; so it wasn't until we were right at NEWEL that I noticed the FMS did not lead the turn to join J60. The FMS did not show NEWEL as a flyover waypoint; but it treated it as such. As the FMS turned the aircraft right over NEWEL; ATC asked if we were in the turn to join J60. I told them we were proceeding to GYNTS intersection from NEWEL. Once on the ground [at destination] I put the FMS to EWR and re-entered the EWR2 Departure off 22R to make sure I hadn't missed the FMS designating NEWEL as a flyover point. This is not the first time I have seen this kind of anomaly where the FMS randomly treats a point as a flyover waypoint without any indication of it in the FMS. The Honeywell FMS in the ERJ145 has some quirks that appear to be increasing and creates a large threat. Even when it does work the concern is when it will do something unusual. Never trust the FMS.

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.