Narrative:

We were being vectored for visual approach to runway 25L in phx. We were slowed to 170 knots and were vectored to a very long final. Eventually; we were given a long left dogleg to join final for visual approach to runway 25L. We saw the rj (regional jet) being vectored to a right base for runway 26. We commented that it looked like it would be a conflict if he overshot. Shortly after that; we received a TA on him. Right about then; ATC called him out as traffic. We responded that we had him in sight. We continued our approach and began a left turn to join extended final. We were in a left turn and couldn't see the rj under us. I was monitoring his position on the TCAS display. It turned red and directed an RA climb. I remember seeing it close and 400 ft separation. My first officer initially rolled out of the left turn and leveled his approach. I directed him to climb to match the TCAS guidance. We informed ATC that we were climbing for an RA. They gave the rj an avoidance vector. Our TCAS changed from a climb to level flight. I noticed that we had slightly overshot final while following our RA guidance. Eventually; the TCAS announced; 'clear of conflict.' ATC sent us to tower. My first officer reattempted an approach; but we were high and fast. We requested an s-turn; but tower was busy with other aircraft and did not grant our request. We approached our 1000 ft slot on glidepath; but too fast to make the approach. We initiated a go-around. Tower asked us why; we informed him that we had to respond to the RA guidance that that put us too high for landing. They issued us instructions and switched us to approach. We came back around for an uneventful approach and landing. Normally; TRACON staggers the approaches to prevent these conflicts. For some reason; it didn't work out this time; probably because they slowed us to 170 knots while on downwind; changing the typical approach timing.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737 Captain reported executing a go-around at PHX following an unstable approach that resulted from an RA encounter with parallel traffic.

Narrative: We were being vectored for Visual Approach to Runway 25L in PHX. We were slowed to 170 knots and were vectored to a very long final. Eventually; we were given a long left dogleg to join final for Visual Approach to Runway 25L. We saw the RJ (Regional Jet) being vectored to a right base for Runway 26. We commented that it looked like it would be a conflict if he overshot. Shortly after that; we received a TA on him. Right about then; ATC called him out as traffic. We responded that we had him in sight. We continued our approach and began a left turn to join extended final. We were in a left turn and couldn't see the RJ under us. I was monitoring his position on the TCAS display. It turned red and directed an RA climb. I remember seeing it close and 400 ft separation. My F/O initially rolled out of the left turn and leveled his approach. I directed him to climb to match the TCAS guidance. We informed ATC that we were climbing for an RA. They gave the RJ an avoidance vector. Our TCAS changed from a climb to level flight. I noticed that we had slightly overshot final while following our RA guidance. Eventually; the TCAS announced; 'Clear of Conflict.' ATC sent us to Tower. My F/O reattempted an approach; but we were high and fast. We requested an S-turn; but Tower was busy with other aircraft and did not grant our request. We approached our 1000 ft slot on glidepath; but too fast to make the approach. We initiated a go-around. Tower asked us why; we informed him that we had to respond to the RA guidance that that put us too high for landing. They issued us instructions and switched us to Approach. We came back around for an uneventful approach and landing. Normally; TRACON staggers the approaches to prevent these conflicts. For some reason; it didn't work out this time; probably because they slowed us to 170 knots while on downwind; changing the typical approach timing.

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.