Mht local controller described near conflict event involving a go around aircraft when the controlle...

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 controller in charge on duty who was combined with FD and ground control 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 controller in charge was not aware that approach controller issued me go around instructions which caused the controller in charge 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.

Original NASA ASRS Text

Title: 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.

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

Attributes
ACN	882524
Time
Date	201004
Local Time Of Day	1201-1800
Place
Locale Reference	MHT.Airport
State Reference	NH
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Other Instrument Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Approach
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Mht local controller described near conflict event involving a go around aircraft when the controller in charge's instructions differed from those received from the TRACON.