Diversion — UAL2366
KRIC · 162026-08-06 20:40 UTC· KIAH → KRIC· UNITED AIRLINES INC· B738
UAL2366 (United Airlines) was operating from KIAH to KIAD (Washington Dulles International Airport) on 2026-08-06. SkyMeter detected a diversion to Richmond International Airport (KRIC) on runway 16 at 20:40 UTC. Peak cruise altitude FL372, turnaround area near Odenville, US. Approach stability score: 91/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 0 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 → - SECURITY6/0929 2026-08-03 12:30Z – 2026-08-08 06:00Z SFC–2,500 ft
MAYPORT, FL, Monday, August 3, 2026 through Saturday, August 8, 2026 Local
View FAA NOTAM → - SECURITY6/1231 2026-08-05 05:00Z – 2026-08-07 09:30Z SFC–17,999 ft
Macon, GA, Wednesday, August 5, 2026 through Friday, August 7, 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
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- Approach stability 91/100
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KRIC 162054Z VRB05KT 10SM FEW300 28/17 A3032 RMK AO2 SLP271 T02780167 56013
Flight context
- UAL2366
- United Airlines
- B738
- KIAH → KRIC
- 2026-08-06 20:40 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