Go-around — DAL2104

KAUS · 18R

2026-06-01 18:17 UTC· KATL KAUS· UMB BANK NA TRUSTEE· A321

DAL2104 (UMB Bank NA) was operating from KATL to KAUS on 2026-06-01. SkyMeter detected a go-around at Austin Bergstrom International Airport (KAUS) on runway 18R at 18:17 UTC. Trace data at the event: 906 ft AGL, 152 kt GS. METAR at the time reported 5 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.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • HAZARDS6/3292 2026-05-27 17:20Z – 2026-06-10 00:15Z SFC–2,000 ft

    22NM SW TALLAHASSEE, FL, Wednesday, May 27, 2026 through Wednesday, June 10, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/3583 2026-05-28 07:00Z – 2026-06-01 23:00Z

    NEW ORLEANS, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 UTC

    View FAA NOTAM →
  • SECURITY6/2647 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft

    New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local

    View FAA NOTAM →
  • SECURITY6/3335 2026-05-28 12:00Z – 2026-06-02 04:00Z SFC–2,000 ft

    New Orleans, LA, Thursday, May 28, 2026 through Monday, June 1, 2026 Local

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

    ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

    FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

    AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 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.

Pilot review data

  • Runway 18R
  • 906 ft AGL at event
  • 152 kt ground speed
  • 0 fpm vertical
  • 5 kt wind
  • 1 kt crosswind component
  • 16,093 m visibility
  • KAUS 181953Z COR 04006G15KT 10SM FEW045 SCT300 35/17 A3005 RMK AO2 SLP165 T03500172 $

Flight context

  • DAL2104
  • UMB Bank NA
  • A321
  • KATL → KAUS
  • 2026-06-01 18:17 UTC
  • KAUS runway 18R

All events on this flight

Go-around 18:17:41 UTC · KAUS runway 18R · 906 ft AGL · 152 kt GS
Go-around 18:17:41 UTC · KAUS runway 18R · 906 ft AGL · 152 kt GS

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

SkyMeter · trace data observed via ADS-B· KAUS