Go-around — AAL935

AAL935 (Wilmington Trust) was operating from KORD to KAUS on 2026-07-02. SkyMeter detected a go-around at Austin Bergstrom International Airport (KAUS) on runway 18R at 04:46 UTC. Trace data at the event: 982 ft AGL, 126 kt GS. METAR at the time reported 8 kt wind, 3 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/3705 2026-05-29 05:00Z – 2026-07-20 08:00Z SFC–400 ft

  DALLAS, TX, Friday, May 29, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/3954 2026-06-01 00:00Z – 2026-07-20 23:59Z

  STILLWATER, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z

  OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC

  View FAA NOTAM →
• SECURITY6/4134 2026-06-01 00:00Z – 2026-07-20 23:59Z

  TULSA, OK, Monday, June 1, 2026 through Monday, July 20, 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/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/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/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/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/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  OKLAHOMA CITY, OK, 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/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  NORMAN, OK, 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 →
• SECURITY6/3952 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Stillwater, OK, 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/4141 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  Tulsa, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Lawrence, KS, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

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

  Kansas City, KS, 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/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/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Fort Worth, TX

  View FAA NOTAM →
• SECURITY6/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Mansfield, TX

  View FAA NOTAM →
• SECURITY6/1457 2026-07-01 11:00Z – 2026-07-06 02:00Z SFC–400 ft

  SILVIS, IL, Wednesday, July 1, 2026 through Sunday, July 5, 2026 Local

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

  Riverside, MO

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

  Kansas City, MO

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

  Frisco, TX

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

  Frisco, TX

  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