Crash Report Sampling System (CRSS)

ICR 201910-2127-002

OMB: 2127-0714

Federal Form Document

Forms and Documents
Document
Name
Status
Supplementary Document
2019-10-30
Supplementary Document
2019-10-30
Supporting Statement A
2019-10-30
Supporting Statement B
2019-10-30
IC Document Collections
IC ID
Document
Title
Status
238347
New
238346
New
238344
New
238343
New
218333
Modified
ICR Details
2127-0714 201910-2127-002
Active 201601-2127-001
DOT/NHTSA
Crash Report Sampling System (CRSS)
Extension without change of a currently approved collection   No
Regular
Approved without change 12/17/2019
Retrieve Notice of Action (NOA) 10/30/2019
  Inventory as of this Action Requested Previously Approved
12/31/2022 36 Months From Approved 12/31/2019
98 0 840
35,680 0 7,280
0 0 0

The Crash Report Sampling System (CRSS) collects data from police-reported crashes involving all types of motor vehicles, pedestrians, and cyclists; this includes property damage only crashes as well as those resulting in injuries and fatalities. CRSS obtains its data from a nationally representative probability sample selected from the estimated six million police-reported crashes that occur annually in the United States. By focusing attention on police-reported crashes, CRSS concentrates on the crashes of greatest concern to the highway safety community and the general public. CRSS depends on the voluntary participation and cooperation of State and law enforcement agencies. This allows the National Highway Traffic Safety Administration (NHTSA) and its contractors to access the crash reports to review, list, and categorize the crashes. The crash reports provide essential data: detailed information regarding the location of the crash, the vehicles, and the people involved. The reports are official local and State government forms that include the location of the crash and the pre-crash environment, explains the number and types of vehicles involved as well as describing the persons, injuries and other variables to express how the person was involved in the crash. No personally identifiable information is collected or released via the CRSS program. Selected crashes are released to the public in the annual CRSS file following quality control processes conducted by NHTSA. These data files are used by NHTSA and the general public for highway safety research purposes.

PL: Pub.L. 89 - 563 106, 108, 112 Name of Law: National Traffic and Motor Vehicle Safety Act of 1966
  
None

Not associated with rulemaking

  84 FR 33314 07/12/2019
84 FR 57157 10/24/2019
Yes

5
IC Title Form No. Form Name
Manual
EDT (Implementation)
EDT (Maintenance)
Web Service
State Website

  Total Approved Previously Approved Change Due to New Statute Change Due to Agency Discretion Change Due to Adjustment in Estimate Change Due to Potential Violation of the PRA
Annual Number of Responses 98 840 0 0 -742 0
Annual Time Burden (Hours) 35,680 7,280 0 0 28,400 0
Annual Cost Burden (Dollars) 0 0 0 0 0 0
No
No
The total burden hour estimate of 35,680 hours represents an increase of 28,400 hours over the previously estimated burden of 7,280 hours. The change in burden hours represents a recalculation designed to more accurately estimate the time required to comply with the collection. The previous calculation was estimated prior to CRSS’s implementation and didn’t take into account the burden of establishing and maintaining cooperation with police jurisdictions and State agencies, to access crash report data. Additional administrative processes and more formalized arrangements which are in place to protect personal identifiable information have been encountered while establishing CRSS. Additionally, the CRSS data collection efforts involves a variety of methods to access crash reports, both manual and electronic processes which were unknown at the prior submission. While CRSS leverages new technology to reduce the burden on respondents wherever possible, initial CRSS burden estimates were calculated based on assumptions rooted in the legacy National Automotive Sampling System General Estimates System (NASS GES) that CRSS has since replaced. With increasing concerns related to liability and privacy protection, police jurisdictions have in many cases implemented stringent and time-consuming oversight requirements related to accessing crash reports. These additional needs include but are not limited to requiring respondent representatives be present while the CRSS sampler is reviewing the crash reports during collection site visits. Administrative burdens such as making paper copies of crash reports and/or uploading electronic crash reports for the CRSS sampler to access when the police jurisdiction is not able to provide a physical work space is also included in the burden estimate. Additionally, the process of establishing cooperation is taking more time than it did under NASS GES with police jurisdictions taking more time to verify the purpose and intent of the program and frequently seeking approval from police chiefs and local legal counsel before providing access. Respondent jurisdictions are now frequently reviewing the CRSS contractor’s statement of work, consulting legal counsel, and requiring specific memoranda of understanding with NHTSA prior to agreeing to participate in the program. These additional activities germane to establishing cooperation and managing manual data collection activities were not anticipated when the original CRSS burden estimate was developed.

$2,846,491
Yes Part B of Supporting Statement
    No
    No
No
No
No
Uncollected
Luke Johnson 202 366-1722

  No

On behalf of this Federal agency, I certify that the collection of information encompassed by this request complies with 5 CFR 1320.9 and the related provisions of 5 CFR 1320.8(b)(3).
The following is a summary of the topics, regarding the proposed collection of information, that the certification covers:
 
 
 
 
 
 
 
    (i) Why the information is being collected;
    (ii) Use of information;
    (iii) Burden estimate;
    (iv) Nature of response (voluntary, required for a benefit, or mandatory);
    (v) Nature and extent of confidentiality; and
    (vi) Need to display currently valid OMB control number;
 
 
 
If you are unable to certify compliance with any of these provisions, identify the item by leaving the box unchecked and explain the reason in the Supporting Statement.
10/30/2019


© 2024 OMB.report | Privacy Policy