,

The Fatal and Injury Crashes Dashboard can be used by the public to locate crashes that result in an injury or fatality. Adjust the Mode, Severity and Date filters to refine the results in the map. All charts will update to reflect the collisions in current map extent. Data are available from 2017-present. Data are updated every Friday.

NOTE: Post-2018 crash data is available here: https://data.somervillema.gov/Public-Safety/Police-Data-Crashes/mtik-28va/about_data,This data set tracks motor vehicle crashes within the City of Somerville from 1/1/2010 through 4/30/2018. This data was created by OSPCD in collaboration with the Somerville Police Department.

,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 Zones Please 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 Crashes Additional Information,Source: Arizona Department of Transportation (ADOT) Contact (author): Shelly Seyler Contact (author) E-Mail: Shelly_Seyler@tempe.gov Contact (maintainer): Julian Dresang Contact (maintainer) E-Mail: Julian_Dresang@tempe.gov Data Source Type: CSV files and Excel spreadsheets can be downloaded from ADOT website Preparation Method: Data is sorted to remove license plate numbers and other sensitive information Publish Frequency: semi-annually Publish Method: Manual Data Dictionary,

,

This data contains information about people involved in a crash and if any injuries were sustained. This dataset should be used in combination with the traffic Crash and Vehicle dataset. Each record corresponds to an occupant in a vehicle listed in the Crash dataset. Some people involved in a crash may not have been an occupant in a motor vehicle, but may have been a pedestrian, bicyclist, or using another non-motor vehicle mode of transportation. Injuries reported are reported by the responding police officer. Fatalities that occur after the initial reports are typically updated in these records up to 30 days after the date of the crash. Person data can be linked with the Crash and Vehicle dataset using the “CRASH_RECORD_ID” field. A vehicle can have multiple occupants and hence have a one to many relationship between Vehicle and Person dataset. However, a pedestrian is a “unit” by itself and have a one to one relationship between the Vehicle and Person table. 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.

This dataset provides information on non-motorists (pedestrians and cyclists) involved in traffic collisions occurring on county and local roadways.The 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 non-motorists 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 - Drivers Data at https://data.montgomerycountymd.gov/Public-Safety/Crash-Reporting-Drivers-Data/mmzv-x632 Update Frequency : Weekly

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