Go-around — UAL2032

UAL2032 (United Airlines) was operating from KORD to CYEG on 2026-06-03. SkyMeter detected a go-around at Edmonton International Airport (CYEG) on runway 02 at 21:25 UTC. Trace data at the event: 2641 ft AGL, 167 kt GS. METAR at the time reported 5 kt wind, 5 kt crosswind component, 24,140 m visibility.

• HAZARDS6/2318 2026-05-22 14:00Z – 2026-06-05 04:00Z SFC–9,000 ft

  17NM SW HELENA, MT, Friday, May 22, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2646 2026-05-25 15:00Z – 2026-06-08 04:00Z SFC–11,000 ft

  22NM SE JACKSON, WY, Monday, May 25, 2026 through Monday, June 8, 2026 UTC

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

  32NM NW TWIN FALLS, ID, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3585 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

  74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/3649 2026-05-28 14:00Z – 2026-06-11 03:00Z SFC–9,000 ft

  74NM S MILES CITY, MT, Thursday, May 28, 2026 through Thursday, June 11, 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/3908 2026-05-29 14:00Z – 2026-06-12 04:00Z SFC–9,000 ft

  23NM SE GLENDIVE, MT, Friday, May 29, 2026 through Friday, June 12, 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 →
• HAZARDS6/4637 2026-06-02 13:00Z – 2026-06-05 03:00Z SFC–10,000 ft

  62NM NW GREEN RIVER, WY, Tuesday, June 2, 2026 through Friday, June 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4940 2026-06-02 14:18Z – 2026-06-09 23:30Z SFC–6,500 ft

  10NM NW ELY, MN, Tuesday, June 2, 2026 through Tuesday, June 9, 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.