Narrative:

Through the weekend the military was working in W174. This was apparently a mission with a name and frequencies and a controlling agency but we had no information on it; and neither did the military operations specialist (mos). The problem arose the first time we worked it; when we had no idea that it had a controlling agency. We cleared aircraft into W174 and capped them at FL280 for traffic; but the aircraft went to the controlling agency frequency when they entered the airspace; and they didn't know they were capped and thought they owned to FL350. Thankfully; we discovered the situation and acted to correct it before a problem arose. Later that evening the controlling agency ceased operations without informing us; and the aircraft came out to operate in the airspace with us (miami ARTCC) acting as the controlling agency. I did not personally observe; but heard that at another time during the shift an aircraft was cleared into airspace that already had a fighter operating in it. The next day we were informed by the mos that the airspace would be active. The controllers were informed; and showed the airspace hot. Three fighters came off looking to enter W174. We called the controlling agency but they were not controlling the airspace. The controllers at the sector asked who was controlling the airspace; and I called the mos for clarification. We ended up clearing the aircraft in and acting as the controlling agency; but the situation was confused and caused disruption to the sector and even the area's operations. Missions operating in miami ARTCC airspace should be pre-coordinated with the facility and the area affected. Paperwork should exist which spells out when the operation is expected to take place and who the controlling agency is. Flexibility is possible within defined parameters; but no activity should be allowed to take place without a clear procedure.

Google
 

Original NASA ASRS Text

Title: ZMA Controller described a very confused operational event involving military airspace including the coordination with the controlling agency; noting the lack of coordination within the facility referencing these types of operations.

Narrative: Through the weekend the Military was working in W174. This was apparently a mission with a name and frequencies and a controlling agency but we had no information on it; and neither did the Military Operations Specialist (MOS). The problem arose the first time we worked it; when we had no idea that it had a controlling agency. We cleared aircraft into W174 and capped them at FL280 for traffic; but the aircraft went to the controlling agency frequency when they entered the airspace; and they didn't know they were capped and thought they owned to FL350. Thankfully; we discovered the situation and acted to correct it before a problem arose. Later that evening the controlling agency ceased operations without informing us; and the aircraft came out to operate in the airspace with us (Miami ARTCC) acting as the controlling agency. I did not personally observe; but heard that at another time during the shift an aircraft was cleared into airspace that already had a fighter operating in it. The next day we were informed by the MOS that the airspace would be active. The controllers were informed; and showed the airspace hot. Three fighters came off looking to enter W174. We called the controlling agency but they were not controlling the airspace. The controllers at the sector asked who was controlling the airspace; and I called the MOS for clarification. We ended up clearing the aircraft in and acting as the controlling agency; but the situation was confused and caused disruption to the sector and even the area's operations. Missions operating in Miami ARTCC airspace should be pre-coordinated with the facility and the area affected. Paperwork should exist which spells out when the operation is expected to take place and who the controlling agency is. Flexibility is possible within defined parameters; but no activity should be allowed to take place without a clear procedure.

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.