Enroute Controller described a loss of separation event during a high volume traffic period complicated by weather factors; the reporter indicating assistance was requested but the supervisor failed to provide same.
Synopsis
Enroute Controller described a loss of separation event during a high volume traffic period complicated by weather factors; the reporter indicating assistance was requested but the supervisor failed to provide same.
Narrative
I was working R20 with a D-Side that had limited RADAR certifications. There was weather in the Northwest and Northeast corners and along the Southern boundary of my airspace. Many; if not all; aircraft were deviating. With the complexity of the aircraft deviating for the weather and the heavy traffic volume the traffic was becoming unmanageable. I asked for a tracker or some form of help at least twice. The supervisor in charge was standing behind me and said; 'you're fine.' I replied; 'no; I'm not.' He continued to stand behind me and watch but did not attempt to get me any help. checked on frequency at FL370. I turned Aircraft X left to go behind Aircraft Z; also level at FL370. By this point the Data Blocks of the 20+ aircraft on my scope were overlapping and I had decreased the range so that I could see better. This; in turn; limited the view of aircraft approaching my airspace. Aircraft Z could not take a left turn due to the weather so I had to turn Aircraft X even further to the left; heading Northwest bound. Aircraft Y was Southeast bound from Denver Center level at FL370. Shortly after Aircraft Y checked on; I turned him right to avoid Aircraft X. The Conflict Alert went off for Aircraft Y and Aircraft X. I turned Aircraft Y further right (twice). I started turning Aircraft X to the right as much as possible to peel him away from Aircraft Y; but couldn't turn him on course yet because of the Aircraft Z. Aircraft X reported he was responding to an RA and was descending. Shortly after that Aircraft X reported level at FL370 again. With all the aircraft involved in this; FL360 and FL380 were not options due to other traffic in the vicinity at those altitudes. There was a loss of separation between Aircraft X and Aircraft Y. I feel like the system; as a whole; broke down. The amount of traffic going into the sector with all the weather deviations should never have been allowed. The TMU should have rerouted aircraft around the sector when the sector was coded red. The Supervisor should have paid more attention to the TSD that predicted the amount of traffic that was going to be in sector and staffed the position appropriately. As the RADAR controller; I should not have had to ask for help (i.e. tracker; reroute aircraft; etc.); but when I did; the supervisor should have immediately paged someone back to be a tracker. The supervisor should have also called TMU and/or adjacent sectors and asked them to reroute some of the aircraft around my sector. The Supervisor also should have put in a D-Side that had a lot more experience. Putting in a D-Side only controller to help in a situation that was so complex and so saturated with traffic was unfair to both the D-Side and the R-Side. If staffing was the issue; the FAA/government needs to figure something out to hire more controllers or use overtime. Any and/or all of those things; would have given me a better chance to ensure the safety and separation of aircraft.
Second reporter narrative
Weather was impacting the sector on both the Northern and Southern boundaries. Sector was constricted and was the only available East-West gap in the weather. Sector was staffed with a CPC working the R-side and a CPCIT working the D-Side. Approximately 15 minutes prior to the incident I informed the STMC that I had concerns about the weather and traffic level in the sector. He acknowledged that the sector was receiving higher than normal trans-continental traffic and saw the weather. He informed me that he didn't think 'it would be too bad'; but volume and complexity built in the sector. I was observing the R-Side Controller; a TMC called to inform me that the sector was alerted. I advised him that I had been observing the sector and had not had time to look at that. He said that the sector was only going to be over for one or two minutes; he didn't think there was anything that he could do at that point but that he would look to move a couple of aircraft. The R-Side Controller issued a vector to Aircraft X for traffic; the turn put that aircraft in confliction with Aircraft Y. After achieving separation between the first two; the R-Side turned the Aircraft X back on course and issued a turn to Aircraft Y; but the turns were not able to achieve separation. Staffing in the area was 10 CPC and 1 CPCIT for the evening shift. Published guidelines in web schedules are 13 CPC for a swing shift; CPCIT are normally not considered part of the staffing when actively training. The weather that impacted the sector was forecasted and built as expected according to the CCFP. Several conversations have occurred over the course of the summer about the need to have a minimum of 11 CPC's assigned to the area on the swing shift; especially when a weather event is forecasted to impact the area. Recommendation: ensure that the Area has 11 CPC on any swing shift that there is weather foretasted to impact the area. The margin of safety with only 10 CPC's during a weather event is not adequate. More aggressive action by both TMU and myself earlier to reduce the volume in the sector.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.