 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pdx controller expressed concern regarding the close proximity of vuo traffic pattern and continued conflicts with pdx traffic.
| Attributes | |
| ACN | 688395 |
| Time | |
| Date | 200602 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : pdx.airport |
| State Reference | OR |
| Altitude | msl single value : 1000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : pdx.tower |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach |
| Route In Use | approach : visual |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Route In Use | approach : traffic pattern |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : radar |
| Experience | controller limited radar : 10.5 controller radar : 8.5 controller time certified in position1 : 9 controller time certified in position2 : 8 |
| ASRS Report | 688395 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : airborne less severe other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Airport Airspace Structure |
| Primary Problem | Airspace Structure |
| Situations | |
| ATC Facility | procedure or policy : pdx.tower |
| Airport | procedure or policy : pdx.airport |
| Airspace Structure | class c : pdx.c |
Narrative:
A B737 on 3 mile final to runway 10R at pdx. Other aircraft was in the pattern at vuo. Vuo aircraft not talking to any controller. I called that traffic to B737 and they said it was 'in sight.' the pilot then stated; 'that is really dangerous;' referring to arrs to pdx getting too close to vuo uncontrolled traffic. The B737 pilot then said he had an 'RA' situation with another vuo aircraft when he was inbound to pdx two weeks ago. I have observed numerous 'RA' and 'close calls' with our traffic and vuo aircraft over the years. An especially dangerous scenario is when the vuo traffic pattern is runway 26 and pdx is arriving to runways 10R and 10L. The ILS runway approach practically flies through the vuo pattern. My solution would be to close vuo to prevent the near midair collision that may happen in the future.
Original NASA ASRS Text
Title: PDX CTLR EXPRESSED CONCERN REGARDING THE CLOSE PROXIMITY OF VUO TFC PATTERN AND CONTINUED CONFLICTS WITH PDX TFC.
Narrative: A B737 ON 3 MILE FINAL TO RWY 10R AT PDX. OTHER ACFT WAS IN THE PATTERN AT VUO. VUO ACFT NOT TALKING TO ANY CTLR. I CALLED THAT TFC TO B737 AND THEY SAID IT WAS 'IN SIGHT.' THE PLT THEN STATED; 'THAT IS REALLY DANGEROUS;' REFERRING TO ARRS TO PDX GETTING TOO CLOSE TO VUO UNCTLED TFC. THE B737 PLT THEN SAID HE HAD AN 'RA' SITUATION WITH ANOTHER VUO ACFT WHEN HE WAS INBOUND TO PDX TWO WEEKS AGO. I HAVE OBSERVED NUMEROUS 'RA' AND 'CLOSE CALLS' WITH OUR TFC AND VUO ACFT OVER THE YEARS. AN ESPECIALLY DANGEROUS SCENARIO IS WHEN THE VUO TFC PATTERN IS RWY 26 AND PDX IS ARRIVING TO RWYS 10R AND 10L. THE ILS RWY APCH PRACTICALLY FLIES THROUGH THE VUO PATTERN. MY SOLUTION WOULD BE TO CLOSE VUO TO PREVENT THE NMAC THAT MAY HAPPEN IN THE FUTURE.
Data retrieved from NASA's ASRS site as of January 2009 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.