Go-around — DAL3106
KATL · 26R2026-08-16 12:13 UTC· KIND → KATL· BANK OF UTAH TRUSTEE· B739
DAL3106 (Bank of Utah) was operating from KIND to KATL on 2026-08-16. SkyMeter detected a go-around at Hartsfield Jackson Atlanta International Airport (KATL) on runway 26R at 12:13 UTC. Trace data at the event: 1354 ft AGL, 151 kt GS. METAR at the time reported 7 kt wind, 2 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/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 → - UAS PUBLIC GATHERING6/3173 2026-08-13 21:00Z – 2026-08-23 07:00Z SFC–400 ft
Lebanon, TN, Thursday, August 13, 2026 through Sunday, August 23, 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.
Pilot review data
- Runway 26R
- 1354 ft AGL at event
- 151 kt ground speed
- 0 fpm vertical
- 7 kt wind
- 2 kt crosswind component
- 16,093 m visibility
- KATL 162052Z 08011G17KT 10SM SCT048TCU SCT070 31/19 A3029 RMK AO2 SLP245 TCU OHD DSNT NE MDT CU N SW W T03060189 56023 $
Flight context
- DAL3106
- Bank of Utah
- B739
- KIND → KATL
- 2026-08-16 12:13 UTC
- KATL runway 26R
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