Traffic Fatalities (NHTSA FARS)

People killed in motor-vehicle crashes on public roads in Georgia and each county, by crash location, with the number of fatal crashes.

Source: National Highway Traffic Safety Administration (NHTSA), Fatality Analysis Reporting System (FARS), national CSV files, crash file (accident.csv): Final Files 2000-2023 and the 2024 Annual Report File (preliminary)
Year coverage: 2000–2024
Updated: annual
Version: 1.0.0
Schema hash: cc2e79e89f9d

Detail levels available

StateCounty · default

Overview

People killed in motor-vehicle traffic crashes in Georgia and in each of its 159 counties, 2000-2024, from the National Highway Traffic Safety Administration's Fatality Analysis Reporting System (FARS), the census of every crash on a public road in which someone died within 30 days. The headline is the number of people killed; the number of fatal crashes they died in is served beside it. Counted in the county where the crash happened. Read from NHTSA's Final Files 2000-2023 and the 2024 Annual Report File (preliminary); file_status marks each year's release.

Row grain: One row per year, county_fips, tract_geoid.

Key metric

num_deaths — Traffic Deaths (count)

The single headline value most answers want.

JSON schema →Data contract (YAML) →

Variables

Every column in the fact table. The code is the exact field name the API returns.

Column	Type	Unit	Range	Null?	Description
`year`Year	integer	—	—	no	Calendar year of the crash (FARS YEAR, equal to the file's data year). A person who died within 30 days of a late-December crash counts in the crash's year. Every year is an NHTSA Final File except the latest, the preliminary Annual Report File (see file_status). Full description▾ Calendar year of the crash (FARS YEAR, equal to the file's data year). A person who died within 30 days of a late-December crash counts in the crash's year. Every year is an NHTSA Final File except the latest, the preliminary Annual Report File (see file_status).
`county_fips`County FIPS	string	—	—	yes	5-digit FIPS code of the county where the crash happened ('13' + FARS's 3-digit COUNTY code), NULL on the Georgia row. Every county has a row every year, 0 when it had no fatal crash. Crashes whose FARS county code names no county are counted in the Georgia row only (listed in limitations). Full description▾ 5-digit FIPS code of the county where the crash happened ('13' + FARS's 3-digit COUNTY code), NULL on the Georgia row. Every county has a row every year, 0 when it had no fatal crash. Crashes whose FARS county code names no county are counted in the Georgia row only (listed in limitations). Joins counties; adds its label columns.
`tract_geoid`Tract GEOID	string	—	—	yes	Always NULL: crashes are counted by state and county only. Kept for the health domain's standard key shape. Full description▾ Always NULL: crashes are counted by state and county only. Kept for the health domain's standard key shape. Joins tracts; adds its label columns.
`num_deaths`Traffic Deaths	integer	count	—	yes	People killed in motor-vehicle crashes on public roads that happened in the place during the year. Full description▾ People killed in motor-vehicle crashes on public roads that happened in the place (Georgia, or the county) during the year: the sum of FARS's FATALS, the people who died within 30 days of the crash, in a vehicle or not (pedestrians and cyclists included), over the year's crash records. Counted where the crash happened, not where the person lived. 0 on a county row is a real zero: no fatal crash in the county that year.
`num_fatal_crashes`Fatal Crashes	integer	count	—	yes	Fatal crashes that happened in the place during the year: the number of FARS crash records (one per crash in which at least one person died within 30 days). Every fatal crash killed at least one person, so num_deaths is never below it. Full description▾ Fatal crashes that happened in the place during the year: the number of FARS crash records (one per crash in which at least one person died within 30 days). Every fatal crash killed at least one person, so num_deaths is never below it.
`file_status`File Status	string	—	—	no	Whether the year's counts are final or preliminary (annual_report_file: NHTSA's Annual Report File, to be revised). Full description▾ Release status of the year's FARS file, the same on every row of a year: final (NHTSA's Final File) or annual_report_file (the Annual Report File, NHTSA's preliminary release of the latest year, replaced by the Final File about a year later, when counts change). Describes the year, not part of the row's key; filter it to 'final' to leave out preliminary counts. 2 allowed values▾ `final` `annual_report_file`

Filters

Query parameters the fact endpoint accepts. Comma-separated values are OR within a parameter; multiple parameters AND together.

Parameter	Kind	Allowed values	Notes
`year`	year_exact	any value	—
`year_min`	year_range	any value	—
`year_max`	year_range	any value	—
`detail`	detail	`countiesstates`	enum-enforced, default: counties
`county_fips`	foreign_key	any value	multi-value
`tract_geoid`	foreign_key	any value	multi-value
`file_status`	categorical	`finalannual_report_file`	multi-value, enum-enforced

Example requests

Run these against the base URL — they return live data.

All rows (first page), counties level

curl "https://georgiacivicdata.org/api/v1/health/traffic_fatalities"

counties data for 2024

curl "https://georgiacivicdata.org/api/v1/health/traffic_fatalities?year=2024"

Filtered to file_status = final for 2024

curl "https://georgiacivicdata.org/api/v1/health/traffic_fatalities?year=2024&file_status=final"

One county (FIPS 13121), 2024

curl "https://georgiacivicdata.org/api/v1/health/traffic_fatalities?county_fips=13121&year=2024&detail=counties"

Download 2024 as CSV

curl "https://georgiacivicdata.org/api/v1/health/traffic_fatalities?year=2024&format=csv"

Notes & limitations

NULL handling

Zero is a real, reported value.

Limitations

Counted where the crash happened, not where the people killed lived, so county figures differ from death-certificate counts by county of residence (such as DPH OASIS motor vehicle deaths). 2024 is NHTSA's preliminary Annual Report File (file_status 'annual_report_file'): its counts will change when NHTSA replaces it with the Final File, about a year later. FARS is a census of fatal crashes, so every county has a row every year and a 0 is a real zero (4 to 13 counties a year had no fatal crash). Final files are revised too: NHTSA re-posts past years' files (the files read here were posted 2026-02-04 for 2000-2020, 2026-04-01 for 2022 and 2023, and 2026-06-24 for 2021), and the 2023 national total moved from 40,901 to 41,025 when it became final. County rows fall short of the Georgia row by exactly 5 crashes (6 deaths) whose county FARS left unknown (code 0 in 2001, 2004, 2005 and 2006; code 999 in 2002), counted in the Georgia row only. Only crashes involving a motor vehicle in transport on a trafficway open to the public, in which someone (a vehicle occupant or not, such as a pedestrian or cyclist) died within 30 days, are counted; crashes on private property such as driveways and parking lots are not. A death is counted in the year of the crash. Counts only, no rate: counties differ greatly in population and traffic, so compare them per resident with a population from the census topics (a rate so made is our calculation, not NHTSA's). Small counties have few deaths and swing from year to year. Deaths come in clusters (up to 7 in one crash, though about 9 in 10 fatal crashes killed one person), so they are not independent events and a test that treats them as such overstates its certainty. These files are as retrieved 2026-10-24. tract_geoid is always NULL.