Narrative:

While working atop sectors 87; 88; 89; 90 I received my position relief briefing; the relieving controller made me aware of a surface to unlimited missile shot block in our airspace. I sat down and immediately called ZMA center to coordinate aircraft X; and aircraft Y on L453. They told me we had a sfc to unlimited block and they couldn't accept the aircraft. I said we were aware of the block and were protecting for it. He stated not if they are on L453 you are not. I told him I would call him back. I picked up the paper copy of the map and noticed that the splash down portion of the surface to unlimited block was not loaded into the atop. Normally this is done by our local military office. By this point it was XX00Z. The block was to go active at XX05Z. Based upon my guess the aircraft were still north of the airspace that was supposed to have been protected. I immediately rerouted the aircraft over to the next airway L454. I was very busy during this time; and the reroutes were compounded by weather further to the south on L454. Once I received read backs of the reroutes I went to the omic desk and notified the midnight omic of the situation. He told me he was not sure what happened and they would get it loaded. I then went back to my sectors and loaded two of my own airspace blocks to protect what I thought was the missile shot airspace until the omic could get the airspace loaded. I was simply too busy with weather deviations and volume to do it myself. After what seemed to be much longer then necessary the omic came to my sector and told me he didn't add the airspace as he saw I had already done it. I told him I loaded two very crude and over protective blocks just so we were covered until he had it in. He told me he was unable to load it as the block had too many points. (This made absolutely zero sense to me. Atop is designed to take airspace blocks with numerous points.) another midnight omic was also on the shift; but I am not sure if assistance was offered with this or not. Finally the omic had an area F controller and former atop sme load the block. Area F controller called me and advised me he had the block loaded and to look at it as the previously rerouted aircraft X and aircraft Y flights were flashing with it (indicating improper separation) as well as another flight. They were out of the airspace; but were in the buffer. Aircraft X would be out of the airspace before a reroute could be issued. So I rerouted aircraft Y and the other flight further east. I recommend that whoever is responsible to load these airspace blocks make sure their job is done properly. This simple mistake put three aircraft in a very serious situation. It also put me in an incredibly stressful and difficult situation. I recommend that midnight omic's be competent on atop enough to load an airspace block. This is not the first time this has been an issue. Normally they cannot load sigmets we just help them with it.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZNY Controller describes a situation where restricted airspace was not depicted on his scope and aircraft were routed to go through this airspace. Restricted airspace was eventually depicted on scope and aircraft were re-routed.

Narrative: While working ATOP Sectors 87; 88; 89; 90 I received my position relief briefing; the relieving controller made me aware of a surface to unlimited missile shot block in our airspace. I sat down and immediately called ZMA center to coordinate Aircraft X; and Aircraft Y on L453. They told me we had a SFC to unlimited block and they couldn't accept the aircraft. I said we were aware of the block and were protecting for it. He stated not if they are on L453 you are not. I told him I would call him back. I picked up the paper copy of the map and noticed that the splash down portion of the surface to unlimited block was not loaded into the ATOP. Normally this is done by our local military office. By this point it was XX00Z. The block was to go active at XX05Z. Based upon my guess the aircraft were still north of the airspace that was supposed to have been protected. I immediately rerouted the aircraft over to the next airway L454. I was very busy during this time; and the reroutes were compounded by weather further to the south on L454. Once I received read backs of the reroutes I went to the OMIC desk and notified the Midnight OMIC of the situation. He told me he was not sure what happened and they would get it loaded. I then went back to my sectors and loaded two of my own airspace blocks to protect what I thought was the missile shot airspace until the OMIC could get the airspace loaded. I was simply too busy with weather deviations and volume to do it myself. After what seemed to be much longer then necessary the OMIC came to my sector and told me he didn't add the airspace as he saw I had already done it. I told him I loaded two very crude and over protective blocks just so we were covered until he had it in. He told me he was unable to load it as the block had too many points. (This made absolutely zero sense to me. ATOP is designed to take airspace blocks with numerous points.) Another midnight OMIC was also on the shift; but I am not sure if assistance was offered with this or not. Finally the OMIC had an Area F controller and former ATOP SME load the block. Area F controller called me and advised me he had the block loaded and to look at it as the previously rerouted Aircraft X and Aircraft Y flights were flashing with it (indicating improper separation) as well as another flight. They were out of the airspace; but were in the buffer. Aircraft X would be out of the airspace before a reroute could be issued. So I rerouted Aircraft Y and the other flight further east. I recommend that whoever is responsible to load these airspace blocks make sure their job is done properly. This simple mistake put three aircraft in a very serious situation. It also put me in an incredibly stressful and difficult situation. I recommend that midnight OMIC's be competent on ATOP enough to load an airspace block. This is not the first time this has been an issue. Normally they cannot load SIGMETS we just help them with it.

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.