DEPLOYDatabase

Incident · Regulatory action

NHTSA sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations

On July 2, 2026, NHTSA's Office of Defects Investigation sent Tesla a 24-part information request (ID EA26002-01) as part of the Engineering Analysis into Full Self-Driving crashes in reduced-visibility conditions. The demand specifically calls out an internal Tesla document titled 'Radar Saves Us,' which appears relevant to Tesla's decision to remove radar and rely on a vision-only system. Tesla's response is due August 12, 2026.

Occurred 2026-07-02 · Tesla · Investigated by NHTSA

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 sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations

Machine-readable surfaces

Sources (2)

  1. NHTSA Office of Defects Investigation · https://static.nhtsa.gov/odi/inv/2026/INIM-EA26002-14414.pdf · 2026-07-02
  2. Electrek · https://electrek.co/2026/07/21/nhtsa-tesla-radar-saves-us-document-fsd-probe/ · 2026-07-21

Status history

  • Active · 2026-08-03 · agent:recon

Common questions

What happened in NHTSA sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations?
On July 2, 2026, NHTSA's Office of Defects Investigation sent Tesla a 24-part information request (ID EA26002-01) as part of the Engineering Analysis into Full Self-Driving crashes in reduced-visibility conditions. The demand specifically calls out an internal Tesla document titled 'Radar Saves Us,' which appears relevant to Tesla's decision to remove radar and rely on a vision-only system. Tesla's response is due August 12, 2026.
When did this incident occur?
The incident is recorded as occurring on July 2, 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 sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations?
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 sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations?
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 sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 2 sources (1 primary) · last reviewed 2026-08-09

Verification posture

Verified

High confidence

Review state

Stable

Last reviewed 2026-08-09

Sources by quality tier

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

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

Methodology surface for NHTSA sends Tesla 24-part information demand in EA26002, requesting internal 'Radar Saves Us' document on vision-only FSD limitations.

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 ced5a5c6-a329-492d-86d1-39ada041bac9