SWA2921 (Boeing) was operating from KMSY to KBWI (Baltimore/Washington International Thurgood Marshall Airport) on 2026-08-08. SkyMeter detected a diversion to Phoenix Sky Harbor International Airport (KPHX) on runway 25L at 22:19 UTC. Peak cruise altitude FL425, turnaround area near Sterling, US. Approach stability score: 67/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 0 kt wind, 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/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/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 → - HAZARDS6/0749 2026-08-01 15:00Z – 2026-08-14 03:00Z SFC–13,000 ft
13NM S SAFFORD, AZ, Saturday, August 1, 2026 through Friday, August 14, 2026 UTC
View FAA NOTAM → - SECURITY6/2553 2026-08-08 06:00Z – 2026-08-09 13:00Z SFC–17,999 ft
Libby AAF, AZ, Friday, August 7, 2026 through Sunday, August 9, 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 25L
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 67/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KPHX 151951Z VRB06KT 10SM FEW100 FEW250 39/13 A2998 RMK AO2 SLP128 T03940128
Flight context
- SWA2921
- Boeing
- B38M
- KMSY → KPHX
- 2026-08-08 22:19 UTC
- KPHX runway 25L
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