Crash Data Clause Samples
The Crash Data clause defines the collection, use, and management of information generated by a device or system during a crash event. Typically, this clause outlines what types of crash-related data are recorded—such as speed, impact force, or system status at the time of the incident—and specifies who may access or analyze this information, such as manufacturers, insurers, or regulatory authorities. Its core practical function is to ensure that relevant crash data is available for safety analysis, liability determination, or compliance with legal requirements, thereby supporting transparency and accountability in the event of an accident.
Crash Data. WSB will utilize MnDOT’s CMAT website to collect and summarize crash rates for the intersection. This information will be included in the ICE report.
Crash Data. The CONSULTANT will obtain the most recent five (5) years of available data from the DEPARTMENT's crash database and other local sources for this Project. The crash data will include the number and type of crashes, crash locations, number of fatalities and injuries, and estimates of property damage and economic loss.
Crash Data. The consultant shall analyze the crash data for the latest three-years available to identify discernible crash patterns. The consultant shall also develop collision diagrams intersection/ corridor using any automated crash mapping tool. Such automated tool shall be presented to the FDOT project manager for approval prior to utilizing it for any project. The consultant shall also develop and implement a QA/QC process for automated collision diagrams. At a minimum the consultant shall create the following histograms and tables as part of the crash analysis: Crashes by type Crashes by contributing cause Crashes by time of day Crashes by lighting condition Crashes by surface condition Crashes by weather condition Crashes by day of the week Crashes by month of the year Crashes by age group at fault Crashes by alcohol/drug involvement High crash spots High crash segments Crash summary by type Crash summary by contributing cause Crash summary by location
Crash Data. The Branch completed a two-year staff supplement contract that employed 16 temporary staff to eliminate the crash-records quality review and assurance backlog of 3.5 years. At present, all historical on-system crash records are processed and available for use. Currently received crash records in 2012—both on and off-system—are processed within four months of receipt from the Department of Revenue. The only remaining backlog is for the 2008-2011 off-system crash records, which will be processed once the Future Staffing of the Traffic Records Unit is addressed and resolved by Management. The Branch is working to achieve all current records with our permanent staff supplemented by a small group of temporary staff who will be with us until late 2013. Prior to their departure CDOT will develop a staffing model to implement in order to keep crash record processing—both for on-system and off-system crashes—within the safety performance measure of six months or less. Colorado does not have a primary seat-belt law. This actually comes from the Governor's Office to FHWA, not through OTS. Colorado is in compliance. Colorado is in compliance.
Crash Data. Provide pertinent motor vehicle crash data (fatalities and injuries) for each of the previous three (3) years.
Crash Data. The MPO shall provide technical resources and data.
Crash Data. For crash related data, the type of motor vehicle, its configuration and identifiers are also provided, alongside crash details containing the count of injuries, fatalities, vehicles involved and outcome containing but not limited to Hazmat involvement, towaway or citations were issued to said driver. Crash inspection data provides location, weather conditions, road surface conditions and light conditions pertaining to the crash incident.
Crash Data. Stantec engineers will request collision information for the study intersections.
4) Forecasted Traffic Volumes: Stantec will review recent traffic studies and establish projections of traffic based on the Town’s Comprehensive Plan and data available from NCTCOG and TxDOT for the area to determine short- and long-term traffic volume forecasts for the intersection after Legacy is extended.