ERAM limitations were cited as a problem for a ZSE controller trying to coordinate two flights of two F15's entering his sector.

Date: 2011-11 · Aircraft: Eagle (F-15) · Phase: cruise

Anomalies: atc-issue-all-types

Synopsis

ERAM limitations were cited as a problem for a ZSE controller trying to coordinate two flights of two F15's entering his sector.

Narrative

Sector 13 called to coordinate F15's X/Y and F15's Z/W and associated block altitudes. However; I had NO STRIPS which printed out even though they had just rerouted the aircraft into my sector AND I had NO FLIGHT INFORMATION IN THE ACL LIST. I had Sector 13 calling me to coordinate on aircraft that were to enter my sector in less than about four minutes and I have nothing on the aircraft in the ACL and no strips. It's very difficult to do my job effectively when I have no flight information on aircraft entering my sector in a matter of a couple minutes. This type of anomaly tells me ERAM either doesn't have a clue where the aircraft is at or if it does know where the aircraft is it doesn't know what to do with the information and populate my ACL accordingly. [It is] totally unacceptable to be having this type of anomaly at this stage of the ERAM game. Recommend ERAM be programmed to populate the ACL even if the aircraft has previously left your sector but will be re-entering at a later time. Program the ACL populate time as it would be with any normal flight entering the sector.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.