_Incident · Regulatory action_

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

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

- **Occurred:** 2026-03-18
- **Kind:** `regulatory_action`
- **Status (derived):** active
- **Company:** [Tesla](/companies/tesla.md) (id: `bde7c8a1-5d35-449d-93b0-2ac8e4601c16`)

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.

## Sources (1)

1. https://panterlaw.com/nhtsa-tesla-full-self-driving-investigation/

## Status history

- **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.

### 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 an active record on the DEPLOY registry; no retraction or correction has been issued.


_API: GET /v1/incidents/adccb2fd-9805-4f3f-8c71-df6f0429a220 · sources: /v1/incidents/adccb2fd-9805-4f3f-8c71-df6f0429a220/sources · responses: /v1/incidents/adccb2fd-9805-4f3f-8c71-df6f0429a220/responses · status: /v1/incidents/adccb2fd-9805-4f3f-8c71-df6f0429a220/status · canonical URL: /incidents/regulatory-action-2026-03-18-tesla_