Narrative:

Unplanned go-around [we were] on runway 25 by an A320 who was under my control at the local control 1 position. Traffic departing 19 complex under the control of local control 2. The A320 advised going around; I immediately looked for traffic off 19's. Traffic was rotating midfield; the departure; P180; was to the left of the A320 on a 175 degree heading. I issued traffic on lear converging and unkeyed to try to hear what local control 2 was instructing his traffic to do. My assistant instructed local control 2 to have his aircraft stay low and pass below the A320. I keyed up to tell the A320 what the lear was going to do but visually; saw the lear climbing and banking right. I instructed the A320 to turn left and established visual separation with lear jet. Local assistant was coordinating with L30 and he told me to turn the A320 to 240 degrees; climbed the A320 to 6;000 confirming still visual separation with lear jet. Told the A320 to contact L30; the A320 came back to my frequency asking what runway he can expect. I advised runway 25L and told to contact departure again. During the time of this situation a traffic management coordinator was the controller in charge. Tmu usually monitors ground control to help them anticipate flow times. I don't know if the traffic management was monitoring a position. I feel if a regular controller was staffing the controller in charge position they might have caught the go around earlier. When I advised local control 2 the A320 was going around I didn't get an immediate response from him that he heard me. Perhaps a supervisor/controller controller in charge would have yelled louder at him. Also a supervisor/controller controller in charge might have taken more immediate action to have local control 2 cancel the take off clearance of another A320 who was departing behind the lear with visual separation.

Google
 

Original NASA ASRS Text

Title: LAS Controllers described a developing conflict involving a go-around on Runway 25L and departure from the Runway 19 complex. The reporter indicated that a more experienced CIC may have completed the need internal coordination more quickly.

Narrative: Unplanned go-around [we were] on Runway 25 by an A320 who was under my control at the Local Control 1 position. Traffic departing 19 complex under the control of Local Control 2. The A320 advised going around; I immediately looked for traffic off 19's. Traffic was rotating midfield; the departure; P180; was to the left of the A320 on a 175 degree heading. I issued traffic on Lear converging and unkeyed to try to hear what Local Control 2 was instructing his traffic to do. My assistant instructed Local Control 2 to have his aircraft stay low and pass below the A320. I keyed up to tell the A320 what the Lear was going to do but visually; saw the Lear climbing and banking right. I instructed the A320 to turn left and established Visual Separation with Lear Jet. Local Assistant was coordinating with L30 and he told me to turn the A320 to 240 degrees; climbed the A320 to 6;000 confirming still visual separation with Lear Jet. Told the A320 to contact L30; the A320 came back to my frequency asking what runway he can expect. I advised Runway 25L and told to contact departure again. During the time of this situation a Traffic Management Coordinator was the CIC. TMU usually monitors Ground Control to help them anticipate flow times. I don't know if the Traffic Management was monitoring a position. I feel if a regular controller was staffing the CIC position they might have caught the go around earlier. When I advised Local Control 2 the A320 was going around I didn't get an immediate response from him that he heard me. Perhaps a Supervisor/Controller CIC would have yelled louder at him. Also a Supervisor/Controller CIC might have taken more immediate action to have Local Control 2 cancel the take off clearance of another A320 who was departing behind the Lear with visual separation.

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.