Narrative:

I was working the radar position at nepta sector 30. Several aircraft I was working were routed through the W155A and W155B airspace that I was showing inactive until XB00Z (posted on the sia). One of the aircraft; aircraft X; was showing an airspace alert for W155A even though the sia board was showing that W155A wouldn't be active until XB00Z and aircraft X would be clear of the airspace by approximately [50 minutes earlier]. I inquired with the west area supervisor why we were getting early alerts for the airspace. I was relieved off nepta sector 30 and while in the process of assuming the controller in charge position from the west area; the supervisor was told by the missions specialist controller that she had released W155A at or below FL320 early starting at XA00Z. The west area supervisor had no prior request or notice from the mission specialist controller of this time update and informed the mission specialist controller that she was unable to release the W155A airspace before xa+20 due to several aircraft that were currently being worked by sectors 30 and 11 within W155A. The mission specialist controller disregarded the west area supervisor's instructions and allowed the W155A airspace to activate at XA00Z. The stmc came to the west area to inform the west area supervisor and myself that the airspace could not be recalled and it would be activated at XA00Z. The stmc approached the brewton (11) sector to observe the aircraft that were within and about to enter W155A airspace. The brewton controller was distracted from the traffic when he was informed that the airspace was going to be activated within 5 minutes. The nepta controller was continuing to work on the other side of the area without coordination that the times were being updated. The stmc asked the brewton controller to point out the impacted flights to seabreeze control (controlling agency of W155). The brewton controller had to leave the frequencies several times to call the seabreeze controllers and coordinate several pointouts and then coordinate this information with the nepta controller. Both controllers were distracted by this situation and were not able to concentrate on working their sectors. The controllers also had additional workload tasked on them to ensure that the seabreeze controllers were aware of the aircraft that would be transiting through the W155 airspace and quickly ensure that other aircraft they were working were rerouted around it. Neither controller were sure that ZHU sectors were informed in a proper amount of time to reroute around W155A and B. The missions specialist controller and the stmc positions should provide areas proper notice for future sua airspace release requests. The missions specialist controller released ZJX airspace to a military controlling agency without the proper approval from the areas controlling this airspace.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZJX Controller describes a situation where aircraft were in or in close proximity to a warning area and the lack of coordination leading up to the airspace becoming active.

Narrative: I was working the Radar Position at Nepta Sector 30. Several aircraft I was working were routed through the W155A and W155B airspace that I was showing inactive until XB00Z (posted on the SIA). One of the aircraft; Aircraft X; was showing an airspace alert for W155A even though the SIA board was showing that W155A wouldn't be active until XB00Z and Aircraft X would be clear of the airspace by approximately [50 minutes earlier]. I inquired with the West Area supervisor why we were getting early alerts for the airspace. I was relieved off Nepta Sector 30 and while in the process of assuming the CIC position from the West Area; the supervisor was told by the Missions Specialist controller that she had released W155A at or below FL320 early starting at XA00Z. The West Area supervisor had no prior request or notice from the Mission Specialist controller of this time update and informed the Mission Specialist controller that she was unable to release the W155A airspace before XA+20 due to several aircraft that were currently being worked by Sectors 30 and 11 within W155A. The Mission Specialist controller disregarded the West Area supervisor's instructions and allowed the W155A airspace to Activate at XA00Z. The STMC came to the West Area to inform the west area supervisor and myself that the airspace could not be recalled and it would be activated at XA00Z. The STMC approached the Brewton (11) sector to observe the aircraft that were within and about to enter W155A airspace. The Brewton controller was distracted from the traffic when he was informed that the airspace was going to be activated within 5 minutes. The Nepta controller was continuing to work on the other side of the area without coordination that the times were being updated. The STMC asked the Brewton controller to point out the impacted flights to Seabreeze control (controlling agency of W155). The Brewton controller had to leave the frequencies several times to call the Seabreeze controllers and coordinate several pointouts and then coordinate this information with the Nepta controller. Both controllers were distracted by this situation and were not able to concentrate on working their sectors. The controllers also had additional workload tasked on them to ensure that the Seabreeze controllers were aware of the aircraft that would be transiting through the W155 airspace and quickly ensure that other aircraft they were working were rerouted around it. Neither controller were sure that ZHU sectors were informed in a proper amount of time to reroute around W155A and B. The Missions Specialist Controller and the STMC positions should provide areas proper notice for future SUA airspace release requests. The Missions Specialist Controller released ZJX airspace to a military controlling agency without the proper approval from the areas controlling this airspace.

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.