Please note that 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024. 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 saving (as Arizona does not partake in daylight saving). 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 2025 data are incomplete and will be updated as additional records become available. Data are complete through 12/31/2024.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 the ADOT websitePreparation Method: Data is sorted to remove license plate numbers and other sensitive informationPublish Frequency: semi-annuallyPublish Method: ManualData Dictionary

the Ministry of Road Transport and Highways of the Government of India releases annual reports on road accidents and casualties in the country. Additionally, many state governments also release data on road accidents within their jurisdiction. There are many potential causes of road accidents, including: Distracted driving (e.g. using a cell phone, eating, or applying makeup while driving) Impaired driving (e.g. driving under the influence of alcohol or drugs) Reckless or aggressive driving (e.g. speeding, tailgating, or running red lights) Fatigue or drowsy driving Poor road conditions (e.g. potholes, debris, or lack of proper signage) Vehicle defects or malfunctions Poor weather conditions (e.g. rain, snow, or fog) Inadequate infrastructure (e.g. lack of proper lighting, median barriers, or guardrails) Pedestrian or bicycle errors Wildlife crossing the road. There are several datasets available on road accidents, depending on the country and region. Here are a few examples:

In the United States, the National Highway Traffic Safety Administration (NHTSA) provides data on vehicle crashes, including details such as the location, cause, and number of injuries and fatalities. The United Kingdom's Department for Transport provides data on reported road accidents, including information on the type of vehicle, number of casualties, and severity of injuries. The World Health Organization (WHO) also has a Global Status Report on Road Safety, which provides data on road accidents and fatalities for countries around the world. In India, the Ministry of Road Transport and Highways (MoRTH) provides annual data on road accidents and fatalities. The Global Road Safety Partnership (GRSP) also has a wealth of data on road accidents and fatalities, particularly in low- and middle-income countries. It is important to note that these datasets may have different data collection methodologies, and may not include all road accidents that have occurred.

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.

A vector street layer. The file has been dissolved on the fields: Full Street Name, Shield, HWY_NUM, FCC, ACC, Jurisdiction. All generic street names (i.e. Driveway, Ramp, etc..) have been changed to null. This file has been intersected with CensusMCD_2000 to allow for the inclusion of the Country_Name and MCD_Name fields.

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.

Context The UK government amassed traffic data from 2000 and 2018, recording over 1.8 million accidents in the process and making this one of the most comprehensive traffic data sets out there. It's a huge picture of a country undergoing change.

Content There is 1 CSV File in this set. Accidents are the primary ones and have references by Accident_Index to the casualties and vehicles tables. This might be better done as a database.

Description This Dataset contains 33 Features covering over a 1.8million records. this dataset consists of various features like, Accidental / Longitude: Location of Accident

Inspiration Questions to ask about this data are, - What is the number of casualties on each day of the week? - On each day of the week, what is the maximum and minimum speed limit on the roads the accidents happened? - What is the importance of Light and Weather conditions in predicting accident severity? - What does your intuition say and what does the data portray? - To predict the severity of the accidents.

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.

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.

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

For each personal injury accident (i.e. an accident on a road open to public traffic, involving at least one vehicle and involving at least one victim requiring treatment), information describing the accident is seized by the police unit (police, gendarmerie, etc.) which intervened at the scene of the accident. These seizures are collected in a sheet entitled ‘Injury Analysis Bulletin’. All these forms constitute the national register of road traffic injuries, known as the ‘BAAC file’, administered by the National Interministerial Observatory for Road Safety (ONISR).

The databases, extracted from the BAAC file, list all road traffic injuries occurring during a specific year in mainland France, in the overseas departments (Guadeloupe, French Guiana, Martinique, Réunion and Mayotte since 2012) and in the other overseas territories (Saint-Pierre-et-Miquelon, Saint-Barthélemy, Saint-Martin, Wallis and Futuna, French Polynesia and New Caledonia; available only from 2019 in open data) with a simplified description. This includes information on the location of the accident, as provided, as well as information on the characteristics of the accident and its location, the vehicles involved and their victims.

Compared to the aggregated databases 2005-2010 and 2006-2011 currently available on the website www.data.gouv.fr, the databases from 2005 to 2023 are now annual and composed of 4 files (Characteristics – Locations – Vehicles – Users) in csv format.

However, those databases conceal certain specific data relating to users and vehicles and their conduct in so far as disclosure of that data would undermine the protection of the privacy of easily identifiable natural persons or reveal the conduct of such persons, whereas disclosure of that conduct could be detrimental to them (CADA opinion – 2 January 2012).

Warning: Data on the classification of injured persons hospitalised since 2018 cannot be compared to previous years following changes in the seizure process of the police. The indicator ‘injured hospitalised’ has no longer been labelled by the public statistics authority since 2019.

The validity of the statistical operations that can be made from this database depends on the verification methods specific to the field of application of road safety and in particular on a precise knowledge of the definitions relating to each variable used. For any operation, it is important to take note in particular of the structure of the attached BAAC sheet and the guide to using the codification of the road traffic accident analysis bulletin.

It should be noted that a number of indicators from this database are labelled by the public statistics authority (Order of 27 November 2019). The list is available at: https://www.onisr.securite-routiere.gouv.fr/statistical tools/labelled indicators

Provide the number of fatalities of 3 or more within 5 years, the number of fatalities and injuries of 10 or more, or the number of injuries of 15 or more, as well as information on the location of major traffic accidents involving the transportation of hazardous materials, explosions, fires, or leaks of toxic liquids (gases), and radioactive substances.

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.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.

Traffic accidents in the City and County of Denver. The data is based on the National Incident Based Reporting System (NIBRS). The data is dynamic, which allows for additions, deletions and/or modifications at any time, resulting in more accurate information in the database. Due to continuous data entry, the number of records in subsequent extractions are subject to change. Accident data is updated Monday through Friday.

Road accidents are accidents in which persons have been killed or injured as a result of driving on public roads and places or where property damage has occurred. The map shows only accidents involving personal injury. Accidents in which only material damage occurred are not shown. The accident atlas contains information from road accident statistics based on reports from police departments.Accidents to which the police have not been called are not included in the statistics. Before the accident coordinates recorded by the police are summarised on the basis of road sections and presented as points in the accident atlas, they must undergo a multi-stage plausibility process.During this process, individual accidents that do not meet plausibility requirements can be sorted out. These accidents are not depicted in the accident atlas. Killed:People who died of the accident within 30 days Severely injured: Persons admitted directly to a hospital for inpatient treatment (at least 24 hours) Lightly injured: all other injured Accident by car: Accident involving at least one car Further information: https://unfallatlas.statistikportal.de/_opendata2021.html Link to the interactive application: https://unfallatlas.statistikportal.de

Dataset Description: This dataset is an amended version of the UC Berkeley Transportation Injury Mapping System (TIMS) collision records from the six SCAG Counties (Imperial, Los Angeles, Orange, Riverside, San Bernardino, and Ventura) of all collisions between January 1, 2015 and December 31, 2019, downloaded from the TIMS webpage on March 23, 2022. SCAG developed this collection of collisions to determine the Regional High-Injury network. This dataset represents collisions between 2015 and 2019 located in the SCAG region that resulted in serious injury or fatality and have a clear mode type (Auto-Auto, Auto-Pedestrian, or Auto-Bicycle). Some collisions from the original dataset needed to be manually verified for location. Data development/processing methodology:SCAG prepared the collision data by filtering out collisions from the data downloaded from TIMS that did not fall into the scope of this analysis per the location, collision severity, and mode parameters. For more details on the methodology, please contact the point of contact.

Overview:

Information on location and characteristics of crashes in Queensland for all reported Road Traffic Crashes occurred from 1 January 2001 to 30 June 2024.

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).

Abstract copyright UK Data Service and data collection copyright owner.Road accident statistics are collected from information about personal injury road accidents and their consequent casualties, to a common national standard. The aim of collecting and publishing national road accident statistics is to inform public debate and to provide the basis for determining and monitoring effective road safety policies to reduce the road accident casualty toll. They are an essential requirement for monitoring targeted reductions in road accident casualties. The credible monitoring of targeted reductions requires that data are reported consistently and accurately, and both national and local government, and local reporting police forces, work closely to achieve a common reporting standard. Users should note that for 1985-1991, and from 2002 onwards, the Vehicle Record file does not contain breath test data. This change has been made in order to protect confidentiality. Data for 1985-1990 were deposited at the Archive at the beginning of 2006. Prior to this, the Archive only held the Road Accident Data series from 1991 onwards. No extra documentation was available for the 1985-1990 data, so users are advised to consult the documentation for the 1991 survey. Further information about the Road Accident Data series and research based on it may be found on the government road accidents and safety statistics webpages. These studies comprise information gathered using STATS19 and STATS20 forms. Main Topics:The collection process for these data includes the recording of details about the accident, together with the vehicles and casualties involved, which in principle can be easily discerned by the police either at the scene of the accident, or when they are reported to the police at a later date after the accident. The details recorded include accident time, date and location; vehicle type, location and manoeuvre; driver details; casualty details and severity.

CrashStats data is provided to users by VicRoads for the purpose of supplying information about road crashes in Victoria for educational purposes. The data provided allows users to analyse Victorian fatal and injury crash data based on time, location, conditions, crash type, road user type, object hit etc. File ACCIDENT.zip contains the following files extracted from the VicRoads CrashStats database. See Additional Information for the period of data extract. The files are as follows: Tables - …Show full descriptionCrashStats data is provided to users by VicRoads for the purpose of supplying information about road crashes in Victoria for educational purposes. The data provided allows users to analyse Victorian fatal and injury crash data based on time, location, conditions, crash type, road user type, object hit etc. File ACCIDENT.zip contains the following files extracted from the VicRoads CrashStats database. See Additional Information for the period of data extract. The files are as follows: Tables - accident (basic accident details, time, severity, location) - person (person based details, age, sex 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 The files contained are documented in the CrashStats User Guide and Appendix, accessible at: http://data.vicroads.vic.gov.au/metadata/crashstats_user_guide_and_appendices.pdf

Information on accidents across Leeds. Data includes location, number of people and vehicles involved, road surface, weather conditions and severity of any casualties.

Please note

• The Eastings and Northings are generated at the roadside where the accident occurred. Sometimes due to poor internet connectivity this data is may not be as accurate as it could be. If you notice any errors please contact accident.studies@leeds.gov.uk.

Due to the format of the report a number of figures in the columns are repeated, these are:

• Reference Number
• Easting
• Northing
• Number of Vehicles
• Accident Date
• Time (24hr)
• 1st Road Class
• Road Surface
• Lighting Conditions
• Weather Conditions

Reference Number

Grid Ref: Easting

Grid Ref: Northing

Number of vehicles

Accident Date

Time (24hr)

21G0539

427798

426248

5

16/01/2015

1205

21G0539

427798

426248

5

16/01/2015

1205

21G1108

431142

430087

1

16/01/2015

1732

21H0565

434602

436699>

1

17/01/2015

930

21H0638

434254

434318

2

17/01/2015

1315

21H0638

434254

434318

2

17/01/2015

1315

Therefore the number of vehicles involved in accident 21G0539 were 5, and in accident 21H0638 were 2. Overall in the example above a total of 9 vehicles were involved in accidents

A useful tool to analyse the data is Excel pivot tables, these help summarise large amounts of data in a easy to view table, for further information on pivot table visit here.

Further Information

• Please see the guidance document for further information on categories.

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 saving (as Arizona does not partake in daylight saving). 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 the ADOT websitePreparation Method: Data is sorted to remove license plate numbers and other sensitive informationPublish Frequency: semi-annuallyPublish Method: ManualData Dictionary