Narrative:

I was working local 2 and helicopter position combined with no local assist. There is currently one runway closed on the north side of the airport; which I was responsible for; leaving one runway for arrivals and departures. I had a big enough hole on final to get two departures out. The second departure was aircraft Z; a B350. Props are issued a 271 degree heading off if they are going northbound; but in the interest of time I did not issue this with the takeoff clearance; but was going to issue it once airborne. There was also a helicopter I approved a transition through the class B airspace northbound at 1500 feet. As aircraft Z was beginning takeoff roll aircraft Y on approximately 2 mile final and announced a go around. I advised aircraft Z to fly runway heading; instructed aircraft Y to maintain 2000 feet and fly runway heading. Aircraft Y was approximately 900 feet at the time. I recognized the helicopter transitioning at 1500 feet was in conflict with aircraft Y and immediately instructed aircraft Y to stop climbing. Aircraft Y leveled off at approximately 1100 feet. My initial focus of attention was on aircraft Z and aircraft Y; since this was the most apparent conflict. I then realized aircraft Y was in conflict with the helo transitioning at 1500 feet and took actions to deconflict. I recommend VFR helicopter transitions and loitering in the vicinity of the runways at any altitude be prohibited. Over the years there have been many close calls with helicopters and go arounds and these operations are unnecessary. There are other options like circumnavigating the class B airspace to the east. Mixing helicopters with jets and sharing altitudes is unsafe; especially with unplanned go arounds.

Google
 

Original NASA ASRS Text

Title: A Tower Local Controller reported an aircraft initiating a go-around was in confliction with a helicopter transitioning the airspace.

Narrative: I was working Local 2 and helicopter position combined with no local assist. There is currently one runway closed on the north side of the airport; which I was responsible for; leaving one runway for arrivals and departures. I had a big enough hole on final to get two departures out. The second departure was Aircraft Z; a B350. Props are issued a 271 degree heading off if they are going northbound; but in the interest of time I did not issue this with the takeoff clearance; but was going to issue it once airborne. There was also a helicopter I approved a transition through the Class B airspace northbound at 1500 feet. As Aircraft Z was beginning takeoff roll Aircraft Y on approximately 2 mile final and announced a go around. I advised Aircraft Z to fly runway heading; instructed Aircraft Y to maintain 2000 feet and fly runway heading. Aircraft Y was approximately 900 feet at the time. I recognized the helicopter transitioning at 1500 feet was in conflict with Aircraft Y and immediately instructed Aircraft Y to stop climbing. Aircraft Y leveled off at approximately 1100 feet. My initial focus of attention was on Aircraft Z and Aircraft Y; since this was the most apparent conflict. I then realized Aircraft Y was in conflict with the helo transitioning at 1500 feet and took actions to deconflict. I recommend VFR helicopter transitions and loitering in the vicinity of the runways at any altitude be prohibited. Over the years there have been many close calls with helicopters and go arounds and these operations are unnecessary. There are other options like circumnavigating the Class B airspace to the east. Mixing helicopters with jets and sharing altitudes is unsafe; especially with unplanned go arounds.

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.