Narrative:

I flew to sfo. We were cleared the RNAV bridge visual to runway 28R. During our step down and eventual clearance for the approach; a B737 was to follow us on runway 28L. After our handoff from norcal to sfo tower we were cleared to land runway 28R. Our B737 traffic was still behind us for runway 28L. At about 800 ft. On profile for 28R we noticed traffic B737 below us on TCAS. At the same time we received a climb RA from the TCAS. Unaware of what was below us; we followed the climb RA as SOP per fom; 'if a climb RA is encountered while in landing configuration; execute a go-around'. After our TCAS RA maneuver and 'adjust vertical speed'; we were not in a position to return to the approach and have stabilized approach criteria. I was flying the aircraft and decided the safest course of action was to execute a go around. The go-around profile was a combination of a TCAS RA maneuver and a go-around maneuver. Based on the altitude that we initiated the TCAS RA maneuver and then decided to go around; I found myself in-between two maneuvers; not something that I have ever done before. We were cleared runway heading to 3;000 ft then to 4;000 ft. We were vectored on a downwind to 28L. We landed without any other incident and taxied to our gate. The tower informed me that no aircraft was below me on approach to runway 28R. I'm aware of our [company's recommendation] about 'TCAS alerts use of TA mode is recommended while performing simultaneous parallel approaches to prevent unnecessary RA's. See fom operating information chapter.' that said; our traffic was below us; not off our wing on a simultaneous approach. There is a difference. We acted in the safest manner possible. I have flown this approach many times; and have never seen this before. Our flight attendants told my first officer (first officer) and I that passengers said they saw an aircraft below us. If it was the B737 in trail or another aircraft; I don't know.

Related reports:

Google
 

Original NASA ASRS Text

Title: Air carrier Captain reported a TCAS RA while on short final at SFO. The Captain elected to execute a go-around.

Narrative: I flew to SFO. We were cleared the RNAV Bridge Visual to runway 28R. During our step down and eventual clearance for the approach; a B737 was to follow us on runway 28L. After our handoff from NORCAL to SFO tower we were cleared to land runway 28R. Our B737 traffic was still behind us for Runway 28L. At about 800 ft. on profile for 28R we noticed traffic B737 below us on TCAS. At the same time we received a Climb RA from the TCAS. Unaware of what was below us; we followed the climb RA as SOP per FOM; 'If a climb RA is encountered while in landing configuration; execute a go-around'. After our TCAS RA maneuver and 'adjust vertical speed'; we were not in a position to return to the approach and have stabilized approach criteria. I was flying the aircraft and decided the safest course of action was to execute a go around. The go-around profile was a combination of a TCAS RA maneuver and a go-around maneuver. Based on the altitude that we initiated the TCAS RA maneuver and then decided to go around; I found myself in-between two maneuvers; not something that I have ever done before. We were cleared runway heading to 3;000 ft then to 4;000 ft. We were vectored on a downwind to 28L. We landed without any other incident and taxied to our gate. The Tower informed me that no aircraft was below me on approach to runway 28R. I'm aware of our [company's recommendation] about 'TCAS Alerts Use of TA mode is recommended while performing simultaneous parallel approaches to prevent unnecessary RA's. See FOM Operating Information chapter.' That said; our traffic was below us; not off our wing on a simultaneous approach. There is a difference. We acted in the safest manner possible. I have flown this approach many times; and have never seen this before. Our flight attendants told my FO (First Officer) and I that passengers said they saw an aircraft below us. If it was the B737 in trail or another aircraft; I don't know.

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.