Diversion — AAL2428
KFTW · 162026-06-14 18:43 UTC· KRSW → KFTW· WILMINGTON TRUST CO TRUSTEE· B738
AAL2428 (Wilmington Trust) was operating from KRSW to KDFW (Dallas Fort Worth International Airport) on 2026-06-14. SkyMeter detected a diversion to Fort Worth Meacham International Airport (KFTW) on runway 16 at 18:43 UTC. Peak cruise altitude FL363, turnaround area near Campbell, US. Approach stability score: 45/100. Scores below 50 occur on under 10% of approaches at this runway and indicate the v2 scorer flagged the approach as highly anomalous (three or more gates exceeded the runway's P90 envelope simultaneously). METAR at the time reported 9 kt wind, 1 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)- SECURITY6/4153 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
Tampa, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - SECURITY6/4156 2026-06-01 04:00Z – 2026-07-21 03:59Z SFC–400 ft
TAMPA, FL, Monday, June 1, 2026 through Monday, July 20, 2026 Local
View FAA NOTAM → - 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/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/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 → - HAZARDS6/5656 2026-06-04 16:19Z – 2026-06-18 00:15Z SFC–2,000 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 2026 UTC
View FAA NOTAM → - HAZARDS6/5771 2026-06-04 21:47Z – 2026-06-18 00:15Z SFC–3,500 ft
22NM SW TALLAHASSEE, FL, Thursday, June 4, 2026 through Thursday, June 18, 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/7620 2026-06-14 14:00Z – 2026-06-14 23:00Z SFC–3,000 ft
Houston, TX, Sunday, June 14, 2026 Local
View FAA NOTAM → - SECURITY6/7619 2026-06-14 17:00Z – 2026-06-15 02:00Z SFC–3,000 ft
Dallas, TX, Sunday, June 14, 2026 through Sunday, June 14, 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 16
- 674 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 45/100
- 9 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KFTW 181953Z 16009KT 10SM CLR 34/17 A3006 RMK AO2 SLP169 T03440172
Flight context
- AAL2428
- Wilmington Trust
- B738
- KRSW → KFTW
- 2026-06-14 18:43 UTC
- KFTW runway 16
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