One in Five US Car Recalls Misses the 60-Day Legal Deadline to Tell Owners — and the Typical One Uses 46 of Those Days

Key facts

• 46 days is the median gap between a manufacturer filing a recall with NHTSA and the owner-notification date recorded for it, across 1,013 car and light-truck campaigns filed 2024-01-01 to 2026-10-07.
• 20.6% of those campaigns (209) carry a notification date more than 60 days after filing — the ceiling set by 49 CFR 577.7(a)(1). Those campaigns cover 25,954,113 vehicles.
• 74.0% took longer than 30 days; 16.8% longer than 90; 6.5% longer than 180; 1.0% longer than a year.
• The average recalled vehicle waits longer than the average recall: unit-weighted, the median lag is 52 days and the mean 82.6, against a campaign mean of 58.1. Big campaigns are slower.
• Chrysler notified fastest at a median 26 days (28 excluding six records dated before their own filing), then GM 34 and Volkswagen 35.5. Ford, the largest filer at 252 campaigns, sits at 40.
• The slowest manufacturer depends on the statistic, so we name none. Tesla has the slowest median (60); Porsche the slowest mean (105.0), with Tesla 7th on that measure.
• Recalls NHTSA pushed for are far slower to reach owners: median 55 days versus 45 for manufacturer-initiated, and 40.7% past the ceiling versus 17.8%.
• Restricting to cars and light trucks raises the median from 41 to 46 days, because RV, bus and heavy-truck filers notify fastest.

How long does it actually take to get a recall notice?

A median of 46 days from the filing date, and the distribution has a hard shape to it: notifications pile up just under the legal ceiling. Of 1,013 campaigns, 142 (14.0%) land in the five-day window from day 56 to day 60, and 34 land on day 60 exactly. The deadline is not a backstop that nobody approaches; it is a scheduling target.

The single longest in the window is Nissan campaign 24V700000, 25,704 vehicles over a traction-motor electrical defect, at 615 days. The largest slow one is Ford 24V031000 — 1,889,110 vehicles, roof and pillar structure — at 181 days.

Which manufacturers notify owners fastest, and which take longest?

Across the 17 car and light-truck filers with at least 10 campaigns in the window:

Two cautions belong with this table rather than below it. First, median and mean disagree, and the disagreement is not cosmetic. Tesla leads on median and is seventh on mean; Porsche is second on median and first on mean by a wide margin; Chrysler's mean (11.2) sits far below its median (26) because six of its campaigns carry notification dates that precede their own filing dates. We therefore make no claim that any one manufacturer is "slowest." Second, these are NHTSA filer names, not corporate families — the MFGTXT field separates a company's US arm from its parent, so these rows are filers, not brands.

Why do Tesla's notices land on day 60 so consistently?

Because 60 days is the limit, and Tesla schedules to it. 15 of Tesla's 30 campaigns in this window carry a notification date exactly 60 days after the report date, and its full spread is unusually tight: 24 of 30 fall between day 56 and day 62.

This is the opposite of a compliance problem, and reading it as one would be the easy mistake. Every campaign at day 60 is inside the legal limit. Tesla's rate of actually exceeding the ceiling is 20.0%, below Ford's 29.8%, Toyota's 34.0% and Porsche's 40.0%. What the pattern shows is a manufacturer treating the statutory maximum as a default schedule rather than a deadline to beat — which matters to a buyer only because it makes the wait predictable, not because it makes it unlawful.

Are the recalls NHTSA had to push for slower?

Yes, and this is the sharpest divide in the data. The flat file records who influenced each recall. Comparing the two main categories:

A recall the agency had to press for takes a median 10 days longer to reach owners and blows the 60-day ceiling more than twice as often. The mean gap is far wider still — 104.3 days against 51.7 — which says the ODI-influenced group contains a long tail of very slow notifications rather than a uniform shift.

What this does not establish is a cause. A recall that NHTSA had to argue for is also likely to be one where the defect's scope, the affected population or the remedy was contested, and any of those would independently delay a letter. The association is solid; the mechanism is not something this file can settle.

Why this is in the news: the Ford headlight recall nobody has been written to about yet

The loudest US recall story of October 5-6 was Ford campaign 26V606000 — 41,748 Expedition and Super Duty vehicles, a contaminated LED chip that can make a headlight fail. It ran across Car and Driver, Fox Business, USA Today, Forbes, Kelley Blue Book and others.

NHTSA received that report on 2026-09-22. As of the file retrieved for this analysis, it carries no owner-notification date at all.

That is worth stating carefully, because the obvious reading is wrong. A missing notification date on a two-week-old filing is normal, not negligent. Measured across the file: 87.7% of campaigns filed within the last 30 days have no notification date recorded yet, falling to 62.5% at 31-60 days, 23.4% at 61-120 days and just 6.0% beyond 120 days. The field fills in as schedules are set. Ford is not an outlier here.

The point is the one a buyer can act on: a recall was national news, it has been public in NHTSA's database for over two weeks, and the people who own those trucks have no letter and no scheduled date for one. Anyone buying a 2025-2027 Expedition or a 2026 Super Duty this month is dealing with a seller who very likely has not been told.

What a VIN check can and cannot tell you here

It can tell you that an open recall exists on a specific vehicle, today, without waiting for anyone's mail. That is the whole practical value of this finding: the recall is public from the filing date, and the median letter is 46 days behind it. A VIN screen also shows accident and damage records including airbag deployment, salvage and junk-auction records, odometer readings and rollback indicators, theft records, ownership history, sales-listing history, specs and safety ratings.

It cannot tell you whether the recall was repaired. No commercial vehicle-history feed carries remedy or "flashed" status for a software fix. NHTSA's own VIN lookup and a franchised dealer are the authorities on repair status, and for a recall this recent the honest answer is usually that the remedy is not yet available.

It cannot tell you whether a letter was sent, or to whom. The notification date in this dataset is a campaign-level schedule, not a per-vehicle delivery record. And a letter addressed to a previous registered owner does not follow the car — which is the structural reason a used buyer cannot rely on notification at all, independently of any delay measured here.

It cannot tell you about an open NHTSA investigation. Preliminary evaluations and engineering analyses are not recalls and do not appear in a VIN feed; NHTSA publishes those itself.

Method: how we counted this, and how to verify it yourself

Source and retrieval. NHTSA Office of Defects Investigation recall flat file FLAT_RCL_POST_2010.txt, retrieved 2026-10-07 at 07:20 UTC. The server reported Last-Modified: Tue, 06 Oct 2026 07:04:59 GMT — the same timestamp as the previous day, so NHTSA had not republished the file in between. It holds 245,719 tab-separated rows and the latest RCDATE in it is 2026-10-01. The archive's CRC was verified before parsing (testzip() returned clean), because this endpoint has twice served a silently truncated extract under a fresh timestamp.

The step that decides whether the numbers are right. The file carries one row per model-year per model inside a campaign, while POTAFF, RCDATE and ODATE are campaign-level fields repeated identically on every one of those rows. Campaign 26V606000 occupies 42 rows, each reading 41,748. Every figure here collapses the file to a single record per CAMPNO before any aggregation.

Universe and exact filter. Keep RCLTYPECD = 'V' (vehicle recalls, excluding equipment, tyre and child-seat campaigns). Bucket on RCDATE from 2024-01-01 to 2026-10-07. Restrict to the 21 passenger-car and light-truck part 573 filers by MFGTXT, because 'V' means "vehicle", not "car" — it also carries motorcycles, buses, heavy trucks, motorhomes and trailers. N = 1,013 campaigns carrying both dates. The unrestricted all-vehicle basis is 2,244.

The metric. · lag = ODATE - RCDATE, in days, compared against the 60-day ceiling in 49 CFR 577.7(a)(1): notification "no later than 60 days from the date the manufacturer files its defect or noncompliance information report under part 573."

Exclusions and what they cost. Campaigns with no ODATE are excluded from every lag figure. Among car filers in this window that is a median of 7.3% per filer (range 0.0% to 16.7%). Ten records (1.0%) carry a notification date earlier than their own filing date; they are retained in the headline figures and the effect of removing them is reported below.

Reversal checks, each reported either way.

1. The superlative does not survive a change of statistic. Tesla has the slowest median (60) but the 7th slowest mean (64.6); Porsche has the slowest mean (105.0). We therefore publish no "slowest manufacturer." This is the check that changed the article.
2. "Chrysler fastest" survives. Dropping the six Chrysler records dated before their own filing moves its median from 26 to 28 days — still fastest, by 6 days over GM. The ordering of all 17 filers is unchanged.
3. The ranking is stable out of sample. Re-ranked over the non-overlapping 2020-2023 window, the filer ordering returns Spearman 0.857 across the 15 filers present in both. Tesla 60/59.5, Porsche 58/58, Toyota 57.5/57, BMW 57/56, Chrysler 26/33.5.
4. The ranking is not an artefact of missing data. If fast filers looked fast because their slow campaigns had no notification date yet, missing-date rate and median lag would be strongly negatively correlated. Pearson r = +0.242 — the wrong sign for that explanation.
5. Narrowing to cars raises the figure. The all-vehicle median is 41 days; cars and light trucks alone give 46, because RV and bus filers are the fastest notifiers in the file. The unrestricted number understates the car buyer's wait.
6. Dropping the pre-filing records moves the overall median from 46 to 47 and the mean from 58.1 to 63.8.

Corroboration against a second NHTSA system. 70 campaigns — all 30 Tesla campaigns plus 40 drawn at random — were re-queried individually against api.nhtsa.gov/recalls/campaignNumber. Units matched 70 of 70 exactly. Report dates matched 59 of 70 exactly, with 11 rendering exactly one day later in the API; the API emits dd/mm/yyyy from a timestamp, so this is a date-rendering difference, not a data defect. It bounds every lag figure here at ±1 day, which does not move a 46-day median or a 34-day spread.

Known limits, each of which bounds a claim above.

• A lag over 60 days is not automatically a violation. 49 CFR 577.7 permits an interim notice when the remedy is not yet available, with a second letter once it is; and it lets the Administrator modify a manufacturer's notification schedule under 573.6(c)(8)(ii). This analysis measures the recorded notification date, not compliance.
• ODATE cannot be cross-checked against a second source. NHTSA's public API exposes the report-received date but not the owner-notification date, so unlike the filing date, half of every lag rests on the flat file alone.
• RCDATE is the date NHTSA received the report, which can differ from the date the manufacturer filed it — the reference point the regulation actually uses.
• The notification date is a campaign-level schedule, not proof of delivery. Nothing here shows a letter was mailed, arrived, or reached the current owner.
• Owners are not the first to be told. For defects posing an immediate and substantial safety risk, dealers must be notified within three to five business days, so a long owner lag does not mean nobody could act.
• POTAFF is the manufacturer's launch-time estimate of units potentially affected. It is not a count of defective vehicles, vehicles still on the road, or vehicles unrepaired.
• Filer names are not corporate families. Figures are per MFGTXT as NHTSA records it.
• The file moves. NHTSA republishes it continuously, so a later re-pull will not reproduce these counts exactly. The frozen CSVs below are the reproducible artefact.

The frozen dataset is published alongside this article: all 1,013 campaign-level rows with both dates and the lag, the per-filer summary with both windows, and the 2010-2026 annual series on both bases.

FAQ

How long does it take to get a recall notice in the mail? A median of 46 days from the day the manufacturer files the recall with NHTSA, across 1,013 US car and light-truck campaigns filed January 2024 to October 2026. Federal law caps it at 60 days and 20.6% ran past that. Three quarters took longer than 30 days.

How long do manufacturers legally have to notify owners? No later than 60 days from filing the part 573 report, under 49 CFR 577.7(a)(1). The rule allows an interim notice when no remedy exists yet, plus a second letter later, and the NHTSA Administrator can modify a manufacturer's schedule — so a longer gap here is not automatically unlawful.

Which carmaker tells owners fastest? Chrysler (FCA US), median 26 days over 127 campaigns, or 28 after dropping six records dated before their own filing. GM follows at 34 and Volkswagen at 35.5. Ford, the biggest filer at 252 campaigns, is at 40.

Which is slowest? It depends on the average, so we do not name one. Tesla is slowest by median (60 days); Porsche is slowest by mean (105.0) with Tesla seventh.

Why do Tesla's notices land on day 60? 15 of its 30 campaigns are dated exactly 60 days after filing — the statutory maximum used as a default schedule. All of them are inside the limit, and Tesla exceeds 60 days less often (20.0%) than Ford (29.8%) or Toyota (34.0%).

Are recalls NHTSA pushed for slower to reach owners? Yes. Median 55 days against 45 for manufacturer-initiated recalls, and 40.7% past the 60-day ceiling against 17.8%. The association is clear; the cause is not something this file can settle.

What is the longest delay recorded? 615 days, Nissan 24V700000 (25,704 vehicles, traction-motor defect). Ten campaigns exceeded a year. The largest slow one is Ford 24V031000 at 181 days over 1,889,110 vehicles.

My car may be recalled and no letter has come. What now? Do not wait for it. Check the VIN at nhtsa.gov/recalls or run a VIN check, and call a franchised dealer. The recall is public from the filing date, a median 46 days before the letter is even scheduled.

Sources

• NHTSA Office of Defects Investigation, recall flat file FLAT_RCL_POST_2010.zip — the source for every figure here. Retrieved 2026-10-07 07:20 UTC, Last-Modified 2026-10-06 07:04:59 GMT. Last verified 2026-10-07.
• 49 CFR 577.7, "Time and manner of notification" — the 60-day ceiling, the interim-notice provision and the Administrator's power to modify a schedule. Cornell Legal Information Institute. Last verified 2026-10-07.
• NHTSA recalls API, api.nhtsa.gov/recalls/campaignNumber — used to corroborate 70 campaigns on units and report dates. Last verified 2026-10-07.
• NHTSA recall lookup, nhtsa.gov/recalls — the authority on whether a specific VIN has an open recall and whether it was remedied. Last verified 2026-10-07.
• Frozen datasets for this analysis, published alongside the article and reproducible without re-pulling NHTSA's moving file. Last verified 2026-10-07.
• All 1,013 campaign rows with both dates, the lag and the over-60 flag: https://zilocar-news.github.io/zilocar-rss/data/car-recall-owner-notification-delay-nhtsa-data-2026-10-07.csv
• Per-filer summary, both windows: https://zilocar-news.github.io/zilocar-rss/data/car-recall-owner-notification-delay-nhtsa-data-by-filer-2026-10-07.csv
• Annual series 2010-2026 on both bases: https://zilocar-news.github.io/zilocar-rss/data/car-recall-owner-notification-delay-nhtsa-data-by-year-2026-10-07.csv