Narrative:

Military special use airspace can be scheduled by different user's facilities. Today one facility sent the mos (military operations specialist) an email 1 month prior scheduling it and another facility scheduled the same airspace yesterday. When we entered the airspace notams into the system; a conflict alert was generated and apparently some work was done by the swing shift yesterday to track down the problem. However they were unable to locate the email from a month prior and assumed it was entered into the system in error. They cancelled the first request and entered the second request into the schedule. The first facility was unaware their schedule was removed and thought they still had the airspace scheduled. It wasn't until this morning that a center oceanic sector noticed the discrepancy and hour before the events and questioned who actually was going to have the airspace. Fortunately we were able to notify the users and cancel one of the missions in time; however this was lucky and was a potentially very dangerous situation.the way warning area schedules are sent to the mos is confusing and inconsistent. We should only receive airspace activation from one entity and only on the day prior. Because the schedules come in different formats and at different times; it is hard (if not impossible) to track and catch errors. Furthermore it should not be the role of the mos to catch and referee scheduling errors especially since center is not the scheduling agency for this airspace. At a minimum consistent forms should be used for all airspace schedules (which would help the mos catch any errors) and ideally we should only receive the schedule from nawc [naval air war center] along with the other daily airspace schedules we receive from them.

Related reports:

Google
 

Original NASA ASRS Text

Title: Center Traffic Management Specialist reported two different agencies had scheduled the same Warning Area at the same time.

Narrative: Military Special Use airspace can be scheduled by different user's facilities. Today one facility sent the MOS (Military Operations Specialist) an email 1 month prior scheduling it and another facility scheduled the same airspace yesterday. When we entered the airspace NOTAMs into the system; a conflict alert was generated and apparently some work was done by the swing shift yesterday to track down the problem. However they were unable to locate the email from a month prior and assumed it was entered into the system in error. They cancelled the first request and entered the second request into the schedule. The first facility was unaware their schedule was removed and thought they still had the airspace scheduled. It wasn't until this morning that a Center Oceanic sector noticed the discrepancy and hour before the events and questioned who actually was going to have the airspace. Fortunately we were able to notify the users and cancel one of the missions in time; however this was lucky and was a potentially very dangerous situation.The way Warning Area schedules are sent to the MOS is confusing and inconsistent. We should only receive airspace activation from one entity and only on the day prior. Because the schedules come in different formats and at different times; it is hard (if not impossible) to track and catch errors. Furthermore it should not be the role of the MOS to catch and referee scheduling errors especially since Center is not the scheduling agency for this airspace. At a minimum consistent forms should be used for all airspace schedules (which would help the MOS catch any errors) and ideally we should only receive the schedule from NAWC [Naval Air War Center] along with the other daily airspace schedules we receive from them.

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.