CrashRate

Fatal crash rate · Utah

Fatal crash rate in Beaver County, Utah

Fatal crashes recorded by NHTSA in Beaver County, Utah, 2020 to 2024, divided by the people who live there. Fatal crashes only: not injuries, not all crashes, not traffic in general.

Beaver County, Utah2024 · fatal crashes recorded by NHTSA

13.6fatal crashes per 100,000 residents in 2024

In 2024, NHTSA recorded 1 fatal crash in Beaver County, Utah, where 7,362 people lived. That is 13.6 fatal crashes for every 100,000 residents, and 1 person died in those crashes. Over 2020 to 2024 the average was 37.9.

The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Beaver County; the white posts are Utah and the United States. The shaded band is how far one crash moves Beaver County’s post.

Small population. Beaver County has 7,362 residents, so one crash moves the rate by 13.6 points and a single bad year can double it. Read the five-year average and the count, not the one-year rate alone.
Per 100,000
1 fatal crashes ÷ 7,362 residents × 100,000 = 13.6
Five-year
11 crashes (2020 to 2024) ÷ 28,998 resident-years × 100,000 = 37.9
Same year
Utah: 251 ÷ 3,502,983 = 7.2 · United States: 36,297 ÷ 340,003,797 = 10.7

Every year, 2020 to 2024

YearFatal crashesDeathsPopulationPer 100,000
2020227,08928.2
2021457,21355.5
2022457,33454.5
2023007,2710.0
2024117,36213.6

2024 is NHTSA’s Annual Report File and will be revised when the final file replaces it. Populations are July 1 estimates, Census Vintage 2025.

What the record says about those crashes, 2020 to 2024

Every figure is a count of the 11 fatal crashes NHTSA coded to Beaver County, Utah over five years, from the fields FARS records. Nothing is estimated or inferred.

Road typeCrashesShare
Interstate545%
Other freeway or expressway00%
Other principal arterial00%
Minor arterial19%
Major collector19%
Minor collector19%
Local road327%
Unknown or not reported00%
Rural11100%
Urban00%
Time of dayCrashesShare
Midnight to 5:59 am00%
6 am to 11:59 am19%
Noon to 5:59 pm655%
6 pm to 11:59 pm436%
Hour unknown00%
LightCrashesShare
Daylight764%
Dark, not lighted (or lighting unknown)218%
Dark, lighted00%
Dawn or dusk218%
Unknown or not reported00%
WeatherCrashesShare
Clear873%
Cloudy19%
Rain19%
Snow, sleet or freezing rain19%
Fog, smog or smoke00%
Severe wind, blowing sand or other00%
Unknown or not reported00%
InvolvingCrashesShare
A pedestrian00%
A bicyclist or other cyclist00%
A speeding-related vehicle655%
A driver police reported as drinking436%
Most-named roadsCrashes
I-155
300 N1
500 W1
SR-1531
SR-211

Road type is FARS FUNC_SYS; speeding is any vehicle coded SPEEDREL 2 to 5; drinking is any driver coded DRINKING = 1 (police-reported, not a blood-alcohol test). Road names are the trafficway strings as the police coded them, counted as written, so the same road can appear under two spellings.

How this is counted

  • Fatal crashes are rows in NHTSA’s Fatality Analysis Reporting System (FARS) file FARS2024NationalCSV.zip, accident.csv, one row per crash on a public road in which someone died within 30 days. Deaths are the FATALS field. Counties are the FARS STATE and COUNTY codes joined to Census FIPS codes.
  • Population is the Census Bureau’s July 1 estimate for the same year, county totals, Vintage 2025. Rate per 100,000 = crashes ÷ population × 100,000.
  • The five-year average is total crashes over the years with both inputs ÷ total population over those years × 100,000, the rolling form in 23 CFR 490.207.
  • What it cannot say. FARS has no injury-only or property-damage crashes, no congestion, and nothing about any one driver, trip or road’s risk. A crash is counted where it happened, not where the people lived. Rates are not ranked here; comparing two places means comparing both sets of inputs.

Informational only, not professional advice. Last reviewed: October 2026. Data snapshot built 2026-10-28.