Go-around — UAL718
KSFO · 28L2026-08-31 18:22 UTC· UNITED AIRLINES INC· A320
UAL718 (United Airlines) was inbound to KSFO on 2026-08-31. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 18:22 UTC. Trace data at the event: 492 ft AGL, 129 kt GS, 0 fpm vertical. METAR at the time reported 10 kt wind, 6 kt crosswind component, 16,093 m visibility. A go-around is a discontinued landing approach in which the pilot adds power and climbs back to a safe altitude before re-attempting the approach or proceeding to an alternate. It is a routine safety response, not an emergency, and is taught as the standard reaction to any unstable approach. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft
Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local
View FAA NOTAM → - SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft
El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local
View FAA NOTAM → - HAZARDS6/7718 2026-08-25 14:00Z – 2026-09-08 04:00Z SFC–8,000 ft
4.5 NM NE BAGDAD, AZ, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/8070 2026-08-26 03:00Z – 2026-09-10 03:00Z SFC–8,500 ft
8NM SE BIG SUR, CA, Wednesday, August 26, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8454 2026-08-26 21:15Z – 2026-09-09 03:00Z SFC–7,500 ft
20NM SW KING CITY, CA, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - HAZARDS6/8493 2026-08-27 13:00Z – 2026-09-10 03:00Z SFC–8,000 ft
20NM SW KING CITY, CA, Thursday, August 27, 2026 through Thursday, September 10, 2026 UTC
View FAA NOTAM → - HAZARDS6/8735 2026-08-28 13:00Z – 2026-09-13 03:00Z SFC–8,000 ft
20NM SW KING CITY, CA, Friday, August 28, 2026 through Sunday, September 13, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7555 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - UAS PUBLIC GATHERING6/7569 2026-08-29 01:00Z – 2026-09-02 06:59Z SFC–400 ft
Santa Clara, CA, Saturday, August 29, 2026 through Wednesday, September 2, 2026 UTC
View FAA NOTAM → - HAZARDS6/8902 2026-08-29 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft
20NM SW KING CITY, CA, Saturday, August 29, 2026 through Sunday, September 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/9187 2026-08-30 13:00Z – 2026-09-13 03:00Z SFC–8,500 ft
20NM SW KING CITY, CA, Sunday, August 30, 2026 through Sunday, September 13, 2026 UTC
View FAA NOTAM → - HAZARDS6/9161 2026-08-30 14:00Z – 2026-09-12 04:00Z SFC–13,000 ft
42NM SE SHOW LOW, AZ, Sunday, August 30, 2026 through Saturday, September 12, 2026 UTC
View FAA NOTAM →
SkyMeter cross-referenced this flight against FAA-published TFRs that were active during its window and within its geographic bounding box. Overlap doesn't necessarily mean violation — the aircraft may have been outside the TFR’s precise polygon or flying under air-traffic-control coordination.
Pilot review data
- Runway 28L
- 492 ft AGL at event
- 129 kt ground speed
- 0 fpm vertical
- 10 kt wind
- 6 kt crosswind component
- 16,093 m visibility
- KSFO 161156Z 21003KT 10SM FEW009 BKN021 15/12 A2991 RMK AO2 SLP127 T01500117 10161 20150 55003
Flight context
- UAL718
- United Airlines
- A320
- 2026-08-31 18:22 UTC
- KSFO runway 28L
Automated analysis. Events shown on this page (such as go-around, unstable approach, or runway events) are heuristic classifications produced by algorithms from publicly broadcast ADS-B data. They are intended to surface flights of interest for further review — they are not findings of fact, and they do not determine pilot fault, regulatory compliance, or the cause of any occurrence. Coverage gaps and sensor noise can affect accuracy. Only the relevant civil aviation authority or accident investigation body can make official determinations. How we detect events · Dispute or correct this data