Go-around — SWA1610

SWA1610 (Southwest Airlines) was operating from KSTL to KBWI on 2026-08-28. SkyMeter detected a go-around at Baltimore/Washington International Thurgood Marshall Airport (KBWI) on runway 33L at 22:45 UTC. Trace data at the event: 1352 ft AGL, 178 kt GS. METAR at the time reported 7 kt wind, 7 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.

• SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft

  Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/0299 2026-06-26 04:00Z – 2026-10-18 03:59Z SFC–5,000 ft

  Key West, FL, Friday, June 26, 2026 through Saturday, October 17, 2026 Local

  View FAA NOTAM →
• SECURITY6/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft

  Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC

  View FAA NOTAM →
• SECURITY6/7271 2026-08-24 12:30Z – 2026-08-29 06:00Z SFC–2,500 ft

  MAYPORT, FL, Monday, August 24, 2026 through Saturday, August 29, 2026 Local

  View FAA NOTAM →
• SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft

  Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 2026 Local

  View FAA NOTAM →
• VIP6/8638 2026-08-28 20:00Z – 2026-08-30 21:00Z SFC–4,999 ft

  Middleburg, VA, Friday, August 28, 2026 through Sunday, August 30, 2026 Local

  View FAA NOTAM →
• UAS PUBLIC GATHERING6/7353 2026-08-28 22:30Z – 2026-08-29 03:30Z SFC–400 ft

  Jacksonville, FL, Friday, August 28, 2026 through Saturday, August 29, 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