Go-around — SWA792

SWA792 (Southwest Airlines) was operating from KLAS to KAUS on 2026-08-27. SkyMeter detected a go-around at Austin Bergstrom International Airport (KAUS) on runway 18L at 23:42 UTC. Trace data at the event: 1695 ft AGL, 200 kt GS. METAR at the time reported 9 kt wind, 2 kt crosswind component, 14,484 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/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/2656 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• SECURITY6/2657 2026-07-05 00:01Z – 2027-01-02 23:59Z SFC–500 ft

  Calexico, CA, Saturday, July 4, 2026 through Saturday, January 2, 2027 Local

  View FAA NOTAM →
• HAZARDS6/5409 2026-08-17 04:00Z – 2026-08-30 04:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Monday, August 17, 2026 through Sunday, August 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/6216 2026-08-19 03:00Z – 2026-09-02 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Wednesday, August 19, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7128 2026-08-23 13:00Z – 2026-09-06 03:00Z SFC–14,500 ft

  26NM NE RUIDOSO, NM, Sunday, August 23, 2026 through Sunday, September 6, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7422 2026-08-24 14:30Z – 2026-09-08 05:00Z SFC–12,500 ft

  26NM NE RUIDOSO, NM, Monday, August 24, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7589 2026-08-24 20:35Z – 2026-08-29 02:00Z SFC–5,500 ft

  2NM W PALO PINTO, TX, Monday, August 24, 2026 through Saturday, August 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7630 2026-08-25 12:00Z – 2026-09-01 02:00Z SFC–5,500 ft

  1NM W PALO PINTO, TX, Tuesday, August 25, 2026 through Tuesday, September 1, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7718 2026-08-25 14:00Z – 2026-09-08 04:00Z SFC–8,000 ft

  4.5 NM NE BAGDAD, AZ, Tuesday, August 25, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/7885 2026-08-25 19:02Z – 2026-09-02 23:45Z SFC–5,500 ft

  PALO PINTO, TX, Tuesday, August 25, 2026 through Wednesday, September 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8092 2026-08-26 00:25Z – 2026-09-09 23:45Z SFC–6,200 ft

  1NM NE EVANT, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8102 2026-08-26 02:25Z – 2026-09-09 02:00Z SFC–5,500 ft

  1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8069 2026-08-26 14:00Z – 2026-09-09 04:00Z SFC–14,000 ft

  26NM SE ALBUQUERQUE, NM, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8445 2026-08-26 20:55Z – 2026-09-09 02:00Z SFC–5,500 ft

  1NM NW PALO PINTO, TX, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8453 2026-08-26 21:02Z – 2026-09-08 00:45Z SFC–6,200 ft

  1NM NE EVANT, TX, Wednesday, August 26, 2026 through Tuesday, September 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8586 2026-08-27 17:30Z – 2026-08-28 04:00Z SFC–14,000 ft

  24NM SE ALBUQUERQUE, NM, Thursday, August 27, 2026 through Friday, August 28, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8590 2026-08-27 18:00Z – 2026-09-09 03:00Z SFC–13,500 ft

  13NM N SANTA FE, NM, Thursday, August 27, 2026 through Wednesday, September 9, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8635 2026-08-27 19:35Z – 2026-08-28 02:30Z SFC–6,000 ft

  1NM NE EVANT, TX, Thursday, August 27, 2026 through Friday, August 28, 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.

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