ZLC controller described a near airspace incursion event when 'restricted airspace' was not displaye...

Narrative:

I received a complete relief briefing; and took over the sector. A few minutes later; the F2TH checked on and requested a descent to 170. I called sector 41 and got control of the aircraft; and then pointed out the aircraft to sector 31. I then descended the aircraft to 170. As I observed the aircraft departing out of FL300; I noticed a 300 drawn on the scope in the corner where the mhrc airspace is usually depicted. I realized that the airspace was hot; and issued a climb to FL310 to the F2TH. At the same time that I issued the climb; the controller in charge called out that the paradise airspace; the conflicting airspace described; was cold. I am not sure when the airspace went cold; so I don't know if there was a deviation or not. Eram removes any airspace from your scope if it is not saved in your preference settings regardless of whether it is active or not. We have a local mitigation strategy that says we will depict with the draw tool that the airspace is active. The mitigation strategy was followed; but I feel that because of the timing; I had not yet recognized that the airspace was no longer depicted on my scope when the aircraft asked for the descent. I feel that a safer way of operating; would be for eram to depict active airspace independent of the preference settings.

Original NASA ASRS Text

Title: ZLC Controller described a near airspace incursion event when 'Restricted Airspace' was not displayed because of ERAM personnel setting functionalities; noting facility procedures and equipment operate counter to each other.

Narrative: I received a complete relief briefing; and took over the sector. A few minutes later; the F2TH checked on and requested a descent to 170. I called Sector 41 and got control of the aircraft; and then pointed out the aircraft to Sector 31. I then descended the aircraft to 170. As I observed the aircraft departing out of FL300; I noticed a 300 drawn on the scope in the corner where the MHRC airspace is usually depicted. I realized that the airspace was hot; and issued a climb to FL310 to the F2TH. At the same time that I issued the climb; the CIC called out that the Paradise Airspace; the conflicting airspace described; was cold. I am not sure when the airspace went cold; so I don't know if there was a deviation or not. ERAM removes any airspace from your scope if it is not saved in your preference settings regardless of whether it is active or not. We have a local mitigation strategy that says we will depict with the draw tool that the airspace is active. The mitigation strategy was followed; but I feel that because of the timing; I had not yet recognized that the airspace was no longer depicted on my scope when the aircraft asked for the descent. I feel that a safer way of operating; would be for ERAM to depict active airspace independent of the preference settings.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	918225
Time
Date	201011
Local Time Of Day	1801-2400
Place
Locale Reference	ZLC.ARTCC
State Reference	UT
Aircraft 1
Make Model Name	Falcon 2000
Flight Phase	Descent
Route In Use	None
Flight Plan	IFR
Person 1
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

ZLC controller described a near airspace incursion event when 'restricted airspace' was not displayed because of eram personnel setting functionalities; noting facility procedures and equipment operate counter to each other.