37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1502090 |
Time | |
Date | 201712 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | P80.TRACON |
State Reference | OR |
Aircraft 1 | |
Make Model Name | Bombardier/Canadair Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR TMBRS TWO |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Route In Use | None |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I was working final on a runway 10 flow into portland. A regional jet was descending via the timbers arrival STAR and level at 5000. I noticed a VFR target squawking 1200 eastbound at 4700. The aircraft preceded to cross the timbers STAR. I issued traffic to the crj and the aircraft never got the 1200 target in sight. I had to turn and issue an expedited descent to the crj to avoid merging the targets. The unidentified aircraft continued eastbound; just south of kpdx and I handed the target off to the hood sector. Hood stopped all pdx departures at 4000 as the target continued to fly up the departure corridor at a slow rate of speed. This was not a safe operation. In no way whatsoever. Our class charlie airspace is completely at fault. The aircraft technically didn't deviate protected airspace. However; our arrival routes are not protected by the class charlie rules. The timbers arrival descends to 5000 feet and often we can't go lower because of terrain and arrivals/departures off of khio airport. The final sector's airspace needs to be protected at the standard downwind/base/final approach altitudes.every day there are targets crossing final in front of aircraft; below aircraft; and above aircraft and we aren't talking to those airplanes and have no way to verify their mode C. It is extremely unsafe; and unfortunately; something will happen someday that we all are desperately trying to avoid. This needs to be fixed soon; like yesterday.
Original NASA ASRS Text
Title: P80 TRACON Controller reported the PDX class C airspace compromises separation for arrivals and departures due to non-participating air traffic in the area.
Narrative: I was working final on a runway 10 flow into Portland. A Regional Jet was descending via the timbers arrival STAR and level at 5000. I noticed a VFR target squawking 1200 eastbound at 4700. The aircraft preceded to cross the timbers STAR. I issued traffic to the CRJ and the aircraft never got the 1200 target in sight. I had to turn and issue an expedited descent to the CRJ to avoid merging the targets. The unidentified aircraft continued eastbound; just south of KPDX and I handed the target off to the hood sector. Hood stopped all PDX departures at 4000 as the target continued to fly up the departure corridor at a slow rate of speed. This was not a safe operation. In no way whatsoever. Our class Charlie airspace is completely at fault. The aircraft technically didn't deviate protected airspace. However; our arrival routes are not protected by the class Charlie rules. The timbers arrival descends to 5000 feet and often we can't go lower because of terrain and arrivals/departures off of KHIO airport. The final sector's airspace needs to be protected at the standard downwind/base/final approach altitudes.Every day there are targets crossing final in front of aircraft; below aircraft; and above aircraft and we aren't talking to those airplanes and have no way to verify their mode C. It is extremely unsafe; and unfortunately; something will happen someday that we all are desperately trying to avoid. This needs to be fixed soon; like yesterday.
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.