Go-around — SWA769

SWA769 (UMB Bank NA) was operating from KLGB to KAUS on 2026-06-16. SkyMeter detected a go-around at Austin Bergstrom International Airport (KAUS) on runway 18R at 21:46 UTC. Trace data at the event: 929 ft AGL, 153 kt GS. METAR at the time reported 10 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.

• SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

  Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

  Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  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 →
• SECURITY6/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/5756 2026-06-05 14:00Z – 2026-06-19 04:00Z SFC–11,500 ft

  3NM E NOGALES, AZ, Friday, June 5, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8083 2026-06-13 17:14Z – 2026-06-27 05:00Z SFC–11,000 ft

  10NM E TUCSON, AZ, Saturday, June 13, 2026 through Saturday, June 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8208 2026-06-14 13:47Z – 2026-06-27 05:00Z SFC–13,000 ft

  38NM NE DOUGLAS, AZ, Sunday, June 14, 2026 through Saturday, June 27, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8228 2026-06-15 14:00Z – 2026-06-28 03:00Z SFC–13,000 ft

  38NM NE DOUGLAS, AZ, Monday, June 15, 2026 through Sunday, June 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8704 2026-06-16 17:05Z – 2026-06-29 05:00Z SFC–11,500 ft

  10NM N TUCSON, AZ, Tuesday, June 16, 2026 through Monday, June 29, 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.

All events on this flight

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