Date: 201201
Local time of day: 1201-1800
Location: ZLC.ARTCC, UT
Aircraft: B737-800
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZLC
ATC / advisory: Center ZLC
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Airspace Violation All Types
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: ATC Equipment / Nav Facility / Buildings; Human Factors
Primary problem: Human Factors

Narrative: Aircraft X was Westbound landing SFO level at 30;000 FT; I had been getting a lot of bad ride reports and aircraft changing altitudes both up and down which is unusual for this sector.  I did not have the ACL (Aircraft List) in the URET (User Request Evaluation Tool) displayed as I don't normally pay that much attention to it anyway because often times it doesn't always give an accurate depiction of traffic.  I had verified the Reveille airspace about 30 minutes prior to the incident and don't know for how long the airspace had been active when the aircraft violated the airspace.  When I was relieved from the sector the aircraft was clear of the airspace with a vector.  The airspace had gone hot and I failed to recognize that Aircraft X was at an altitude that would violate the airspace.  Also; there had not been a line drawn on the scope for the Northern border of the Reveille airspace which is missing from the display because of ERAM limitations from the last drop.  I believe that the amount of ride reports and coordination involved in moving aircraft up and down for the bad rides played a factor in this incident; also the fact that Reveille does not show the Northern boundary may have been a causal factor along with me not having the ACL pulled up on the URET.  I did look at the URET display after I recognized the situation and it did show the aircraft was entering the airspace; I don't know if this would have made any difference or if I would have looked at that if it was displayed either way.  Recommendations: 1. Probably should always have the ACL display up-whether this would prevent the incident or not depends on how much one looks at the URET.  2. Possibly either a reminder call or similar reminder especially for the sector directly overseeing the airspace maybe 5 minutes before the airspace goes active.  3. As far as I know; the airspace indicator on the scope does not display until the airspace actually represents active but I'm not positive.  There is no advance warning for the airspace.  Possibly add a 15 minute buffer for the airspace so the red outline indicating hot airspace before the airspace actually goes hot.  4. Displays of the map that the controller is using should be accurate when they are presented to the control floor; there should not be lines missing or lines charted in the wrong places.  These should be accurate before being used on the floor.




Synopsis: ZLC Controller described an unauthorized airspace entry event; the reporter listing airspace map anomalies; airspace notification procedures and failure to use ERUT ACL functions as causal factors in the incident.