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
Open Government Licence - Canada 2.0https://open.canada.ca/en/open-government-licence-canada
License information was derived automatically
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.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
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.
This dataset contains crash information from the last five years to the current date. The data is based on the National Incident Based Reporting System (NIBRS). The data is dynamic, allowing for additions, deletions and modifications at any time, resulting in more accurate information in the database. Due to ongoing and continuous data entry, the numbers of records in subsequent extractions are subject to change.About Crash DataThe Cary Police Department strives to make crash data as accurate as possible, but there is no avoiding the introduction of errors into this process, which relies on data furnished by many people and that cannot always be verified. As the data is updated on this site there will be instances of adding new incidents and updating existing data with information gathered through the investigative process.Not surprisingly, crash data becomes more accurate over time, as new crashes are reported and more information comes to light during investigations.This dynamic nature of crash data means that content provided here today will probably differ from content provided a week from now. Likewise, content provided on this site will probably differ somewhat from crime statistics published elsewhere by the Town of Cary, even though they draw from the same database.About Crash LocationsCrash locations reflect the approximate locations of the crash. Certain crashes may not appear on maps if there is insufficient detail to establish a specific, mappable location.
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.
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 traffic crash records for crashes which have occurred within current City of Austin Full Purpose boundaries, inclusive of all public safety jurisdictions, in the last ten years. It is one of two datasets which power our Vision Zero Viewer dashboard, available here: https://visionzero.austin.gov/viewer.
Crash data may take several weeks to be submitted, reviewed, and finalized for inclusion in this dataset. To provide the most accurate information as possible, we only provide crash data as recent as two weeks old. Please also note that some crash records may take even longer to appear in this dataset, depending on the circumstances of the crash and the ensuing law enforcement investigation.
Crash data is obtained from the Texas Department of Transportation (TxDOT) Crash Record Information System (CRIS) database, which is populated by reports submitted by Texas Peace Officers throughout the state, including Austin Police Department (APD).
The data and information on this website is for informational purposes only. While we seek to provide accurate information, please note that errors may be present and information presented may not be complete.
CC0 1.0 Universal Public Domain Dedicationhttps://creativecommons.org/publicdomain/zero/1.0/
License information was derived automatically
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.
This dataset contains all traffic crashes reported to CSPD . This dataset may be tied to the Tickets and Citations dataset by ticket number.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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.
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.
These tables present high-level breakdowns and time series. A list of all tables, including those discontinued, is available in the table index. More detailed data is available in our data tools, or by downloading the open dataset.
We are proposing to make some changes to these tables in future, further details and a link to a feedback form can be found alongside the 2024 annual report.
The tables below are the latest final annual statistics for 2024, which are currently the latest available data. Provisional statistics for the first half of 2025 will be published in November 2025.
A list of all reported road collisions and casualties data tables and variables in our data download tool is available in the https://assets.publishing.service.gov.uk/media/68d3edb0ca266424b221b287/reported-road-casualties-gb-index-of-tables.ods">Tables index (ODS, 28.9 KB).
https://assets.publishing.service.gov.uk/media/68d42292b6c608ff9421b2d2/ras-all-tables-excel.zip">Reported road collisions and casualties data tables (zip file) (ZIP, 11.2 MB)
RAS0101: https://assets.publishing.service.gov.uk/media/68d3cdeeca266424b221b253/ras0101.ods">Collisions, casualties and vehicles involved by road user type since 1926 (ODS, 34.7 KB)
RAS0102: https://assets.publishing.service.gov.uk/media/68d3cdfee65dc716bfb1dcf3/ras0102.ods">Casualties and casualty rates, by road user type and age group, since 1979 (ODS, 129 KB)
RAS0201: https://assets.publishing.service.gov.uk/media/68d3ce0bc908572e81248c1f/ras0201.ods">Numbers and rates (ODS, 37.5 KB)
RAS0202: https://assets.publishing.service.gov.uk/media/68d3ce17b6c608ff9421b25e/ras0202.ods">Sex and age group (ODS, 178 KB)
RAS0203: https://assets.publishing.service.gov.uk/media/67600227b745d5f7a053ef74/ras0203.ods">Rates by mode, including air, water and rail modes (ODS, 24.2 KB) - this table will be updated for 2024 once data is available for other modes.
RAS0301: https://assets.publishing.service.gov.uk/media/68d3ce2b8c739d679fb1dcf6/ras0301.ods">Speed limit, built-up and non-built-up roads (ODS, 20.8 KB)
RAS0302: <span class="gem-c-attachmen
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
Vision Zero Boston is our commitment to focus the city’s resources on proven strategies to eliminate fatal and serious traffic crashes in the city by 2030. We are inspired by the belief that even one fatality is too many. Learn more about about the Vision Zero Boston program at https://www.boston.gov/departments/transportation/vision-zero.
This dataset, provided as part of the Vision Zero Boston program, contains records of the date, time, location, and type of crash for incidents requiring public safety response which may involve injuries or fatalities. All records are compiled by the Department of Innovation and Technology from the City's Computer-Aided Dispatch (911) system and verified as having required a response from a public safety agency. To protect the privacy of individuals involved in these incidents, we do not indicate the severity of specific crashes or whether medical care was provided in any specific case.
Additional notes:
ODC Public Domain Dedication and Licence (PDDL) v1.0http://www.opendatacommons.org/licenses/pddl/1.0/
License information was derived automatically
List of crashes involving motor vehicles, bicycles and/or pedestrians reported in the City of Cambridge since 2015.
Any data or text that may identify specific persons or companies has been omitted. Please see attached MassTRAC documentation for additional explanation about crash reporting data elements.
Note: crashes involving pedestrians are indicated in the “P1 Non Motorist Desc” and “P2 Mon Motorist Desc” columns. When using Socrata's built in visualization tools to map crashes, please use the geocoded "Location" column. The column "May involve cyclist" specifies whether a given incident may involve a bicycle operator.
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 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.
Attributes about each crash case which may consist of a single or multiple reports occurring during the year.
Crash data are provided by the Washington State Patrol, Washington State Department of Transportation, and the Washington Traffic Safety Commission. These data tools represent the best available information and are updated regularly.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Update Frequency: Daily
This data-set includes traffic crash information including case number, accident date and the location.
Reportable crash reports can take up to 10 business days to appear after the date of the crash if there are no issues with the report.
If you cannot find your crash report after 10 business days, please call the Milwaukee Police Department Open Records Section at (414) 935-7435 for further assistance.
Non-reportable crash reports can only be obtained by contacting the Open Records Section and will not show up in a search on this site. A non-reportable crash is any accident that does not:
1) result in injury or death to any person
2) damage government-owned non-vehicle property to an apparent extent of $200 or more
3) result in total damage to property owned by any one person to an apparent extent of $1000 or more.
Online Request: Request your Crash Report online at WisDOT-DMV website, https://app.wi.gov/crashreports.
Mail: Wisconsin Department of Transportation Crash Records Unit P.O. Box 7919 Madison, WI 53707-7919
Phone: (608) 266-8753
To download XML and JSON files, click the CSV option below and click the down arrow next to the Download button in the upper right on its page.
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.
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