Narrative:

4 separate TCAS events within 45-60 secs. We received a TCAS TA; traffic was approximately 8 o'clock and less than 1 mile 800 feet below. We then received a TCAS RA (monitor vertical speed; target vs zero). I complied with the TA; and told the pm to notify ATC. The TA was over; and I returned to a descent to maintain glideslope. We then received another RA (monitor vertical speed; target vs +300-500). I complied with the second TA; and when the RA was over I returned to a descent to re-establish glideslope. We then received a third RA (climb vs target +2000). Strike 3; game over; I'm all done playing; max effort climb to escape the traffic. Traffic on ILS 16L encroached on our 16R final approach course. We were established on the localizer/GS and maintain 210 KTS about 3 miles from the final approach fix.I applied full thrust and began an escape maneuver. I asked the pm to notify ATC that we were in a TCAS climb. She asked if we wanted another approach; and before I could answer she broke us off the ILS with a right turn to 260. We were at 10;400 and requested a new altitude assignment. We were given 10;000 and I descended. Autopilot was re-engaged. We were vectored for another visual to 16R and landed without further incident. While being vectored back to the approach; ATC said: 'if you would just notify ATC that you can't accept simultaneous ILS approaches we could give you extra spacing.' I responded that we shoot close proximity simultaneous ILS every day; and the TCAS never goes off 4 times; with 3 separate RA commands. I further stated that we had been established on the localizer/GS and the airbus on 16L seemed very close to us in our estimation (800 ft below and less than 1 mile). ATC advised that we had 'both looked pretty good to her.' I was flabbergasted that she made it seem like it was my fault? Clearly there was a loss of separation today. We all concurred that the airbus on 16L was clearly too close to us.

Related reports:

Google
 

Original NASA ASRS Text

Title: EMB145 flight crew reported multiple TCAS RA events during an ILS 16R approach to DEN and went around.

Narrative: 4 separate TCAS events within 45-60 secs. We received a TCAS TA; traffic was approximately 8 o'clock and less than 1 mile 800 feet below. We then received a TCAS RA (Monitor Vertical Speed; target VS zero). I complied with the TA; and told the PM to notify ATC. The TA was over; and I returned to a descent to maintain glideslope. We then received another RA (Monitor Vertical Speed; target VS +300-500). I complied with the second TA; and when the RA was over I returned to a descent to re-establish glideslope. We then received a third RA (CLIMB VS target +2000). Strike 3; game over; I'm all done playing; max effort climb to escape the traffic. Traffic on ILS 16L encroached on our 16R final approach course. We were established on the LOC/GS and maintain 210 KTS about 3 miles from the final approach fix.I applied full thrust and began an escape maneuver. I asked the PM to notify ATC that we were in a TCAS Climb. She asked if we wanted another approach; and before I could answer she broke us off the ILS with a right turn to 260. We were at 10;400 and requested a new altitude assignment. We were given 10;000 and I descended. Autopilot was re-engaged. We were vectored for another visual to 16R and landed without further incident. While being vectored back to the approach; ATC said: 'if you would just notify ATC that you can't accept simultaneous ILS approaches we could give you extra spacing.' I responded that we shoot close proximity simultaneous ILS every day; and the TCAS never goes off 4 times; with 3 separate RA commands. I further stated that we had been established on the LOC/GS and the Airbus on 16L seemed very close to us in our estimation (800 ft below and less than 1 mile). ATC advised that we had 'both looked pretty good to her.' I was flabbergasted that she made it seem like it was my fault? Clearly there was a loss of separation today. We all concurred that the Airbus on 16L was clearly TOO CLOSE TO US.

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.