Will NHTSA EA26002 trigger an FSD recall?

The question

Will nhtsa's Engineering Analysis EA26002 (opened March 2026, covering ~3.2M Tesla vehicles for FSD reduced-visibility failures) conclude in a mandatory recall, a mitigation order, or closure without action?

Why it matters

The outcome materially reshapes tesla-fsd's product roadmap. An EA historically resolves within ~18 months; completed EAs often precede recall 2026-04-20-autoresearch-tesla-fsd. A recall would force either software remediation, hardware changes, or both — and would be the strongest signal yet that vision-only perception (see vision-only-vs-sensor-fusion) is insufficient for the operating domain Tesla sells.

What we currently believe

• An EA escalation from a PE is already a significant signal; NHTSA staff clearly found enough to warrant deeper technical testing and manufacturer comparison 2026-04-20-autoresearch-tesla-fsd.
• The specific technical concern — FSD failing to detect degraded camera visibility until immediately before impact — is directly tied to the sensor architecture, not a tunable software flag. A software-only remediation may be insufficient.
• Tesla has historically remediated via OTA software recalls.

Evidence we have

• EA26002 scope: ~3.2M vehicles, nine crashes in reduced visibility with one fatality and one injury, plus six additional incidents under examination 2026-04-20-autoresearch-tesla-fsd.
• Parallel probe PE25012 on traffic violations (~80 incidents by December 2025) — shows regulator is actively compiling evidence across multiple failure modes 2026-04-20-autoresearch-tesla-fsd.

Evidence we need

• Outcome timing: when does EA26002 close?
• Remediation form: software-only, hardware, or both?
• Whether Tesla fights vs complies.

How to resolve

• Track NHTSA docket updates on EA26002.
• Watch for Tesla OTA updates specifically addressing camera-degradation detection.

Related

• nhtsa
• tesla-fsd
• fsd-safety-data-validity