Date: 201208
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: B737-700
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Climb
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Communication Breakdown; Situational Awareness
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
Result: General None Reported / Taken
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

Narrative: There was a minimal amount of traffic at Sector 22 with weather in the southeastern portion. After reviewing our available resources to estimate traffic volume; I decided to keep my eye on the sector for the possibility of increasing volume. I also ensured that a D-Side was available in the event it became necessary. There was a D-Side working at another sector that would be able to move to Sector 22 if needed. I was also in the process of getting a team of controllers out for team training. My operations supervisor replacement arrived to relieve me from my position. Prior to his arrival; I wanted to ensure that the R22 Controller was comfortable with his traffic; and did not need additional resources. I observed the sector; the volume; and the demeanor of the Controller and did not feel that a D-Side was necessary; but asked the Controller 'Are you OK; or do you want a D Side'. The Controller responded 'I'm OK; there's nothing really going on here'. This re-assured me that he was indeed OK. I began to brief my replacement and brought the situation at Sector 22 to his attention. I advised him that he had an available D-Side at another sector if needed; and I also had a Controller that was being relieved from another sector available if he felt a D-Side was necessary. I and my replacement both looked again at the sector; and my replacement again questioned if the Controller was OK and did not need a D-Side. The Controller again replied that he was OK. When I left the area; I felt the R22 Controller was not overwhelmed or even overly busy; and that I left the relieving Supervisor with a clear picture of the area; as well as two available resources to place a D-Side in Sector 22 if he felt it was necessary. After 2 supervisors; as well as the Controller working the position verified that a D-Side was not necessary; I felt I had left the area well under control. The remainder of this is speculation because I was not present after that point. I understand that the R22 Controller asked for a D-Side minutes after I left the area; and was immediately given one by the Supervisor. A couple of minutes later; there was a loss of separation between a B737 and another Air Carrier; and both aircraft responded to a TCAS alert. The upper management recommendation never changes. If there was no D-Side; there should have been a D-Side. If there was a D-Side; there should have been a Tracker. If there was a Tracker; the Supervisor should have worked more with the Traffic Management Unit to ensure the sector was not overloaded. The buck always stops with the FLM. There is never a mistake made by a controller because we are in a 'just culture'. I say we; but the fact is; the controllers are in a 'just culture' and feel that ATSAP is nothing more than a 'get out of jail free' card. We as managers have our hands tied. We are not in the bargaining unit; so rather than hold a controller accountable for his or her actions and deal with the Union fallout that is certain to follow; the 'easy out' is to always blame the manager. Could there have been a D-Side? Certainly. We could have had a D-Side at every single sector. The fact is; there were 5 other sectors open and if the same situation played out during this time period at any one of them; the same result would occur. We do not have unlimited resources to work with. We have to do the best we can with the people we have. I personally believe my job is to ensure the resources are AVAILABLE for the controllers to do their jobs. In this case; multiple resources were available if the controller needed it; and in fact the resource was immediately placed in position when the controller asked for it. There were 6 total sectors in the area that were all experiencing weather deviations and a moderate level of traffic. I worked the traffic on a D-Side and an R-Side for 3 hours that day. With all the additional and tremendous amount of work that is placed on an operations supervisor at a busy facility; we can't be expected to stand behind every single sector at every single moment the way that operations managers feel we should. We have to rely at times on the controllers having the responsibility to keep us informed on changing conditions; and when resources are available (especially just steps away); to be responsible enough to simply say 'I need a D-Side'. I wish I had a magic answer that could prevent every 'event' from happening. Unfortunately; I don't. But 'Monday morning quarterbacking' every single event; and saying 'you should have had a D-Side' is certainly not going to stop this unless we have the personnel to simply place a D-Side at every sector every time it's open. Most likely; I will be found at fault here. In fact; I feel I already have been. I have been found at the very least to be a contributing factor to this error. The absolute best information I could give to assist with this not happening again is to do away with the tons of additional paperwork; scheduling; briefings; training and other duties that are placed on a front line manager and allow them to have more time to sit behind each and every controller and practically 'babysit' them the way upper management desires.




Synopsis: Enroute FLM expressed his view on a recent operational decision that was questioned by higher management with regard to position management.