37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1474499 |
Time | |
Date | 201708 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | S46.TRACON |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Learjet 31 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2.6 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
I was working arrival sectors combined. It was a busy and complex session with numerous arrivals; lots of VFR targets; practice approaches in and through my airspace. Aircraft X checked in on frequency descending for bfi and I already knew that I would be issuing many traffic advisories thanks to how many I had to issue to the preceding bfi arrival. Once I got aircraft X down to 2200 feet and in a position to turn towards bfi I scanned and saw a couple of VFR targets that might conflict with the base turn. Aircraft X had reported one of them in sight previously on the descent; so I asked if he still had the traffic in sight; but he did not. Instead of creating a direct conflict with the vfrs; I elected to give aircraft X a left 360 to bring him back to the final approach course. This abnormal maneuver was caused by the presence of VFR aircraft in proximity to the bfi arrivals. Aircraft X landed without incident.while the VFR targets in proximity to aircraft X were further away from the final approach fix than some of my previous reports; they are still transiting a very busy segment of our airspace at altitudes which put them in direct conflict with our IFR arrival traffic to bfi. This was not a slow moving VFR aircraft either. The target was at 2000 feet and showing 200 knots groundspeed on the radar. I later observed the target enter pae's class D airspace and was able to ask the tower controller for a callsign and type which was a [high performance aircraft].something needs to change. The VFR aircraft are transiting a very narrow; busy corridor of airspace and are doing so without any communication with ATC. It is simply unsafe. The VFR aircraft in this area at the very least need to be in communication with ATC so that we can assign; as necessary; altitude restrictions ensuring the safety of all the aircraft involved. The solutions are not hard and while they are potentially more restrictive to VFR aircraft the bottom line is that what happens day in and day out in that airspace as it exists and operates now will eventually result in a very bad accident.
Original NASA ASRS Text
Title: Air Traffic Controller reported the need to vector an aircraft off the final approach course to avoid fast moving VFR traffic in the area of Boeing Field .
Narrative: I was working Arrival sectors combined. It was a busy and complex session with numerous arrivals; lots of VFR targets; practice approaches in and through my airspace. Aircraft X checked in on frequency descending for BFI and I already knew that I would be issuing many traffic advisories thanks to how many I had to issue to the preceding BFI arrival. Once I got Aircraft X down to 2200 feet and in a position to turn towards BFI I scanned and saw a couple of VFR targets that might conflict with the base turn. Aircraft X had reported one of them in sight previously on the descent; so I asked if he still had the traffic in sight; but he did not. Instead of creating a direct conflict with the VFRs; I elected to give Aircraft X a left 360 to bring him back to the final approach course. This abnormal maneuver was caused by the presence of VFR aircraft in proximity to the BFI arrivals. Aircraft X landed without incident.While the VFR targets in proximity to Aircraft X were further away from the Final Approach fix than some of my previous reports; they are still transiting a very busy segment of our airspace at altitudes which put them in direct conflict with our IFR arrival traffic to BFI. This was not a slow moving VFR aircraft either. The target was at 2000 feet and showing 200 knots groundspeed on the radar. I later observed the target enter PAE's Class D airspace and was able to ask the tower controller for a callsign and type which was a [high performance aircraft].Something needs to change. The VFR aircraft are transiting a very narrow; busy corridor of airspace and are doing so without any communication with ATC. It is simply unsafe. The VFR aircraft in this area at the very least need to be in communication with ATC so that we can assign; as necessary; altitude restrictions ensuring the safety of all the aircraft involved. The solutions are not hard and while they are potentially more restrictive to VFR aircraft the bottom line is that what happens day in and day out in that airspace as it exists and operates now will eventually result in a very bad accident.
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.