Diversion — AAL1386

AAL1386 (Wilmington Trust) was operating from KATL to KDFW (Dallas Fort Worth International Airport) on 2026-07-12. SkyMeter detected a diversion to Austin Bergstrom International Airport (KAUS) on runway 18R at 23:29 UTC. Peak cruise altitude FL384, turnaround area near Concordia, US. Approach stability score: 91/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 6 kt wind, 2 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/3999 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  ARLINGTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4000 2026-06-01 05:00Z – 2026-07-21 04:59Z

  MANSFIELD, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/4002 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  FORT WORTH, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• 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 →
• SECURITY6/4025 2026-06-01 05:00Z – 2026-07-21 04:59Z

  DENTON, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/4030 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4031 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  AUSTIN, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4059 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4068 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft

  HOUSTON, TX, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• SECURITY6/4097 2026-06-01 05:00Z – 2026-07-21 04:59Z

  SAN ANTONIO, TX, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

  View FAA NOTAM →
• SECURITY6/6447 2026-06-09 05:01Z – 2026-07-20 04:59Z SFC–1,000 ft

  Houston, TX, Tuesday, June 9, 2026 through Sunday, July 19, 2026 Local

  View FAA NOTAM →
• SECURITY6/6840 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Mansfield, TX

  View FAA NOTAM →
• SECURITY6/6842 2026-06-29 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Fort Worth, TX

  View FAA NOTAM →
• SECURITY6/6843 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Frisco, TX

  View FAA NOTAM →
• SECURITY6/6844 2026-07-01 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Frisco, TX

  View FAA NOTAM →
• SECURITY6/6787 2026-07-03 15:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6783 2026-07-03 16:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/6820 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  San Antonio, TX

  View FAA NOTAM →
• SECURITY6/6834 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  San Antonio, TX

  View FAA NOTAM →
• SECURITY6/6838 2026-07-09 11:07Z – 2026-07-21 04:59Z SFC–400 ft

  Houston, TX

  View FAA NOTAM →
• SECURITY6/4909 2026-07-11 12:00Z – 2026-07-16 23:59Z SFC–400 ft

  Pell City, AL, Saturday, July 11, 2026 through Thursday, July 16, 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.

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