Narrative:

ZDC was in eram and ZNY is not in eram. Aircraft X flight plan came from ZNY and was flashing at pinion with no fourth line data. The route was bombed out and showed; mol.(XXX)..DIRTY2.katl. The STAR was correctly numbered; we took out the extra pads; we tried a 6/7/10 [flight plan revision]; we tried different fixes on the arrival nothing worked. I asked the pilot if he was RNAV equipped and he said yes. Then a few minutes later he requested the WHINZ3 after mol; he said he was unable the DIRTY2. Coordination was done. This problem happened during a busy push with over 40 aircraft in the [airspace]; and I had a d-side. There was lots of coordination that needed to be done with aircraft; plus another aircraft that had bad preferential (pref) routing I had to fix. After talking with one of the eram leads here at ZDC; it was determined that the pilot had filed his equipment appropriately; which was not pbn approved; however he filed for the DIRTY2 (or at least that's what we showed-not sure). The system (ZNY host and ZDC eram) had allowed the route to be entered even though it was wrong. There was no pref route that kicked out. This created a lot of extra work and coordination during a busy push that should not be necessary just to try to get a proper flight plan.1) the system (host or eram) should not allow a route to be accepted that does not match the equipment. Whatever system the pilot originally filed his route through should have told him he could not fly the DIRTY2.2) it would be helpful to have pref routes for atl show up for ZNY and ZDC so that these problems can be addressed sooner and alleviate any discrepancies. 3) ZDC had a briefing over the last year about equipment codes and such; however; it was a short useless briefing that did not teach us anything; and it was not cohesive. Request more briefings at ZDC on how equipment is handled in eram.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZDC Controller reports of an aircraft route issue and possible problem related to ERAM vs Host.

Narrative: ZDC was in ERAM and ZNY is not in ERAM. Aircraft X flight plan came from ZNY and was flashing at Pinion with no fourth line data. The route was bombed out and showed; MOL.(XXX)..DIRTY2.KATL. The STAR was correctly numbered; we took out the extra pads; we tried a 6/7/10 [flight plan revision]; we tried different fixes on the arrival nothing worked. I asked the pilot if he was RNAV equipped and he said yes. Then a few minutes later he requested the WHINZ3 after MOL; he said he was unable the DIRTY2. Coordination was done. This problem happened during a busy push with over 40 aircraft in the [airspace]; and I had a D-side. There was lots of coordination that needed to be done with aircraft; plus another aircraft that had bad preferential (pref) routing I had to fix. After talking with one of the ERAM leads here at ZDC; it was determined that the pilot had filed his equipment appropriately; which was not PBN approved; however he filed for the DIRTY2 (or at least that's what we showed-not sure). The system (ZNY HOST and ZDC ERAM) had allowed the route to be entered even though it was wrong. There was no pref route that kicked out. This created a lot of extra work and coordination during a busy push that should not be necessary just to try to get a proper flight plan.1) The system (HOST or ERAM) should not allow a route to be accepted that does not match the equipment. Whatever system the pilot originally filed his route through should have told him he could not fly the DIRTY2.2) It would be helpful to have pref routes for ATL show up for ZNY and ZDC so that these problems can be addressed sooner and alleviate any discrepancies. 3) ZDC had a briefing over the last year about equipment codes and such; however; it was a short useless briefing that did not teach us anything; and it was not cohesive. Request more briefings at ZDC on how equipment is handled in ERAM.

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.