Narrative:

A B737 was coming down the atlantic routes. After he checked in he asked for a short cut to apolo. The warning area was both briefed and listed on our position status board as only being hot to 5;000 ft. I waited several minutes before giving him a short cut to petee direct apolo to join the CWRLD2 arrival. After he was established direct petee; I issued him to cross apolo at 14;000. Before the aircraft got to petee; I was relieved from the position for r-side training. A few minutes later; my d-side informed me that sealord had called to let us know that the aircraft just north of petee had violated their airspace and that the warning areas were indeed hot to 43;000 ft. All of the status information boards in the area were showing the warning areas only hot to 5;000 ft. However; the enhanced status information system (esis) showed the warning airspace active 43;000 ft and below. No one knows when or how the status on the esis was updated. The information on the esis was never passed along to the controllers or the status boards for the positions in the area. Recommendation; there is a problem with the notification process of getting the information from the traffic management unit; tmu; to the sectors. The new process is for tmu to call the area and notify the supervisor and the supervisor notifies the controllers on the positions. Previously; they were required to also send out a gi message to the sectors of the active airspace as well as make the phone call to the supervisor. Things now are being displayed on the esis with no notification to anyone about the information being inputted to the esis. My recommendation is that there needs to be a redundant way to ensure that the controllers have the proper information or tell me how often I need to turn away from my active sector to make sure my status board accurately reflects that information of the esis board.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZMA Controller described an airspace incursion; claiming that the Enhanced Status Information System (ESIS) did not contain the correct airspace information.

Narrative: A B737 was coming down the Atlantic Routes. After he checked in he asked for a short cut to APOLO. The Warning Area was both briefed and listed on our position status board as only being hot to 5;000 FT. I waited several minutes before giving him a short cut to PETEE direct APOLO to join the CWRLD2 arrival. After he was established direct PETEE; I issued him to cross APOLO at 14;000. Before the aircraft got to PETEE; I was relieved from the position for R-Side training. A few minutes later; my D-Side informed me that SEALORD had called to let us know that the aircraft just north of PETEE had violated their airspace and that the warning areas were indeed hot to 43;000 FT. All of the status information boards in the area were showing the warning areas only hot to 5;000 FT. However; the Enhanced Status Information System (ESIS) showed the warning airspace active 43;000 FT and below. No one knows when or how the status on the ESIS was updated. The information on the ESIS was never passed along to the Controllers or the status boards for the positions in the area. Recommendation; there is a problem with the notification process of getting the information from the Traffic Management Unit; TMU; to the sectors. The new process is for TMU to call the area and notify the Supervisor and the Supervisor notifies the Controllers on the positions. Previously; they were required to also send out a GI message to the sectors of the active airspace as well as make the phone call to the Supervisor. Things now are being displayed on the ESIS with no notification to anyone about the information being inputted to the ESIS. My recommendation is that there needs to be a redundant way to ensure that the Controllers have the proper information or tell me how often I need to turn away from my active sector to make sure my status board accurately reflects that information of the ESIS board.

Data retrieved from NASA's ASRS site as of April 2012 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.