Narrative:

I was training a developmental in local 1. There had been reports of a 10 to 15 knot tailwind and the wind we were showing was around 120@10 landing 25L and departing 25R and the intersecting runways 19L and 19R. A couple of the heavy aircraft were unable to depart due to the winds so after having to taxi an aircraft down the runway the trainee gave the intersection to local 2 so that he could depart a corporate jet off of 19R. Final was still bringing aircraft to land 25L and there was a line up to 25R; the trainee was asking all the aircraft in line if they would be able to depart with the current winds while local 2 had the intersection. Air carrier X was over the threshold and appeared to be landing when he said that he was going to go-around due to a 20 knot tailwind. At that point the corporate jet was already committed to his takeoff. The trainee said traffic departing 19R just taking off report that traffic in sight. There was a long pause then the air carrier X crew was able to report the traffic in sight she told him to maintain visual separation fly runway heading and climb maintain 7;000 feet. Local 2 gave the corporate jet a traffic alert on the air carrier X and told him to stay low. The corporate jet reported the air carrier X in sight and acknowledged to stay low. Then the corporate jet received an RA and began to climb. The corporate jet pulled up hard and was able to go above the air carrier X and since the air carrier crew had the corporate jet insight he descended slightly so that the corporate jet would go above him as well. With the numerous reports of a tailwind to the aircraft on 25L we could have changed configuration sooner to prevent the go-around off of 25L and then there would not have been the go-around in the first place.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air Carrier flight crew and the LAS Tower Controller involved describe an airborne conflict between the Air Carrier going around from a Runway 25L approach and a Coporate jet departing Runway 19R. The Corporate jet crew is instructed to stay low but responds to a TCAS RA and goes high requiring the Air Carrier crew to go under.

Narrative: I was training a Developmental in Local 1. There had been reports of a 10 to 15 knot tailwind and the wind we were showing was around 120@10 landing 25L and departing 25R and the intersecting runways 19L and 19R. A couple of the heavy aircraft were unable to depart due to the winds so after having to taxi an aircraft down the runway the trainee gave the intersection to Local 2 so that he could depart a Corporate jet off of 19R. Final was still bringing aircraft to land 25L and there was a line up to 25R; the trainee was asking all the aircraft in line if they would be able to depart with the current winds while Local 2 had the intersection. Air Carrier X was over the threshold and appeared to be landing when he said that he was going to go-around due to a 20 knot tailwind. At that point the Corporate jet was already committed to his takeoff. The trainee said traffic departing 19R just taking off report that traffic in sight. There was a long pause then the Air Carrier X crew was able to report the traffic in sight she told him to maintain visual separation fly runway heading and climb maintain 7;000 feet. Local 2 gave the Corporate jet a traffic alert on the Air Carrier X and told him to stay low. The Corporate jet reported the Air Carrier X in sight and acknowledged to stay low. Then the Corporate jet received an RA and began to climb. The Corporate jet pulled up hard and was able to go above the Air Carrier X and since the Air Carrier crew had the Corporate jet insight he descended slightly so that the Corporate jet would go above him as well. With the numerous reports of a tailwind to the aircraft on 25L we could have changed configuration sooner to prevent the go-around off of 25L and then there would not have been the go-around in the first place.

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.