Go-around — DAL2129

KMSP · 12R

2026-03-18 22:47 UTC· KMIA KMSP· BANK OF UTAH TRUSTEE· B739

DAL2129 (Bank of Utah) was operating from KMIA to KMSP on 2026-03-18. SkyMeter detected a go-around at Minneapolis-St Paul International/Wold-Chamberlain Airport (KMSP) on runway 12R at 22:47 UTC. Trace data at the event: 950 ft AGL, 153 kt GS. METAR at the time reported 8 kt wind, 5 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)
  • SECURITY5/2858 2025-12-26 04:59Z – 2026-07-02 03:59Z SFC–1,000 ft

    OCHOPPEE, FL, Thursday, December 25, 2025 through Wednesday, July 1, 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 12R
  • 950 ft AGL at event
  • 153 kt ground speed
  • 0 fpm vertical
  • 8 kt wind
  • 5 kt crosswind component
  • 16,093 m visibility
  • KMSP 221253Z 08008KT 10SM SCT150 11/05 A3036 RMK AO2 SLP283 T01060050

Flight context

  • DAL2129
  • Bank of Utah
  • B739
  • KMIA → KMSP
  • 2026-03-18 22:47 UTC
  • KMSP runway 12R

All events on this flight

Go-around 22:47:32 UTC · KMSP runway 12R · 950 ft AGL · 153 kt GS
Go-around 22:47:38 UTC · KMSP runway 12R · 1,109 ft AGL · 160 kt GS
Go-around 22:47:38 UTC · KMSP runway 12R · 1,109 ft AGL · 160 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· KMSP