Fatal crash rate in Sanpete County, Utah
Fatal crashes recorded by NHTSA in Sanpete County, Utah, 2020 to 2024, divided by the people who live there. Fatal crashes only: not injuries, not all crashes, not traffic in general.
Sanpete County, Utah2024 · fatal crashes recorded by NHTSA
16.2fatal crashes per 100,000 residents in 2024
In 2024, NHTSA recorded 5 fatal crashes in Sanpete County, Utah, where 30,881 people lived. That is 16.2 fatal crashes for every 100,000 residents, and 6 people died in those crashes. Over 2020 to 2024 the average was 14.1.
The road is a scale of fatal crashes per 100,000 residents in 2024, 0 to 40. The yellow post is Sanpete County; the white posts are Utah and the United States.
- Per 100,000
- 5 fatal crashes ÷ 30,881 residents × 100,000 = 16.2
- Five-year
- 21 crashes (2020 to 2024) ÷ 148,849 resident-years × 100,000 = 14.1
- Same year
- Utah: 251 ÷ 3,502,983 = 7.2 · United States: 36,297 ÷ 340,003,797 = 10.7
Every year, 2020 to 2024
| Year | Fatal crashes | Deaths | Population | Per 100,000 |
|---|---|---|---|---|
| 2020 | 4 | 4 | 28,528 | 14.0 |
| 2021 | 3 | 4 | 29,104 | 10.3 |
| 2022 | 5 | 5 | 29,771 | 16.8 |
| 2023 | 4 | 4 | 30,565 | 13.1 |
| 2024 | 5 | 6 | 30,881 | 16.2 |
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 21 fatal crashes NHTSA coded to Sanpete County, Utah over five years, from the fields FARS records. Nothing is estimated or inferred.
| Road type | Crashes | Share |
|---|---|---|
| Interstate | 0 | 0% |
| Other freeway or expressway | 0 | 0% |
| Other principal arterial | 10 | 48% |
| Minor arterial | 0 | 0% |
| Major collector | 4 | 19% |
| Minor collector | 3 | 14% |
| Local road | 4 | 19% |
| Unknown or not reported | 0 | 0% |
| Rural | 20 | 95% |
| Urban | 1 | 5% |
| Time of day | Crashes | Share |
|---|---|---|
| Midnight to 5:59 am | 0 | 0% |
| 6 am to 11:59 am | 6 | 29% |
| Noon to 5:59 pm | 9 | 43% |
| 6 pm to 11:59 pm | 6 | 29% |
| Hour unknown | 0 | 0% |
| Light | Crashes | Share |
|---|---|---|
| Daylight | 12 | 57% |
| Dark, not lighted (or lighting unknown) | 5 | 24% |
| Dark, lighted | 2 | 10% |
| Dawn or dusk | 2 | 10% |
| Unknown or not reported | 0 | 0% |
| Weather | Crashes | Share |
|---|---|---|
| Clear | 17 | 81% |
| Cloudy | 3 | 14% |
| Rain | 0 | 0% |
| Snow, sleet or freezing rain | 1 | 5% |
| Fog, smog or smoke | 0 | 0% |
| Severe wind, blowing sand or other | 0 | 0% |
| Unknown or not reported | 0 | 0% |
| Involving | Crashes | Share |
|---|---|---|
| A pedestrian | 1 | 5% |
| A bicyclist or other cyclist | 0 | 0% |
| A speeding-related vehicle | 8 | 38% |
| A driver police reported as drinking | 2 | 10% |
| Most-named roads | Crashes |
|---|---|
| US-89 | 5 |
| SR-89 | 2 |
| SR-132 | 2 |
| BRICKHILL ROAD | 1 |
| 400 W | 1 |
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 theFATALSfield. Counties are the FARSSTATEandCOUNTYcodes 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.