MHT local controller described near conflict event involving a go around aircraft when the CIC's instructions differed from those received from the TRACON.
Synopsis
MHT local controller described near conflict event involving a go around aircraft when the CIC's instructions differed from those received from the TRACON.
Narrative
I was on position as Local Control. I had launched an air carrier off of Runway 35. Air Carrier X was on ILS final to Runway 35. When Air Carrier X was at about a 2 mile final the Approach Controller told me if Air Carrier X goes around because he is too high have him fly runway heading and to climb and maintain 3 thousand feet. When Air Carrier X called a go around I issued the instructions the Approach Controller told me to issue. At this time the CIC on duty who was combined with FD and GC told me to issue Air Carrier X a 020 heading. He was not aware of a point out who was on an ILS approach to CON that a 020 heading would lose separation between Air Carrier X and the point out. At this point I issued Air Carrier X a 090 for divergence separation but lateral separation might have been lost. I would [say] that communication between controllers was the main reason for this event. The CIC was not aware that Approach Controller issued me go around instructions which caused the CIC to issue me a 020 heading. Also Approach did not tell us that that they had turned the departure aircraft to establish divergence between the departure and the go around aircraft.
Second reporter narrative
Air Carrier X was going around on a missed approach. Tower contacted me and said Air Carrier X was turning to a 020 heading. Joining the localizer at a satellite airport was a Bonanza. The 020 heading put Air Carrier X in conflict with the Bonanza. Bonanza was previously pointed out to the Tower. In order to prevent the conflict from developing further; I immediately contacted Tower and had them turn Air Carrier X to a 090 heading and to change him to my frequency. Divergence was achieved before separation was lost. Recommendation; in the future Tower should not turn missed approaches in the direction of traffic that was previously pointed out to them.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.