Diversion — UAL1508
KSFO · 28L2026-08-04 05:15 UTC· KBUR → KSFO· UNITED AIRLINES INC· A320
UAL1508 (United Airlines) was operating from KBUR to KEUG (Mahlon Sweet Field) on 2026-08-04. SkyMeter detected a diversion to San Francisco International Airport (KSFO) on runway 28L at 05:15 UTC. Peak cruise altitude FL321, turnaround area near Avenal, US. 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)- HAZARDS6/7246 2026-07-21 05:00Z – 2026-08-21 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Friday, August 21, 2026 UTC
View FAA NOTAM → - HAZARDS6/7372 2026-07-21 13:38Z – 2026-08-22 03:00Z SFC–10,500 ft
20NM N INDEPENDENCE, CA, Tuesday, July 21, 2026 through Saturday, August 22, 2026 UTC
View FAA NOTAM → - HAZARDS6/7909 2026-07-22 18:11Z – 2026-08-08 04:00Z SFC–12,500 ft
20NM N INDEPENDENCE, CA, Wednesday, July 22, 2026 through Saturday, August 8, 2026 UTC
View FAA NOTAM → - HAZARDS6/9881 2026-07-29 02:10Z – 2026-08-12 04:00Z SFC–13,500 ft
25NM S BISHOP, CA, Wednesday, July 29, 2026 through Wednesday, August 12, 2026 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 28L
- 0 ft AGL at event
- 0 kt ground speed
- 0 fpm vertical
- 0 kt wind
- 0 kt crosswind component
- 16,093 m visibility
- KSFO 162056Z 26015G25KT 10SM FEW005 BKN019 18/12 A3000 RMK AO2 SLP158 T01780117 58003
Flight context
- UAL1508
- United Airlines
- A320
- KBUR → KSFO
- 2026-08-04 05:15 UTC
- KSFO runway 28L
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