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.

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.

Community Maps provides Wisconsin's law enforcement agencies and county Traffic Safety Commissions with a statewide map of all police reported motor vehicle crashes from 2010 to the current year. Fatal crashes are included from 2001. Crashes are updated on a nightly basis using geo-coded locations from the Wisconsin Department of Transportation DT4000 police crash report. The Community Maps system was designed to support and enhance traffic safety planning, resource allocation, and decision support at the local level, in particular through the regular review of crashes at each of the county quarterly TSC meetings.

Community Maps is hosted at the University of Wisconsin-Madison by the Wisconsin Traffic Operations and Safety (TOPS) Laboratory in collaboration with the Wisconsin Department of Transportation (WisDOT) Bureau of Transportation Safety (BOTS).

New: For crash data analysis requests, please email the BOTS Program and Policy Unit at CrashDataAnalysis@dot.wi.gov.

For Community Maps technical support, please email community-maps@topslab.wisc.edu.

To request access to Community Maps Advanced features, please use the WisTransPortal online User Account Request Form.

Additional contact information:

Randy Wiessinger Statewide Law Enforcement Liaison Bureau of Transportation Safety (BOTS) Division of State Patrol, WisDOT Email: rpw@wiessinger.com

Steven T. Parker, Ph.D. Traffic Operations and Safety (TOPS) Laboratory UW-Madison Department of Civil and Environmental Engineering E-mail: sparker@engr.wisc.edu

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.

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

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.

The Delaware Department of Safety and Homeland Security (DSHS) is the official custodian of Delaware crash reports and is responsible for statewide crash data collection and dissemination. A crash report is a summary of information collected about a collision and is filled out by a Delaware law enforcement officer who is investigating the crash. The data contained on FirstMap and the Open Data Portal represents the best available information at DSHS and is not an official record of what transpired in a particular crash or for a particular crash type and does not contain personal information. This data is generated from crash reports and allows any member of the public to engage in interactive analysis and data exploration for the purpose of identifying, evaluating or planning the safety enhancement of potential crash sites, hazardous roadway conditions, or railway-highway crossings. This data is updated monthly and contains crashes that occurred since 2009 through six months ago. Official crash reports are confidential and are not a public record under the Delaware Freedom of Information Act. Authorized parties may contact the reporting police agency directly for official copies of crash reports (21 Del. C. §313). DSHS is committed to bringing public awareness to crash information. The Office of Highway Safety’s annual reports (https://ohs.delaware.gov/reports.shtml), the Office of Highway Safety’s annual safety plan (https://ohs.delaware.gov/reports.shtml), and the Delaware State Police Traffic Statistical Reports (https://dsp.delaware.gov/reports/) also contain a variety of information and data. In addition, the State of Delaware’s Strategic Highway Safety Plan is available at https://deldot.gov/Programs/DSHSP/index.shtml and is updated every five years.

description:

View crash information from the last five years to current date.

This dataset includes crashes in the Town of Cary for the previous four calendar years plus the current year to 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 become 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 data is updated daily.

View crash information from the last five years to current date.

This dataset includes crashes in the Town of Cary for the previous four calendar years plus the current year to 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 become 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 data is updated daily.

The Traffic_Crashes feature class 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.

NOTE: This map utilizes crash data from the Washington Department of Transportation (WSDOT); data is updated weekly, however, due to processing time required, final reporting statistics are generally provided 4-5 months after incident occurrence (i.e. final crash reporting for February will be reflected in June, etc.).

Contains locations and information about every crash incident reported to the police in Westmoreland County from 2011 to 2015. 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 data is historical only, but new data can be found on PennDOT's Crash Download Map tool linked in the Resources section.

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.

Person specific data from the prior 10 years. Data compiled in this format for the Traffic Safety Data and Analysis website (www.iowadot.gov/tsda). These point features depict the last 10 years of crash data and data that is related to injured person information. Data is updated monthly. Metadata available here.

This file contains reported cases of impacts between on-track equipment and any user of a public or private highway-rail intersection. National files from 1975 through the current year are available for download. In addition, individual files by State are available for the years 1991 through the current year.

Contains locations and information about every crash incident reported to the police in Butler County from 2011 to 2015. 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 data is historical only, but new data can be found on PennDOT's Crash Download Map tool linked in the Resources section.

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

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.

HEPGIS is a web-based interactive geographic map server that allows users to navigate and view geo-spatial data, print maps, and obtain data on specific features using only a web browser. It includes geo-spatial data used for transportation planning. HEPGIS previously received ARRA funding for development of Economically distressed Area maps. It is also being used to demonstrate emerging trends to address MPO and statewide planning regulations/requirements , enhanced National Highway System, Primary Freight Networks, commodity flows and safety data . HEPGIS has been used to help implement MAP-21 regulations and will help implement the Grow America Act, particularly related to Ladder of Opportunities and MPO reforms.

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.