Narrative:

Restricted area r-abcd had been active for over an hour and a half; from the surface to FL300; without my knowledge! R-abcd went active at XA00Z; and I took over the sector shortly after that time; around XB05Z. I recalled no mention of the restricted area status in the position relief briefing; nor was the restricted area depicted on my scope. It is normally not used much on the weekends; so I did not question it. About an hour and a half later (around XC45Z); another controller asked me if the restricted area was hot. My reply was; 'no.' he said the esis (enhanced status information system) is showing that it went hot at XA00Z. I immediately asked my supervisor and approach control if r-abcd was hot; and they said 'yes.'restricted area was being used for artillery fire from the surface to 30;000 ft. My sector owns from the surface to 23;000 ft. This is a big safety issue. Imagine what could've happened during that hour and a half that it was active without my knowing it. The only way our sector gets notified of the restricted area's status is from a screen on the wall called the esis. It can be written in different formats; the information can be placed in different locations on the screen... It is not the best 'attention-getter' for such a crucial piece of information. Sometimes the supervisor will verbally announce that 'there are restricted area times posted.' and even then; that may be hours in advance; leaving plenty of chances for the error chain to develop. There needs to be a better system for notifying the affected sectors of the restricted area's status. Maybe a required call from approach to center at the time it goes active; to make sure we're on the same page; or a required reminder from the supervisor or tmc coordinator when it goes active (a check and balance system). An even better automated solution would be to have the restricted area; MOA; etc automatically display on your scope when it goes active (or maybe 5 minutes prior). This would require a lot of automation; and would depend on accurate time input on someone's part; but in this day and age; there should be a better system.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZME Controller reported a restricted area within his sector was hot for 90 minutes without his knowledge. Reporter suggests an automation solution.

Narrative: Restricted Area R-ABCD had been active for over an hour and a half; from the surface to FL300; without my knowledge! R-ABCD went active at XA00Z; and I took over the sector shortly after that time; around XB05Z. I recalled no mention of the Restricted Area status in the position relief briefing; nor was the restricted area depicted on my scope. It is normally not used much on the weekends; so I did not question it. About an hour and a half later (around XC45Z); another controller asked me if the restricted area was hot. My reply was; 'No.' He said the ESIS (Enhanced Status Information System) is showing that it went hot at XA00Z. I immediately asked my supervisor and Approach Control if R-ABCD was hot; and they said 'Yes.'Restricted Area was being used for artillery fire from the surface to 30;000 FT. My sector owns from the surface to 23;000 FT. This is a big safety issue. Imagine what could've happened during that hour and a half that it was active without my knowing it. The only way our sector gets notified of the Restricted Area's status is from a screen on the wall called the ESIS. It can be written in different formats; the information can be placed in different locations on the screen... It is not the best 'attention-getter' for such a crucial piece of information. Sometimes the supervisor will verbally announce that 'There are Restricted Area times posted.' And even then; that may be hours in advance; leaving plenty of chances for the error chain to develop. There needs to be a better system for notifying the affected sectors of the Restricted Area's status. Maybe a required call from Approach to Center at the time it goes active; to make sure we're on the same page; or a required reminder from the supervisor or TMC coordinator when it goes active (A check and balance system). An even better automated solution would be to have the Restricted Area; MOA; etc automatically display on your scope when it goes active (or maybe 5 minutes prior). This would require a lot of automation; and would depend on accurate time input on someone's part; but in this day and age; there should be a better system.

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.