Introduction
The Statewide Integrated Traffic Records System (SWITRS) consists of data collected and maintained by the California Highway Patrol (CHP). SWITRS contains all crashes that were reported to CHP by local and governmental agencies. For more information regarding SWITRS or for detailed summaries by year, please visit the CHP website. You can also download complete datasets and request statistical reports via the I-SWITRS Website provided by CHP.
If you are interested in SWITRS crash rankings of cities or counties without investigating the actual datasets, the California Office of Traffic Safety (OTS) has an excellent resource at: OTS Crash Rankings. Their site allows you to choose a county or city and see crash rankings by total count, vehicle miles travelled, or by average population.
Final vs Provisional
We determine the dataset is final when we process the data after CHP announces the report of the specific year. CHP hasn't released the 2023 SWITRS Annual Report on CHP SWITRS website yet so we say provisional for 2023 and later datasets.
Working with the relational database structure
The data have a hierarchical structure.
- The
CRASH
table contains information on each crash, one line per crash. - The
PARTY
table contains information from all parties involved in the crash, one line per party. Parties are the major players in a traffic crash - drivers, pedestrians, bicyclists, and parked vehicles. The information includes personal descriptors and vehicle descriptors. - The
VICTIM
table contains information about the victims - persons associated with each party. For example, a motorcyclist and his passenger are each a victim. Injury severity is included in theVICTIM
table.
The victims can be thought of as being nested within parties and parties can be thought of as being nested within crashes. Another way to conceptualize the data is to use the entity-relationship model common in relational database management systems. In this data model, CRASH
, PARTY
, and VICTIM
are entities that have very specific relationships to each other. CRASH
is a “strong” or “parent” entity because it can exist on its own. PARTY
is a “weak” or “child” entity, because it logically depends on an instance of CRASH
. In other words, a driver cannot be a party in a crash unless the crash exists and is in the crash table. Likewise, VICTIM
is a weak entity, because it depends on PARTY
for its existence.
The figure shows an example database with CRASH
, PARTY
, and VICTIM
tables.
The database is tiny – it only contains information on 2 crashes. CRASH
has 3 variables: CASE ID
,
DAY OF WEEK
, and COUNTY
.
PARTY
has 4 variables: CASE ID
, PARTY NUMBER
, PARTY AGE
, and VEHICLE MAKER
.
VICTIM
has 7 variables: CASE ID
, PARTY NUMBER
, VICTIM GENDER
, VICTIM AGE
, VICTIM ROLE
, VICTIM SEATING POSITION
, and VICTIM SAFETY EQUIPMENT
.
The relationships between each pair of tables are represented below. It is important to understand the relationships when merging tables.
The rectangles represent data tables; the arrows and accompanying text describe the relationship.
In the CRASH
- PARTY
relationship, the records are linked with the CASE ID
variable and any number of PARTY
records can be associated with a crash.
The PARTY
- VICTIM
relationship tells us that the linkage require two variables,
CASE ID
and PARTY NUMBER
and that any number of victims can be associated with a party.
An important aspect of the relationship between the PARTY
and VICTIM
tables is that some parties (i.e., drivers, bicyclists, pedestrians) will also appear in the VICTIM
table.
Injured parties will appear in the VICTIM
table; uninjured parties will not.
A common way to work with data of this structure is to create a PARTY
table or a VICTIM
table that has data from all its parents joined to each row.
For example, if you plan to do analyses at the victim-level, you can start with a VICTIM
table and join in
values from corresponding PARTY
and CRASH
tables. In the figure, the CRASH
variables and the PARTY
variables are joined to the VICTIM
table.
Doing so provides a victim-level table that can be summarized (for example, count or sums can be generated),
while considering PARTY
or CRASH
variables.
You must keep in mind that the PARTY
and CRASH
variable will repeat for as many victims as there are.
Codebook
The SWITRS codebook provides a complete description of all the fields including the variable name and all possible values for the field.
If you want to download a Microsoft Word version of the codebook, please click here.
Last Update: 1/23/2024
New Level of Victim Degree of Injury New
CHP has added three additional classifications of injury status based on the Model Minimum Uniform Crash Criteria (MMUCC) 5th Edition released in 2017. The MMUCC is a standardized method for reporting traffic crashes and the vehicles, persons, and environment involved.
New Victim Degree of Injury | Old Definition of Victim Degree of Injury |
---|---|
5 - Suspected Serious Injury | 2 - Severe Injury |
6 - Suspected Minor Injury | 3 - Other Visible Injury |
7 - Possible Injury | 4 - Complaint of Pain |
For the purpose of analysis across multiple years with old definition (2, 3, and 4), we combined injury status categories using the latest definitions (5, 6 and 7); i.e., all victims coded as "Severe Injury" or "Suspected Serious Injury" are shown as "Suspected Serious Injury" in our tools.
Crash Level
Item Name | Variable Name | Description | Values |
---|---|---|---|
Case Id | CASE_ID | The unique identifier of the crash case(barcode beginning 2002; 19 digit code prior to 2002) | |
Crash Year | ACCIDENT_YEAR | The year when the crash occurred | |
Processing Date | PROC_DATE | The date that the crash case was last changed (YYYYMMDD) | |
Jurisdiction | JURIS | Law enforcement agency that has jurisdiction over the crash. For allied agency, it is a four character subset of the "NCIC number" assigned by the FBI. For the CHP, it is 9 followed by a three-digit area number. | |
Crash Date | COLLISION_DATE | The date when the crash occurred (YYYYMMDD) | |
Crash Time | COLLISION_TIME | The time when the crash occurred in 24 hour military time. Unknown time is coded as 2500-2559. (24 hour time) | Data may appear with no leading zero(s). |
Officer Id | OFFICER_ID | The badge number of the officer who wrote the crash report. | |
Reporting District | REPORTING_DISTRICT | Value of the field "reporting district on the crash report. | |
Day of Week | DAY_OF_WEEK | The code for the day of the week when the crash occurred |
|
CHP Shift | CHP_SHIFT | CHP shift at the time of the crash |
|
Population | POPULATION | Deprecated. See notesi. | |
County City Location | CNTY_CITY_LOC | The city or unincorporated county where the crash occurred. | Data may appear with no leading zero. |
Special Condition | SPECIAL_COND | A computed value. 0 means not private property. |
|
Beat Type | BEAT_TYPE | Location of crash based on beat. |
|
CHP Beat Type | CHP_BEAT_TYPE | Location of crash based on beat. |
|
City Division LAPD | CITY_DIVISION_LAPD | Deprecated. See notesii. | |
CHP Beat Class | CHP_BEAT_CLASS | Location of crash based on beat. |
|
Beat Number | BEAT_NUMBER | Beat of the officer who reported the crash. | |
Primary Rd | PRIMARY_RD | The name of roadway on which the crash occurred | |
Secondary Rd | SECONDARY_RD | The name of the roadway that intersects the primary roadway | |
Distance | DISTANCE | Distance of the crash from the intersection with the secondary roadway in feet | |
Direction | DIRECTION | Direction of the crash from the intersection with the secondary roadway. |
|
Intersection | INTERSECTION | A flag that denotes if the crash occurred at the intersection with the secondary roadway |
|
Weather 1 | WEATHER_1 | Weather condition at the time of the crash |
|
Weather 2 | WEATHER2 | Additional weather condition at the time of the crash | same as weather 1 above |
State Highway Indicator | STATE_HWY_IND | A flag to indicate whether the crash is on or near a state highway. See notesiii. |
|
Caltrans County | CALTRANS_COUNTY | Deprecated. See notesiv. | |
Caltrans District | CALTRANS_DISTRICT | Deprecated. See above. | |
State Route | STATE_ROUTE | Deprecated. See above. | 0 - Not State Highway |
Route Suffix | ROUTE_SUFFIX | Deprecated. See above. | |
Postmile Prefix | POSTMILE_PREFIX | Deprecated. See above. | |
Postmile | POSTMILE | Deprecated. See above. | |
Location Type | LOCATION_TYPE | Deprecated. See above. |
|
Ramp Intersection | RAMP_INTERSECTION | Deprecated. See above. |
|
Side Of Highway | SIDE_OF_HWY | Code provided by Caltrans Coders; applies to divided highway, based on nominal direction of route; for single vehicle is same as nominal direction of travel, overruled by impact with second vehicle after crossing median |
|
Tow Away | TOW_AWAY | A flag to indicate whether the vehicle was towed away from the crash scene. |
|
Crash Severity | COLLISION_SEVERITY | The worst injury suffered by any victim in the crash. |
|
Killed victims | NUMBER_KILLED | Number of killed victims | 0 to N for each crash |
Injured victims | NUMBER_INJURED | Number of injured victims | 0 to N for each crash |
Party Count | PARTY_COUNT | Number of parties involved in the crash. Note: a vehicle counts as one party regardless of the number of occupants. | 1 to N for each crash |
Primary Crash Factor | PRIMARY_COLL_FACTOR | The primary cause of the crash |
|
PCF Violation Code | PCF_CODE_OF_VIOL | The law code that was violated and was the primary cause of the crash. Note: Vehicle Code is usually omitted. |
|
PCF Violation Category | PCF_VIOL_CATEGORY | A value computed from the law section that was given as the primary cause of the crash. |
|
PCF Violation | PCF_VIOLATION | The law section given as the primary cause of the crash. The subsection is in the data element pcf_viol_subsection | |
PCF Violation Subsection | PCF_VIOL_SUBSECTION | The subsection of the law section given as the primary cause of the crash in the data element pcf_violation | Blank if no subsection. |
Hit And Run | HIT_AND_RUN | A flag to indicate the severity of hit -and-run crash. Felony hit-and-run resulted in injury or death to other parties. Misdemeanor hit-and-run did not result in injury or death to other parties. |
|
Type of Crash | TYPE_OF_COLLISION | The general type of crash as determined by the first injury or damage-causing event. |
|
Motor Vehicle Involved With | MVIW | Describes what, in conjunction with a motor vehicle in-transport, produced the first injury or damage-causing event, on or off the road. |
|
Ped Action | PED_ACTION | The action just prior to the crash of the first pedestrian injured or otherwise involved. |
|
Road Surface | ROAD_SURFACE | Roadway surface condition at the time of the crash in the traffic lane(s) involved. |
|
Road Condition 1 | ROAD_COND_1 | Roadway condition at the time of the crash in the traffic lane(s) involved. |
|
Road Condition 2 | ROAD_COND_2 | Second roadway condition at the time of the crash in the traffic lane(s) involved. | same as road condition 1 above |
Lighting | LIGHTING | Lighting conditions at the crash location and the time of the crash. |
|
Control Device | CONTROL_DEVICE | Presence and condition of crash related traffic control devices at the time of the crash. Control devices include regulatory, warning, and construction signs. This excludes striping and officers or other persons directing traffic. |
|
CHP RoadType | CHP_ROAD_TYPE | Deprecated. See notesv. | |
Pedestrian Crash | PEDESTRIAN_ACCIDENT | Indicates whether the crash involved a pedestrian | Y or blank |
Bicycle Crash | BICYCLE_ACCIDENT | Indicates whether the crash involved a bicycle | Y or blank |
Motorcycle Crash | MOTORCYCLE_ACCIDENT | Indicates whether the crash involved a motorcycle | Y or blank |
Truck Crash | TRUCK_ACCIDENT | Indicates whether the crash involved a big truck | Y or blank |
Not Private Property | NOT_PRIVATE_PROPERTY | Y indicates that the crash did not occur on private property | Y or blank |
Alcohol Involved | ALCOHOL_INVOLVED | Indicates whether the crash involved a party that had been drinking. Note: a passenger does not count as a party. | Y or blank |
Statewide Vehicle Type At Fault | STWD_VEHTYPE_AT_FAULT | Indicates the Statewide Vehicle Type of the party who is at fault | see Party folder Statewide Vehicle Type item |
CHP Vehicle Type At Fault | CHP_VEHTYPE_AT_FAULT | indicates the CHP Vehicle Type of the party who is at fault | see Party folder CHP Vehicle Type Towing item |
Severe Injury count | COUNT_SEVERE_INJ | Number of victims in the crash with suspected serious injury or severe injury | 0 to N for each crash |
Other Visible Injury count | COUNT_VISIBLE_INJ | Number of victims in the crash with suspected minor injury or visible injury | 0 to N for each crash |
Complaint of Pain Injury count | COUNT_COMPLAINT_PAIN | Number of victims in the crash with possible injury or complaint of pain | 0 to N for each crash |
Pedestrian Killed count | COUNT_PED_KILLED | Number of killed pedestrian victims | 0 or 1 for each crash |
Pedestrian Injured count | COUNT_PED_INJURED | Number of injured pedestrian victims | 0 or 1 for each crash |
Bicyclist Killed count | COUNT_BICYCLIST_KILLED | Number of killed bicyclists | 0 to N for each crash |
Bicyclist Injured count | COUNT_BICYCLIST_INJURED | Number of injured bicyclists | 0 to N for each crash |
Motorcyclist Killed count | COUNT_MC_KILLED | Number of killed motorcyclists | 0 to N for each crash |
Motorcyclist Injured count | COUNT_MC_INJURED | Number of injured motorcyclists | 0 to N for each crash |
Primary Ramp | PRIMARY_RAMP | A description of the ramp, if any, on primary roadway. This value is computed by the key operator from information on the crash report. |
|
Secondary Ramp | SECONDARY_RAMP | A description of the ramp, if any, on secondary roadway. This value is computed by the key operator from information on the crash report. | Same as primary_ramp |
CHP generated GPS latitude coordinate | LATITUDE | Latitude of the crash location in decimal degrees. The decimal point is included. LATITUDE and LONGITUDE are from the crash report. | |
CHP generated GPS longitude coordinate | LONGITUDE | Longitude of the crash location in decimal degrees. The decimal point is included. There is no minus sign. The longitude is understood to be west of meridian. LATITUDE and LONGITUDE are from the crash report. | |
Local Report Number | local_report_number | The report number assigned by the reporting agency to the crash report | |
X Coordinate Location | POINT_X | The longitude of the geocoded location; uses the World Geodetic System from 1984 (WGS84). POINT_X and POINT_Y are generated using the geocoding process by UC Berkeley SafeTREC | |
Y Coordinate Location | POINT_Y | The latitude of the geocoded location; uses the World Geodetic System from 1984 (WGS84). POINT_X and POINT_Y are generated using the geocoding process by UC Berkeley SafeTREC. | |
City | CITY | ||
County | COUNTY |
Party Level
Item Name | Variable Name | Description | Values |
---|---|---|---|
Case Id | CASE_ID | The unique identifier of the crash case | |
Party Number | PARTY_NUMBER | A number that together with the case_id uniquely identifies a party in a crash. | 1 to 999 |
Party Type | PARTY_TYPE | Involved party type |
|
At Fault | AT_FAULT | Indicates whether the party was at fault in the crash |
|
Party Sex | PARTY_SEX | The gender of the party |
|
Party Age | PARTY_AGE | The age of the party at the time of the crash | 0 to 125+ (998=UNKNOWN) |
Party Sobriety | PARTY_SOBRIETY | The state of sobriety of the party |
|
Party Drug Physical | PARTY_DRUG_PHYSICAL | The state of the party with regard to drugs and physical condition |
|
Direction Of Travel | DIR_OF_TRAVEL | Direction that the party was traveling at the time of the crash. The direction is the direction of the highway, not the compass direction. For example, I-5 direction is N or S even though near Sacramento International Airport its compass direction is east-west. |
|
Party Safety Equipment 1 | PARTY_SAFETY_EQUIP_1 | The safety equipment of the party |
|
Party Safety Equipment 2 | PARTY_SAFETY_EQUIP_2 | The safety equipment of the party | same as Party Safety Equipment 1 above |
Financial Responsibility | FINAN_RESPONS | Financial responsibility of the party |
|
Special Information 1 | SP_INFO_1 | Value A indicates that the crash involved a vehicle known to be, or believed to be, transporting a hazardous material as defined in CVC Section 353, whether or not the crash involved a Hazardous Material Incidentvi. |
|
Special Information 2 | SP_INFO_2 | Cell phone |
|
Special Information 3 | SP_INFO_3 | Value E indicates that the crash involved a motor vehicle in-transport passing a stopped school bus with its red signal lamps in operation, pursuant to CVC Section 22112, or reacting to, pursuant to CVC Section 22454vii. |
|
OAF Violation Code | OAF_VIOLATION_CODE | Other associated factor law code violated |
|
OAF Violation Category | OAF_VIOL_CAT | Category of the factor that contributed to the crash but was not the primary cause of the crash. |
|
OAF Violation Section | OAF_VIOL_SECTION | The CVC section of the secondary violation that contributed to the crash. | |
OAF Violation Suffix | OAF_VIOLATION_SUFFIX | The subsection of the CVC section of the secondary violation that contributed to the crash. | Blank may appear if no suffix. |
Other Associated Factor 1 | OAF_1 | A factor that contributed to the crash but was not the primary cause of the crash. |
|
Other Associated Factor 2 | OAF_2 | A factor that contributed to the crash but was not the primary cause of the crash. | same as OAF 1 above |
Party Number Killed | PARTY_NUMBER_KILLED | Number of killed victims in the party | 0 to N for each party |
Party Number Injured | PARTY_NUMBER_INJURED | Number of injured victims in the party | 0 to N for each party |
Movement Preceding Crash | MOVE_PRE_ACC | The action of the vehicle prior to the crash and before evasive action. This movement does not have to correspond with the PCFviii. |
|
Vehicle Year | VEHICLE_YEAR | The model year of the party's vehicle | 9999 or blank = not stated |
Vehicle Make | VEHICLE_MAKE | The make of the party's vehicle | |
Statewide Vehicle Type | STWD_VEHICLE_TYPE | Type of the party's vehicle according to a list called "statewide vehicle type" |
|
CHP Vehicle Type Towing | CHP_VEH_TYPE_TOWING | The type of the solitary vehicle or the tractor unit according to the CHP manual HPM 110.5 Chapter 3 Annex F Vehicle Type Codes. |
|
CHP Vehicle Type Towed | CHP_VEH_TYPE_TOWED | The type of the first trailer unit according to the CHP manual HPM 110.5 Chapter 3 Annex F Vehicle Type Codes. | same as CHP vehicle type towing above |
Party Race | RACE | The party’s race based on the reporting officer's judgment. |
|
Inattention | INATTENTION | Type of inattention |
|
Special Info F | SPECIAL_INFO_F | The value F indicates that the party's vehicle is a 75 ft Motor Truck Combo. The current crash report form no longer has a box to indicate this. |
|
Special Info G | SPECIAL_INFO_G | The value G indicates that the party's vehicle is a 32 ft Trailer Combo. The current crash report form no longer has a box to indicate this. |
|
Local Report Number | local_report_number | The value G indicates that the party's vehicle is a 32 ft Trailer Combo. The current crash report form no longer has a box to indicate this. | The report number assigned by the reporting agency to the crash report |
Victim Level
Item Name | Variable Name | Description | Values |
---|---|---|---|
Case Id | CASE_ID | The unique identifier of the crash case | |
Party Number | PARTY_NUMBER | The unique identifier of the party in the crash that this victim belongs to | 1 to 999 |
Victim Role | VICTIM_ROLE | The role of the victim |
|
Victim Sex | VICTIM_SEX | The gender of the victim |
|
Victim Age | VICTIM_AGE | The age of the victim at the time of the crash |
|
Victim Degree of Injury | VICTIM_DEGREE_OF_INJURY | The severity of the injury to the victim |
|
Victim Seating Position | VICTIM_SEATING_POSITION | The severity of the injury to the victim |
|
Victim Safety Equipment 1 | VICTIM_SAFETY_EQUIP_1 | The safety equipment of the victim |
|
Victim Safety Equipment 2 | VICTIM_SAFETY_EQUIP_2 | The safety equipment of the victim | same as Victim Safety Equipment 1 above (eff. Jan 2002) |
Victim Ejected | VICTIM_EJECTED | Indicates whether the victim was ejected from the vehicle |
|
Victim Number | VICTIM_NUMBER | The unique identifier of the victim |
- i The data element was intended to be the population count of the city or county at the time of the crash. However, population count is time-dependent. Existing values are computed from a lookup table with no effective dates. Therefore the value cannot be accurate over time.
- ii The column translates the value of the data element "reporting_district" in crashes reported by LAPD to a single letter. However, LAPD currently has 21 districts but the translation only covers 18 districts. Anyone wanting LAPD district can get it from the last two digits of the data element "reporting_district".
- iii The officer checks the box "state highway related" if the crash was on or near a state highway. When the box is checked, the data element has the value Y. However, if Caltrans later decides that the crash was not state highway related, the data element is changed to N, for not state highway related.
- iv These data elements are from Caltrans coding form Card 8. The values are available only on some highway related documents that were received as hardcopy and are meaningful only to Caltrans.
- v The type of roadway at the location of the crash. This column is deprecated. The value is based on CHP beat and post mile. The post mile is from Caltrans coding form Card 8 but we stopped doing Card 8 on CHP crashes in 2015.
- vi HPM 110.5 chapter 4 paragraph 28. a.
- vii HPM 110.5 chapter 4 paragraph 28. f.
- viii HPM 110.5 chapter 4 paragraph 26