Retracted · 2026-07-24

Duplicate ingestion of the same event as regulatory-action-2026-03-19-tesla, the canonical record for "Tesla NHTSA EA26002 FSD reduced-visibility (2026-03)". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction fairness policy.

Incident · Regulatory action · Retracted

NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles

Original claim shown above is no longer asserted. See the retraction notice for context.

Occurred 2026-03-18 · Tesla

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.

Track NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles

Machine-readable surfaces

Markdown mirror: /incidents/regulatory-action-2026-03-18-tesla.md
JSON-LD: embedded in this page’s head
REST API: /v1/incidents/adccb2fd-9805-4f3f-8c71-df6f0429a220
Data documentation: /data
Query this programmatically: Deploy MCP

Sources (2)

Status history

Retracted · 2026-07-24
Duplicate ingestion of the same event as regulatory-action-2026-03-19-tesla, the canonical record for "Tesla NHTSA EA26002 FSD reduced-visibility (2026-03)". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction fairness policy.
Active · 2026-07-03 · agent:depth

Common questions

What happened in NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles?

NHTSA upgraded its Tesla Full Self-Driving investigation to Engineering Analysis EA26002 with an expanded scope of 3,203,754 vehicles. The investigation found Tesla FSD did not detect reduced visibility conditions and failed to alert drivers. This incident was later retracted; see the retraction banner at the top of the page for the correction.

When did this incident occur?

The incident is recorded as occurring on March 18, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

Who was involved in NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles?

The incident is recorded as involving Tesla on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

Has anyone responded to NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles?

No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.

What is the current status of NHTSA escalates Tesla FSD investigation to Engineering Analysis EA26002 covering 3.2M vehicles?

This incident is retracted on the DEPLOY registry. The page remains so the correction reaches readers, but the incident is suppressed from aggregate counts (company / model / location) so it no longer counts against anyone.

Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-07-14

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-07-14

Sources by quality tier

1: unclassified; Unclassified source
1: primary-regulatory-filing; Regulatory filing

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.

Canonical ID adccb2fd-9805-4f3f-8c71-df6f0429a220