Go-around — SCX307

SCX307 (SUN Country) was operating from KMSP to KAVL on 2026-07-19. SkyMeter detected a go-around at Asheville Regional Airport (KAVL) on runway 35 at 22:51 UTC. Trace data at the event: 2616 ft AGL, 171 kt GS. METAR at the time reported 2 kt wind, 2 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/4114 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  LOUISVILLE, KY, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  CARMEL, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  CINNCINATI, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  MILFORD, OH, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  WESTFIELD, IN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  NASHVILLE, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Nashville, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  CLAYTON, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  St, Louis, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/7205 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

  Carmel, IN

  View FAA NOTAM →
• SECURITY6/7208 2026-06-23 21:07Z – 2026-07-21 03:59Z SFC–400 ft

  Westfield, IN

  View FAA NOTAM →
• SECURITY6/7972 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Nashville, TN

  View FAA NOTAM →
• SECURITY6/7967 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Nashville, TN

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

  Columbus, OH

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

  Louisville, KY

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

  Cinncinati, OH

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

  Milford, OH

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

  St Louis, MO

  View FAA NOTAM →
• SECURITY6/5591 2026-07-15 17:00Z – 2026-07-20 04:59Z SFC–400 ft

  Hammond, IN, Wednesday, July 15, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/5201 2026-07-19 17:00Z – 2026-07-20 04:30Z SFC–400 ft

  madison, WI, Sunday, July 19, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/7645 2026-07-19 19:07Z – 2026-07-21 04:59Z SFC–400 ft

  Clayton, MO

  View FAA NOTAM →
• SECURITY6/7649 2026-07-19 19:07Z – 2026-07-21 03:59Z SFC–400 ft

  Clayton, MO

  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