Go-around — DAL1330
KMSP · 12R2026-08-12 13:32 UTC· CT35 → KMSP· UMB BANK NA TRUSTEE· A321
DAL1330 (UMB Bank NA) was operating from CT35 to KMSP on 2026-08-12. SkyMeter detected a go-around at Minneapolis-St Paul International/Wold-Chamberlain Airport (KMSP) on runway 12R at 13:32 UTC. Trace data at the event: 1678 ft AGL, 207 kt GS. METAR at the time reported 7 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)- UAS PUBLIC GATHERING6/0460 2026-08-06 13:00Z – 2026-08-17 05:00Z SFC–400 ft
Milwaukee, WI, Thursday, August 6, 2026 through Monday, August 17, 2026 UTC
View FAA NOTAM → - SECURITY6/3696 2026-08-11 22:30Z – 2026-08-13 05:00Z SFC–400 ft
Dyersville, IA, Tuesday, August 11, 2026 through Thursday, August 13, 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
- 1678 ft AGL at event
- 207 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KMSP 162153Z 11010KT 10SM FEW150 SCT190 BKN250 23/08 A3026 RMK AO2 SLP247 T02330083
Flight context
- DAL1330
- UMB Bank NA
- A321
- CT35 → KMSP
- 2026-08-12 13:32 UTC
- KMSP runway 12R
All events on this flight
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