Diversion — AAL2520
KRIC · 162026-08-30 23:49 UTC· KDFW → KRIC· AMERICAN AIRLINES INC· B738
AAL2520 (American Airlines) was operating from KDFW to KDCA (Ronald Reagan Washington National Airport) on 2026-08-30. SkyMeter detected a diversion to Richmond International Airport (KRIC) on runway 16 at 23:49 UTC. Peak cruise altitude FL394, turnaround area near Mount Pleasant, US. Approach stability score: 93/100. Scores in this band are observed on roughly 50% of approaches at this runway and represent the centerline of normal operations. METAR at the time reported 3 kt wind, 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/0708 2026-08-01 00:01Z – 2027-08-01 23:59Z SFC–400 ft
Goodlettsville, TN, Saturday, August 1, 2026 through Sunday, August 1, 2027 UTC
View FAA NOTAM → - HAZARDS6/8103 2026-08-26 12:00Z – 2026-09-09 02:00Z SFC–4,000 ft
21NM NW BROKEN BOW, OK, Wednesday, August 26, 2026 through Wednesday, September 9, 2026 UTC
View FAA NOTAM → - SECURITY6/6989 2026-08-27 21:00Z – 2026-09-02 21:00Z SFC–400 ft
Asheville, NC, Thursday, August 27, 2026 through Wednesday, September 2, 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
- 161 ft AGL at event
- 120 kt ground speed
- 0 fpm vertical
- Approach stability 93/100
- 3 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KRIC 160454Z 00000KT 10SM CLR 17/15 A3035 RMK AO2 SLP279 T01720150 402670139 $
Flight context
- AAL2520
- American Airlines
- B738
- KDFW → KRIC
- 2026-08-30 23:49 UTC
- KRIC runway 16
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