Go-around — SWA3939
KIND · 23R2026-09-01 19:54 UTC· KTPA → KIND· UMB BANK NA TRUSTEE· B738
SWA3939 (UMB Bank NA) was operating from KTPA to KIND on 2026-09-01. SkyMeter detected a go-around at Indianapolis International Airport (KIND) on runway 23R at 19:54 UTC. Trace data at the event: 1398 ft AGL, 151 kt GS. METAR at the time reported 11 kt wind, 1 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/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 → - SECURITY6/8831 2026-09-01 05:00Z – 2026-09-04 09:30Z SFC–17,999 ft
Macon, GA, Tuesday, September 1, 2026 through Friday, September 4, 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 23R
- 1398 ft AGL at event
- 151 kt ground speed
- 0 fpm vertical
- 11 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KIND 161654Z 18006KT 10SM FEW040 SCT160 BKN250 31/22 A3027 RMK AO2 SLP242 T03110222
Flight context
- SWA3939
- UMB Bank NA
- B738
- KTPA → KIND
- 2026-09-01 19:54 UTC
- KIND runway 23R
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