B737 captain reported that while established on the final approach course at den; he received an RA ...

Narrative:

On arrival to denver runway 16R; we were slowed to 170 knots approximately 30 miles north of denver for approach spacing. We were eventually cleared for a visual approach to runway 16R following traffic. Denver approach called out traffic for the parallel runway at our seven o'clock at a lower altitude and stated they had a 40 knot overtake. I asked if we could increase our speed to avoid the other aircraft overtaking us and I stated we would most likely get a TCAS RA on the aircraft. ATC said we were four miles in trail of the traffic and could increase slightly. We increased 10 knots; but as anticipated; we received a TCAS RA. We complied with the RA and ATC broke us off the approach. We were vectored for a subsequent approach and landed on runway 16R. This cost 800 pounds of fuel and approximately 10 minutes time.this is the third TCAS RA involving runways 16L and 16R I have experienced in the last few months; one of which resulted in a divert due to weather that impacted the field during the go around and re-sequencing. I contacted my dispatcher to advise of the situation; and was transferred to the ATC desk. I advised the ATC desk what happened and asked if they would like to be on a call with me to the denver TRACON. They declined. I contacted the denver TRACON to discuss the handling my flight received and inquired why an aircraft was allowed to overtake us. We had a long discussion with the end result of me being told this is basically how denver TRACON does business.I did not select TA only on the TCAS as I feel turning off this safety system defeats the purpose of the system. I also do not feel we should turn it to TA only to accommodate the way ATC is handling our aircraft on these runways as a normal means of business. I have previously notified [company] of the TCAS RA events via a report; but feel this needs to be addressed at a higher level.

Original NASA ASRS Text

Title: B737 Captain reported that while established on the final approach course at DEN; he received an RA for traffic established on the final approach course of a parallel runway and had to go around.

Narrative: On arrival to Denver Runway 16R; we were slowed to 170 knots approximately 30 miles north of Denver for approach spacing. We were eventually cleared for a Visual Approach to Runway 16R following traffic. Denver Approach called out traffic for the parallel Runway at our seven o'clock at a lower altitude and stated they had a 40 knot overtake. I asked if we could increase our speed to avoid the other aircraft overtaking us and I stated we would most likely get a TCAS RA on the aircraft. ATC said we were four miles in trail of the traffic and could increase slightly. We increased 10 knots; but as anticipated; we received a TCAS RA. We complied with the RA and ATC broke us off the approach. We were vectored for a subsequent approach and landed on Runway 16R. This cost 800 pounds of fuel and approximately 10 minutes time.This is the third TCAS RA involving Runways 16L and 16R I have experienced in the last few months; one of which resulted in a divert due to weather that impacted the field during the go around and re-sequencing. I contacted my dispatcher to advise of the situation; and was transferred to the ATC desk. I advised the ATC desk what happened and asked if they would like to be on a call with me to the Denver TRACON. They declined. I contacted the Denver TRACON to discuss the handling my flight received and inquired why an aircraft was allowed to overtake us. We had a long discussion with the end result of me being told this is basically how Denver TRACON does business.I did not select TA Only on the TCAS as I feel turning off this safety system defeats the purpose of the system. I also do not feel we should turn it to TA only to accommodate the way ATC is handling our aircraft on these runways as a normal means of business. I have previously notified [company] of the TCAS RA events via a report; but feel this needs to be addressed at a higher level.

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.

Attributes
ACN	1401300
Time
Date	201611
Place
Locale Reference	DEN.Airport
State Reference	CO
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Total 9529 Flight Crew Type 5867
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Inflight Event / Encounter Other / Unknown

B737 captain reported that while established on the final approach course at den; he received an RA for traffic established on the final approach course of a parallel runway and had to go around.