Traffic crash occurrence and sequence

The anonymously downloadable 2024 Final coordinated FARS files cover every qualifying U.S. fatal motor-vehicle traffic crash and provide year plus ST_CASE, crash time and jurisdiction/location, first harmful event, manner of collision, involved-unit/body classes, and explicitly numbered EVENTNUM/SOE sequences. Scope is limited to the final fatal-crash universe and 2024 schema/release.

The anonymously downloadable 2024 CRSS public-use family records sampled eligible police-reported crashes under year plus CASENUM, with crash time and national region/urbanicity context, first harmful event, manner of collision, involved-unit/body classes, and explicitly numbered EVENTNUM/SOE sequences. It is sampled evidence, not a census or arbitrary known-crash lookup; population estimates require weight, stratum, and variance-PSU fields.

The standing TIMS Crash and Party download links rows by CASE_ID and supplies crash date, time, reported and geocoded location, TYPE_OF_COLLISION determined by the first injury- or damage-causing event, MVIW describing what produced that event, party count and vehicle or party class, and pre-crash movement. This is strong occurrence, first-event, manner, and involved-unit evidence, but TIMS does not provide an ordered multi-event sequence and manoeuvre must not be treated as one. Pin answers to California scope, PROC_DATE, the codebook vintage, and documented final-versus-provisional status.

Anonymous crash-grain SODA/full-file rows identify each event by crash_record_id and emit the officer-entered crash date/time, street and coordinates, first_crash_type, crash_type, and num_units. This establishes recorded occurrence, location, first-collision/manner classification, and unit count for CPD-jurisdiction Chicago crashes. It does not emit involved-unit classes or a detailed ordered event sequence; retain crash_record_id, the partial-2015/citywide-from-September-2017 coverage boundary, and the extraction/metadata timestamp because no row-level release-vintage or coded-field-version field is exposed.

The open final coordinated collision and vehicle files identify a crash by collision_index or collision_year plus collision_ref_no and supply date, time, location, vehicle count and type, manoeuvre, skidding or overturning, object impacts, carriageway departure, and first point of impact. This is useful official occurrence and involved-unit circumstance evidence, but STATS19 does not supply a first-harmful-event field, a general collision-manner field, or an ordered multi-event sequence; first point of impact must not be represented as sequence. Pin answers to Great Britain scope, the final 2025 data published 2026-07-30, and 2024-specification mappings.

Anonymous unit-grain rows join to the crash event through crash_record_id and emit crash_date, unit_type, vehicle_type and use, travel direction, pre-crash maneuver, and first contact point. This usefully establishes involved-unit classes and recorded pre-crash/first-impact circumstances. It does not independently provide event location, first-crash classification, or a detailed ordered sequence, so it complements rather than replaces the Crashes asset; retain the crash/unit key, Chicago scope, and extraction/metadata timestamp.