![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1557318 |
| Time | |
| Date | 201807 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | P80.TRACON |
| State Reference | OR |
| Aircraft 1 | |
| Make Model Name | PA-44 Seminole/Turbo Seminole |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | RV-6 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Flight Plan | VFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
| Miss Distance | Vertical 100 |
Narrative:
I believe I took a point out via landline communications from the north controller on aircraft Y southbound VFR at 065. I thought the point out was accomplished because the top of my airspace is 060 and VFR traffic at 065 is still a factor for traffic I could potentially have at 060.I was working the V satellite sector. Aircraft X requested an RNAV approach runway 35 at uao via the full procedure over ubg. I approved his request and he was tracking direct ubg at 050. I then proceeded to resolve other conflicts and accomplish other satellite landline coordination. While accomplishing those tasks; I observed a ca (collision advisory) with aircraft X and aircraft Y over the ubg VOR at 050. I immediately issued a safety alert and turned aircraft X to the right in order to resolve the ca since it appeared aircraft Y was tracking south-eastbound.if I knew aircraft Y wanted to descend I would have taken radar contact on him and de-conflicted him with other traffic in my sector. I think we have a cultural problem of being 'too loose' with reference to working aircraft in other controller's airspace.
Original NASA ASRS Text
Title: P80 TRACON controllers reported a near mid-air collision due to lack of communication and a plan between the controllers.
Narrative: I believe I took a point out via landline communications from the N controller on Aircraft Y southbound VFR at 065. I thought the point out was accomplished because the top of my airspace is 060 and VFR traffic at 065 is still a factor for traffic I could potentially have at 060.I was working the V satellite sector. Aircraft X requested an RNAV approach RWY 35 at UAO via the full procedure over UBG. I approved his request and he was tracking direct UBG at 050. I then proceeded to resolve other conflicts and accomplish other satellite landline coordination. While accomplishing those tasks; I observed a CA (Collision Advisory) with Aircraft X and Aircraft Y over the UBG VOR at 050. I immediately issued a safety alert and turned Aircraft X to the right in order to resolve the CA since it appeared Aircraft Y was tracking south-eastbound.If I knew Aircraft Y wanted to descend I would have taken radar contact on him and de-conflicted him with other traffic in my sector. I think we have a cultural problem of being 'too loose' with reference to working aircraft in other controller's airspace.
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.