Go-around — SWA2612

KBWI · 15R

2026-06-25 15:41 UTC· KMCO KBWI· UMB BANK NA TRUSTEE· B38M

SWA2612 (UMB Bank NA) was operating from KMCO to KBWI on 2026-06-25. SkyMeter detected a go-around at Baltimore/Washington International Thurgood Marshall Airport (KBWI) on runway 15R at 15:41 UTC. Trace data at the event: 516 ft AGL, 144 kt GS. METAR at the time reported 9 kt wind, 8 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.

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/9513 2026-06-22 12:30Z – 2026-06-26 06:00Z SFC–2,500 ft

    MAYPORT, FL, Monday, June 22, 2026 through Friday, June 26, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9423 2026-06-22 13:00Z – 2026-06-27 01:00Z SFC–1,000 ft

    Williamsburg, VA, Monday, June 22, 2026 through Friday, June 26, 2026 Local

    View FAA NOTAM →
  • SECURITY6/9498 2026-06-24 11:00Z – 2026-06-30 23:59Z SFC–2,000 ft

    Baltimore, MD, Wednesday, June 24, 2026 through Tuesday, June 30, 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 →
  • SECURITY6/0512 2026-06-25 12:00Z – 2026-06-26 20:00Z SFC–2,000 ft

    Laurel, MD, Thursday, June 25, 2026 through Friday, June 26, 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 15R
  • 516 ft AGL at event
  • 144 kt ground speed
  • 0 fpm vertical
  • 9 kt wind
  • 8 kt crosswind component
  • 16,093 m visibility
  • KBWI 172154Z 25003KT 10SM FEW026 FEW160 BKN180 BKN250 27/23 A3011 RMK AO2 SLP193 T02670233

Flight context

  • SWA2612
  • UMB Bank NA
  • B38M
  • KMCO → KBWI
  • 2026-06-25 15:41 UTC
  • KBWI runway 15R

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