Go-around — UAL1436

UAL1436 (United Airlines) was inbound to KDEN on 2026-08-24. SkyMeter detected a go-around at Denver International Airport (KDEN) on runway 35R at 23:18 UTC. Trace data at the event: 5535 ft AGL, 183 kt GS. METAR at the time reported 12 kt wind, 4 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/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/5136 2026-08-14 22:00Z – 2026-08-29 04:00Z SFC–10,000 ft

  10NM E HAMILTON, MT, Friday, August 14, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5460 2026-08-17 12:00Z – 2026-08-30 04:00Z SFC–10,500 ft

  9NM SW HAMILTON, MT, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

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

  20NM NE SALT LAKE CITY, UT, Monday, August 17, 2026 through Sunday, August 30, 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 →
• HAZARDS6/6728 2026-08-20 13:00Z – 2026-08-27 03:00Z SFC–14,500 ft

  8NM N ASPEN, CO, Thursday, August 20, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6599 2026-08-20 13:00Z – 2026-09-03 03:00Z SFC–11,000 ft

  21NM SE HAMILTON, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6723 2026-08-20 14:00Z – 2026-09-03 04:00Z SFC–9,000 ft

  16NM E BIG TIMBER, MT, Thursday, August 20, 2026 through Thursday, September 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6954 2026-08-21 14:00Z – 2026-09-04 03:00Z SFC–11,000 ft

  33NM SW POCATELLO, ID, Friday, August 21, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7092 2026-08-22 13:00Z – 2026-09-04 03:00Z SFC–14,000 ft

  26NM SW PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7115 2026-08-22 23:30Z – 2026-09-04 03:00Z SFC–13,000 ft

  41NM E PRICE, UT, Saturday, August 22, 2026 through Friday, September 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7331 2026-08-24 01:00Z – 2026-08-25 04:00Z SFC–10,000 ft

  11NM SE HAMILTON, MT, Monday, August 24, 2026 through Tuesday, August 25, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7347 2026-08-24 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7337 2026-08-24 14:00Z – 2026-09-08 03:30Z SFC–10,000 ft

  11NM SE HAMILTON, MT, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7530 2026-08-24 17:00Z – 2026-09-06 03:00Z SFC–10,000 ft

  35NM SW PROVO, UT, Monday, August 24, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7591 2026-08-24 21:45Z – 2026-08-26 04:00Z SFC–12,500 ft

  34NM S HAMILTON, MT, Monday, August 24, 2026 through Wednesday, August 26, 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