Diversion — AAL2811

AAL2811 (American Airlines) was operating from KLAX to KDFW (Dallas Fort Worth International Airport) on 2026-06-07. SkyMeter detected a diversion to Austin Bergstrom International Airport (KAUS) on runway 18R at 16:37 UTC. Peak cruise altitude FL368, turnaround area near Luna, US. METAR at the time reported 10 kt wind, 5 kt crosswind component, 16,093 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.

• SECURITY6/0091 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  Coyote Wells, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/0092 2026-01-04 00:01Z – 2026-07-04 23:59Z SFC–500 ft

  CALEXICO, CA, Saturday, January 3, 2026 through Saturday, July 4, 2026 Local

  View FAA NOTAM →
• SECURITY6/4165 2026-02-14 07:00Z – 2026-08-15 06:59Z SFC–400 ft

  Nogales, AZ, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4160 2026-02-14 08:00Z – 2026-08-15 06:59Z SFC–400 ft

  Chula Vista, CA, Saturday, February 14, 2026 through Friday, August 14, 2026 Local

  View FAA NOTAM →
• SECURITY6/4240 2026-03-08 08:00Z – 2026-11-01 07:00Z SFC–180 ft

  SAN ANGELO, TX, Sunday, March 8, 2026 through Sunday, November 1, 2026 Local

  View FAA NOTAM →
• HAZARDS6/2830 2026-05-25 15:45Z – 2026-06-11 16:00Z SFC–5,000 ft

  GARDEN GROVE, CA, Monday, May 25, 2026 through Thursday, June 11, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/2866 2026-05-25 22:04Z – 2026-06-08 03:00Z SFC–13,000 ft

  24NM NE DOUGLAS, AZ, Monday, May 25, 2026 through Monday, June 8, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4313 2026-05-31 14:00Z – 2026-06-14 03:00Z SFC–8,000 ft

  13NM NW CARLSBAD, NM, Sunday, May 31, 2026 through Sunday, June 14, 2026 UTC

  View FAA NOTAM →
• HAZARDS6/4403 2026-05-31 14:00Z – 2026-06-14 04:00Z SFC–11,000 ft

  18NM NE TUCSON, AZ, Sunday, May 31, 2026 through Sunday, June 14, 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/3948 2026-06-01 07:00Z – 2026-07-21 06:59Z

  MESA, AZ, Monday, June 1, 2026 through Tuesday, July 21, 2026 UTC

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

  Mesa, AZ, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Irvine, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Los Angeles, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  IRVINE, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  Dana Point, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

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

  San Diego, CA, Monday, June 1, 2026 through Monday, July 20, 2026 Local

  View FAA NOTAM →
• HAZARDS6/5756 2026-06-05 14:00Z – 2026-06-19 04:00Z SFC–11,500 ft

  3NM E NOGALES, AZ, Friday, June 5, 2026 through Friday, June 19, 2026 UTC

  View FAA NOTAM →
• SECURITY6/5757 2026-06-06 06:00Z – 2026-06-07 13:00Z SFC–17,999 ft

  LIBBY AFB, AZ, Friday, June 5, 2026 through Sunday, June 7, 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.

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