![]()  | 
            37000 Feet | Browse and search NASA's Aviation Safety Reporting System  | 
            
                
  | 
        
| Attributes | |
| ACN | 321765 | 
| Time | |
| Date | 199511 | 
| Day | Sun | 
| Local Time Of Day | 0601 To 1200 | 
| Place | |
| Locale Reference | atc facility : slc | 
| State Reference | UT | 
| Altitude | msl bound lower : 6000 msl bound upper : 6000  | 
| Environment | |
| Flight Conditions | VMC | 
| Light | Daylight | 
| Aircraft 1 | |
| Controlling Facilities | tracon : slc | 
| Operator | common carrier : air carrier | 
| Make Model Name | Commercial Fixed Wing | 
| Operating Under FAR Part | Part 121 | 
| Flight Phase | cruise other | 
| Route In Use | enroute : on vectors | 
| Flight Plan | IFR | 
| Aircraft 2 | |
| Operator | general aviation : personal | 
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer | 
| Operating Under FAR Part | Part 91 | 
| Flight Phase | cruise other | 
| Route In Use | enroute : direct | 
| Flight Plan | VFR | 
| Person 1 | |
| Affiliation | company : air carrier | 
| Function | flight crew : captain oversight : pic  | 
| Qualification | pilot : atp | 
| Experience | flight time last 90 days : 180 flight time total : 15000 flight time type : 180  | 
| ASRS Report | 321765 | 
| Person 2 | |
| Affiliation | company : air carrier | 
| Function | flight crew : first officer | 
| Qualification | pilot : commercial pilot : instrument  | 
| Events | |
| Anomaly | conflict : airborne less severe | 
| Independent Detector | other flight crewa | 
| Resolutory Action | none taken : anomaly accepted | 
| Consequence | faa : reviewed incident with flight crew | 
| Miss Distance | vertical : 500 | 
| Supplementary | |
| Primary Problem | ATC Human Performance | 
| Air Traffic Incident | other | 
Narrative:
Air carrier X was on a right downwind, for a visual approach to runway 16L. At slc a light aircraft was observed northwest of the airport, on a 090 degree heading. This aircraft passed under us, as we turned base. After landing, I telephoned the tower to find out why I wasn't notified of the traffic. They informed me that there is a VFR corridor, north of the airport, running e-w. They also said that several aircraft on final had to execute missed approachs due to TCASII 'RA' advisories. This is not a good area for a VFR corridor. The tower should be required to point out traffic before clearing an aircraft for a visual.
Original NASA ASRS Text
Title: ACR HAD CONFLICT WITH VFR ACFT IN CLASS B AIRSPACE.
Narrative: ACR X WAS ON A R DOWNWIND, FOR A VISUAL APCH TO RWY 16L. AT SLC A LIGHT ACFT WAS OBSERVED NW OF THE ARPT, ON A 090 DEG HDG. THIS ACFT PASSED UNDER US, AS WE TURNED BASE. AFTER LNDG, I TELEPHONED THE TWR TO FIND OUT WHY I WASN'T NOTIFIED OF THE TFC. THEY INFORMED ME THAT THERE IS A VFR CORRIDOR, N OF THE ARPT, RUNNING E-W. THEY ALSO SAID THAT SEVERAL ACFT ON FINAL HAD TO EXECUTE MISSED APCHS DUE TO TCASII 'RA' ADVISORIES. THIS IS NOT A GOOD AREA FOR A VFR CORRIDOR. THE TWR SHOULD BE REQUIRED TO POINT OUT TFC BEFORE CLRING AN ACFT FOR A VISUAL.
Data retrieved from NASA's ASRS site as of July 2007 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.