Return to field — SWA822

KBWI · 28

2026-07-02 15:34 UTC· KBWI → KBWI· SOUTHWEST AIRLINES CO· B38M

▶ Replay 📊 Analyse

SWA822 (Southwest Airlines) was operating from KBWI to KBWI (Baltimore/Washington International Thurgood Marshall Airport) on 2026-07-02. SkyMeter detected a return to field at Baltimore/Washington International Thurgood Marshall Airport (KBWI) on runway 28 at 15:34 UTC. Peak cruise altitude FL395, turnaround area near Sneads Ferry, 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 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)
  • AIR SHOWS/SPORTS6/0757 2026-07-02 15:40Z – 2026-07-02 16:05Z SFC–5,000 ft

    Washington, DC, Thursday, July 2, 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.

Pilot review data

  • Runway 28
  • 39528 ft AGL at event
  • 491 kt ground speed
  • 0 fpm vertical
  • Approach stability 37/100
  • 0 kt wind
  • 0 kt crosswind component
  • 16,093 m visibility
  • KBWI 071454Z 23009KT 10SM CLR 17/09 A3005 RMK AO2 SLP174 T01720094 58008

Flight context

  • SWA822
  • Southwest Airlines
  • B38M
  • KBWI → KBWI
  • 2026-07-02 15:34 UTC
  • KBWI runway 28

All events on this flight

Return to field 15:34:07 UTC · KBWI runway 28 · 39,528 ft AGL · 491 kt GS
Unstable approach 23:33:13 UTC · KBWI runway 04 · 1,246 ft AGL · 165 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· KBWI