Narrative:

While working R87; I overheard a landline conversation at ocala sector (15) with jax approach that R2903 was active to FL320. The D15 controller called the supervisor on the landline who stated that to his knowledge it was cold; and the controller asked him to verify the status of this airspace with missions sector in tmu. Upon several promptings for a status verification from the D15 controller; with no response from the supervisor; the D15 controller took the initiative to call the missions sector himself. After several minutes it was established that R2903 was in fact active to FL320. Shortly after being relieved from position I proceeded to the missions sector in tmu and inquired as to what time R2903 went active. The missions controller told me it had been active for some time. There may have been several controllers and several aircraft that came into an unsafe proximity or possibly violated this airspace. Additionally; the supervisor's lack of concern and urgency for establishing the status of this airspace is unacceptable. There was a clear breakdown of communication between the missions sector in tmu and the flm's in the gulf area. Without knowing where or how this breakdown occurred; I can't provide recommendations to prevent this from happening again. However; in light of the lack of concern for the status of the airspace and safety of the area; the supervisor needs to be reminded of needed priorities.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZJX Controller voiced concern regarding the lack of timely and accurate information referenced the status of R2903; the reporter listing several communication breakdowns within the facility.

Narrative: While working R87; I overheard a landline conversation at Ocala Sector (15) with JAX Approach that R2903 was active to FL320. The D15 Controller called the Supervisor on the landline who stated that to his knowledge it was cold; and the Controller asked him to verify the status of this airspace with Missions Sector in TMU. Upon several promptings for a status verification from the D15 Controller; with no response from the Supervisor; the D15 Controller took the initiative to call the Missions Sector himself. After several minutes it was established that R2903 was in fact active to FL320. Shortly after being relieved from position I proceeded to the Missions Sector in TMU and inquired as to what time R2903 went active. The Missions Controller told me it had been active for some time. There may have been several controllers and several aircraft that came into an unsafe proximity or possibly violated this airspace. Additionally; the Supervisor's lack of concern and urgency for establishing the status of this airspace is unacceptable. There was a clear breakdown of communication between the Missions Sector in TMU and the FLM's in the Gulf Area. Without knowing where or how this breakdown occurred; I can't provide recommendations to prevent this from happening again. However; in light of the lack of concern for the status of the airspace and safety of the area; the Supervisor needs to be reminded of needed priorities.

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.