Diversion — AAL2774
KRIC · 162026-08-02 15:43 UTC· KAUS → KRIC· BANK OF UTAH TRUSTEE· A319
AAL2774 (Bank of Utah) was operating from KAUS to KPHL (Philadelphia International Airport) on 2026-08-02. SkyMeter detected a diversion to Richmond International Airport (KRIC) on runway 16 at 15:43 UTC. Peak cruise altitude FL392, turnaround area near Carbon Hill, US. Approach stability score: 89/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 6 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)- HAZARDS6/6848 2026-07-20 00:32Z – 2026-08-03 23:45Z SFC–3,000 ft
2NM W SHULERVILLE, SC, Monday, July 20, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - HAZARDS6/0628 2026-07-31 13:07Z – 2026-08-03 01:30Z SFC–1,300 ft
13NM S TAYLOR, FL, Friday, July 31, 2026 through Monday, August 3, 2026 UTC
View FAA NOTAM → - 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 →
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 89/100
- 6 kt wind
- 1 kt crosswind component
- 16,093 m visibility
- KRIC 162154Z 14006KT 10SM FEW300 27/17 A3031 RMK AO2 SLP266 T02720172
Flight context
- AAL2774
- Bank of Utah
- A319
- KAUS → KRIC
- 2026-08-02 15:43 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