Device: Samsung Galaxy S24 FE
Operating system: Android 16, One UI 8.5
An automatic system warning detected another aircraft as being on final for Runway 28L shortly after I touched down on Runway 28L at KSFO. Interestingly, the warning did not appear while I was still on the short final or before touchdown. After I had slowed down sufficiently and opened the map, I noticed that the warning appeared to have been triggered by another aircraft approaching the same runway, Runway 28L. However, the aircraft was still relatively far away, approximately 11+ NM from the approach end of the runway/glideslope.
I am not certain whether other users are able to reproduce this issue, but it may be worth testing at the same location, specifically Runway 28L at KSFO. One possible factor could be the relatively close proximity of the parallel Runway 28R, which may potentially cause the system to incorrectly identify or associate an aircraft on approach.
This issue is relatively minor, but it can be somewhat confusing for pilots when the warning appears only after touchdown despite there being no corresponding warning during the approach.
Reproduction location:
KSFO, Runway 28L
Observed behavior:
The aircraft-on-final warning appeared shortly after touchdown, even though no warning was displayed while I was on short final. The system appeared to identify another aircraft approximately 11+ NM away as being on final for the same runway.
Expected behavior:
The warning should be triggered consistently when another aircraft is detected on final for the same runway, with appropriate timing and runway identification. Like below 7-10 nm in the localizer.
