Go-around — UAL1989

UAL1989 (United Airlines) was inbound to KORD on 2026-08-19. SkyMeter detected a go-around at Chicago O'Hare International Airport (KORD) on runway 09L at 21:28 UTC. Trace data at the event: 943 ft AGL, 148 kt GS. METAR at the time reported 12 kt wind, 8 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/2313 2026-08-05 20:36Z – 2026-08-20 04:00Z SFC–13,000 ft

  34NM SW BUTTE, MT, Wednesday, August 5, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2488 2026-08-06 14:00Z – 2026-08-20 05:00Z SFC–13,500 ft

  28NM W AFTON, WY, Thursday, August 6, 2026 through Thursday, August 20, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2761 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft

  10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2829 2026-08-07 14:00Z – 2026-08-22 03:30Z SFC–12,000 ft

  10NM SE LIVINGSTON, MT, Friday, August 7, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2917 2026-08-08 14:00Z – 2026-08-22 05:00Z SFC–13,500 ft

  20NM E AFTON, WY, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3041 2026-08-08 17:46Z – 2026-08-23 04:00Z SFC–13,000 ft

  36NM SW BUTTE, MT, Saturday, August 8, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3042 2026-08-08 18:30Z – 2026-08-22 04:00Z SFC–12,000 ft

  1NM E GRACE, ID, Saturday, August 8, 2026 through Saturday, August 22, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3102 2026-08-09 12:00Z – 2026-08-23 04:00Z SFC–12,000 ft

  56NM E HELENA, MT, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3098 2026-08-09 14:00Z – 2026-08-23 04:00Z SFC–12,000 ft

  1NM E GRACE, ID, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3118 2026-08-09 14:00Z – 2026-08-23 04:00Z SFC–12,000 ft

  1NM E GRACE, ID, Sunday, August 9, 2026 through Sunday, August 23, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3161 2026-08-10 12:00Z – 2026-08-25 03:30Z SFC–16,000 ft

  13NM SE LANDER, WY, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3618 2026-08-10 22:20Z – 2026-08-25 04:00Z SFC–13,000 ft

  36NM SW BUTTE, MT, Monday, August 10, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4088 2026-08-12 00:39Z – 2026-08-27 04:00Z SFC–13,000 ft

  36NM SW BUTTE, MT, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4089 2026-08-12 12:00Z – 2026-08-27 03:30Z SFC–15,000 ft

  2NM SE LANDER, WY, Wednesday, August 12, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4893 2026-08-13 13:00Z – 2026-08-28 03:00Z SFC–9,000 ft

  43NM E HOT SPRINGS, SD, Thursday, August 13, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5929 2026-08-18 12:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  36NM SW BUTTE, MT, Tuesday, August 18, 2026 through Monday, August 31, 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