Diversion — SWA1121

KTPA · 19R

2026-06-28 20:40 UTC· KBWI → KTPF· SOUTHWEST AIRLINES CO· B38M

▶ Replay 📊 Analyse

SWA1121 (Southwest Airlines) was operating from KBWI to KLAS (McCarran International Airport) on 2026-06-28. SkyMeter detected a diversion to Tampa International Airport (KTPA) on runway 19R at 20:40 UTC. Peak cruise altitude FL383, turnaround area near Clarendon, US. Approach stability score: 37/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 10 kt wind, 10 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

Active FAA TFR during this flight

Source: FAA TFR archive (hourly snapshot)
  • SECURITY6/3968 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft

    Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    White Sulphur Springs, WV, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Winston Salem, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    GREENSBORO, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Greensboro, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

    TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local

    View FAA NOTAM →
  • AIR SHOWS/SPORTS6/8970 2026-06-24 16:00Z – 2026-06-28 20:00Z SFC–15,000 ft

    Baltimore, MD, Wednesday, June 24, 2026 through Sunday, June 28, 2026 UTC

    View FAA NOTAM →
  • VIP6/0779 2026-06-28 12:00Z – 2026-06-28 22:00Z SFC–9,999 ft

    Sterling, VA, Sunday, June 28, 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 19R
  • 11 ft AGL at event
  • 120 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 10 kt wind
  • 10 kt crosswind component
  • 16,093 m visibility
  • KTPA 181053Z 03005KT 10SM FEW075 FEW250 24/22 A3007 RMK AO2 SLP182 T02390217 $

Flight context

  • SWA1121
  • Southwest Airlines
  • B38M
  • KBWI → KTPF
  • 2026-06-28 20:40 UTC
  • KTPA runway 19R

All events on this flight

Diversion 20:40:33 UTC · KTPA runway 19R · 11 ft AGL · 120 kt GS
Diversion 20:40:33 UTC · KTPF runway 18 · 7 ft AGL · 120 kt GS
Unstable approach 20:36:34 UTC · KTPF runway 36 · 1,100 ft AGL · 150 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· KTPA