Published September 10, 2025
How Crash Data Leads to Vehicle Recalls
Vehicle recalls do not happen in isolation — they are often driven by crash data that reveals patterns of defect-related accidents. NHTSA uses crash investigation data, along with consumer complaints and manufacturer reports, to identify safety defects that require recall action.
NHTSA Crash Investigation Programs
NHTSA operates several crash investigation programs that feed into recall decisions. The Special Crash Investigations (SCI) program conducts detailed investigations of individual crashes that may involve safety defects. The Crash Investigation Sampling System (CISS) provides statistical data on crash causes and outcomes. Together, these programs create a comprehensive view of how vehicle defects contribute to real-world crashes.
From Crashes to Investigations
When crash investigations reveal a pattern of defect-related accidents, NHTSA's Office of Defects Investigation opens a formal investigation. For example, if multiple crashes involve vehicles that experienced sudden steering failure, and the investigation reveals a common manufacturing defect in the steering system, the crash data provides the evidence needed to pursue a recall.
Manufacturer Early Warning Reports
Under the TREAD Act, manufacturers must submit quarterly reports to NHTSA that include data on crashes, injuries, and deaths potentially related to their vehicles. These Early Warning Reports (EWRs) are a critical data source for identifying defect patterns. When EWR data shows an unusual concentration of crashes involving a specific vehicle system, it can trigger a preliminary evaluation.
The Data-to-Recall Pipeline
The path from crash data to recall typically follows a pattern: crash investigations identify a potential defect pattern, NHTSA cross-references crash data with consumer complaints and EWRs, a formal investigation is opened, engineering analysis confirms the defect, and a recall is issued. This process can take months to years depending on the complexity of the defect and the strength of the evidence.
High-Profile Examples
Several major recalls were directly driven by crash data analysis. The Toyota unintended acceleration investigation was triggered partly by crash data showing an unusual pattern of high-speed rear-end collisions. The GM ignition switch recall was linked to crash data showing airbag non-deployments in frontal collisions. In both cases, crash investigation data provided evidence that consumer complaints alone could not.
How You Can Contribute
If you are involved in a crash that you believe was caused by a vehicle defect, report it to NHTSA. File a complaint at NHTSA.gov/complaints with as much detail as possible about the defect that contributed to the crash. Your report becomes part of the crash data that NHTSA uses to identify defect patterns. View crash and complaint data on our complaint rankings page.
Frequently Asked Questions
No. NHTSA investigates crashes that show patterns suggesting a vehicle defect rather than driver error or road conditions. A single crash rarely triggers an investigation unless it reveals clear evidence of a defect. Patterns of similar crashes involving the same vehicle and defect type are what trigger investigations.
The timeline varies significantly. In urgent cases involving clear defects and severe consequences, a recall can be issued within weeks. In more complex cases requiring extensive engineering analysis, the process can take 1-3 years from initial crash pattern identification to recall issuance.
Yes. NHTSA publishes crash investigation reports and data through its website. Special Crash Investigation reports are publicly available, and complaint data (which includes crash-related complaints) is searchable at NHTSA.gov/complaints.