 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Nct controller reported an air carrier responded to a TCAS RA for a VFR aircraft that had been instructed to maintain visual separation.
| Attributes | |
| ACN | 1370121 |
| Time | |
| Date | 201607 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | NCT.TRACON |
| State Reference | CA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Descent |
| Route In Use | VFR Route |
| Flight Plan | VFR |
| Person 1 | |
| Function | Approach Instructor |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.3 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict |
Narrative:
I was conducting OJT on mulford/grove combined sectors. Traffic was very heavy and very complex. My trainee issued to aircraft Y; which was aircraft X. Aircraft Y was VFR descending southbound towards rhv and about 25 miles southeast of oak at 5;500 feet. Aircraft X was inbound to oak coming in from the southeast and was issued a descent to 5;000 feet. Aircraft Y reported aircraft X 'in sight' and was told to maintain visual separation. The pilot acknowledged correctly. Aircraft X continued descending from 7;000 to about 6;000 and then said on frequency that he was responding to an RA and would 'level off at 6;000.' at this point; aircraft X was passing just over the top of aircraft Y.the sfo class bravo airspace does not protect the oak final airspace. This airspace needs to be redesigned so that VFR aircraft (whether talking to us or not) cannot fly through the path of inbound IFR traffic to oak. I feel that if TCAS were not being used; a midair collision would have already occurred in the oak final airspace. Please change the sfo class bravo airspace so that the oak final approach airspace is protected.
Original NASA ASRS Text
Title: NCT Controller reported an air carrier responded to a TCAS RA for a VFR aircraft that had been instructed to maintain visual separation.
Narrative: I was conducting OJT on Mulford/Grove combined sectors. Traffic was very heavy and very complex. My trainee issued to Aircraft Y; which was Aircraft X. Aircraft Y was VFR descending southbound towards RHV and about 25 miles southeast of OAK at 5;500 feet. Aircraft X was inbound to OAK coming in from the southeast and was issued a descent to 5;000 feet. Aircraft Y reported Aircraft X 'in sight' and was told to maintain visual separation. The pilot acknowledged correctly. Aircraft X continued descending from 7;000 to about 6;000 and then said on frequency that he was responding to an RA and would 'level off at 6;000.' At this point; Aircraft X was passing just over the top of Aircraft Y.The SFO Class Bravo airspace does not protect the OAK final airspace. This airspace needs to be redesigned so that VFR aircraft (whether talking to us or not) cannot fly through the path of inbound IFR traffic to OAK. I feel that if TCAS were not being used; a midair collision would have already occurred in the OAK final airspace. Please change the SFO Class Bravo airspace so that the OAK final approach airspace is protected.
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.