P80 approach controller reported an unidentified VFR target not displaying a transponder created a c...

Narrative:

I was working the final position on a VFR day. Pdx was landing on runways 10L/10R. There are always VFR targets everywhere crossing through final and zigzagging around our arrival traffic. About half the time the mode C is indicating that they are low and even though we can't trust the mode C when it's busy; we just call traffic and trust that the altitude is correct as there would be no way to vector around the hornet's nest of VFR targets flying through final's airspace. Sometimes the altitude is indicating that the 1200 squawking target will be a factor and we have to vector around it. This is a real safety concern. Today; however; there was a primary only target just outside the outer ring of the class charlie maneuvering right along the runway 10 final. This target was a factor for at least 5 aircraft within a 15 to 20 minute period. I even had to cancel an approach clearance for one aircraft; as the primary target reversed course and flew back through final.these events are caused by the fact that no one seems to care that we are having close calls daily with VFR aircraft flying through the runway 10 final. I have filed countless reports and it isn't doing anything. We need a class charlie extension or a class bravo airspace at pdx. The airspace needs to be protected much further out because we can't vector close in as per our noise ordinance rules. If that is impossible then there needs to be a VFR corridor at or below a certain altitude. Or you could change the hio procedures and not allow VFR aircraft to enter or exit the class delta airspace from the north. There are several ways we can fix this problem; or at least make it better. But again; no one seems to care. Unfortunately someone or possibly hundreds of people are going to be killed once there is an inevitable mid-air collision. It's only a matter of time. Someone needs to do something.

Original NASA ASRS Text

Title: P80 Approach Controller reported an unidentified VFR target not displaying a transponder created a conflict with several air carriers on final approach.

Narrative: I was working the final position on a VFR day. PDX was landing on Runways 10L/10R. There are always VFR targets everywhere crossing through final and zigzagging around our arrival traffic. About half the time the Mode C is indicating that they are low and even though we can't trust the Mode C when it's busy; we just call traffic and trust that the altitude is correct as there would be no way to vector around the hornet's nest of VFR targets flying through final's airspace. Sometimes the altitude is indicating that the 1200 squawking target will be a factor and we have to vector around it. This is a real safety concern. Today; however; there was a primary only target just outside the outer ring of the Class Charlie maneuvering right along the Runway 10 final. This target was a factor for at least 5 aircraft within a 15 to 20 minute period. I even had to cancel an approach clearance for one aircraft; as the primary target reversed course and flew back through final.These events are caused by the fact that no one seems to care that we are having close calls daily with VFR aircraft flying through the Runway 10 final. I have filed countless reports and it isn't doing anything. We need a Class Charlie extension or a Class Bravo airspace at PDX. The airspace needs to be protected much further out because we can't vector close in as per our noise ordinance rules. If that is impossible then there needs to be a VFR corridor at or below a certain altitude. Or you could change the HIO procedures and not allow VFR aircraft to enter or exit the Class Delta airspace from the north. There are several ways we can fix this problem; or at least make it better. But again; no one seems to care. Unfortunately someone or possibly hundreds of people are going to be killed once there is an inevitable mid-air collision. It's only a matter of time. Someone needs to do something.

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	1688695
Time
Date	201910
Local Time Of Day	0601-1200
Place
Locale Reference	P80.TRACON
State Reference	OR
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	Dash 8-400
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Aircraft 2
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Final Approach Initial Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 14
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

P80 approach controller reported an unidentified VFR target not displaying a transponder created a conflict with several air carriers on final approach.