Narrative:

Both ZMP and ZAU are operating on the eram flight processing computer. The flight plan ZMP cleared acft X was cad..lot. Lot is a chicago satellite airport. Acft X was 20N of the ZMP/ZAU boundary when the flight was handed off to chicago. Upon hand off acceptance at ZAU; ZAU eram sent back its own flight plan on the aircraft which ZMP then displayed at the ZMP sector. The ZAU route included pref routing and passed it back to ZMP as though the controller at ZAU issued it. The ZAU flight plan was cad..oxi..lot.ZMP flight plan: cad..lot ZAU flight plan: cad..oxi..lot. I was training the D side controller who was using the route display on the radar scope to judge whether to point the flight out. The route display did not match the flight track of acft X; so the r-side questioned acft X about the route. Pilot said they were going direct lot; (as cleared); but the eram showed them going direct oxi. The d-side coordinated acft X direct lot with ZAU to resolve any confusion. The incorrect route and route display lead the ZMP controller; who is actively controlling the flight; to think the flight was doing something entirely different and may contribute to an operational error or deviation. Recommendation; upon investigation; eram aims issue a software engineering fix to address this and other similar situations. It has been marked 'critical' by several facilities and is not scheduled to be released in the near future. The situation discribed above mostly occurs in the summer with the summer vacation traffic from northern michigan to the chicago area between ZAU eram and ZMP eram. A more urgent and dangerous situation with this will occur when ZOB starts running on their eram [winter] system. ZMP sectors tvc and pln lo meet ZOB fnt and lan lo sectors on a conical boundary. This same situation that is occurring with flights from northern michigan to chicago will also occur with ZOB on the northern michigan to detroit flights. With the shape of the ZMP/ZOB boundary and sectors; the ZOB eram passing back a different flight plan to ZMP sectors will contribute to increased operational deviations and possible operational errors.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMP Controller voiced concern regarding the functionality of the ERAM equipment processing flight plan information.

Narrative: Both ZMP and ZAU are operating on the ERAM flight processing computer. The flight plan ZMP cleared acft X was CAD..LOT. LOT is a Chicago satellite airport. Acft X was 20N of the ZMP/ZAU boundary when the flight was handed off to Chicago. Upon hand off acceptance at ZAU; ZAU ERAM sent back its own flight plan on the aircraft which ZMP then displayed at the ZMP Sector. The ZAU route included Pref Routing and passed it back to ZMP as though the Controller at ZAU issued it. The ZAU flight plan was CAD..OXI..LOT.ZMP flight plan: CAD..LOT ZAU flight plan: CAD..OXI..LOT. I was training the D Side Controller who was using the route display on the RADAR scope to judge whether to point the flight out. The route display did not match the flight track of acft X; so the R-Side questioned acft X about the route. Pilot said they were going direct LOT; (as cleared); but the ERAM showed them going direct OXI. The D-Side coordinated acft X direct LOT with ZAU to resolve any confusion. The incorrect Route and Route Display lead the ZMP Controller; who is actively controlling the flight; to think the flight was doing something entirely different and may contribute to an Operational Error or Deviation. Recommendation; upon investigation; ERAM AIMS issue a software engineering fix to address this and other similar situations. It has been marked 'Critical' by several facilities and is NOT scheduled to be released in the near future. The situation discribed above mostly occurs in the summer with the summer vacation traffic from Northern Michigan to the Chicago area between ZAU ERAM and ZMP ERAM. A more urgent and dangerous situation with this will occur when ZOB starts running on their ERAM [Winter] system. ZMP sectors TVC and PLN LO meet ZOB FNT and LAN Lo sectors on a conical boundary. This same situation that is occurring with flights from Northern Michigan to Chicago will also occur with ZOB on the Northern Michigan to Detroit flights. With the shape of the ZMP/ZOB Boundary and sectors; the ZOB ERAM passing back a different flight plan to ZMP sectors will contribute to increased Operational Deviations and possible Operational Errors.

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.