Diversion — AAL3115
KOMA · 14R2026-05-24 21:04 UTC· KCLT → KOMA· US BANK NA TRUSTEE· A320
AAL3115 (US Bank NA) was operating from KCLT to KOMA (Eppley Airfield) on 2026-05-24. SkyMeter detected a diversion to Eppley Airfield (KOMA) on runway 14R at 21:04 UTC. Peak cruise altitude FL399, turnaround area near Flora, US. Approach stability score: 74/100. Scores in this band are observed on roughly 25% of approaches at this runway: one or more gates outside the per-runway tightest envelope, but still inside the typical operating range. METAR at the time reported 19 kt wind, 5 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)- VIP6/2150 2026-05-22 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft
CINCINNATI, OH, Friday, May 22, 2026 through Monday, May 25, 2026 Local
View FAA NOTAM → - VIP6/2530 2026-05-23 21:00Z – 2026-05-25 14:00Z SFC–4,999 ft
CINCINNATI, OH, Saturday, May 23, 2026 through Monday, May 25, 2026 Local
View FAA NOTAM → - SECURITY6/1953 2026-05-24 12:00Z – 2026-05-24 23:59Z SFC–2,000 ft
Indianapolis, IN, Sunday, May 24, 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 14R
- 980 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 74/100
- 19 kt wind
- 5 kt crosswind component
- 16,093 m visibility
- KOMA 200450Z AUTO 04006KT 10SM -RA BKN014 OVC022 19/17 A2998 RMK P0001 T01900170 LTG DSNT SE! MADISHF
Flight context
- AAL3115
- US Bank NA
- A320
- KCLT → KOMA
- 2026-05-24 21:04 UTC
- KOMA runway 14R
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