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 State Traffic Safety Information (STSI) portal is part of the larger Fatality Analysis Reporting System (FARS) Encyclopedia. STSI provides state-by-state traffic safety profiles, including: crash data, lives saved/savable, legislation, economic costs, grant funding, alcohol related crash data, performance measures, and geographic maps of crash data.

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 is updated daily.

Please note that 2024 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2023.Fatal and serious injury crashes are not “accidents” and are preventable. The City of Tempe is committed to reducing the number of fatal and serious injury crashes to zero. This data page provides details about the performance measure related to High Severity Traffic Crashes as well as access to the data sets and any supplemental data. The Engineering and Transportation Department uses this data to improve safety in Tempe.This data includes vehicle/vehicle, vehicle/bicycle and vehicle/pedestrian crashes in Tempe. The data also includes the type of crash and location. This layer is used in the related Vision Zero story map, web maps and operations dashboard. Time ZonesPlease note that data is stored in Arizona time which is UTC-07:00 (7 hours behind UTC) and does not adjust for daylight savings (as Arizona does not partake in daylight savings). The data is intended to be viewed in Arizona time. Data downloaded as a CSV may appear in UTC time and in some rare circumstances and locations, may display online in UTC or local time zones. As a reference to check data, the record with incident number 2579417 should appear as Jan. 10, 2012 9:04 AM.Please note that 2024 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2023.This page provides data for the High Severity Traffic Crashes performance measure. The performance measure page is available at 1.08 High Severity Traffic CrashesAdditional InformationSource: Arizona Department of Transportation (ADOT)Contact (author): Shelly SeylerContact (author) E-Mail: Shelly_Seyler@tempe.govContact (maintainer): Julian DresangContact (maintainer) E-Mail: Julian_Dresang@tempe.govData Source Type: CSV files and Excel spreadsheets can be downloaded from ADOT websitePreparation Method: Data is sorted to remove license plate numbers and other sensitive informationPublish Frequency: semi-annuallyPublish Method: ManualData Dictionary

The provided crash data comes directly from the standard DMV-349 Crash Form completed by the initial officer at the scene of a crash. Only completed crash reports will be mapped in this data. The coordinates for the crash reports are entered manually by the officer and may be subject to error. Therefore, only crashes with coordinates in Raleigh will be shown on the map. Instructions for filtering data are available on the Open Data blog. Follow this link to access the NC DOT DMV-349 Instruction Manual for code descriptions and definitions.https://connect.ncdot.gov/business/DMV/DMV%20Documents/DMV-349%20Instructional%20Manual.pdfTerms of UseThe Raleigh Police Department does not guarantee the accuracy of the information contained herein. While all attempts are made to ensure the correctness and suitability of information under our control and to correct any errors brought to our attention, no representation or guarantee can be made as to the correctness or suitability of the information that is presented, referenced, or implied. Data is provided by initial reports received and processed by the Raleigh Police Department. Data may be amended or corrected by the Raleigh Police Department at any time to reflect changes in the investigation, nature, or accuracy of the initial report and the Raleigh Police Department is not responsible for any error or omission, or for the use of or the results obtained from the use of this information. Misuse of the data may subject a party to criminal prosecution for false advertising under NC GS § 14-117. The Raleigh Police Department may, at its discretion, discontinue or modify this service at any time without notice.

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.

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.

Crash Map is an interactive mapping tool developed by Metro to help people access and explore historic motor-vehicle related crash data in Clackamas, Multnomah and Washington Counties. The most recent five-years of crash data available is included in the tool.Crash information is collected statewide by the Oregon Department of Motor Vehicles. It is then aggregated and geocoded (mapped) by the Oregon Department of Transportation’s Crash Analysis and Reporting Unit. The 2018 Motor Vehicle Traffic Analysis and Code Manual provides information on how crash information is coded, including unlocatable crashes. Aggregated, geo-coded crash data is typically available to Metro and other agencies two years after the crash occurred. Metro processes the crash data for the greater Portland area and supports this map for public access.

The map shows the volume of daily traffic over each road segment in Utah, and a measure of safety for those road segments. The map demonstrates the use of smart mapping on two key attributes in a traffic safety database: daily traffic volume, and Safety Index. "The Safety Index offers a statewide comparison of UDOT roadways, taking into account the different traffic patterns and volumes experienced in urban and rural areas. The Safety Index is a combination of four, equally weighted safety analysis sub-scores: Crash Rate Score, Severe Crash Rate Score, Crashes per Mile Score, Severe Crashes per Mile Score. The Safety Index is reported on a 0 to 10 scale, with 10 representing the worst conditions. The data reflect crashes from 2011 through 2013. For more information please see the Data Assessment Form. To download this data please visit UDOT's Open Data Site." -- Utah Department of TransportationThe Safety Index represents factors that transportation experts consider when prioritizing changes to the roads.The original map was the inspiration for this map. See its full explanation here.

Overview:

Information on location and characteristics of crashes in Queensland for all reported Road Traffic Crashes occurred from 1 January 2001 to 30 November 2023. Fatal crashes to 30 November 2023. Non-fatal, hospitalisation, medical treatment and minor injury crashes to 30 June 2023 and property damage only crashes to 31 December 2010.

_Fatal, Hospitalisation, Medical treatment and Minor injury: _

This dataset contains information on crashes reported to the police which resulted from the movement of at least 1 road vehicle on a road or road related area. Crashes listed in this resource have occurred on a public road and meet one of the following criteria:

• a person is killed or injured, or
• at least 1 vehicle was towed away, or
• the value of the property damage meets the appropriate criteria listed below.

_Property damage: _

1. $2500 or more damage to property other than vehicles (after 1 December 1999)
2. $2500 or more damage to vehicle and/or other property (after 1 December 1991 and before 1 December 1999)
3. value of property damage is greater than $1000 (before December 1991).

_Please note: _

• This data has been extracted from the Queensland Road Crash Database.
• Information held in the Road Crash Database on events occurring within the last 12 months is considered preliminary as investigations into crashes can take up to 1 year to finalise.
• Property damage only crashes ceased to be reported/recorded by Queensland Police Service after 31 December 2010.
• These crash location coordinates reference the current Australian geodetic datum is GDA2020 (previously it was GDA94).

This dataset contains all reportable traffic crashes contained within the physical jurisdiction of the City of Norfolk. The data is owned by the Virginia Department of Motor Vehicles (DMV) and provided through a public portal by the Virginia Department of Transportation (VDOT): https://www.virginiaroads.org/maps/1a96a2f31b4f4d77991471b6cabb38ba/about. The dataset includes information about the severity of the crash, injuries and fatalities, if alcohol or drugs were involved, driver actions, if pedestrians or bikes were involved, if the driver was speeding, and other important information. This dataset will be updated quarterly.

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.

The High Crash Network includes Portland’s most dangerous streets and intersections for people driving, walking, and bicycling. This dataset delineates the streets which are among the top 20 crash streets for motor vehicles, for pedestrians and for bicyclists. Many streets are high crash streets for multiple transportation modes. Together, they form a network of 30 high crash streets.-- Additional Information: Category: Transportation - Streets Purpose: To delineate streets with a high occurrence of traffic crashes. Update frequency: As needed-- Metadata Link: https://www.portlandmaps.com/metadata/index.cfm?&action=DisplayLayer&LayerID=54465

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.

This dataset shows the position of vehicular crash incidents in Queensland. This includes fatalities, injuries and vehicular damage. The point of truth for this dataset is the Queensland government open data website at, https://data.qld.gov.au/dataset/crash-data-from-queensland-roads

A companion table for the Crashes in DC layer. This is a related table linked by field attribution, 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.Crash details related table,Type of participant (driver, occupant, bicyclist, pedestrian)Age of participantsIf injured, severity (minor, major, fatal)Type of vehicle (passenger car, large truck, taxi, government, bicycle, pedestrian, etc)If persons issued a ticketIf a vehicle, the state (jurisdiction) license plate was issued (not license plate number)Are any persons deemed ‘impaired’Was person in vehicle where speeding was indicatedRead 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.

On Road Cyclist Crashes, since 2012, which have been reported by the Police or the Public through the AFP Crash Report Form. Please note; Although crash data is updated on regular bases it will always have a backlog of entries hence it is not a true reflection of the up to date crash locations. Crash locations are only indicative and may not reflect an accurate position of persons involved in an incident. Casualty crashes are occasionally omitted from some maps or crash reports if they are still under investigation.

The provided crash data comes directly from the standard DMV-349 Crash Form completed by the initial officer at the scene of a crash. Only completed crash reports will be mapped in this data. The coordinates for the crash reports are entered manually by the officer and may be subject to error. Therefore, only crashes with coordinates in Raleigh will be shown on the map.

Instructions for filtering data are available on the Open Data blog.

Follow this link to access the NC DOT DMV-349 Instruction Manual for code descriptions and definitions.https://connect.ncdot.gov/business/DMV/DMV%20Documents/DMV-349%20Instructional%20Manual.pdfUpdate Frequency: DailyTime Period: 2015-PresentTerms of UseThe Raleigh Police Department does not guarantee the accuracy of the information contained herein. While all attempts are made to ensure the correctness and suitability of information under our control and to correct any errors brought to our attention, no representation or guarantee can be made as to the correctness or suitability of the information that is presented, referenced, or implied. Data is provided by initial reports received and processed by the Raleigh Police Department. Data may be amended or corrected by the Raleigh Police Department at any time to reflect changes in the investigation, nature, or accuracy of the initial report and the Raleigh Police Department is not responsible for any error or omission, or for the use of or the results obtained from the use of this information. Misuse of the data may subject a party to criminal prosecution for false advertising under NC GS § 14-117. The Raleigh Police Department may, at its discretion, discontinue or modify this service at any time without notice.

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