Narrative:

I was working the radar position at R11 - brewton sector when I received an inter-phone call; from the eglin missions controller inquiring if I was aware that the eglin east atcaa and restricted areas (R2914-ab; R2915-abc; R2918; R2919-ab) were active up to FL350. I responded that I was only showing it active up to FL300. When I received the call; an air carrier; aircraft X level at FL340; was in the middle of the airspace transiting from east to west on a direct route to aex; which I had issued to the aircraft previously. The previous route of aircraft X would have cleared the airspace in question prior to me clearing the aircraft direct aex. The eglin controller assured me that he had seen the discrete code and everything was ok; but that the airspace was activated up to FL350. I had assumed the position at which time the briefing included information that the airspace was only active up to FL300. When the eglin controller informed me of the issue; I did look at the esis which indeed showed the altitudes of fl240b350; however when I assumed the position the altitudes indicated fl240b300. Apparently there was a change in the altitudes of the airspace that I was not informed of. Had I known of the change in the altitudes I never would have cleared aircraft X direct aex putting the aircraft through restricted areas. I did call the eglin controller back to confirm that the previous altitudes were indeed fl240b300; and he did confirm this but they had a second mission come up which required the higher altitudes.this seems to be an ongoing issue in which airspace activation or changes is not being disseminated from the missions coordinator; through the flm and eventually to the controller/s working the airspace or adjacent airspace. There is obviously a breakdown in communications. My recommendation is to establish a procedure to ensure that once sua is activated and any changes thereof; it is disseminated all the way to the controller involved; be it by verbal; or automated means; but something needs to happen.

Google
 

Original NASA ASRS Text

Title: Center Controller received phone call from Military Facility advising a Restricted Area was hot; up to an altitude the Center Controller was not aware of; thus causing an airspace violation.

Narrative: I was working the Radar position at R11 - Brewton Sector when I received an inter-phone call; from the Eglin Missions Controller inquiring if I was aware that the Eglin E ATCAA and Restricted areas (R2914-AB; R2915-ABC; R2918; R2919-AB) were active up to FL350. I responded that I was only showing it active up to FL300. When I received the call; an air carrier; Aircraft X level at FL340; was in the middle of the airspace transiting from east to west on a direct route to AEX; which I had issued to the aircraft previously. The previous route of Aircraft X would have cleared the airspace in question prior to me clearing the aircraft direct AEX. The Eglin Controller assured me that he had seen the discrete code and everything was OK; but that the airspace was activated up to FL350. I had assumed the position at which time the briefing included information that the airspace was only active up to FL300. When the Eglin Controller informed me of the issue; I did look at the ESIS which indeed showed the altitudes of FL240B350; however when I assumed the position the altitudes indicated FL240B300. Apparently there was a change in the altitudes of the airspace that I was not informed of. Had I known of the change in the altitudes I never would have cleared Aircraft X direct AEX putting the aircraft through Restricted Areas. I did call the Eglin Controller back to confirm that the previous altitudes were indeed FL240B300; and he did confirm this but they had a second mission come up which required the higher altitudes.This seems to be an ongoing issue in which airspace activation or changes is not being disseminated from the Missions Coordinator; through the FLM and eventually to the controller/s working the airspace or adjacent airspace. There is obviously a breakdown in communications. My recommendation is to establish a procedure to ensure that once SUA is activated and any changes thereof; it is disseminated all the way to the Controller involved; be it by verbal; or automated means; but something needs to happen.

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.