Go-around — UAL1604

UAL1604 (United Airlines) was operating from KSFO to KDEN on 2026-06-30. SkyMeter detected a go-around at Denver International Airport (KDEN) on runway 16R at 20:02 UTC. Trace data at the event: 5816 ft AGL, 174 kt GS. METAR at the time reported 11 kt wind, 5 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/3475 2026-03-08 09:00Z – 2026-11-01 09:59Z SFC–180 ft

  BEALE AFB, CA, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• SECURITY6/5797 2026-04-03 00:01Z – 2026-09-28 23:59Z SFC–400 ft

  SACRAMENTO, CA, Thursday, April 2, 2026 through Monday, September 28, 2026 Local

  View FAA NOTAM →
• SECURITY6/4061 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  BERKLEY, CA, Monday, June 1, 2026 through Tuesday, July 21, 2026 Local

  View FAA NOTAM →
• SECURITY6/4060 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Oakland, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/9412 2026-06-20 17:53Z – 2026-07-03 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 20, 2026 through Friday, July 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9460 2026-06-21 14:00Z – 2026-07-04 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Sunday, June 21, 2026 through Saturday, July 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9981 2026-06-23 13:28Z – 2026-07-07 15:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9985 2026-06-23 13:54Z – 2026-07-07 15:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0134 2026-06-23 17:52Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Tuesday, June 23, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0277 2026-06-24 12:00Z – 2026-07-08 04:00Z SFC–12,000 ft

  2NM S RIFLE, CO, Wednesday, June 24, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0416 2026-06-24 14:54Z – 2026-07-07 04:00Z SFC–13,500 ft

  3NM E BEAVER, UT, Wednesday, June 24, 2026 through Tuesday, July 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1019 2026-06-26 23:25Z – 2026-07-08 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Friday, June 26, 2026 through Wednesday, July 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1053 2026-06-27 14:00Z – 2026-07-11 04:00Z SFC–15,000 ft

  21NM NW BLANDING, UT, Saturday, June 27, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1072 2026-06-27 14:12Z – 2026-07-10 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1074 2026-06-27 14:41Z – 2026-07-10 04:00Z SFC–11,000 ft

  7NM S SCIPIO, UT, Saturday, June 27, 2026 through Friday, July 10, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1130 2026-06-28 06:00Z – 2026-07-12 04:00Z SFC–12,500 ft

  22NM N CORTEZ, CO, Sunday, June 28, 2026 through Sunday, July 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1178 2026-06-28 13:31Z – 2026-07-13 04:00Z SFC–17,000 ft

  2NM N OURAY, CO, Sunday, June 28, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1144 2026-06-28 14:00Z – 2026-07-11 04:00Z SFC–11,000 ft

  27NM SW PROVO, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1220 2026-06-28 16:15Z – 2026-07-11 04:00Z SFC–15,500 ft

  3NM E BEAVER, UT, Sunday, June 28, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1335 2026-06-29 01:32Z – 2026-07-13 04:00Z SFC–12,000 ft

  6NM S SCIPIO, UT, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1333 2026-06-29 03:06Z – 2026-07-13 04:00Z SFC–17,000 ft

  8NM SW LEADVILLE, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1310 2026-06-29 12:00Z – 2026-07-13 04:00Z SFC–17,000 ft

  2NM N OURAY, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1324 2026-06-29 12:00Z – 2026-07-13 05:00Z SFC–13,000 ft

  18NM N CORTEZ, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1334 2026-06-29 12:00Z – 2026-07-13 04:00Z SFC–12,000 ft

  25NM W GRAND JUNCTION, CO, Monday, June 29, 2026 through Monday, July 13, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1416 2026-06-29 14:37Z – 2026-07-14 04:00Z SFC–13,500 ft

  15NM NW CAÑON CITY, CO, Monday, June 29, 2026 through Tuesday, July 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1726 2026-06-29 22:46Z – 2026-07-02 04:00Z SFC–12,000 ft

  19NM N LINCOLN COUNTY, NV, Monday, June 29, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1727 2026-06-29 22:51Z – 2026-07-02 04:00Z SFC–12,000 ft

  19NM N LINCOLN COUNTY, NV, Monday, June 29, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1775 2026-06-30 06:00Z – 2026-07-14 04:00Z SFC–15,000 ft

  4NM SW PUEBLO, CO, Tuesday, June 30, 2026 through Tuesday, July 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/1778 2026-06-30 14:00Z – 2026-07-13 04:00Z SFC–16,000 ft

  16NM W MONTICELLO, UT, Tuesday, June 30, 2026 through Monday, July 13, 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