Go-around — UAL2077

UAL2077 (United Airlines) was operating from KEUG to KSFO on 2026-07-30. SkyMeter detected a go-around at San Francisco International Airport (KSFO) on runway 28L at 23:07 UTC. Trace data at the event: 339 ft AGL, 137 kt GS, 0 fpm vertical. METAR at the time reported 19 kt wind, 9 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.

• HAZARDS6/6363 2026-07-17 01:54Z – 2026-07-31 04:00Z SFC–8,000 ft

  20NM NW MEDFORD, OR, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6741 2026-07-19 12:00Z – 2026-08-02 04:00Z SFC–6,500 ft

  7NM NE REDDING, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7914 2026-07-22 18:44Z – 2026-08-05 04:00Z SFC–7,000 ft

  20NM NW MEDFORD, OR, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8326 2026-07-24 00:00Z – 2026-08-05 05:00Z SFC–10,000 ft

  35NM E ROSEBURG, OR, Friday, July 24, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8423 2026-07-24 16:00Z – 2026-08-07 04:00Z SFC–9,500 ft

  35NM SE ROSEBURG, OR, Friday, July 24, 2026 through Friday, August 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9403 2026-07-28 13:00Z – 2026-08-10 03:00Z SFC–7,000 ft

  20NM NW MEDFORD, OR, Tuesday, July 28, 2026 through Monday, August 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9888 2026-07-29 13:00Z – 2026-08-12 03:00Z SFC–6,000 ft

  20NM NW MEDFORD, OR, Wednesday, July 29, 2026 through Wednesday, August 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.

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