Narrative:

We were established on the localizer for runway 25L at las. We reported the airport in sight and were cleared for the visual approach. Las approach controller told us to maintain 170 knots until 5 mile final. I was PF and was stabilized on glideslope at 170 knots/flaps 10 degrees. Inside of shand at 4900 feet the controller sequenced a regional jet from the south; 2 1/2 miles in front of us on a left base. Approach asked us to slow to 150 knots; and we complied. We lost sight of the rj and called 'no joy' with the traffic ahead. I offered to side step to runway 25R; but controller cancelled our approach clearance and told us to maintain runway heading and climb to 5000 feet. I did a 'go around' and we were vectored south of the airport at 7000 feet. 2 miles south of relin; we were given a 060 heading; and the approach controller asked if we had the airport in sight. The captain replied 'negative; because the airport was at our 5 o'clock position. The controller gave us a left turn heading 180 and told us to descend to 5500 feet. He then cleared us for the visual approach to runway 25L and handed us off to tower. We were over relin at 5000 feet and knew we couldn't comply with SOP and make a stabilized approach from this position. The captain asked the tower for a left 360 to descend; but was denied. The captain and I agreed that we needed to make a second go around. While on downwind for runway 25L; the captain requested a phone number for the las TRACON when we got on the ground. The captain talked to the ATC supervisor during the van ride to the hotel and expressed his displeasure with the chain of events that took place during our approach into las. The supervisor told the captain that he had already reviewed the tapes; and thanked him for our professionalism while complying with all of the controller's instructions. He also agreed with the captain that the controller's performance was not acceptable; and apologized for the mishap. He assured the captain that corrective measures would be taken so that this did not happen again in the future. Don't try to stick a slower airplane so close in front of a faster airplane. Also; better vectors so that when you cross the FAF you are able to be at the correct altitude.

Google
 

Original NASA ASRS Text

Title: Air carrier flight crew reported ATC vectored an aircraft in front of them on final approach resulting in a go around. On the second approach; ATC vectors were in too close and too high for a stable approach and another go around was executed.

Narrative: We were established on the LOC for Runway 25L at LAS. We reported the airport in sight and were cleared for the Visual Approach. LAS approach controller told us to maintain 170 knots until 5 mile final. I was PF and was stabilized on Glideslope at 170 knots/flaps 10 degrees. Inside of SHAND at 4900 feet the controller sequenced a Regional jet from the south; 2 1/2 miles in front of us on a left base. Approach asked us to slow to 150 Knots; and we complied. We lost sight of the RJ and called 'No Joy' with the traffic ahead. I offered to side step to Runway 25R; but controller cancelled our approach clearance and told us to maintain runway heading and climb to 5000 feet. I did a 'Go Around' and we were vectored south of the airport at 7000 feet. 2 miles south of RELIN; we were given a 060 heading; and the approach controller asked if we had the airport in sight. The Captain replied 'Negative; because the airport was at our 5 o'clock position. The controller gave us a left turn heading 180 and told us to descend to 5500 feet. He then cleared us for the Visual Approach to Runway 25L and handed us off to tower. We were over RELIN at 5000 feet and knew we couldn't comply with SOP and make a stabilized approach from this position. The Captain asked the tower for a left 360 to descend; but was denied. The Captain and I agreed that we needed to make a second go around. While on Downwind for Runway 25L; the Captain requested a phone number for the LAS TRACON when we got on the ground. The Captain talked to the ATC Supervisor during the van ride to the hotel and expressed his displeasure with the chain of events that took place during our approach into LAS. The Supervisor told the Captain that he had already reviewed the tapes; and thanked him for our professionalism while complying with all of the controller's instructions. He also agreed with the Captain that the controller's performance was not acceptable; and apologized for the mishap. He assured the Captain that corrective measures would be taken so that this did not happen again in the future. Don't try to stick a slower airplane so close in front of a faster airplane. Also; better vectors so that when you cross the FAF you are able to be at the correct altitude.

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