Utah Weekly Crash Forecast  ·  Jul 27 – Aug 2, 2026

About 1,046 crashes projected this week.

Summary: About 1,046 traffic crashes are projected across Utah for Jul 27 – Aug 2, 2026, with Salt Lake County the top hotspot and 🚦 Afternoon Rush (3–7 PM) the highest-risk hazard. Based on five years of UDOT crash data for this same calendar window. The top three counties — Salt Lake, Utah, Davis — historically account for 65% of the statewide total.

What this means for your weekIf you drive in Salt Lake County, your highest-risk window this week is Afternoon Rush (3–7 PM) (~392 crashes statewide in that window). Watch especially for Afternoon Rush (3–7 PM) incidents.
Projected this week
1,046crashes
Year-over-year
+0.8%
Top hazard
🚦 Afternoon Rush (3–7 PM)
Hotspot county
Salt Lake
~405 crashes / week
Statewide

This week's hot spots

Pulsing markers show counties with the highest projected crash volume for the next 7 days. Numbered pins call out the top 5 statewide crash segments. Tap any county or pin to open the crash map filtered to that area.

Utah Risk Map

— · — · —

Top counties this week

By projected crash volume
  • #01Salt Lake County~405/wk-5.8%
  • #02Utah County~183/wk+6.8%
  • #03Davis County~87/wk-5.2%
  • #04Weber County~78/wk+19.2%
  • #05Washington County~51/wk+0.9%
  • #06Cache County~42/wk-14.7%
  • #07Tooele County~24/wk-25.6%
  • #08Summit County~23/wk-0.5%
  • #09Box Elder County~21/wk+31.8%
  • #10Iron County~19/wk+11.4%
Open statewide map
7-day outlook

Daily projection

Year-weighted historical average for each calendar day, adjusted for day-of-week patterns. Holiday weekends bump projections slightly upward to reflect recreational travel.

Top 10 segments

Statewide hotspots

Single quarter-mile street segments with the most crashes in this calendar window across 2021–2025. Each row deep-links to the crash map zoomed to that segment.

#LocationCrashes
01I15, South Salt LakeSalt Lake County9View on map
02I80, South Salt LakeSalt Lake County9View on map
03I15, South Salt LakeSalt Lake County8View on map
046630 S STATE ST @ i-215 Eastbound, MurraySalt Lake County8View on map
05Sr224 @ Olympic Parkway, Summit Co.Summit County8View on map
06MAIN STREET @ 650 NORTH, Spanish ForkUtah County7View on map
07E STATE ST N NORTH COUNTY BLVD @ NORTH COUNTY BLVD, American ForkUtah County7View on map
08500 W 7200 S, MidvaleSalt Lake County7View on map
09I15, South Salt LakeSalt Lake County7View on map
101900 W HINCKLEY DR @ 5600 S, RoyWeber County7View on map
By hazard type

What to watch for

Hazards grouped by category — severity first, weather last. Within each group, cards are listed in an order optimized for audience clarity (most-serious-first for severity, vulnerable-users-first for people, morning-to-late-night for time). Each card links to the crash map filtered to that hazard.

By county

Where it's happening

Top counties by projected weekly crash volume. Each card shows projected count, year-over-year change, the dominant hazard, and the top 3 segments where crashes cluster in each commute window — morning rush, midday, and afternoon rush.

5-year context

This week, over time

Total crashes in the same ±7-day calendar window across the last five years.

About

Utah traffic crash data analysis

StreetExplor provides ongoing Utah traffic crash data analysis, combining five years of historical UDOT highway-safety records with predictive modeling and live Open-Meteo weather inputs. Each week we project crash risk for the next seven days across Utah's counties and highest-risk road segments — mapped to the same quarter-mile street_id network used by our interactive PMTiles crash map. The forecast numbers above refresh weekly; the methodology and data sources behind every projection are described below.

Method

How we forecast Utah crash risk

For today's day-of-year, we pull every crash within ±7 days across 2021–2025 — a 15-day rolling window across five years, roughly 75 days of comparable historical observations.

The baseline is a year-weighted average (recent years weight more: 0.28 (2025), 0.24, 0.20, 0.16, 0.12 (2021)). Each forecast day starts as the baseline scaled by its day-of-week multiplier. Holiday weekends (Memorial Day, Independence Day, Pioneer Day, Labor Day, Thanksgiving) receive an 8–12% bump for recreational travel.

The risk score for each hazard combines relative volume (60%), severity weighting (KSI and pedestrians up-weighted because Vision Zero and HSIP optimize for these outcomes), and a year-over-year trend bonus.

The forecast also uses weather. UDOT tags every crash with the weather at the time of the crash (rain, snow, fog, etc.) and the road surface (wet, snow/ice, dry). For each weather category we compute an empirical day-level rate: how many crashes per day occur when, say, snow is reported, versus a comparable day without snow. That ratio becomes a multiplier — for example, snow days in Utah historically run about 1.4–1.8× the dry-day rate. When the 7-day weather forecast from Open-Meteo calls for snow on a given day, that day's projection is multiplied by the snow multiplier from your own data. When the empirical sample is too small (fewer than 3 weather-days in the window), we fall back to FHWA's published rates from How Do Weather Events Impact Roads? (FHWA-HOP-15-038).

Locations are joined to UDOT's road network by street_id — the same quarter-mile segments used by the PMTiles crash map. Every count on this page ties back to a column in udot_stats.csv, and every address links to the crash map zoomed to that segment.

How hotspots are ranked. Most hazard hotspots are ranked within the same ±7-day seasonal window. But for rare, high-severity categories — KSI (killed or seriously injured), pedestrian, and bicycle crashes — a 15-day window holds too few events to rank locations reliably, so a single seasonal incident could outrank a persistently dangerous corridor. For these categories we instead rank hotspots on the full 2021–2025 record, surfacing structurally dangerous segments rather than seasonal flukes. Ties are broken deterministically so rankings are reproducible. Because a recurring severe or pedestrian/bicycle crash is a meaningful structural signal regardless of how busy a road is, these categories are always presented as definitive hotspots. For higher-volume hazards, segments with too few crashes to rank reliably are instead flagged as a low-confidence signal. All other projections, shares, and risk scores remain window-based.

What "#1 hotspot" vs. "recent activity" means. "#1 hotspot" is a confident label — the top segment has enough crashes to stand out reliably. "Recent activity" is a cautious label, shown only when a category is so sparse that its busiest segment has too few crashes to call a definitive hotspot. A common category like weekday crashes shows "#1 hotspot" precisely because it has plenty of data, while a rare category in a quiet week may show "recent activity" instead.

Data source: UDOT Highway Safety  ·  Live crash map