Narrative:

Working arrivals and departures on runway 16L. Aircraft X initiates a go around because he was too fast. After handing off and vectoring the go around I cleared aircraft Y for takeoff and put aircraft Z in position; as aircraft a was now on final. Aircraft Y asked to verify his takeoff clearance which was done. Aircraft Z was cleared and aircraft a put into position with aircraft B on a 4 mile final. I cleared aircraft a for takeoff anticipating aircraft Z will be 6;000 feet and airborne by the time aircraft a starts to roll. Aircraft B stated he needed to go missed because he's too high. I elected to cancel the takeoff clearance for aircraft a shortly after they started to roll as I was concerned he may become an issue with aircraft B. Aircraft a then taxied back to the end and took off. The front line manager (flm) said I was clean; and nice job.if I had put aircraft Y in position right after the go around of aircraft X things wouldn't have ended up so tight. As I cleared aircraft Y for takeoff I may have caused some confusion as I put aircraft Z into position right behind him causing aircraft Y to confirm he was cleared for takeoff; slowing their departure. Additionally we were just about to go into a runway use plan which calls for the runway I was working to be departure only. The tower flm wanted the program to start earlier and traffic management in the TRACON didn't want to. I think the TRACON was trying to hurry aircraft X and aircraft B in before the program started which resulted in unstabilized approaches and back to back pilot initiated go arounds. I made a judgment call to cancel the takeoff clearance of aircraft a since they just barely started to roll.

Google
 

Original NASA ASRS Text

Title: An SLC Controller reports of an operation that resulted in a go-around due to traffic on the runway and an arrival being higher than normal.

Narrative: Working arrivals and departures on RWY 16L. Aircraft X initiates a go around because he was too fast. After handing off and vectoring the go around I cleared Aircraft Y for takeoff and put Aircraft Z in position; as Aircraft A was now on final. Aircraft Y asked to verify his takeoff clearance which was done. Aircraft Z was cleared and Aircraft A put into position with Aircraft B on a 4 mile final. I cleared Aircraft A for takeoff anticipating Aircraft Z will be 6;000 feet and airborne by the time Aircraft A starts to roll. Aircraft B stated he needed to go missed because he's too high. I elected to cancel the takeoff clearance for Aircraft A shortly after they started to roll as I was concerned he may become an issue with Aircraft B. Aircraft A then taxied back to the end and took off. The Front Line Manager (FLM) said I was clean; and nice job.If I had put Aircraft Y in position right after the go around of Aircraft X things wouldn't have ended up so tight. As I cleared Aircraft Y for takeoff I may have caused some confusion as I put Aircraft Z into position right behind him causing Aircraft Y to confirm he was cleared for takeoff; slowing their departure. Additionally we were just about to go into a runway use plan which calls for the runway I was working to be departure only. The tower FLM wanted the program to start earlier and traffic management in the TRACON didn't want to. I think the TRACON was trying to hurry Aircraft X and Aircraft B in before the program started which resulted in unstabilized approaches and back to back pilot initiated go arounds. I made a judgment call to cancel the takeoff clearance of Aircraft A since they just barely started to roll.

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.