Diversion — DAL3161
KFTY · 092026-06-08 03:33 UTC· KATL → KFTY· UMB BANK NA TRUSTEE· A321
DAL3161 (UMB Bank NA) was operating from KATL to KDFW (Dallas Fort Worth International Airport) on 2026-06-08. SkyMeter detected a diversion to Fulton County Airport Brown Field (KFTY) on runway 09 at 03:33 UTC. Peak cruise altitude FL363, turnaround area near Edwards, US. Approach stability score: 55/100. Scores in this band occur on roughly 10-15% of approaches at this runway, with multiple gates outside the per-runway envelope. METAR at the time reported 4 kt wind, 3 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/4008 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4009 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
FRISCO, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4019 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
IRVING, TX, Monday, June 1, 2026 through Monday, July 20, 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 09
- 810 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 55/100
- 4 kt wind
- 3 kt crosswind component
- 16,093 m visibility
- KFTY 182053Z 00000KT 10SM CLR 34/19 A3007 RMK AO2 SLP172 T03390194 56025
Flight context
- DAL3161
- UMB Bank NA
- A321
- KATL → KFTY
- 2026-06-08 03:33 UTC
- KFTY runway 09
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