Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types
General None Reported / Taken
Airspace Structure; Human Factors; Procedure
C172 called over Vancouver Lake inbound to VUO on the VUO CTAF. I issued traffic on a heavy inbound for PDX. I found out today that a helicopter was northbound head-on with C172. I don't recall seeing the target. On the replay it looked liked they both turned to avoid each other. I believe fatigue was an issue as well. I should have seen and called traffic. Even though neither was RADAR identified; I can guess where C172 might be and at least give him something to look for. If there is traffic on my scope; I should see it and take appropriate action; whether I'm specifically required to or not. Having said that; it was two VFR aircraft; neither RADAR identified; outside Class C and Class D airspace. I had no communication with one aircraft; and the other was transiting to an uncontrolled airport (VUO) on a Common Traffic Advisory Frequency (CTAF). The Pearson Advisory position was created to issue PDX traffic overflying VUO on the VUO CTAF. ATC should not be on a CTAF at an uncontrolled airport. It confuses many of the pilots. A CTAF is for pilots to talk to each other and separate themselves. When a pilot hears ATC on frequency; doesn't he expect us to provide more service than we are giving? Pilots frequently withhold their pattern calls because ATC is on frequency. They probably think we are controlling the pattern. The current VUO procedures are a joke. The Pearson Advisory position is a joke. Pearson Advisory is not a RADAR position; nor a tower position. I guess it's more of a flight service position? Whatever it is; it's half-baked and dangerous. Due to proximity to PDX; there needs be a tower at VUO; with RADAR capabilities; staffed by PDX controllers.
PDX Controller described a VFR conflict event between two unidentified targets; noting the current procedures covering transiting aircraft are in need of revision.