Narrative:

I was the local controller during a moderately busy period. Traffic consisted of multiple IFR practice approaches arrivals and departures. During this event; an aircraft on a practice IFR approach was on 6 mile final with a climbout procedure. The climbout is a heading of 180; climb to 3;000 feet and is usually pre-coordinated. It is not an official climbout; but it is an understanding between radar and tower controller. Aircraft X called up ready for takeoff with an IFR flight plan southbound also with a 180 heading climbout. With VFR traffic in the tower pattern; two other aircraft approaching the initial for the overhead; two other instrument approaches on final and simultaneous converging arrival on an intersecting runway with an air carrier and an small aircraft; I determined I had the time and spacing to clear aircraft X for takeoff with a heading of 200 to create divergence with aircraft Y when he completes his approach. Usually a 200 heading should be pre-coordinated but due to the traffic complexity and volume between myself and the radar controller; we were unable to coordinate. I monitored radar's frequency several times for a break between transmissions but the frequency was heavily congested. Aircraft Y executed a missed approach for training and started his right southbound turnout earlier than anticipated with the overhead aircraft approaching numbers for the right break. I instructed the overhead pattern traffic to 'break now' to avoid any conflict with the aircraft Y on his missed approach turn.I gave a traffic call to aircraft Y on aircraft X that was a few miles upwind and verified aircraft Y's 180 heading. I then instructed aircraft X to check in on his 200 heading with approach due to it being a nonstandard heading. I was not aware of any loss of separation at the time and was notified days later. I recommend better coordination would prevent a re-occurrence of this event as well as having the climbout published. I understand that it was used in the past and would like for it to be a part of our climbout procedures.

Related reports:

Google
 

Original NASA ASRS Text

Title: Local Tower Controller and Radar Controller reported a conflict between a go-around aircraft and a slower moving departure.

Narrative: I was the Local Controller during a moderately busy period. Traffic consisted of multiple IFR practice approaches arrivals and departures. During this event; an aircraft on a practice IFR approach was on 6 mile final with a climbout procedure. The climbout is a heading of 180; climb to 3;000 feet and is usually pre-coordinated. It is not an official climbout; but it is an understanding between Radar and Tower Controller. Aircraft X called up ready for takeoff with an IFR flight plan southbound also with a 180 heading climbout. With VFR traffic in the Tower pattern; two other aircraft approaching the initial for the overhead; two other instrument approaches on final and simultaneous converging arrival on an intersecting runway with an air carrier and an small aircraft; I determined I had the time and spacing to clear Aircraft X for takeoff with a heading of 200 to create divergence with Aircraft Y when he completes his approach. Usually a 200 heading should be pre-coordinated but due to the traffic complexity and volume between myself and the Radar Controller; we were unable to coordinate. I monitored Radar's frequency several times for a break between transmissions but the frequency was heavily congested. Aircraft Y executed a missed approach for training and started his right southbound turnout earlier than anticipated with the overhead aircraft approaching numbers for the right break. I instructed the overhead pattern traffic to 'break now' to avoid any conflict with the Aircraft Y on his missed approach turn.I gave a traffic call to Aircraft Y on Aircraft X that was a few miles upwind and verified Aircraft Y's 180 heading. I then instructed Aircraft X to check in on his 200 heading with approach due to it being a nonstandard heading. I was not aware of any loss of separation at the time and was notified days later. I recommend better coordination would prevent a re-occurrence of this event as well as having the climbout published. I understand that it was used in the past and would like for it to be a part of our climbout procedures.

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.