Go-around — SWA575

SWA575 (Southwest Airlines) was operating from KOAK to KSAN on 2026-06-24. SkyMeter detected a go-around at San Diego International Airport (KSAN) on runway 27 at 15:59 UTC. Trace data at the event: 400 ft AGL, 154 kt GS, 0 fpm vertical. METAR at the time reported 3 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/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/4052 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

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

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

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

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

  Oakland, CA, 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/4189 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Santa Barbara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  GOLETA, 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 →
• SECURITY6/4204 2026-06-01 07:00Z – 2026-07-21 06:59Z SFC–400 ft

  Santa Clara, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/7265 2026-06-12 21:07Z – 2026-07-16 06:29Z SFC–400 ft

  Manhattan Beach, CA

  View FAA NOTAM →
• HAZARDS6/8547 2026-06-16 02:03Z – 2026-06-30 03:00Z SFC–6,000 ft

  3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Tuesday, June 30, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/8709 2026-06-16 17:25Z – 2026-06-29 00:15Z SFC–6,000 ft

  3.1NM S CALIMESA, CA, Tuesday, June 16, 2026 through Monday, June 29, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9305 2026-06-19 03:51Z – 2026-07-02 02:30Z SFC–8,000 ft

  30NM W BAKERSFIELD, CA, Friday, June 19, 2026 through Thursday, July 2, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/9824 2026-06-23 14:00Z – 2026-06-27 02:00Z SFC–200 ft

  LONG BEACH, CA, Tuesday, June 23, 2026 through Saturday, June 27, 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