Narrative:

Controller on R41 was descending the aircraft into evv. He descending the aircraft over R3702 because he thought only R3702A was active. Controller R42 called to R41 to say that R3702B was also active up to FL220. Controller R41 told me that he just deviated R3702 because we were not showing the airspace active. I went to tmu and inquired about the status of R3702 and they said both a and B were active and that it was briefed in the stand up briefing. However; that information was not changed on the esis board or written down the on the clip board where the flm takes notes during the stand up briefing. During the briefing when I took controller in charge; R3702A was only briefed as being active; by the flm. I talked to the flm in area 6 who is adjacent to our airspace and he was not aware of R3702 being active. He did not remember that being discussed at the stand up briefing. Area also had only R3702A only active on their esis board. R42 was the only person in the building that was showing R3702B as active. Area 1 flm also came down and was unaware of the activity of R3702B. There seems to be a breakdown between tmu putting an update through on the esis and flm's running the areas affected by R3702. I would recommend that they record the stand up briefing in the future so they could see if this information was actually briefed. I am not sure of the procedures in tmu but perhaps they could do a walk through of the areas to check that the esis boards are up to date with the latest information.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZME Controller described a restricted area incursion likely caused by incomplete briefing mechanisms within the operations quarters.

Narrative: Controller on R41 was descending the aircraft into EVV. He descending the aircraft over R3702 because he thought only R3702A was active. Controller R42 called to R41 to say that R3702B was also active up to FL220. Controller R41 told me that he just deviated R3702 because we were not showing the airspace active. I went to TMU and inquired about the status of R3702 and they said both A and B were active and that it was briefed in the stand up briefing. However; that information was not changed on the ESIS board or written down the on the clip board where the FLM takes notes during the Stand Up briefing. During the briefing when I took CIC; R3702A was only briefed as being active; by the FLM. I talked to the FLM in Area 6 who is adjacent to our airspace and he was not aware of R3702 being active. He did not remember that being discussed at the stand up briefing. Area also had only R3702A only active on their ESIS board. R42 was the only person in the building that was showing R3702B as active. Area 1 FLM also came down and was unaware of the activity of R3702B. There seems to be a breakdown between TMU putting an update through on the ESIS and FLM's running the areas affected by R3702. I would recommend that they record the stand up briefing in the future so they could see if this information was actually briefed. I am not sure of the procedures in TMU but perhaps they could do a walk through of the areas to check that the ESIS boards are up to date with the latest information.

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.