Date: 201706
Local time of day: 1201-1800
Location: ZNY.ARTCC, NY
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Airspace: Class A ZNY
ATC / advisory: TRACON PHL
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Communication Breakdown; Confusion
Second reporter function: Enroute
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Human Factors; Weather; Procedure
Primary problem: Weather

Narrative: Aircraft deviating for weather over CMK opposite direction traffic on top of normal flow at sector 56. This was working in the beginning because it was limited traffic. ZBW called the supervisor's desk to coordinate what they were already doing. When the CIC asked me; my response was 'that is exactly what they have been doing'. As the traffic picked up and weather moved further east adding to the deviations by all aircraft; it became unsustainable. On top of deviations; reroutes needed to be issued; and climb/descend opposite direction to meet restrictions. An inexperienced Controller did what they could to the best of their ability; new Controller in Charge (CIC) didn't know what was happening until it was too late; and Traffic Management Unit (TMU) was unaware of the entire situation. I could've stopped the traffic earlier or realized something wasn't right when ZBW called to coordinate what they were doing; TMU could've been monitoring the situation; CIC could've monitored situation and replaced inexperienced Controller with an experienced one


Second narrative: A lot was going on due to weather and deviations. This report is associated with the report filed yesterday. Aircraft X; departure off PHL routed over CMK (where all the weather was) was allowed to depart into known weather that no aircraft would go near. I had little room to vector away from aircraft descending into BOS. On top of deviations adding to workload; this was unnecessary. Aircraft Y deviating around weather and BDR when able (believe they were supposed to advise when back on course). Aircraft Y seemed to be heading on an easterly heading. Seeing this; I thought I could turn the Aircraft Z to the north and descend. As soon as I issued the clearance; I noticed Aircraft Y was back on course. I climbed Aircraft Z back up to FL320 and Aircraft Y responded to a TCAS RA and descend.Not realizing B31 was spinning Aircraft A deep in my airspace; when Aircraft B asked for a descent; I started him down and gave the crossing restriction. As soon as Aircraft B started the descent I noticed that Aircraft A was turning toward Aircraft B.I was beyond overwhelmed with amount of traffic and not knowing exactly where the aircraft were going since most were deviating. The constant questions about the weather and rides clogging the frequency added to this. Having to issue normal reroutes didn't help the situation.Not allowing all traffic to deviate and go back on course opposite direction of the normal traffic. Make sure the supervisor/Controller in Charge (CIC) is aware of what is going on. Have an experienced RA working the position. Find it hard to believe TMU had no clue what was going on since the weather was affecting ZNY traffic; but ensure the supervisor/CIC bring the situation to their attention.


Synopsis: New York Center Controllers reported that aircraft were deviating due to weather and the sector was not controlled with aircraft turning into each other.