Go-around — DAL1443

DAL1443 (Delta AIR Lines) was operating from KMCI to KATL on 2026-06-30. SkyMeter detected a go-around at Hartsfield Jackson Atlanta International Airport (KATL) on runway 08L at 22:15 UTC. Trace data at the event: 1172 ft AGL, 165 kt GS. METAR at the time reported 1 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/3979 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

  ATLANTA, GA, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

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

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

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

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

  MARIETTA, GA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• 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/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/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/4151 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

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

  PRAIRIE VILLAGE, KS, 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/4162 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kansas City, MO, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Kennesaw, GA, Wednesday, June 17, 2026 through Thursday, July 16, 2026 Local

  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