Pdx controller described an issued go around event when traffic on final for pdx runway 10R was in c...

Narrative:

PIREPS at the time indicated cloud tops 2;000 ft and bases 700 ft on the facility. Aircraft X was on the ILS10R approach to pdx. I noticed a 1;200 (VFR) target in the vicinity of pearson field; turning eastbound as if to land on runway 8 at vuo. The unverified mode-C was indicating approximately 1;500 ft. The DH8 was nearing the VFR target and at 3 miles west of pdx the [dash 8] would be immediately adjacent to pearson. At this point the [dash 8] flight was also indicating descending through 1;500 ft. I became concerned because the two targets were appearing to merge; with less than 500 ft vertical separation. I issued at least two traffic alerts to [the dash 8]. The pilot reported no visual contact with the traffic. Somewhat surprisingly; the pilot never advised he had received a RA from his TCAS. As the traffic was still closing; I canceled aircraft X's approach clearance when the VFR target was about 1/2 mile north of the DH8; same indicated altitude; and issued a climb to 2;000 ft and vectored the aircraft right heading 210. Coordination for this go-around was accomplished with the hood and final P80 sectors. Aircraft X's second approach was uneventful. Recommendation: shut down pearson field. That airport is notorious for generating traffic alerts; TCAS ras and concerns from pilots flying into pdx. This airport being 3 miles west of pdx underneath two ILS approach courses is an accident waiting to happen.

Original NASA ASRS Text

Title: PDX Controller described an issued go around event when traffic on final for PDX Runway 10R was in conflict with an unknown suspected Pearson Field VFR target; the reporter advocating the closure of Pearson Airport.

Narrative: PIREPS at the time indicated cloud tops 2;000 FT and bases 700 FT on the FAC. Aircraft X was on the ILS10R approach to PDX. I noticed a 1;200 (VFR) target in the vicinity of Pearson Field; turning eastbound as if to land on Runway 8 at VUO. The unverified Mode-C was indicating approximately 1;500 FT. The DH8 was nearing the VFR target and at 3 miles west of PDX the [Dash 8] would be immediately adjacent to Pearson. At this point the [Dash 8] flight was also indicating descending through 1;500 FT. I became concerned because the two targets were appearing to merge; with less than 500 FT vertical separation. I issued at least two Traffic Alerts to [the Dash 8]. The pilot reported no visual contact with the traffic. Somewhat surprisingly; the pilot never advised he had received a RA from his TCAS. As the traffic was still closing; I canceled Aircraft X's approach clearance when the VFR target was about 1/2 mile north of the DH8; same indicated altitude; and issued a climb to 2;000 FT and vectored the aircraft right heading 210. Coordination for this go-around was accomplished with the Hood and Final P80 sectors. Aircraft X's second approach was uneventful. Recommendation: shut down Pearson Field. That airport is notorious for generating Traffic Alerts; TCAS RAs and concerns from pilots flying into PDX. This airport being 3 miles west of PDX underneath two ILS approach courses is an accident waiting to happen.

Data retrieved from NASA's ASRS site as of April 2012 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	928816
Time
Date	201101
Local Time Of Day	1801-2400
Place
Locale Reference	PDX.Tower
State Reference	OR
Aircraft 1
Make Model Name	Dash 8 Series Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

Pdx controller described an issued go around event when traffic on final for pdx runway 10R was in conflict with an unknown suspected pearson field VFR target; the reporter advocating the closure of pearson airport.