Pdx tower controllers reported an arriving airliner responded to a RA and executed a go around due t...

Attributes
ACN	1584831
Time
Date	201810
Local Time Of Day	1801-2400
Place
Locale Reference	PDX.Tower
State Reference	OR
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Initial Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Landing
Route In Use	None
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Other / Unknown

Narrative:

I was working advisory next to LC1 (local controller) when aircraft Y reported inbound for rwy 8 at [nearby] vuo. I told the LC1 controller that aircraft Y was inbound to vuo. I noticed aircraft X on final for 10L [at pdx] and advised aircraft Y; who was on a left downwind (southwest bound); about the traffic. Aircraft Y reported that they had aircraft X in sight. LC1 issued the traffic to aircraft X and advised that aircraft X also had aircraft Y in sight. I looked out the window and aircraft X appeared to be climbing; so I advised LC1. LC1 acknowledged my information about the same time that aircraft X was probably transmitting to LC1 that they were going around due to a TCAS RA. I recommend that a tower be built at vuo so we can control the pattern traffic there and reduce the number of RA's that occur due to pdx landing to the east and vuo traffic being right under them. Both aircraft had each other in sight; but aircraft X had to go around due to the TCAS RA. This is preventable!

Original NASA ASRS Text

Title: PDX Tower Controllers reported an arriving airliner responded to a RA and executed a go around due to VFR traffic in the pattern at nearby VUO.

Narrative: I was working Advisory next to LC1 (Local Controller) when Aircraft Y reported inbound for rwy 8 at [nearby] VUO. I told the LC1 controller that Aircraft Y was inbound to VUO. I noticed Aircraft X on final for 10L [at PDX] and advised Aircraft Y; who was on a left downwind (SW bound); about the traffic. Aircraft Y reported that they had Aircraft X in sight. LC1 issued the traffic to Aircraft X and advised that Aircraft X also had Aircraft Y in sight. I looked out the window and Aircraft X appeared to be climbing; so I advised LC1. LC1 acknowledged my information about the same time that Aircraft X was probably transmitting to LC1 that they were going around due to a TCAS RA. I recommend that a tower be built at VUO so we can control the pattern traffic there and reduce the number of RA's that occur due to PDX landing to the east and VUO traffic being right under them. Both aircraft had each other in sight; but Aircraft X had to go around due to the TCAS RA. This is preventable!

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.

Pdx tower controllers reported an arriving airliner responded to a RA and executed a go around due to VFR traffic in the pattern at nearby vuo.