SFO Tower Controller reported an airborne conflict with arrivals inbound to 28L and 28R.

Date: 2022-08 · Aircraft: Commercial Fixed Wing · Phase: approach

Anomalies: atc-issue-all-types|deviation-altitude-overshoot|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit

Synopsis

SFO Tower Controller reported an airborne conflict with arrivals inbound to 28L and 28R.

Narrative

I was working Local Assist and CIC (Controller in Charge) concurrently. Aircraft X was on a visual approach to Runway 28 Left; unknown if Tipp Toe or just visual. Aircraft Y was on a visual approach to Runway 28 Right; unknown if FMS Bridge or down the bay. Aircraft X Low Altitude Alert went off; and I waited for finals to call me then acknowledged their coordination. When I went by to monitoring Local Control; Aircraft X said they had a 'TA'. This made no sense to me as a TA would not drive them down towards the surface. I had Local confirm it was an 'R'. Yes it was; and Local had asked them their intention and the crew said continue the approach.I am not sure how to rid the NAS of the seemingly nuisance RA's with our closely spaced parallel runways. I am pretty sure no [committee] could mitigate the risks down to allow for the current design of SFO Airport to get off of the drafting table. With that said; we have what we have to work with; and it isn't much. I know asking all arrivals to go TA only at some point leaves everyone vulnerable should an actual mid collision occur; and it were to hit the media. We could not really explain that one away.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.