National Collision Database (NCDB) – a database containing all police-reported motor vehicle collisions on public roads in Canada. Selected variables (data elements) relating to fatal and injury collisions for the collisions from 1999 to the most recent available data.

The Motor Vehicle Collisions crash table contains details on the crash event. Each row represents a crash event. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf). It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details.For the most accurate, up to date statistics on traffic fatalities, please refer to the NYPD Motor Vehicle Collisions page (updated weekly) or Vision Zero View (updated monthly). Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles to other problems. Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions. Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety. Police officers complete form MV-104AN for all vehicle collisions. The MV-104AN is a New York State form that has all of the details of a traffic collision. Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts. Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City. TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014. Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities. Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS). FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse. Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

The Motor Vehicle Collisions vehicle table contains details on each vehicle involved in the crash. Each row represents a motor vehicle involved in a crash. The data in this table goes back to April 2016 when crash reporting switched to an electronic system. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf). It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details. Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles to other problems. Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions. Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety. Police officers complete form MV-104AN for all vehicle collisions. The MV-104AN is a New York State form that has all of the details of a traffic collision. Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts. Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City. TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014. Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities. Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS). FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse. Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

This dataset contains information about vehicles (or units as they are identified in crash reports) involved in a traffic crash. This dataset should be used in conjunction with the traffic Crash and People dataset available in the portal. “Vehicle” information includes motor vehicle and non-motor vehicle modes of transportation, such as bicycles and pedestrians. Each mode of transportation involved in a crash is a “unit” and get one entry here. Each vehicle, each pedestrian, each motorcyclist, and each bicyclist is considered an independent unit that can have a trajectory separate from the other units. However, people inside a vehicle including the driver do not have a trajectory separate from the vehicle in which they are travelling and hence only the vehicle they are travelling in get any entry here. This type of identification of “units” is needed to determine how each movement affected the crash. Data for occupants who do not make up an independent unit, typically drivers and passengers, are available in the People table. Many of the fields are coded to denote the type and location of damage on the vehicle. Vehicle information can be linked back to Crash data using the “CRASH_RECORD_ID” field. Since this dataset is a combination of vehicles, pedestrians, and pedal cyclists not all columns are applicable to each record. Look at the Unit Type field to determine what additional data may be available for that record.

The Chicago Police Department reports crashes on IL Traffic Crash Reporting form SR1050. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available here.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

Contains locations and information about every crash incident reported to the police in Allegheny County from 2004 to 2024. Fields include injury severity, fatalities, information about the vehicles involved, location information, and factors that may have contributed to the crash. Data is provided by PennDOT and is subject to PennDOT's data privacy restrictions, which are noted in the metadata information section below.

The NHTSA Vehicle Crash Test Database contains engineering data measured during various types of research, the New Car Assessment Program (NCAP), and compliance crash tests. Information in this database refers to the performance and response of vehicles and other structures in impacts. This database is not intended to support general consumer safety issues. For general consumer information please see the NHTSA's information on buying a safer car.

The main source of the crash data is owned and maintained by the Virginia Department of Motor Vehicle (DMV). DMV’s Traffic Records Electronic Data System (TREDS) is a state-of-the-art data system maintained by the DMV Highway Safety Office (HSO) that automates and centralizes all crash data in Virginia. Per data sharing use agreement with DMV, VDOT publishes the non-privileged crash data through Virginia Roads data portal. In providing this data, VDOT assumes no responsibility for the accuracy and completeness of the data. In the process of recording and compiling the data, some deletions and/or omissions of data may occur and VDOT is not responsible for any such occurrences. The most recent data contained in this dataset is preliminary and subject to change.

Please be advised that, under Title 23 United State Code – Section 407, this crash information cannot be used in discovery or as evidence in a Federal or State court proceeding or considered for other purposes in any action for damages against VDOT or the State of Virginia arising from any occurrence at the location identified.

All users shall comply with and be subject to all applicable laws and regulations, whether federal or state, in connection with any of the receipt and use of DMV data including, but not limited to, (1) the Federal Drivers Privacy Protection Act (18 U.S.C. § 2721 et seq.), (2) the Government Data Collection and Dissemination Practices Act (Va. Code § 2.2-3800 et seq.), (3) the Virginia Computer Crimes Act (Va. Code § 18.2-152.1 et seq.), (4) the provisions of Va. Code §§ 46.2-208 and 58.1-3, and (5) any successor rules, regulations, or guidelines adopted by DMV with regard to disclosure or dissemination of any information obtained from DMV records or files.

***The Los Angeles Police Department (LAPD) has transitioned traffic collision reporting to our new Records Management System (RMS) as part of our ongoing efforts to modernize data collection and comply with the FBI’s National Incident-Based Reporting System (NIBRS). This transition will improve the accuracy and detail of reported traffic-related incidents.

During this process, there will be a delay in the availability of new traffic collision datasets while they are being developed for the new system. In the meantime, users will continue to see only historical data from the retired system. We appreciate your patience as we complete this transition. ***

This dataset reflects traffic collision incidents in the City of Los Angeles dating back to 2010. This data is transcribed from original traffic reports that are typed on paper and therefore there may be some inaccuracies within the data. Some location fields with missing data are noted as (0°, 0°). Address fields are only provided to the nearest hundred block in order to maintain privacy. This data is as accurate as the data in the database. Please note questions or concerns in the comments.

Crashes on the roadway blocks network of Washington, DC maintained by the District Department of Transportation (DDOT). In addition to locations, a related table consisting of crash details is available for each crash. This table provides some anonymized information about each of the persons involved in the crash (linked by CRASHID). These crash data are derived from the Metropolitan Police Department's (MPD) crash data management system (COBALT) and represent DDOT's attempt to summarize some of the most requested elements of the crash data. Further, DDOT has attempted to enhance this summary by locating each crash location along the DDOT roadway block line, providing a number of location references for each crash. In the event that location data is missing or incomplete for a crash, it is unable to be published within this dataset. Location points with some basic summary statistics,The DC ward the crash occurredSummary totals for: injuries (minor, major, fatal) by type (pedestrian, bicycle, car), mode of travel involved (pedestrian, bicycle, car), impaired participants (pedestrian, bicyclist, car passengers)If speeding was involvedNearest intersecting street nameDistance from nearest intersectionCardinal direction from the intersectionRead more at https://ddotwiki.atlassian.net/wiki/spaces/GIS0225/pages/2053603429/Crash+Data. Questions on the contents of these layers should be emailed to Metropolitan Police Department or the DDOT Traffic Safety Division. Questions regarding the Open Data DC can be sent to @OpenDataDC

The Motor Vehicle Collisions person table contains details for people involved in the crash. Each row represents a person (driver, occupant, pedestrian, bicyclist,..) involved in a crash. The data in this table goes back to April 2016 when crash reporting switched to an electronic system. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. The police report (MV104-AN) is required to be filled out for collisions where someone is injured or killed, or where there is at least $1000 worth of damage (https://www.nhtsa.gov/sites/nhtsa.dot.gov/files/documents/ny_overlay_mv-104an_rev05_2004.pdf). It should be noted that the data is preliminary and subject to change when the MV-104AN forms are amended based on revised crash details. Due to success of the CompStat program, NYPD began to ask how to apply the CompStat principles to other problems. Other than homicides, the fatal incidents with which police have the most contact with the public are fatal traffic collisions. Therefore in April 1998, the Department implemented TrafficStat, which uses the CompStat model to work towards improving traffic safety. Police officers complete form MV-104AN for all vehicle collisions. The MV-104AN is a New York State form that has all of the details of a traffic collision. Before implementing Trafficstat, there was no uniform traffic safety data collection procedure for all of the NYPD precincts. Therefore, the Police Department implemented the Traffic Accident Management System (TAMS) in July 1999 in order to collect traffic data in a uniform method across the City. TAMS required the precincts manually enter a few selected MV-104AN fields to collect very basic intersection traffic crash statistics which included the number of accidents, injuries and fatalities. As the years progressed, there grew a need for additional traffic data so that more detailed analyses could be conducted. The Citywide traffic safety initiative, Vision Zero started in the year 2014. Vision Zero further emphasized the need for the collection of more traffic data in order to work towards the Vision Zero goal, which is to eliminate traffic fatalities. Therefore, the Department in March 2016 replaced the TAMS with the new Finest Online Records Management System (FORMS). FORMS enables the police officers to electronically, using a Department cellphone or computer, enter all of the MV-104AN data fields and stores all of the MV-104AN data fields in the Department’s crime data warehouse. Since all of the MV-104AN data fields are now stored for each traffic collision, detailed traffic safety analyses can be conducted as applicable.

This data has been consolidated from Victoria Police reports and Hospital injury information, then validated and enriched to provide a comprehensive and detailed view of road crashes and injuries across Victoria. The data provides users with information about Victorian fatal and injury road crash data based on time, location, conditions, crash type, road user type, and other relevant attributes. Data Currency This information will be updated on a monthly basis but with a 7 month lag in order to provide a comprehensive view of incidents during that time period. Data Structure The CSV data is split across multiple tables with attributes to facilitate joins between the information. This has been captured as part of the supporting documentation in the metadata. The tables and attributes include: - accident (basic accident details, time, severity, location) - person (person based details, age, gender etc) - vehicle (vehicle based data, vehicle type, make etc) - accident_event (sequence of events e.g. left road, rollover, caught fire) - road_surface_cond (whether road was wet, dry, icy etc) - atmospheric_cond (rain, winds etc) - sub_dca (detailed codes describing accident) - accident_node (master location table - NB subset of accident table) - Node Table with Lat/Long references There is also a lite Victoria Road Crash .csv dataset is a single flat file containing a subset of the attributes from the other CSV files. It provides a single set of attributes for each road crash that has occurred within Victoria. Supporting documentation in the metadata will provide further details of the attributes. This used to be a .GeoJSON file however due to feedback from a significant number of Open Data users, this was changed to a .csv file. Disclaimer No claim is made as to the accuracy or currency of the content on this site at any time, there will be instances where attributes relating to a crash are amended over time. This data is provided on the basis that users undertake responsibility for assessing the relevance and accuracy of its content. Data relating to fatal crashes that have occurred recently are provisional and are subject to change or removal. They will have a high level of incompleteness and details will be amended before they are finalised. The Victorian Government and Department of Transport and Planning accept no liability to any person or group for the data or advice (or the use of such data or advice) which is provided or incorporated into it by reference.

This dataset provides information on motor vehicle operators (drivers) involved in traffic collisions occurring on county and local roadways. The dataset reports details of all traffic collisions occurring on county and local roadways within Montgomery County, as collected via the Automated Crash Reporting System (ACRS) of the Maryland State Police, and reported by the Montgomery County Police, Gaithersburg Police, Rockville Police, or the Maryland-National Capital Park Police. This dataset shows each collision data recorded and the drivers involved. Please note that these collision reports are based on preliminary information supplied to the Police Department by the reporting parties. Therefore, the collision data available on this web page may reflect: -Information not yet verified by further investigation -Information that may include verified and unverified collision data -Preliminary collision classifications may be changed at a later date based upon further investigation -Information may include mechanical or human error This dataset can be joined with the other 2 Crash Reporting datasets (see URLs below) by the State Report Number. * Crash Reporting - Incidents Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Incidents-Data/bhju-22kf * Crash Reporting - Non-Motorists Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Non-Motorists-Data/n7fk-dce5 Update Frequency : Weekly

The State of Michigan’s criteria for a crash is a motor vehicle that was in transport and on the roadway, that resulted in death, injury, or property damage of $1,000 or more. Traffic crashes in this dataset are derived from SEMCOG’s Open Data Portal. Each row in the dataset represents a traffic crash that includes data about when and where the crash occurred, road conditions, number of individuals involved in the crash, and various factors that apply to the crash (Train, Bus, Deer, etc.). Also included is the number of injuries and fatalities that are associated with the crash.

This dataset contains all traffic crashes reported to CSPD . This dataset may be tied to the Tickets and Citations dataset by ticket number.

Crashes data includes crash event level details such as location - the Lat/Long of the nearest intersection, A and B street names, with distance and direction of the crash from nearest intersection, etc... It also includes crash level details like weather and roadway conditions, and time of day. Also included are the involved party (vehicle involved with), primary collision factor and severity of injury in terms of fatalities, and severe, moderate and minor injuries per crash.

The vehicles data includes the vehicle level details of the crash such as vehicle types, driver's (vehicle, party) age and sex, driver conditions and violations proceeding the crash, etc...

There is a one to many relationship that needs to be built that relates the crash to the vehicles involved. (i.e. there are an average of 2.07 vehicles/parties involved per crash)

Match the Crash name in vehicle data to the Name in the Crash data to relate the two sets of data.

Crash data shows information about each traffic crash on city streets within the City of Chicago limits and under the jurisdiction of Chicago Police Department (CPD). Data are shown as is from the electronic crash reporting system (E-Crash) at CPD, excluding any personally identifiable information. Records are added to the data portal when a crash report is finalized or when amendments are made to an existing report in E-Crash. Data from E-Crash are available for some police districts in 2015, but citywide data are not available until September 2017. About half of all crash reports, mostly minor crashes, are self-reported at the police district by the driver(s) involved and the other half are recorded at the scene by the police officer responding to the crash. Many of the crash parameters, including street condition data, weather condition, and posted speed limits, are recorded by the reporting officer based on best available information at the time, but many of these may disagree with posted information or other assessments on road conditions. If any new or updated information on a crash is received, the reporting officer may amend the crash report at a later time. A traffic crash within the city limits for which CPD is not the responding police agency, typically crashes on interstate highways, freeway ramps, and on local roads along the City boundary, are excluded from this dataset.

All crashes are recorded as per the format specified in the Traffic Crash Report, SR1050, of the Illinois Department of Transportation. The crash data published on the Chicago data portal mostly follows the data elements in SR1050 form. The current version of the SR1050 instructions manual with detailed information on each data elements is available here.

As per Illinois statute, only crashes with a property damage value of $1,500 or more or involving bodily injury to any person(s) and that happen on a public roadway and that involve at least one moving vehicle, except bike dooring, are considered reportable crashes. However, CPD records every reported traffic crash event, regardless of the statute of limitations, and hence any formal Chicago crash dataset released by Illinois Department of Transportation may not include all the crashes listed here.

Change 11/21/2023: We have removed the RD_NO (Chicago Police Department report number) for privacy reasons.

Attributes about each crash case which may consist of a single or multiple reports occurring during the year.

The Connecticut Crash Data Repository (CTCDR) is a web tool designed to provide access to select crash information collected by state and local police. This data repository enables users to query, analyze and print/export the data for research and informational purposes. The CTCDR is comprised of crash data from two separate sources; The Department of Public Safety (DPS) and The Connecticut Department of Transportation (CTDOT). The purpose of the CTCDR is to provide members of the traffic-safety community with timely, accurate, complete and uniform crash data. The CTCDR allows for complex queries of both datasets such as, by date, route, route class, collision type, injury severity, etc. For further analysis, this data can be summarized by user-defined categories to help identify trends or patterns in the crash data.

The Traffic Crashes feature layer models roadway traffic crashes within the Pikes Peak Area Council of Governments (PPACG) region, typically over a five-year period. This data is developed from crash data records compiled by CDOT from police accident reports filed with the state by each jurisdiction in the region. CDOT consolidates the police reports into a single database, removes personal identifying information, and then provides PPACG with an exported table of crash data records. The majority of the crash records (greater than 99.99%) are successfully linear referenced to routes or geocoded to address information acquired from CDOT, the El Paso-Teller County E911 Authority, and Park County. All crash records associated with roadways modeled in PPACG's Route Centerlines feature class are further refined by PPACG to align with coincident roadway network links and intersections.The 'Crash_ID' field stores the unique ID value for each feature in this data set, and is derived as a concatenation of the crash year and the 'CUID' CDOT crash database identifier field. The 'CUID' field is provided by CDOT in their crash data deliverable, and may not be unique. The 'RouteCL_ID' field, the ‘NetLink_ID' field, and the 'Intrsct_ID' fields record the foreign keys for any related features in PPACG's respective Route Centerlines, Roadway Network Links, and Roadway Network Intersections feature classes. The ‘Severity’ field categorizes each crash according to the severity of injuries or resultant fatalities, if any, as reported in the crash data. The 'Date_Time' field stores the concatenated crash date and crash time from each report into a single date field, while the 'Day' field records the day of the week of each crash. The 'DriveImp_1', 'DriveImp_2', and 'NM_Imp' fields identify if the drivers or non-motorist involved in each crash was suspected of drug or alcohol impairment according to the crash record, which may have included field sobriety testing. Those fields are not updated with the results of any further tests or other conclusive measures that may have been performed after the crash report was filed. All remaining fields are derived directly from CDOT crash data records, altered by PPACG to provide descriptive and consistent field names and aliases that still logically reference the original CDOT crash data schema, and primarily describe the location, roadway features, conditions, vehicle information, and driver actions documented with each crash record.