Narrative:

While working mon-O I observed the WX approaching from the south. One of the aircraft that ended up on runway 9R was a go around due to microburst alert to runway 10. The WX was moving and it was a matter of time before the aircraft on the other runways were going to go around. I did advise a flm of this fact and that these 3 aircraft may also go around due to the WX and an asde-X failure. Air carrier X executed a missed approach inside 1 mi to runway 9R due to radar indicated microburst of -40K on a 2 mi final. Air carrier Y (MD88) just outside the FAF and air carrier Z on a 12 mi final subsequently said that they wanted to go around. I announced that there were 3 go around's on the south side. I instructed air carrier Y to climb and maintain 4000 ft and track the localizer. I canceled air carrier Z approach clearance and turned him sbound. Since I did not see the approach wall flm I initiated a call to LC4 to ask whether he was going straight out or sbound with air carrier X; there was microburst alerts off the departure end of the runway also. He indicated that he wanted to go sbound but he thought the tower flm wanted him to go straight out (LC4 had not received any instructions from the tower flm). Not having the WX depicted at my position and unable to see an approach flm I told LC4 whatever he needed. He said he was going to a 180 degree heading and 3500 ft. I canceled air carrier Z approach clearance and turned him right to 180 degrees and climbed to 4000 ft. The approach flm walked behind me and I advised him that all the aircraft were being turned sbound. I was unable to see air carrier X from the prm scope and his tag had changed to an 'south' tag on the BRITE above the prm scopes making him a limited data block. Therefore I went to the 'left' scope to see the aircraft and splat them to satellite. I returned to mon-O to call sat from the rdvs and received a pointout from the sat handoff. I called air carrier X twice to climb and maintain 5000 ft. Then LC4 told me that he had switched him to departure; I missed the frequency change while I was moving from my position to another scope (because the prm scope does not depict WX and I couldn't see the aircraft on the BRITE scope above the prm scope) and coordinating with other position. I went back to mon-O position and asked departure-south if they were talking to air carrier X and he said no. I unkeyed the rdvs and when I returned to the 'left' scope; air carrier X and air carrier Y were converging at 4000 ft. The data tags were overlapped and I attempted to issue a traffic alert but I issued it to the wrong aircraft. At this point I find out that ar-O is working air carrier X so I go to his position and turn air carrier Z and air carrier Y wbound and switch them to the ar-O controller. Lessons learned: don't work if I'm not feeling 100%. Management knew I was sick and had me work mon-O. They preferred that I do that instead of going home on sick leave. Don't worry about someone else's traffic until I've got a handle on my own. Work my traffic from my position with the equipment the FAA has provided me.

Related reports:

Google
 

Original NASA ASRS Text

Title: A80 CTLR EXPERIENCED OPERROR DURING MULTIPLE GAR'S DUE TO WINDSHEAR; FAILING TO FOCUS ON PERTINENT TFC AND USING MULTIPLE DISPLAYS.

Narrative: WHILE WORKING MON-O I OBSERVED THE WX APCHING FROM THE S. ONE OF THE ACFT THAT ENDED UP ON RWY 9R WAS A GAR DUE TO MICROBURST ALERT TO RWY 10. THE WX WAS MOVING AND IT WAS A MATTER OF TIME BEFORE THE ACFT ON THE OTHER RWYS WERE GOING TO GO AROUND. I DID ADVISE A FLM OF THIS FACT AND THAT THESE 3 ACFT MAY ALSO GO AROUND DUE TO THE WX AND AN ASDE-X FAILURE. ACR X EXECUTED A MISSED APCH INSIDE 1 MI TO RWY 9R DUE TO RADAR INDICATED MICROBURST OF -40K ON A 2 MI FINAL. ACR Y (MD88) JUST OUTSIDE THE FAF AND ACR Z ON A 12 MI FINAL SUBSEQUENTLY SAID THAT THEY WANTED TO GO AROUND. I ANNOUNCED THAT THERE WERE 3 GAR'S ON THE S SIDE. I INSTRUCTED ACR Y TO CLB AND MAINTAIN 4000 FT AND TRACK THE LOC. I CANCELED ACR Z APCH CLRNC AND TURNED HIM SBOUND. SINCE I DID NOT SEE THE APCH WALL FLM I INITIATED A CALL TO LC4 TO ASK WHETHER HE WAS GOING STRAIGHT OUT OR SBOUND WITH ACR X; THERE WAS MICROBURST ALERTS OFF THE DEP END OF THE RWY ALSO. HE INDICATED THAT HE WANTED TO GO SBOUND BUT HE THOUGHT THE TWR FLM WANTED HIM TO GO STRAIGHT OUT (LC4 HAD NOT RECEIVED ANY INSTRUCTIONS FROM THE TWR FLM). NOT HAVING THE WX DEPICTED AT MY POS AND UNABLE TO SEE AN APCH FLM I TOLD LC4 WHATEVER HE NEEDED. HE SAID HE WAS GOING TO A 180 DEG HDG AND 3500 FT. I CANCELED ACR Z APCH CLRNC AND TURNED HIM R TO 180 DEGS AND CLBED TO 4000 FT. THE APCH FLM WALKED BEHIND ME AND I ADVISED HIM THAT ALL THE ACFT WERE BEING TURNED SBOUND. I WAS UNABLE TO SEE ACR X FROM THE PRM SCOPE AND HIS TAG HAD CHANGED TO AN 'S' TAG ON THE BRITE ABOVE THE PRM SCOPES MAKING HIM A LIMITED DATA BLOCK. THEREFORE I WENT TO THE 'L' SCOPE TO SEE THE ACFT AND SPLAT THEM TO SATELLITE. I RETURNED TO MON-O TO CALL SAT FROM THE RDVS AND RECEIVED A POINTOUT FROM THE SAT HDOF. I CALLED ACR X TWICE TO CLB AND MAINTAIN 5000 FT. THEN LC4 TOLD ME THAT HE HAD SWITCHED HIM TO DEP; I MISSED THE FREQ CHANGE WHILE I WAS MOVING FROM MY POS TO ANOTHER SCOPE (BECAUSE THE PRM SCOPE DOES NOT DEPICT WX AND I COULDN'T SEE THE ACFT ON THE BRITE SCOPE ABOVE THE PRM SCOPE) AND COORDINATING WITH OTHER POS. I WENT BACK TO MON-O POS AND ASKED DEP-S IF THEY WERE TALKING TO ACR X AND HE SAID NO. I UNKEYED THE RDVS AND WHEN I RETURNED TO THE 'L' SCOPE; ACR X AND ACR Y WERE CONVERGING AT 4000 FT. THE DATA TAGS WERE OVERLAPPED AND I ATTEMPTED TO ISSUE A TFC ALERT BUT I ISSUED IT TO THE WRONG ACFT. AT THIS POINT I FIND OUT THAT AR-O IS WORKING ACR X SO I GO TO HIS POS AND TURN ACR Z AND ACR Y WBOUND AND SWITCH THEM TO THE AR-O CTLR. LESSONS LEARNED: DON'T WORK IF I'M NOT FEELING 100%. MGMNT KNEW I WAS SICK AND HAD ME WORK MON-O. THEY PREFERRED THAT I DO THAT INSTEAD OF GOING HOME ON SICK LEAVE. DON'T WORRY ABOUT SOMEONE ELSE'S TFC UNTIL I'VE GOT A HANDLE ON MY OWN. WORK MY TFC FROM MY POS WITH THE EQUIP THE FAA HAS PROVIDED ME.

Data retrieved from NASA's ASRS site as of January 2009 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.