Pdx tower controller and an air carrier pilot reported a go-around event at pdx due to a TCAS/RA tri...

Attributes
ACN	1520765
Time
Date	201802
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	EMB ERJ 170/175 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Descent
Flight Plan	IFR
Aircraft 2
Make Model Name	Skyhawk 172/Cutlass 172
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	VFR Route
Flight Plan	VFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6.0
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

I was working local control. Aircraft Y reported in the pattern at pearson opposite direction to portland flow. Aircraft X was on final and I told him about aircraft Y in the pattern at pearson. He did not respond; and after I told him about the traffic a second time; he said 'go around instructions?' I asked him if he was going around and he replied 'affirmative'; so I issued him go-around instructions. I had advised aircraft Y to remain outside class C airspace and caution wake turbulence for arrivals from the west. I told him about the traffic inbound but he did not report it in sight. After I issued go around instructions to aircraft X; I asked what the nature of the go around was; and he replied that it was a TCAS RA due to the traffic at pearson.build a tower at pearson airport so we can control the traffic in and out of that airport reference portland traffic and give them better advisories about portland traffic; since we would know exactly what phase of flight the pearson aircraft are in.

Original NASA ASRS Text

Title: PDX Tower Controller and an air carrier pilot reported a go-around event at PDX due to a TCAS/RA triggered by a light aircraft in the pattern at an adjacent airport underneath the instrument final approach course.

Narrative: I was working Local Control. Aircraft Y reported in the pattern at Pearson opposite direction to Portland flow. Aircraft X was on final and I told him about Aircraft Y in the pattern at Pearson. He did not respond; and after I told him about the traffic a second time; he said 'Go around instructions?' I asked him if he was going around and he replied 'affirmative'; so I issued him go-around instructions. I had advised Aircraft Y to remain outside Class C airspace and caution wake turbulence for arrivals from the west. I told him about the traffic inbound but he did not report it in sight. After I issued go around instructions to Aircraft X; I asked what the nature of the go around was; and he replied that it was a TCAS RA due to the traffic at Pearson.Build a tower at Pearson airport so we can control the traffic in and out of that airport reference Portland traffic and give them better advisories about Portland traffic; since we would know exactly what phase of flight the Pearson aircraft are in.

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 controller and an air carrier pilot reported a go-around event at pdx due to a TCAS/RA triggered by a light aircraft in the pattern at an adjacent airport underneath the instrument final approach course.