2011-07 · NASA ASRS report 959922
Enroute FLM described a loss of separation event after two separate notifications to the Controller involved that a conflict was developing; the Supervisor questioning current Controllers' safety culture commitment.
I was walking around in the area monitoring the sectors and I noticed that Aircraft Y had been given a descent clearance to FL260. I also noticed that Air Carrier X had been issued holding instructions at ZZZZZ descending to FL260. I know that the holding pattern is left turns and I knew immediately that Air Carrier X was going to turn left in the direct flight path of Aircraft Y. When the aircraft were approximately 14 miles apart and Aircraft Y was above FL300 descending to FL260; I told the D-Side to make sure the R-Side was aware of the potential conflict because of the left hand turns of the holding pattern. The D-Side assured me he would take care of it. I walked around the area and checked on R01 and a NORAC aircraft and then I returned to Sector 6 to see that the situation had been corrected. The aircraft were approximately 12 miles apart at this time with Air Carrier X level at FL260 and Aircraft Y's data block reflected the aircraft was out of FL285 descending to FL240. I saw that Air Carrier X was about to make the left turn at ZZZZZ and that he would be in direct conflict with Aircraft Y. I asked the R-Side what altitude Aircraft Y was descending to and the R-Side said FL270. The D-Side then said; 'I dressed the data block up; but Aircraft Y is only going to FL270.' I did not address that the data block was dressed up at the time; but decided I would discuss it with both of them when they got off of the sector. I walked around to the FLM desk and I heard the R-Side issuing a traffic alert to Air Carrier X and I immediately returned to the sector to see the aircraft barely miss each other. I wanted to ensure that everyone had the entire story of this event so that they could understand that the FLM had advised them of the traffic on two separate occasions and the event still happened. I think that the environment that we work in these days is much different from the environment I trained in. There is less of an emphasis on safety and there is little to no accountability for the controllers working the aircraft. I understand that people make mistakes; but the mistakes that are being made have shown an outright disregard for safety or a desire to maintain the proper spacing. I don't think that this was the case in this incident; but I have to wonder how hard people try to keep planes apart when they think that nothing is going to happen to them.
I issued Aircraft Y a descent clearance to FL260. I thought I issued FL270; which was a safe altitude; clear of my holding pattern. During the time frame on Sector 6; weather was a major factor. The arrival airport was shut down as well as [the entire] arrival corridor to the satellite airports. I was holding at the outer fixes and Aircraft Y was trying to go to a satellite airport. There were multiple deviations and request for altitude changes. I should have paid better attention to the read back since I was sure as to what I thought I issued. This would have broken the chain of events and prevented the situation from happening.
More incidents for this aircraft family
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.