Commercial Fixed Wing
Air Traffic Control Developmental
Other / Unknown
ATC Issue All Types; Conflict Airborne Conflict; Inflight Event / Encounter Weather / Turbulence
Air Traffic Control Issued Advisory / Alert; Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Airport; Procedure; Weather
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.
We were cleared to land Runway 25L and Tower called winds approximately 140 at 15. Our FMS indicated a 20-knot tailwind approximately 5 NM from the field and this tailwind continued all the way down on final approach. Crew kept close watch on wind readout to ensure tailwind was less than 10 knots on short final (about 100 feet AGL) thus allowing us to land. At 100 feet; the tailwind was still greater than 10 knots so we executed a go-around. Pilot not flying informed ATC of this immediately. Pilot flying did not hear a radio call telling us to 'use caution for aircraft departing crossing runway;' but pilot not flying did. Near the end of Runway 25L; pilot not flying asked pilot flying if he had the other aircraft in sight and told pilot flying to 'lower the nose' and then took the aircraft and maneuvered it to avoid a collision with a Corporate jet that had departed Runway 19L. Sometime during this maneuvering; ATC issued instructions to 'fly runway heading and maintain 7;000.' The Corporate jet appeared to pass straight overhead less than 500 feet away.Develop alternate go-around procedures for VMC conditions in the event an aircraft is departing the crossing runway (either 19L/R) when one is landing 25L to include developing alternate departure procedures for smaller aircraft departing Runway 19L/R allowing them to turn toward the west while the aircraft from 25L turns toward the south. This event only occurs if the landing aircraft has to go-around or abort the landing on Runway 25L and an aircraft has departed Runway 19L/R.
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.