37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1345940 |
Time | |
Date | 201604 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Environment | |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 129 |
Flight Phase | Cruise |
Route In Use | Oceanic |
Flight Plan | IFR |
Person 1 | |
Function | Enroute Oceanic |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
Person 2 | |
Function | Oceanic Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.5 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
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.
Original NASA ASRS Text
Title: 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.
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.
Data retrieved from NASA's ASRS site 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.