CrashRate

Fatal crash rate · Utah

Fatal crash rate in Box Elder County, Utah

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

Box Elder County, Utah2024 · fatal crashes recorded by NHTSA

14.1fatal crashes per 100,000 residents in 2024

In 2024, NHTSA recorded 9 fatal crashes in Box Elder County, Utah, where 63,985 people lived. That is 14.1 fatal crashes for every 100,000 residents, and 10 people died in those crashes. Over 2020 to 2024 the average was 15.4.

The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Box Elder County; the white posts are Utah and the United States.

Per 100,000
9 fatal crashes ÷ 63,985 residents × 100,000 = 14.1
Five-year
47 crashes (2020 to 2024) ÷ 305,980 resident-years × 100,000 = 15.4
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
20206657,94410.4
2021151859,68625.1
20227861,54811.4
2023101262,81715.9
202491063,98514.1

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 47 fatal crashes NHTSA coded to Box Elder County, Utah over five years, from the fields FARS records. Nothing is estimated or inferred.

Road typeCrashesShare
Interstate1634%
Other freeway or expressway00%
Other principal arterial715%
Minor arterial919%
Major collector817%
Minor collector49%
Local road36%
Unknown or not reported00%
Rural2451%
Urban2349%
Time of dayCrashesShare
Midnight to 5:59 am1021%
6 am to 11:59 am1021%
Noon to 5:59 pm1328%
6 pm to 11:59 pm1328%
Hour unknown12%
LightCrashesShare
Daylight2451%
Dark, not lighted (or lighting unknown)1940%
Dark, lighted36%
Dawn or dusk12%
Unknown or not reported00%
WeatherCrashesShare
Clear3166%
Cloudy1021%
Rain24%
Snow, sleet or freezing rain36%
Fog, smog or smoke12%
Severe wind, blowing sand or other00%
Unknown or not reported00%
InvolvingCrashesShare
A pedestrian511%
A bicyclist or other cyclist12%
A speeding-related vehicle919%
A driver police reported as drinking1430%
Most-named roadsCrashes
I-1513
SR-306
SR-1026
SR-134
US-893

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.