CrashRate

Fatal crash rate · Minnesota

Fatal crash rate in Steele County, Minnesota

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

Steele County, Minnesota2024 · fatal crashes recorded by NHTSA

16.0fatal crashes per 100,000 residents in 2024

In 2024, NHTSA recorded 6 fatal crashes in Steele County, Minnesota, where 37,453 people lived. That is 16.0 fatal crashes for every 100,000 residents, and 6 people died in those crashes. Over 2020 to 2024 the average was 8.7.

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

Per 100,000
6 fatal crashes ÷ 37,453 residents × 100,000 = 16.0
Five-year
13 crashes (2020 to 2024) ÷ 149,774 resident-years × 100,000 = 8.7
Same year
Minnesota: 431 ÷ 5,797,405 = 7.4 · United States: 36,297 ÷ 340,003,797 = 10.7

Every year, 2020 to 2024

YearFatal crashesDeathsPopulationPer 100,000
20204437,38810.7
20210037,4410.0
20222237,4715.3
20231137,4622.7
20246637,45316.0

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

Road typeCrashesShare
Interstate323%
Other freeway or expressway00%
Other principal arterial215%
Minor arterial18%
Major collector431%
Minor collector18%
Local road18%
Unknown or not reported18%
Rural862%
Urban431%
Time of dayCrashesShare
Midnight to 5:59 am323%
6 am to 11:59 am431%
Noon to 5:59 pm431%
6 pm to 11:59 pm18%
Hour unknown18%
LightCrashesShare
Daylight646%
Dark, not lighted (or lighting unknown)431%
Dark, lighted00%
Dawn or dusk215%
Unknown or not reported18%
WeatherCrashesShare
Clear969%
Cloudy18%
Rain00%
Snow, sleet or freezing rain215%
Fog, smog or smoke00%
Severe wind, blowing sand or other00%
Unknown or not reported18%
InvolvingCrashesShare
A pedestrian215%
A bicyclist or other cyclist00%
A speeding-related vehicle431%
A driver police reported as drinking215%
Most-named roadsCrashes
I-353
US-2182
CR-7 LEMOND RD1
CR-171
CR-48 E MAIN ST1

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.