Go-around — UAL870

UAL870 (United Airlines) was operating from YSSY to KSFO on 2026-02-02. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 15:04 UTC. Trace data at the event: 1168 ft AGL, 145 kt GS. METAR at the time reported 1 kt wind, 1 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/8818 2016-03-23 15:38Z – 2027-10-18 11:03Z

  Special Notice, USA

  View FAA NOTAM →
• SECURITY0/0367 2020-01-15 00:01Z – 2027-10-18 11:03Z

  USA, Wednesday, January 15, 2020 UTC

  View FAA NOTAM →
• SPECIAL1/5060 2021-09-29 16:37Z – 2027-10-18 11:03Z SFC–999 ft

  USA, Wednesday, September 29, 2021 UTC

  View FAA NOTAM →
• SECURITY2/8783 2022-02-28 19:15Z – 2027-10-18 11:03Z

  USA, Monday, February 28, 2022 UTC

  View FAA NOTAM →
• SECURITY4/1789 2024-06-21 17:35Z – 2027-10-18 11:03Z

  USA, Friday, June 21, 2024 UTC

  View FAA NOTAM →
• SECURITY4/2565 2024-06-24 16:00Z – 2027-10-18 11:03Z

  USA, Monday, June 24, 2024 UTC

  View FAA NOTAM →
• SECURITY4/9433 2024-09-03 20:30Z – 2027-10-18 11:03Z

  USA, Tuesday, September 3, 2024 UTC

  View FAA NOTAM →
• SECURITY5/6874 2025-03-01 05:00Z – 2027-03-31 05:00Z

  USA, Saturday, March 1, 2025 through Wednesday, March 31, 2027 UTC

  View FAA NOTAM →
• SECURITY5/6914 2025-05-06 23:30Z – 2027-10-18 11:03Z SFC–6,000 ft

  South Padre Island, TX, Tuesday, May 6, 2025 Local

  View FAA NOTAM →
• SECURITY5/2787 2025-05-22 00:01Z – 2026-05-22 00:01Z SFC–6,000 ft

  S. FINEGAYAN, GU, Thursday, May 22, 2025 through Friday, May 22, 2026 Local

  View FAA NOTAM →
• SECURITY5/7224 2025-09-03 15:10Z – 2027-10-18 11:03Z

  WASHINGTON, DC, Wednesday, September 3, 2025 UTC

  View FAA NOTAM →
• SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

  Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• SECURITY5/6379 2025-10-29 14:30Z – 2027-10-29 14:30Z

  USA, Wednesday, October 29, 2025 through Friday, October 29, 2027 UTC

  View FAA NOTAM →
• SECURITY5/3402 2025-11-06 20:00Z – 2027-10-18 11:03Z

  USA, Thursday, November 6, 2025 UTC

  View FAA NOTAM →
• SECURITY5/0601 2025-11-30 19:00Z – 2026-05-31 18:59Z SFC–400 ft

  Los Angeles, CA, Sunday, November 30, 2025 through Sunday, May 31, 2026 Local

  View FAA NOTAM →
• SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

  OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 2026 Local

  View FAA NOTAM →
• SECURITY5/3678 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–2,000 ft

  Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

  View FAA NOTAM →
• SECURITY5/3679 2026-01-01 05:00Z – 2027-01-01 05:59Z SFC–5,000 ft

  Brownsville, TX, Thursday, January 1, 2026 through Friday, January 1, 2027 Local

  View FAA NOTAM →
• SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• HAZARDS6/2698 2026-01-19 09:00Z – 2026-12-18 21:00Z SFC–5,000 ft

  VIEQUES, PR, Monday, January 19, 2026 through Friday, December 18, 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.

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