Go-around — UAL436

UAL436 (United Airlines) was inbound to KSFO on 2026-06-07. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28R at 02:59 UTC. Trace data at the event: 371 ft AGL, 131 kt GS, 0 fpm vertical. METAR at the time reported 10 kt wind, 3 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.

• SECURITY6/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

  View FAA NOTAM →
• HAZARDS6/3889 2026-05-28 22:59Z – 2026-06-10 04:00Z SFC–10,500 ft

  11NM SE SPANISH FORK, UT, Thursday, May 28, 2026 through Wednesday, June 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3574 2026-05-29 14:00Z – 2026-06-10 02:00Z SFC–13,000 ft

  38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3888 2026-05-29 14:00Z – 2026-06-10 04:00Z SFC–13,000 ft

  38NM SE TWIN FALLS, ID, Friday, May 29, 2026 through Wednesday, June 10, 2026 UTC

  View FAA NOTAM →
• SECURITY6/4164 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4167 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4054 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  San Jose, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/5894 2026-06-05 20:31Z – 2026-06-19 02:00Z SFC–10,000 ft

  38NM SE TWIN FALLS, ID, Friday, June 5, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5936 2026-06-06 03:00Z – 2026-06-19 02:00Z SFC–7,500 ft

  27NM SE TWIN FALLS, ID, Saturday, June 6, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• SECURITY6/5786 2026-06-07 00:01Z – 2026-06-07 07:00Z SFC–400 ft

  BOULDER, CO, Saturday, June 6, 2026 Local

  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.

All events on this flight

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