Return to field — AAL2431
KCLT · 36C2026-07-08 11:26 UTC· KCLT → KCLT· UMB BANK NA TRUSTEE· A319
AAL2431 (UMB Bank NA) was operating from KCLT to KORD (Chicago O'Hare International Airport) on 2026-07-08. SkyMeter detected a return to field at Charlotte Douglas International Airport (KCLT) on runway 36C at 11:26 UTC. Peak cruise altitude FL406, turnaround area near Abraham’s Bay, BS. METAR at the time reported 0 kt wind, 12,875 m visibility. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY5/2809 2025-10-20 12:00Z – 2026-10-20 12:00Z SFC–2,000 ft
Palm Beach, FL, Monday, October 20, 2025 through Tuesday, October 20, 2026 Local
View FAA NOTAM → - SECURITY6/4004 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHARLOTTE, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4007 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Charlotte, NC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4129 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
BOCA RATON, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4130 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MIAMI, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4131 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
MYRTLE BEACH, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4132 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Conway, SC, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4133 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
PALM BEACH GARDENS, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4142 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Miami, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4144 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
FORT LAUDERDALE, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4150 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0777 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft
Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/0782 2026-06-26 04:01Z – 2026-07-21 03:59Z SFC–400 ft
Fort Lauderdale, FL, Friday, June 26, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7906 2026-06-29 15:07Z – 2026-07-21 03:59Z SFC–400 ft
Boca Raton, FL
View FAA NOTAM → - SECURITY6/1796 2026-07-02 04:00Z – 2026-07-10 03:59Z SFC–1,000 ft
OCHOPPEE, FL, Thursday, July 2, 2026 through Thursday, July 9, 2026 Local
View FAA NOTAM → - SECURITY6/2665 2026-07-07 12:30Z – 2026-07-11 06:00Z SFC–2,500 ft
MAYPORT, FL, Tuesday, July 7, 2026 through Saturday, July 11, 2026 Local
View FAA NOTAM → - SECURITY6/7889 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL
View FAA NOTAM → - SECURITY6/7899 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Palm Beach Gardens, FL
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 36C
- 40618 ft AGL at event
- 481 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 12,875 m visibility
- KCLT 170952Z 32003KT 8SM CLR 18/17 A3029 RMK AO2 SLP264 T01830172
Flight context
- AAL2431
- UMB Bank NA
- A319
- KCLT → KCLT
- 2026-07-08 11:26 UTC
- KCLT runway 36C
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