Date: 201603
Local time of day: 0601-1200
Location: ZKC.ARTCC, KS
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZKC
ATC / advisory: Center ZKC
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Time Pressure; Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic
Contributing factors: Airspace Structure; Staffing; Weather; Environment - Non Weather Related
Primary problem: Environment - Non Weather Related

Narrative: I ran to the sector to plug in and assist from the tracker position. After assuming the seated position; I started highlighting call signs of aircraft that were on frequency. About 4 minutes into that; I heard from across the room 'watch those 34's' I asked which '34's' and saw [Aircraft X] 2 seconds before the conflict alert activated with [Aircraft Y]. I suggested a 30 degree left turn and descent to 32;000 feet to get [Aircraft Y] away from [Aircraft X]; with another aircraft passing off the right of [Aircraft Y] at 33;000 feet. Radar controller turned Aircraft Y right to heading 340 to try to put [Aircraft Y] behind the [Following aircraft]. With wind out of the south; [Aircraft Y] picked up some speed. By the naked eye; I thought [Aircraft Y] never entered the 5 mile polygon fully indicating lost separation. The sector was already saturated to the point of unworkable by the time I sat down to track. I was informed that Traffic Management Unit (TMU) for aircraft to be routed around ARTCC airspace as we had moderate to severe turbulence reported at numerous altitudes; and severe thunderstorms. It appeared that no aircraft were routed around; and the aircraft deviating for the weather all ended up in the sector at the same time. I was too busy to see how many aircraft were on frequency at the same time; but with EVERY aircraft asking about the rides and constantly asking for different altitudes; it would have been impossible to work by anybody! Couple this non-routing around us with the fact that the routes that 90% of the aircraft were on were wrong. A lot of fixing was involved and very little preplanning by TMU; System Command Center; and sectors east of us. It is a miracle that no aircraft had RA's during this time. Had I been working radar at this sector; before it got busy; I would have reached out to other sectors and have them route traffic north of the sector airspace. This would have alleviated all the choke points and numerous crossing traffic at the same altitudes. If they didn't want to comply; they would have held aircraft until they complied.When System Command Center is asked to reroute aircraft around the airspace for weather and sever or worse turbulence; they should really do it! Controllers make it work. TMU and System Command Center should suggests helpful solutions instead of turning controllers down. Who has final say at the sector? Controllers. Heed what controllers say.




Synopsis: ZKC ARTCC sector requested an aircraft be routed around its airspace due to weather and traffic saturation deviating for the weather. The request was denied. An aircraft was issued a vector to avoid another aircraft but the vector was not enough to maintain required lateral separation.