CrashRate

Fatal crash rate · Minnesota

Fatal crash rate in Pipestone County, Minnesota

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

Pipestone County, Minnesota2024 · fatal crashes recorded by NHTSA

0.0fatal crashes per 100,000 residents in 2024

NHTSA recorded no fatal crashes in Pipestone County, Minnesota in 2024, where 9,251 people lived. Over 2021 to 2022 the average was 16.0.

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

Small population. Pipestone County has 9,251 residents, so one crash moves the rate by 10.8 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
0 fatal crashes ÷ 9,251 residents × 100,000 = 0.0
Five-year
3 crashes (2021 to 2022) ÷ 18,693 resident-years × 100,000 = 16.0
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
2020009,4180.0
2021119,35910.7
2022229,33421.4
2023009,2890.0
2024009,2510.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 3 fatal crashes NHTSA coded to Pipestone County, Minnesota over five years, from the fields FARS records. Nothing is estimated or inferred.

Road typeCrashesShare
Interstate00%
Other freeway or expressway00%
Other principal arterial133%
Minor arterial267%
Major collector00%
Minor collector00%
Local road00%
Unknown or not reported00%
Rural3100%
Urban00%
Time of dayCrashesShare
Midnight to 5:59 am00%
6 am to 11:59 am267%
Noon to 5:59 pm00%
6 pm to 11:59 pm133%
Hour unknown00%
LightCrashesShare
Daylight133%
Dark, not lighted (or lighting unknown)133%
Dark, lighted00%
Dawn or dusk133%
Unknown or not reported00%
WeatherCrashesShare
Clear133%
Cloudy133%
Rain00%
Snow, sleet or freezing rain00%
Fog, smog or smoke133%
Severe wind, blowing sand or other00%
Unknown or not reported00%
InvolvingCrashesShare
A pedestrian00%
A bicyclist or other cyclist00%
A speeding-related vehicle133%
A driver police reported as drinking133%
Most-named roadsCrashes
SR-302
SR-231
81ST STREET1

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.