B737 Undifferentiated or Other Model
Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Other / Unknown
Air Traffic Control Issued Advisory / Alert; Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Airport; Airspace Structure; Procedure
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!
B737 on final for 10L [at PDX] was issued traffic on Aircraft Y (downwind for RY08 @ VUO) that was opposite direction. B737 had Aircraft Y in sight. Once B737 was over the VUO airport they went around because of an RA.VUO traffic pattern when PDX is on a 10 flow is dangerous. There needs to be a tower at VUO or the airport needs to be shut down.
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.