NHTSA recalls & campaign detail
Official model campaigns, consequence, remedy, campaign-level advisory fields and affected-unit context.
Browse vehicle recall pages →Sources & methodology
Source first. Interpretation second.
Every RecallSight report separates official agency records, public reports, indexed manufacturer communications and RecallSight-derived organization or chronology.
01Identify the source02Match the vehicle03Label the evidence04Show limitations
Vehicle data sources
What can contribute to a report
NHTSA complaints
Public consumer reports. They can contain crash, fire, injury and component fields but do not by themselves prove a defect.
How complaints fit the evidence path →NHTSA 5-Star Safety Ratings
RecallSight resolves tested configurations and detailed VehicleId records rather than inventing ratings for untested configurations.
Manufacturer communications / TSBs
Bulk-indexed NHTSA communications can include service bulletins, repair instructions, warranty programs and other manufacturer notices.
ODI investigations
Official defect-investigation records are indexed from NHTSA bulk data and kept distinct from recalls and complaints.
EPA/DOE & Transport Canada
Fuel-economy and cross-border recall context are supplemental and are shown only when a reliable match or response is available.
Interpretation rules
What RecallSight will not infer
A complaint is a public report, not a verified finding.
Year/make/model campaigns do not establish whether a specific VIN still needs repair.
A bulletin or complaint appearing before a recall does not prove prior knowledge or causation.
RecallSight prefers transparent evidence and denominators over a mystery risk rating.
Matching & freshness
How RecallSight avoids false certainty
Vehicle names are normalized against official NHTSA taxonomy where possible. API failure is kept separate from a genuine zero-result response. Public evidence cached in D1 is labeled as indexed or cached, rather than presented as live.
VIN-backed reports use VIN context for better configuration matching, but the full VIN is not stored in RecallSight’s server-side evidence index.