37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1486646 |
Time | |
Date | 201710 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | SFO.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 17.8 |
Events | |
Anomaly | ATC Issue All Types Inflight Event / Encounter Other / Unknown |
Narrative:
Aircraft X and aircraft Y were paired almost exactly side by side for the right and left runways. There was a heavy B777 that had preceded both to the left runway; with a southwest wind. Aircraft X announced they were 'on the go.' I gave standard missed approach instructions; heading 280 and 3;000 feet. Once they had read back and were climbing; I inquired if it was for a TCAS RA for the parallel traffic; since it could have easily been for wake turbulence. They keyed up with some sort of mechanical voice I am not familiar with in the background and said yes; it was a TCAS RA.after coordinating with TRACON for the go around; I resumed working traffic. I eventually called over to the ramp where company of aircraft Y parks and asked the ramp controller to confirm a coordinated TCAS occurred with aircraft Y. Aircraft Y pilot said they did not have an RA. I guess if one (below) is in TA mode; the one on top could still get the RA and climb. I do not have a suggestion; as I am not certain myself or any other controller fully understands how the TCAS beast exists in our national airspace system (NAS).
Original NASA ASRS Text
Title: A Tower Controller reported an aircraft initiated a go-around due to a TCAS/RA it received for parallel runway traffic that it had in sight.
Narrative: Aircraft X and Aircraft Y were paired almost exactly side by side for the right and left runways. There was a heavy B777 that had preceded both to the left runway; with a southwest wind. Aircraft X announced they were 'on the go.' I gave standard missed approach instructions; heading 280 and 3;000 feet. Once they had read back and were climbing; I inquired if it was for a TCAS RA for the parallel traffic; since it could have easily been for wake turbulence. They keyed up with some sort of mechanical voice I am not familiar with in the background and said yes; it was a TCAS RA.After coordinating with TRACON for the go around; I resumed working traffic. I eventually called over to the ramp where company of Aircraft Y parks and asked the Ramp Controller to confirm a coordinated TCAS occurred with Aircraft Y. Aircraft Y pilot said they did not have an RA. I guess if one (below) is in TA mode; the one on top could still get the RA and climb. I do not have a suggestion; as I am not certain myself or any other controller fully understands how the TCAS beast exists in our National Airspace System (NAS).
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.