No Aircraft
Air Traffic Control Fully Certified
Communication Breakdown
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; Airspace Structure; ATC Equipment / Nav Facility / Buildings; Procedure
I was asked to take the TMML/MOS position and training; specifically for the late night changeover. We discussed a couple of tasks and duties regarding the position and performing the changeover that we do on a daily basis. We logged into the scheduling website (SAMS) and we began to approve the schedule requests for the [next two] days. After approving all pertinent schedules; we then moved to the MAST (Military Airspace Scheduling Tool) and ultimately printed out the sheet. My trainee was accomplishing this at a steady pace and we also had additional steps to take due to a new MAST under trial at this time. My trainee started to input the schedules into our URET; and then recognized that R5107B airspace was not active and the sheet stated that it should be active currently. We then revisited the SAMS website to check status of R5107B and found that the SAMS site stated that R5107B was active. I then informed my STMC; and ultimately; the supervisors in those affected areas/operations manager were informed. We activated the airspace for the remainder of the time requested. After some research; we found out that the airspace requested (R5107B) was created in SAMS. The airspace went active. No phone call from the scheduling agency was made to the MOS position; even though normally when add-on/amendment is made in SAMS we receive a call/heads up to ensure everyone is aware of the pending change. Our Operations Manager stated that numerous aircraft traversed this restricted airspace that was supposed to be shown active. Ultimately; an agency not giving the MOS a phone call and submitting a request only 61 minutes prior to activation of the airspace is unsatisfactory; to say the least; thankfully; no known incidents/accidents due to airspace encroachment. Although there are several LOAs and rules set up for prior notice and recall time needed; I believe that there should be at least a 3 hour notice of any changes/add ons made in SAMS; or a phone call made to the MOS position if within that period of time and a request is made. Also; if the airspace request has not been 'approved' by MOS; coordination with TMU needs to be made prior to activating/use of the requested airspace.
ZAB TMU Controller voiced concern regarding notification procedures on restricted airspace activation; noting that several aircraft transversed restricted airspace because of flawed equipment and procedures.