Narrative:

Working the worst session I have ever worked here in ZJX; weather was blocking the departure corridor from mco and tpa complexes. All arrivals and departures were opposite direction traffic descending and climbing respectively. All aircraft were crossing on the boundary with sectors 30;17;88;16; and ZMA 08. Immediately prior to first loss of separation 17 told 16 no more departures until DARBS19 procedures go into effect. DARBD19 is not possible with active W470; acmi; and nova airspace hot up to FL240 and FL250. The r-side at 16 started turning every departure to 250 headings to miss sector 17. Then sector 30 said no more hand offs or point outs from us because they cannot see data blocks in that area. The R16 turned departures southbound to miss sector 30. During the southbound heading; an E135 was given a climb to FL270; both R16 and I did not notice the excel at FL270 immediately behind the E135. I may have been coordinating on another line; or maybe I missed it during the mayhem. The excel was supposed to be below FL250 per sops. I tried to coordinate the E135 descending back lower with D88 but they had already descended the excel. Then after that problem separated R16 climbed the E135 and a LR31 to the same altitude. At that point a tracker 16 was trying to get in place to help and conflict alert went off again. Both departures (the E135 and the LR31) made a full 360 degree turn before proceeding on course. Immediately following these situations the tracker 16 called 88 and 14 and shut departures off. There were too many unsafe situations during this period to remember all of them. The sector was out of control. Recommendation; northbound and southbound route/s in this area that are not on a bunch of boundaries. More help from tmu and military areas. W470 should not have been hot; we needed DARBS19 procedures along with more organized routes and ground stops to mco and tpa complexes.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZJX Controller described possible multiple loss of separation events when inbound and outbound traffic was routed in opposite direction/s due to significant weather impacts; noting both Traffic Management and the Military; i.e. 'release of airspace;' could have assisted in this scenario.

Narrative: Working the worst session I have ever worked here in ZJX; weather was blocking the departure corridor from MCO and TPA complexes. All arrivals and departures were opposite direction traffic descending and climbing respectively. All aircraft were crossing on the boundary with Sectors 30;17;88;16; and ZMA 08. Immediately prior to first loss of separation 17 told 16 no more departures until DARBS19 procedures go into effect. DARBD19 is not possible with active W470; ACMI; and NOVA airspace hot up to FL240 and FL250. The R-Side at 16 started turning every departure to 250 headings to miss Sector 17. Then Sector 30 said no more hand offs or point outs from us because they cannot see data blocks in that area. The R16 turned departures southbound to miss Sector 30. During the southbound heading; an E135 was given a climb to FL270; both R16 and I did not notice the Excel at FL270 immediately behind the E135. I may have been coordinating on another line; or maybe I missed it during the mayhem. The Excel was supposed to be below FL250 per SOPs. I tried to coordinate the E135 descending back lower with D88 but they had already descended the Excel. Then after that problem separated R16 climbed the E135 and a LR31 to the same altitude. At that point a Tracker 16 was trying to get in place to help and Conflict Alert went off again. Both departures (the E135 and the LR31) made a full 360 degree turn before proceeding on course. Immediately following these situations the Tracker 16 called 88 and 14 and shut departures off. There were too many unsafe situations during this period to remember all of them. The sector was out of control. Recommendation; northbound and southbound route/s in this area that are not on a bunch of boundaries. More help from TMU and Military areas. W470 should not have been hot; we needed DARBS19 procedures along with more organized routes and ground stops to MCO and TPA complexes.

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.