Narrative:

I de-combined sectors and received aircraft X. Under the new implementation of stars; when a sector is decombined; restricted areas show inactive on a local geography display regardless of its actual status. I was unaware that when a position is decombined that a supervisor must run a new macro to show the correct status of the restricted area.this was not done and the restricted area showed inactive above 3;000 feet on the decombined scope only. Not being aware of this issue; I put aircraft X on a vector at 8;000 feet through the restricted area that I believed was not active. The receiving controller had the correct local geography display on his scope showing it was active and advised me. I issued an immediate turn to the aircraft and the aircraft went about a mile into the restricted area in his turn. The status of this deficiency in the latest stars implementation has not been disseminated to all controllers and after this event I was told this is a known issue and the same type of event has occurred more than onceeven though I am told the problem will be fixed in the next implementation; it still needs to be disseminated to the controllers so they are aware that the local geography display on their scope may be incorrect if a new macro has not been run concurrent with decombining a position.

Related reports:

Google
 

Original NASA ASRS Text

Title: PCT Supervisor reported failing to not make the correct system macro entries after de-combining a sector. The Restricted Area status displayed not in use on the Controller's radar display when it was actually in use. The Controller allowed an aircraft to enter the Restricted Area.

Narrative: I de-combined sectors and received Aircraft X. Under the new implementation of STARS; when a sector is decombined; restricted areas show inactive on a local geography display regardless of its actual status. I was unaware that when a position is decombined that a supervisor must run a new macro to show the correct status of the restricted area.This was not done and the restricted area showed inactive above 3;000 feet on the decombined scope only. Not being aware of this issue; I put Aircraft X on a vector at 8;000 feet through the restricted area that I believed was not active. The receiving controller had the correct local geography display on his scope showing it was active and advised me. I issued an immediate turn to the aircraft and the aircraft went about a mile into the restricted area in his turn. The status of this deficiency in the latest STARS implementation has not been disseminated to all controllers and after this event I was told this is a known issue and the same type of event has occurred more than onceEven though I am told the problem will be fixed in the next implementation; it still needs to be disseminated to the controllers so they are aware that the local geography display on their scope may be incorrect if a new macro has not been run concurrent with decombining a position.

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