Go-around — SWA410

SWA410 (UMB Bank NA) was operating from KSMF to KSLC on 2026-07-29. SkyMeter detected a go-around at Salt Lake City International Airport (KSLC) on runway 16R at 08:48 UTC. Trace data at the event: 4374 ft AGL, 169 kt GS. METAR at the time reported 11 kt wind, 3 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 →
• HAZARDS6/6221 2026-07-16 17:58Z – 2026-07-30 04:00Z SFC–12,000 ft

  9NM SE DUGWAY, UT, Thursday, July 16, 2026 through Thursday, July 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6388 2026-07-17 02:26Z – 2026-07-31 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6393 2026-07-17 02:30Z – 2026-07-31 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6434 2026-07-17 05:07Z – 2026-08-01 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6433 2026-07-17 05:08Z – 2026-08-01 04:00Z SFC–10,000 ft

  63NM NE REDDING, CA, Friday, July 17, 2026 through Saturday, August 1, 2026 UTC

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

  9NM SE DUGWAY, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6733 2026-07-19 12:00Z – 2026-08-02 04:00Z SFC–10,500 ft

  16NM NE SUSANVILLE, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6774 2026-07-19 18:27Z – 2026-08-02 04:00Z SFC–10,500 ft

  22NM NE SUSANVILLE, CA, Sunday, July 19, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7245 2026-07-21 03:43Z – 2026-08-04 03:30Z SFC–7,000 ft

  9NM NW GRASS VALLEY DISPATCH CENTER, CA, Tuesday, July 21, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7854 2026-07-22 17:23Z – 2026-08-05 04:00Z SFC–7,000 ft

  9NM NW GRASS VALLEY DISPATCH CENTER, CA, Wednesday, July 22, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8487 2026-07-25 01:02Z – 2026-08-08 04:00Z SFC–10,500 ft

  12NM NE SUSANVILLE, CA, Saturday, July 25, 2026 through Saturday, August 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8875 2026-07-27 14:00Z – 2026-08-04 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Monday, July 27, 2026 through Tuesday, August 4, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8928 2026-07-27 14:00Z – 2026-08-05 04:00Z SFC–12,500 ft

  14NM NE AUSTIN, NV, Monday, July 27, 2026 through Wednesday, August 5, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9397 2026-07-28 01:03Z – 2026-08-11 04:00Z SFC–5,000 ft

  9NM NW GRASS VALLEY, CA, Tuesday, July 28, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9393 2026-07-28 14:00Z – 2026-08-11 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Tuesday, July 28, 2026 through Tuesday, August 11, 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