A vehicle owner can file a safety complaint in minutes. What happens afterward may take months or years—and the public data does not support a simple stopwatch from one complaint to one recall.
To establish a useful baseline, we analyzed closed National Highway Traffic Safety Administration defect investigations with opening dates from 2016 onward. After deduplicating repeated records, the file contained 300 investigations. The median elapsed time from opening to closing was 418 days, or about 13.7 months.
One quarter closed within roughly 228 days. Three quarters closed within about 777 days. The longest in this recent-decade group ran 2,694 days.
Batmandir · Guest Passes Step inside for a day. Guest passes from $161/day — brought in by a member. See guest passes →Those figures describe investigation duration, not bureaucratic delay by themselves. NHTSA investigates different questions through different processes, and a case may close because of a recall, a safety improvement, insufficient evidence, a transfer to another stage, or another documented reason.
The investigation types are not comparable tasks
NHTSA’s Office of Defects Investigation uses several investigation types. The recent closed cases in the file produced these medians:
| Investigation type | Closed cases | Median elapsed days | NHTSA process target |
|---|---|---|---|
| Preliminary Evaluation (PE) | 170 | 383 | 8 months |
| Engineering Analysis (EA) | 26 | 1,091 | 18 months |
| Recall Query (RQ) | 42 | 331 | 8 months |
| Defect Petition (DP) | 38 | 274 | 4 months |
| Audit Query (AQ) | 15 | 1,236 | Not used here as a direct score |
Median elapsed time for closed NHTSA investigations
Calendar days between opening and closing dates, 2016–2025 cohort
274Recall Query
331Preliminary Evaluation
383Engineering Analysis
1,091Audit Query
1,236
*Graphic: USA Times analysis of NHTSA’s public investigations download. Elapsed time is descriptive and is not, by itself, a performance score.*
The target periods come from NHTSA’s published investigation-process material. Comparing a median with a target is informative, but it is not a pass-fail audit. Targets describe process expectations; elapsed calendar days in the public file can reflect case complexity, extensions, transitions, scope changes, negotiations, and closure mechanics.
Engineering analyses are expected to be deeper than preliminary evaluations, and the data reflects that. Their median exceeded three years. Audit queries in this slice were similarly long, though there were only 15, making the estimate more sensitive to individual cases.
Why complaint-to-recall is the wrong headline metric
The tempting question is: “How long after a consumer complains does NHTSA order a recall?” The datasets do not create that direct causal chain.
Many complaints may describe the same suspected defect. Investigators may also rely on manufacturer reports, warranty claims, field data, testing, early-warning submissions, foreign actions, and petitions. A recall can begin without a public investigation, and an investigation can examine multiple vehicles or components. A single complaint row therefore cannot safely be matched to a later recall merely because the make, model, component, and narrative look similar.
A defensible event timeline needs explicit identifiers or case documents that establish the connection. Without them, a date join can manufacture a relationship that the agency never asserted.
That is why this analysis answers the narrower, reference-worthy question: once NHTSA formally opened an investigation, how long did closed investigations remain open?
What owners should read in an investigation record
Elapsed time is only one field. A useful investigation ledger should also retain:
| Field | Why it matters |
|---|---|
| Investigation number | Stable identifier for documents and updates |
| Type | Indicates the procedural stage or purpose |
| Open and close dates | Defines the public elapsed interval |
| Make, model, and year | Shows the covered population |
| Component | Identifies the alleged safety system or part |
| Summary | Explains the suspected defect |
| Closing resume | States why the inquiry ended or changed stage |
| Associated recalls | Shows outcomes when NHTSA explicitly links them |
An investigation closing without a recall is not proof that every complaint was baseless. It means the agency closed that particular inquiry on the record it describes. Likewise, an open investigation is not a finding that a manufacturer violated the law or that every covered vehicle is defective.
Why complaints, investigations and recalls cannot be collapsed into one rate
NHTSA publishes complaints, investigations and recalls as related but distinct parts of the safety system. A complaint can contribute to pattern detection; an investigation is a formal agency inquiry; and a recall is a remedy addressing a safety defect or noncompliance. They do not form a clean one-to-one pipeline.
Those totals should not be combined into a “complaints per recall” conversion rate. The populations, periods, and pathways differ. The separation is precisely why the investigation archive matters: it records the formal cases between raw complaint intake and any eventual recall action.
For consumers, filing still matters. Complaints can help the agency detect patterns that are invisible in one repair shop or one household. But a complaint is a signal submitted for evaluation, not a case number guaranteeing a particular investigation or recall.
Reproducing the baseline
The raw investigation archive contained repeated rows, so records were deduplicated before calculating durations. We retained unique closed investigations with valid opening and closing dates, then limited the main baseline to cases opened from 2016 onward. Calendar duration equals closing date minus opening date.
The source ZIP used for the analysis has SHA-256 hash:
b292b46b32066c6dae1f14e0eda381cde1bf7948da067451d25d0794ff03db09
Our broader deduplicated file contained 5,115 closed investigations across the archive. The 300-case recent-decade subset is used to keep the headline baseline more relevant to the current process. Future updates should use a fixed cutoff and show open cases separately; excluding open investigations can make durations look shorter because the longest-running current cases have not yet reached a closing date.
That last limitation is important. This is a distribution of completed cases, not a prediction that a newly opened case will close in 418 days.
The practical benchmark
The public record supports a clear expectation: formal vehicle-defect investigations are generally measured in months, and often in years. In the recent closed sample, the midpoint was 418 days. Engineering analyses took substantially longer.
That number is useful to reporters, owners, and policymakers only if it remains attached to its definition. It measures the public open-to-close interval for investigations—not the time from the first crash, first complaint, or first internal warning to a remedy.
Method and sources
Primary sources: NHTSA’s datasets and APIs page, investigation and recall resources, quarterly ODI metrics, and the agency’s flat investigation archive. We deduplicated investigation records, parsed valid dates, and calculated calendar-day intervals. Results do not establish that any duration was unreasonable or connect individual complaints causally to recalls.
