37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1546221 |
Time | |
Date | 201805 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | P80.TRACON |
State Reference | OR |
Aircraft 1 | |
Make Model Name | Gulfstream G650 |
Flight Phase | Climb |
Route In Use | SID BERNI3 |
Flight Plan | IFR |
Aircraft 2 | |
Flight Phase | Cruise |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 0 Vertical 100 |
Narrative:
I think this happened towards earlier part of the session. Was training. Aircraft X was released on a berni RNAV departure. Prior to being airborne; a VFR started flying south of hio westbound 3;100; aircraft X climbing to 4;000. Aircraft X called at 1;600 non radar and we gave traffic but had very limited options being climbing fast and just getting ahold of them. Aircraft X got them inside maybe a mile or 2 prior to crossing over top of the VFR by maybe 100 feet. Was very close and very dangerous with the VFR deciding to fly over a hot spot area barely above hio airspace. Very similar issue as we have with vfrs getting in the way on purpose through our arrivals and departures because people don't want to give us a modified charlie airspace to protect our RNAV departures and arrivals. We were training; and this got very close.I had another instance almost exactly like this that I stopped them at 3;000 for a primary; not in tower's airspace; and was lucky they were at 3;500 when the departure got them in sight telling me it was a good call to stop them at 3;000 right away when they checked on. Hio called and distracted my trainee before calling traffic. All they were telling us is they did not give traffic on that 3;100 target. I told the trainee in debrief his very first call should have been maintain 2;500 then identify for radar and then answer hio. I should have over keyed and done this myself; because they literally passed about 100 feet over top of this guy and felt we had almost no control over the situation other than watch an aircraft depart in an unprotected dangerous hotspot area well known for busy VFR traffic that are most [of] the time flying clueless wherever they want because it's easier than calling us for a safer flight; but maybe slightly sent off course so people don't die. Just like how we need the pdx charlie to be up to 7;000 because our rnavs depart to 7;000 and not guaranteed to call us to stop them in [the] event someone gets in the way. The hio airport area needs some sort of protection as well; or the charlie needs to be extended more than 10 miles to cover hio.
Original NASA ASRS Text
Title: P80 Controller reported an aircraft departing HIO; on initial contact; was in conflict with non-participating VFR traffic. The Controller reported this as a frequent issue.
Narrative: I think this happened towards earlier part of the session. Was training. Aircraft X was released on a BERNI RNAV departure. Prior to being airborne; a VFR started flying south of HIO westbound 3;100; Aircraft X climbing to 4;000. Aircraft X called at 1;600 non RADAR and we gave traffic but had very limited options being climbing fast and just getting ahold of them. Aircraft X got them inside maybe a mile or 2 prior to crossing over top of the VFR by maybe 100 feet. Was very close and very dangerous with the VFR deciding to fly over a hot spot area barely above HIO airspace. Very similar issue as we have with VFRs getting in the way on purpose through our arrivals and departures because people don't want to give us a modified Charlie airspace to protect our RNAV departures and arrivals. We were training; and this got very close.I had another instance almost exactly like this that I stopped them at 3;000 for a primary; not in Tower's airspace; and was lucky they were at 3;500 when the departure got them in sight telling me it was a good call to stop them at 3;000 right away when they checked on. HIO called and distracted my trainee before calling traffic. All they were telling us is they did not give traffic on that 3;100 target. I told the trainee in debrief his very first call should have been maintain 2;500 then IDENT for radar and then answer HIO. I should have over keyed and done this myself; because they literally passed about 100 feet over top of this guy and felt we had almost no control over the situation other than watch an aircraft depart in an unprotected dangerous hotspot area well known for busy VFR traffic that are most [of] the time flying clueless wherever they want because it's easier than calling us for a safer flight; but maybe slightly sent off course so people don't die. Just like how we need the PDX Charlie to be up to 7;000 because our RNAVs depart to 7;000 and not guaranteed to call us to stop them in [the] event someone gets in the way. The HIO airport area needs some sort of protection as well; or the Charlie needs to be extended more than 10 miles to cover HIO.
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.