Iah controller described a go-around event resulting in a conflict when coordination between the tow...

Attributes
ACN	1101998
Time
Date	201307
Local Time Of Day	1801-2400
Place
Locale Reference	IAH.Airport
State Reference	TX
Aircraft 1
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Landing
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Departure Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Narrative:

I was working arriving aircraft to runway 8L. A B737 was on a 3 mile left base for runway 8L on a visual approach. The B737 initiated a go-around due to windshear. I climbed aircraft to 3;000 ft and turned to a heading of 360 (normal procedure). I issued an additional turn to a heading of 300 for a downwind back to the airport and was getting ready to transfer communication when I notice a B767 going around on runway 8R and turning to the north inside the B737. I immediately turned the B737 back to a heading of 360 to avoid conflict with the B767. Then the monitor took over and climbed the B737 to 4;000 ft and initiated another turn. The monitor then assumed control of the B767 to bring the aircraft around for another approach. I had no idea I90 was turning the aircraft on runway 8R to the north. Some communication would have been helpful for this event.

Original NASA ASRS Text

Title: IAH Controller described a go-around event resulting in a conflict when coordination between the Tower and TRACON was ineffective.

Narrative: I was working arriving aircraft to Runway 8L. A B737 was on a 3 mile left base for Runway 8L on a visual approach. The B737 initiated a go-around due to windshear. I climbed aircraft to 3;000 FT and turned to a heading of 360 (normal procedure). I issued an additional turn to a heading of 300 for a downwind back to the airport and was getting ready to transfer communication when I notice a B767 going around on Runway 8R and turning to the north inside the B737. I immediately turned the B737 back to a heading of 360 to avoid conflict with the B767. Then the Monitor took over and climbed the B737 to 4;000 FT and initiated another turn. The Monitor then assumed control of the B767 to bring the aircraft around for another approach. I had no idea I90 was turning the aircraft on Runway 8R to the north. Some communication would have been helpful for this event.

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

Iah controller described a go-around event resulting in a conflict when coordination between the tower and TRACON was ineffective.