2011-02 · NASA ASRS report 934162
When an ARTCC Front Line Manager working a sector confused two similar call signs; a clearance was issued to the wrong aircraft resulting in a loss of separation. The reporter cited heavy traffic and lack of proficiency as contributory.
Aircraft ABCDE was northeast bound landing ZZZ. He had been temporarily stopped at FL370. I needed to get him down to FL350 per LOA and was anticipating him possibly asking for lower. Aircraft AFGDE was southwest bound at FL400. I had not noticed that he was landing soon and was not anticipating him asking for lower. I was busy answering the green light when aircraft AFGDE requested lower and I did not hear him. I asked him to say again and aircraft AFGDE asked for lower. I was looking at aircraft ABCDE's data block and had in my head that it was him that asking for lower. I said aircraft AFGDE's call sign when I told him to descend and maintain FL350; but I still had in my head that I was talking to aircraft ABCDE and typed the altitude into his data block. A few seconds later I realized that aircraft AFGDE was descending head on with aircraft ABCDE. I asked aircraft AFGDE to verify assigned altitude thinking it might have been a bad mode C hit. Then I immediately stopped his descent at FL380. He later said he shot through 100 FT. I then descended aircraft ABCDE from FL370 to FL350. I asked aircraft ABCDE if he had received an RA and he said yes that he showed aircraft AFGDE 700 FT above him. I believe similar sounding call signs had something to do with situation. I also believe that as an FLM; we are not as proficient as we should be to work a sector. We are only required to get 8 hours per month time on position. That is not enough time to be safe! FLM's should have to get more time on position to be safe or should not work sectors at all.
I was CIC during this event. I had just asked if they were comfortable working this amount of traffic -- approximately 12-13 aircraft -- or [if] they want a D-side. The Controller said they were good. I reminded them of the strong winds out of the west and walked away. A Controller gave me a head nod a few minutes later in that direction. When I got over there they still had vertical and I said to stop aircraft AFGDE at FL380. Transposed call signs with aircraft ABCDE and this lost valuable time. At the same time I had instructed another Controller to plug in. The volume of traffic spiked considerably without notification on the TSD. The TSD showed 13; 13; 14 for the next 45 minutes. When the error occurred there were probably 17 data blocks on the scope.I will not trust the TSD. I will constantly monitor or have a D-side in when a Supervisor is working traffic.
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.