This data set contains crash data for many years from the Pennsylvania Department of Transportation (Penn DOT). This is a subset of the [annual Crash Data compiled](https://crashinfo.penndot.gov/PCIT/welcome.html) and released by Penn DOT for the entire state.

,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 Data,The 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 Locations,Crash 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.,

A. SUMMARY This table contains all parties involved in a traffic crash resulting in an injury in the City of San Francisco. Fatality year-to-date crash data is obtained from the Office of the Chief Medical Examiner (OME) death records, and only includes those cases that meet the San Francisco Vision Zero Fatality Protocol maintained by the San Francisco Department of Public Health (SFDPH), San Francisco Police Department (SFPD), and San Francisco Municipal Transportation Agency (SFMTA). Injury crash data is obtained from SFPD’s Interim Collision System for 2018 to YTD, Crossroads Software Traffic Collision Database (CR) for years 2013-2017 and the Statewide Integrated Transportation Record System (SWITRS) maintained by the California Highway Patrol for all years prior to 2013. Only crashes with valid geographic information are mapped. All geocodable crash data is represented on the simplified San Francisco street centerline model maintained by the Department of Public Works (SFDPW). Collision injury data is queried and aggregated on a quarterly basis. Crashes occurring at complex intersections with multiple roadways are mapped onto a single point and injury and fatality crashes occurring on highways are excluded. The crash, party, and victim tables have a relational structure. The traffic crashes table contains information on each crash, one record per crash. The party table contains information from all parties involved in the crashes, one record per party. Parties are individuals involved in a traffic crash including drivers, pedestrians, bicyclists, and parked vehicles. The victim table contains information about each party injured in the collision, including any passengers. Injury severity is included in the victim table. For example, a crash occurs (1 record in the crash table) that involves a driver party and a pedestrian party (2 records in the party table). Only the pedestrian is injured and thus is the only victim (1 record in the victim table). B. HOW THE DATASET IS CREATED Traffic crash injury data is collected from the California Highway Patrol 555 Crash Report as submitted by the police officer within 30 days after the crash occurred. All fields that match the SWITRS data schema are programmatically extracted, de-identified, geocoded, and loaded into TransBASE. See Section D below for details regarding TransBASE. C. UPDATE PROCESS After review by SFPD and SFDPH staff, the data is made publicly available approximately a month after the end of the previous quarter (May for Q1, August for Q2, November for Q3, and February for Q4). D. HOW TO USE THIS DATASET This data is being provided as public information as defined under San Francisco and California public records laws. SFDPH, SFMTA, and SFPD cannot limit or restrict the use of this data or its interpretation by other parties in any way. Where the data is communicated, distributed, reproduced, mapped, or used in any other way, the user should acknowledge TransBASE.sfgov.org as the source of the data, provide a reference to the original data source where also applicable, include the date the data was pulled, and note any caveats specified in the associated metadata documentation provided. However, users should not attribute their analysis or interpretation of this data to the City of San Francisco. While the data has been collected and/or produced for the use of the City of San Francisco, it cannot guarantee its accuracy or completeness. Accordingly, the City of San Francisco, including SFDPH, SFMTA, and SFPD make no representation as to the accuracy of the information or its suitability for any purpose and disclaim any liability for omissions or errors that may be contained therein. As all data is associated with methodological assumptions and limitations, the City recommends that users review methodological documentation associated with the data prior to its analysis, interpretation, or c

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

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.

The Fatality Analysis Reporting System (FARS) 2023 Initial Release - Fatal Motor Vehicle Accidents dataset was compiled from January 1, 2023 to December 31, 2023 by the National Highway Traffic Safety Administration (NHTSA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This geospatial dataset is the accident file from the initial release of FARS 2023 data. This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529018

The Fatality Analysis Reporting System (FARS) 2021 Final Release - Fatal Motor Vehicle Accidents dataset was compiled from January 1, 2021 to December 31, 2021 by the National Highway Traffic Safety Administration (NHTSA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This geospatial dataset is the accident file from the FARS 2021 Final Release Data. The Final Release Data is published 12-15 months, after the initial release of FARS, and could contain additional fatal accidents due to the delay in police reporting, toxicology reports, etc., along with changes to attribute information for previously reported fatal accidents. This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash.

The Fatality Analysis Reporting System (FARS) 2022 Initial Release - Fatal Motor Vehicle Accidents dataset was compiled from January 1, 2022 to December 31, 2022 by the National Highway Traffic Safety Administration (NHTSA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This geospatial dataset is the accident file from the initial release of FARS 2021 data. This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash.

The Fatality Analysis Reporting System (FARS) 2022 Final Release - Fatal Motor Vehicle Accidents dataset was compiled from January 1, 2022 to December 31, 2022 by the National Highway Traffic Safety Administration (NHTSA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This geospatial dataset is the accident file from the FARS 2022 Final Release Data. The Final Release Data is published 12-15 months, after the initial release of FARS, and could contain additional fatal accidents due to the delay in police reporting, toxicology reports, etc., along with changes to attribute information for previously reported fatal accidents. This data file contains information about crash characteristics and environmental conditions at the time of the crash. There is one record per crash. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529018