Go-around — SWA1880

SWA1880 (Bank of Utah) was operating from KGEG to KDEN on 2026-07-10. SkyMeter detected a go-around at Denver International Airport (KDEN) on runway 16R at 23:10 UTC. Trace data at the event: 5813 ft AGL, 176 kt GS. METAR at the time reported 4 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.

• SECURITY6/4158 2026-06-01 06:00Z – 2026-07-21 05:59Z SFC–400 ft

  MERIDIAN, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Boise, ID, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Sandy, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Salt Lake City, UT, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 2026 UTC

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

  37NM SW GRANGEVILLE, ID, Saturday, June 27, 2026 through Sunday, July 12, 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/2268 2026-07-01 13:00Z – 2026-07-14 03:00Z SFC–14,500 ft

  27NM SE JACKSON, WY, Wednesday, July 1, 2026 through Tuesday, July 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2576 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft

  38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2586 2026-07-02 13:00Z – 2026-07-16 02:00Z SFC–10,000 ft

  38NM SW GRANGEVILLE, ID, Thursday, July 2, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7864 2026-07-03 15:07Z – 2026-07-21 05:59Z SFC–400 ft

  Sandy, UT

  View FAA NOTAM →
• SECURITY6/7862 2026-07-03 16:07Z – 2026-07-21 05:59Z SFC–400 ft

  Salt Lake City, UT

  View FAA NOTAM →
• SECURITY6/3018 2026-07-06 14:00Z – 2026-07-10 23:00Z SFC–400 ft

  Provo, UT, Monday, July 6, 2026 through Friday, July 10, 2026 Local

  View FAA NOTAM →
• SECURITY6/3019 2026-07-07 14:00Z – 2026-07-13 03:00Z SFC–400 ft

  Sun Valley, ID, Tuesday, July 7, 2026 through Sunday, July 12, 2026 Local

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

  17NM NE WINNEMUCCA, NV, Tuesday, July 7, 2026 through Tuesday, July 21, 2026 UTC

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

  4NM NE BOISE, ID, Wednesday, July 8, 2026 through Wednesday, July 22, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7869 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Meridian, ID

  View FAA NOTAM →
• SECURITY6/7871 2026-07-09 11:07Z – 2026-07-21 05:59Z SFC–400 ft

  Boise, ID

  View FAA NOTAM →
• HAZARDS6/4268 2026-07-09 14:00Z – 2026-07-16 04:00Z SFC–12,000 ft

  24NM S ELKO, NV, Thursday, July 9, 2026 through Thursday, July 16, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4402 2026-07-09 19:27Z – 2026-07-11 04:00Z SFC–10,500 ft

  86NM NE ELKO, NV, Thursday, July 9, 2026 through Saturday, July 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4555 2026-07-10 14:00Z – 2026-07-23 04:00Z SFC–10,500 ft

  44NM NE WELLS, NV, Friday, July 10, 2026 through Thursday, July 23, 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