Go-around — SKW3786

SKW3786 (Delta AIR Lines) was operating from KFAT to KSLC on 2026-08-26. SkyMeter detected a go-around at Salt Lake City International Airport (KSLC) on runway 34L at 17:59 UTC. Trace data at the event: 5005 ft AGL, 171 kt GS. METAR at the time reported 9 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.

• HAZARDS6/5067 2026-08-14 02:15Z – 2026-08-27 04:00Z SFC–11,000 ft

  15NM NW RENO, NV, Friday, August 14, 2026 through Thursday, August 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5242 2026-08-15 23:15Z – 2026-08-29 04:00Z SFC–9,500 ft

  15NM NW RENO, NV, Saturday, August 15, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5246 2026-08-16 02:15Z – 2026-08-30 04:00Z SFC–13,000 ft

  37NM SE SOUTH LAKE TAHOE, CA, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

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

  52NM NE FALLON, NV, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

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

  37NM SE SOUTH LAKE TAHOE, CA, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5423 2026-08-16 19:15Z – 2026-08-30 04:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Sunday, August 16, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5937 2026-08-18 13:00Z – 2026-08-31 03:00Z SFC–13,000 ft

  4NM W RICHFIELD, UT, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/5897 2026-08-18 14:00Z – 2026-08-31 02:00Z SFC–7,500 ft

  15NM NW RENO, NV, Tuesday, August 18, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6067 2026-08-18 18:15Z – 2026-09-01 02:00Z SFC–11,000 ft

  52NM NE FALLON, NV, Tuesday, August 18, 2026 through Tuesday, September 1, 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/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/7654 2026-08-25 13:00Z – 2026-09-07 04:00Z SFC–10,000 ft

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

  View FAA NOTAM →
• HAZARDS6/7898 2026-08-25 19:45Z – 2026-09-01 04:00Z SFC–13,000 ft

  7NM E WINNEMUCCA, NV, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7943 2026-08-25 20:30Z – 2026-08-31 04:00Z SFC–13,000 ft

  7NM E WINNEMUCCA, NV, Tuesday, August 25, 2026 through Monday, August 31, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7986 2026-08-25 21:45Z – 2026-09-07 04:00Z SFC–12,000 ft

  32NM SW TOOELE, UT, Tuesday, August 25, 2026 through Monday, September 7, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8238 2026-08-26 15:00Z – 2026-09-02 03:00Z SFC–13,000 ft

  7NM E WINNEMUCCA, NV, Wednesday, August 26, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8332 2026-08-26 17:45Z – 2026-09-05 04:00Z SFC–11,000 ft

  51NM NE FALLON, NV, Wednesday, August 26, 2026 through Saturday, September 5, 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