Narrative:

Captain flying visual approach: 1. Cleared visual approach 2. Descent to 2700' for glideslope intercept 3. Intercepted localizer above glidepath. 4. Descending to capture glide path received TCAS traffic alert followed immediately by monitor vertical speed. Auto pilot off to comply with alert. 5. TCAS showed traffic passing below us by only 400'. 6. Cleared traffic but now very high on glide slope. Decided to continue approach since we were still outside 6 miles from the field. 7. Configured aircraft to land but still high at 1000' 8. Opted to continue approach to 500'. Stable at 500' and continued to land. 9. Upon landing; aircraft bounced and throttles did not seem to retard so go-around executed. Elected to go around after landing bounce because of tail strike concerns. 10. Normal go-around to down wind. 11. On second approach; tried to get aircraft into managed speed mode but power advanced. Disconnected auto thrust but unable to salvage approach. Unstable because of airspeed so missed approach at 500' 12. On missed approach; tower directed a right turn to 155 and climb to 400'. Tower also called out departure traffic. We called traffic in sight. Overshot 155 heading while looking for traffic but immediately corrected back to assigned heading. 13. Returned for normal landing. Although we experienced the incredibly unusual situation of having to go around twice; I believe we complied with all procedures and operated the aircraft in a safe manner. Although we were stable at 500' I did think I was 'behind the airplane' slightly and that may have contributed to the bounce on landing. In hindsight I think that the more conservative action would have been to go-around after the TCAS warning.had the unusual occurrence of a TCAS event during approach. Although I did not think so at the time; this event caused us to get outside of our normal habit pattern. Were this to happen to me again; I would definitely go around.

Google
 

Original NASA ASRS Text

Title: Air carrier flight crew reported a NMAC on arrival preceded a bounced landing and a go-around; followed by an unstabilized approach to another go-around.

Narrative: Captain flying visual approach: 1. Cleared visual approach 2. Descent to 2700' for glideslope intercept 3. Intercepted localizer above glidepath. 4. Descending to capture glide path received TCAS traffic alert followed immediately by monitor vertical speed. Auto pilot off to comply with alert. 5. TCAS showed traffic passing below us by only 400'. 6. Cleared traffic but now very high on glide slope. Decided to continue approach since we were still outside 6 miles from the field. 7. Configured aircraft to land but still high at 1000' 8. Opted to continue approach to 500'. Stable at 500' and continued to land. 9. Upon landing; aircraft bounced and throttles did not seem to retard so go-around executed. Elected to go around after landing bounce because of tail strike concerns. 10. Normal go-around to down wind. 11. On second approach; tried to get aircraft into managed speed mode but power advanced. Disconnected auto thrust but unable to salvage approach. Unstable because of airspeed so missed approach at 500' 12. On missed approach; tower directed a right turn to 155 and climb to 400'. Tower also called out departure traffic. We called traffic in sight. Overshot 155 heading while looking for traffic but immediately corrected back to assigned heading. 13. Returned for normal landing. Although we experienced the incredibly unusual situation of having to go around twice; I believe we complied with all procedures and operated the aircraft in a safe manner. Although we were stable at 500' I did think I was 'behind the airplane' slightly and that may have contributed to the bounce on landing. In hindsight I think that the more conservative action would have been to go-around after the TCAS warning.Had the unusual occurrence of a TCAS event during approach. Although I did not think so at the time; this event caused us to get outside of our normal habit pattern. Were this to happen to me again; I would definitely go around.

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.