Go-around — SKW3488

SKW3488 (Skywest Airlines) was operating from KSAN to KSLC on 2026-07-31. SkyMeter detected a go-around at Salt Lake City International Airport (KSLC) on runway 16L at 01:12 UTC. Trace data at the event: 5074 ft AGL, 169 kt GS. METAR at the time reported 4 kt wind, 1 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/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

  Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/2652 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/4812 2026-07-15 07:00Z – 2027-07-14 06:59Z SFC–17,999 ft

  El Centro, CA, Wednesday, July 15, 2026 through Tuesday, July 13, 2027 Local

  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/6359 2026-07-17 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Friday, July 17, 2026 through Friday, July 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6569 2026-07-18 14:00Z – 2026-07-31 03:00Z SFC–15,500 ft

  5NM E BEAVER, UT, Saturday, July 18, 2026 through Friday, July 31, 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/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 →
• HAZARDS6/9567 2026-07-28 16:27Z – 2026-08-02 04:00Z SFC–8,500 ft

  YUCAIPA, CA, Tuesday, July 28, 2026 through Sunday, August 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9875 2026-07-29 12:00Z – 2026-08-03 04:00Z SFC–11,500 ft

  20NM W RICHFIELD, UT, Wednesday, July 29, 2026 through Monday, August 3, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9879 2026-07-29 14:00Z – 2026-08-11 04:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Wednesday, July 29, 2026 through Tuesday, August 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0406 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/0407 2026-07-30 14:00Z – 2026-08-12 05:00Z SFC–13,000 ft

  60NM NE FALLON, NV, Thursday, July 30, 2026 through Wednesday, August 12, 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