Narrative:

I was assigned controller in charge so that that the supervisor could conduct a checkride on a controller who had just reached their minimum training hours a few minutes prior. During the briefing; the supervisor advised me that there were multiple re-routes westbound into sector [xx] and that the sector was going red 'but only up to 19.' the map (monitor alert parameter) value for red for this sector is 16. I asked if anything was being done or traffic slowed to keep aircraft out of the sector and he replied 'no; but it's your desk...' implying that he wasn't doing anything; but I could try. He did keep reiterating that there was heavy volume and complexity at that sector [and] implying he had been aware of this for some time but chose not to take any action. As the briefing was wrapping up; the controller at sector [xx] yelled over the arrival routing 'isn't working anymore...they won't fly through it because the weather.' the supervisor shrugged his shoulders and said the controller in charge 'is in charge now.' I got on the phone with tmu (traffic management unit) and asked for the rerouting. The supervisor tmc (traffic management coordinator) advised me that he had never heard of the reroute; even though this is an official playbook move that we were briefed on traffic management just a week ago. Frustrated; I explained that it keeps traffic out of sector [xx] and I was really just looking for help from him to reduce the volume at the sector since it was going well above its map value. He said he'd look at it and 'oh; by the way; there won't be any more aircraft coming over the arrival routing; they've all been rerouted to keep them clear of that weather you won't see any more'. I said 'ok that's great.'I then was advised by the [xx] controller that another sector was still attempting to hand-off aircraft on the arrival route and deviating. I told the [xx] controller they are not to be routed over that fix and that tmu had advised me those routes would be fixed; not to take the handoff and I would call the other sector's area supervisor. I called the area supervisor and I asked him if they would fix the routes on aircraft X and aircraft Y because tmu had advised no more aircraft over [fix]. The supervisor shouted at me and said that their sector was 'very busy; the sector is red and I have a tracker in there right now so I cannot get them to fix the route'. I advised him that [xx] was red too; and that we needed the route fixed. The supervisor continued to berate me on the line saying his sector was 'so busy and red; with a tracker and d-side' and that he couldn't do it. I then quick-looked their sector and counted 7 data blocks in the sector at the time. A view at the position log and a walk past their area showed that there was no tracker at that sector either. There also wasn't a d-side. I became very disappointed that not only was a delivering area unwilling to help out the request of the receiving controller; but that the supervisor lied to me on a recorded line about how he was staffing his area.traffic management unit should be more proactive to ensure sectors don't go red with excessive volume and aircraft impacted by weather; and supervisors should be more willing to accept/listen to the requests of the receiving controllers vs. Berating them and coming up with excuses for why you can't do it. I believe it was unnecessary for the supervisor to rush to conduct the check ride on the controller who had just gotten their minimum hours a few minutes prior; thus; placing me right into the fire by taking over the desk.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZBW Center Controller in charge reported an adjacent sector was not complying with flow control instructions to regulate traffic flow due to weather deviations.

Narrative: I was assigned Controller in Charge so that that the Supervisor could conduct a checkride on a controller who had just reached their minimum training hours a few minutes prior. During the briefing; the Supervisor advised me that there were multiple re-routes westbound into Sector [xx] and that the sector was going red 'but only up to 19.' The MAP (Monitor Alert Parameter) value for red for this sector is 16. I asked if anything was being done or traffic slowed to keep aircraft out of the sector and he replied 'no; but it's your desk...' implying that he wasn't doing anything; but I could try. He did keep reiterating that there was heavy volume and complexity at that sector [and] implying he had been aware of this for some time but chose not to take any action. As the briefing was wrapping up; the controller at Sector [xx] yelled over the arrival routing 'isn't working anymore...they won't fly through it because the weather.' The Supervisor shrugged his shoulders and said the Controller in Charge 'is in charge now.' I got on the phone with TMU (Traffic Management Unit) and asked for the rerouting. The Supervisor TMC (Traffic Management Coordinator) advised me that he had never heard of the reroute; even though this is an official playbook move that we were briefed on Traffic Management just a week ago. Frustrated; I explained that it keeps traffic out of Sector [xx] and I was really just looking for help from him to reduce the volume at the sector since it was going well above its MAP value. He said he'd look at it and 'oh; by the way; there won't be any more aircraft coming over the arrival routing; they've all been rerouted to keep them clear of that weather you won't see any more'. I said 'ok that's great.'I then was advised by the [xx] controller that another sector was still attempting to hand-off aircraft on the arrival route and deviating. I told the [xx] controller they are not to be routed over that fix and that TMU had advised me those routes would be fixed; not to take the handoff and I would call the other sector's Area Supervisor. I called the Area Supervisor and I asked him if they would fix the routes on Aircraft X and Aircraft Y because TMU had advised no more aircraft over [fix]. The Supervisor shouted at me and said that their sector was 'very busy; the sector is red and I have a tracker in there right now so I cannot get them to fix the route'. I advised him that [xx] was red too; and that we needed the route fixed. The Supervisor continued to berate me on the line saying his sector was 'so busy and red; with a Tracker and D-side' and that he couldn't do it. I then quick-looked their sector and counted 7 data blocks in the sector at the time. A view at the position log and a walk past their area showed that there was no Tracker at that sector either. There also wasn't a D-side. I became very disappointed that not only was a delivering Area unwilling to help out the request of the receiving controller; but that the Supervisor lied to me on a recorded line about how he was staffing his area.Traffic Management Unit should be more proactive to ensure sectors don't go red with excessive volume and aircraft impacted by weather; and supervisors should be more willing to accept/listen to the requests of the receiving controllers vs. berating them and coming up with excuses for why you can't do it. I believe it was unnecessary for the Supervisor to rush to conduct the check ride on the controller who had just gotten their minimum hours a few minutes prior; thus; placing me right into the fire by taking over the desk.

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.