Date: 201604
Local time of day: 1801-2400
Location: ZNY.ARTCC, NY
Weather elements / visibility: Thunderstorm
Light: Dusk
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 129
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZNY
ATC / advisory: Center ZNY
Reporter organization: Government
Reporter function: Enroute; Oceanic
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Situational Awareness; Communication Breakdown
Second reporter function: Oceanic; Enroute
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Requested ATC Assistance / Clarification; General Work Refused; General Flight Cancelled / Delayed; General Release Refused / Aircraft Not Accepted
Contributing factors: Airspace Structure; Procedure; Staffing; Weather; Human Factors
Primary problem: Human Factors

Narrative: I was in the process of relieving a trainee and his trainer off the X Sector when I was told there was an issue with the Y Sector controller already in progress.  I was briefed that the controller who was working at Y Sector was refusing to type in a reroute that had already been issued to the aircraft due to extreme weather deviation at the pilot's request. At the time I had plugged in; the Radar Controller had tried to call Y Sector in an attempt to get the new route coordinated with the controller. By the end of the call Y Sector was uncooperative and the Radar Controller was unable to confirm with him what altitude and routing had been approved; so he held Aircraft X. During this time; I had told the supervisor twice that they needed to get that controller off the Y Sector. He said he couldn't do that at which time the Y Sector Supervisor had walked into our area and I said; yeah but their supervisor can pull him; I don't know what the dialogue was between the two. By this time the aircraft was coming back around; we had gotten a new time for the fix and established with the flight that he would be able to start to work his way toward his original route. I called to coordinate the information with Y Sector. After giving all necessary coordination information Y Sector controller told me 'I'll call you back' at which time I said 'no you won't; I need an approval.'  He said 'Did you hear what I said?? I'LL CALL YOU BACK' to which I said 'Did you hear what I said? I need you to do your job and give me an approval; he has spun once already.'  He hung up on me and I yelled to the supervisor to 'GET HIM OFF POSITION NOW!' I told my Radar Controller to hold the airplane again. As he is explaining to Aircraft X that he has to hold again; the aircraft states that if he holds again; he will be critical fuel. There were 2-3 aircraft that needed communication changes that my Radar Controller was not able to talk to because we were consumed with Aircraft X. Y Sector then calls me back and tries to explain that he had to assume the aircraft because he had flipped over (etc...) takes the coordination; I tell my Radar Controller Aircraft X is good; he sends him direct to the next fix and tells him to call the front desk and file a complaint regarding the poor service.This is not the first report I have filed on this controller and his passive aggressive way of controlling aircraft. He likes to mess with other controllers by messing with the airplanes and that is appalling and unacceptable; and MUST be stopped.  He is unsafe and a danger to the flying public.  There is absolutely no reason for him to have turned down the reroute other than sheer laziness; and/or vendetta against the controller(s) on the other end of the line and it is absolutely inexcusable that management has allowed his antics to get this far. The supervisor in charge of the Y Sector controller should have pulled him off position when he learned what he was doing. This is unacceptable behavior for someone in a management position.


Second narrative: Aircraft X departed headed to [fix]. Weather was impacting sector. Aircraft X requested to deviate to the east which I approved and cleared direct [fix] when able. Maybe 10 minutes goes by and flight said they cannot rejoin at [fix] and was requesting another route farther east. At this point the plane was about 70-80 miles off the original route. I offered direct to a route that would tie back in later. Flight accepted this route and was cleared as such. The flight was originally coordinated over [fix] as normal. Then we called again to coordinate a route change. A new controller sat down at Y Sector and told us he would call back. Y Sector then called back and the Handoff Controller tried to coordinate a present position LAT/LONG direct. Y Sector told him that he didn't want to do that. I am not quite sure why. He instead offered to just put a deviation into ATOP. Which is fine if the plane was still on the original route. I called Y Sector and asked why they couldn't put the new route in and was told it sounded like I didn't know what route the plane was on. I had to hold the plane because at that point I didn't know what route was coordinated 100%. After the Handoff Controller was relieved; the new Handoff Controller had some words and yelling on the line. I eventually re-cleared the flight back on original route with a significant weather deviation clearance to the left. Keep in mind; throughout this entire event; other flights were deviating all over the place headed northbound and I still had to put them 20 miles in trail all while letting them maneuver around weather. Anyway Aircraft X finally left sector unhappy and was given phone number for watch desk to call when they landed.Have more training for ATOP on special circumstances. Do not be lazy and just instantly deny a request from another controller. Have some sort of Area to Area meeting to discuss what seems like false claims for people on both sides. There are what appears to be lots of rumors flying around.


Synopsis: ZNY controllers reported that another Controller refused to accept a handoff on an aircraft. The Controller refused to enter the route amendment for the aircraft into the database.