EmergencyDescent — AAL768
2026-07-10 04:35 UTC· KCLT → KOKC· AWAS 2595 TRUST· A319
AAL768 (Awas 2595 Trust) was operating from KCLT to KOKC on 2026-07-10. SkyMeter detected a emergencydescent at 04:35 UTC. Trace data at the event: 33274 ft AGL, 450 kt GS. Approach stability score: 69/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 9 kt wind, 2 kt crosswind component. Detection algorithm and known limitations: see SkyMeter methodology.
Active FAA TFR during this flight
Source: FAA TFR archive (hourly snapshot)- SECURITY6/3996 2026-06-01 00:00Z – 2026-07-20 23:59Z
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 UTC
View FAA NOTAM → - SECURITY6/3980 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3990 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
CHATTANOOGA, TN, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/3997 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
NORMAN, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4022 2026-06-01 05:00Z – 2026-07-21 04:59Z SFC–400 ft
OKLAHOMA CITY, OK, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/7600 2026-07-07 13:07Z – 2026-07-21 03:59Z SFC–400 ft
Chattanooga, TN
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
- 33274 ft AGL at event
- 450 kt ground speed
- 0 fpm vertical
- Approach stability 69/100
- 9 kt wind
- 2 kt crosswind component
Flight context
- AAL768
- Awas 2595 Trust
- A319
- KCLT → KOKC
- 2026-07-10 04:35 UTC
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