DEPLOYDatabase

Incident · Regulatory action

NHTSA opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin

NHTSA opened an audit query investigation into Tesla's Cybercab deployment on September 4, 2026, mere hours after Tesla put the first Cybercabs on public roads in Austin, Texas. The Cybercab is a two-seat fully autonomous vehicle with no steering wheel or brake pedals. Tesla told NHTSA it self-certified the Cybercab as compliant with all Federal Motor Vehicle Safety Standards.

NHTSA is examining the certification process and technical data, particularly whether Tesla's certification depended on determinations that certain FMVSS rules are inapplicable. The same audit query process was used for Zoox in 2023.

Occurred 2026-09-04 · Cybercab · Tesla · Robotaxis · 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.

Machine-readable surfaces

Sources (3)

  1. TechCrunch · https://techcrunch.com/2026/09/04/feds-launch-investigation-into-teslas-cybercab-deployment/ · 2026-09-04
  2. New York Times · https://www.nytimes.com/2026/09/05/business/tesla-cybercab-nhtsa-investigation.html · 2026-09-05
  3. https://electrek.co/2026/09/15/nhtsa-tesla-cybercab-special-order-fmvss-certification/ · 2026-09-15

Status history

  • Active · 2026-09-06 · agent:recon

Common questions

What happened in NHTSA opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin?
NHTSA opened an audit query investigation into Tesla's Cybercab deployment on September 4, 2026, mere hours after Tesla put the first Cybercabs on public roads in Austin, Texas. The Cybercab is a two-seat fully autonomous vehicle with no steering wheel or brake pedals. Tesla told NHTSA it self-certified the Cybercab as compliant with all Federal Motor Vehicle Safety Standards. NHTSA is examining the certification process and technical data, particularly whether Tesla's certification depended on determinations that certain FMVSS rules are inapplicable. The same audit query process was used for Zoox in 2023.
When did this incident occur?
The incident is recorded as occurring on September 4, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in NHTSA opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin?
Cybercab is the recorded robot involved in this incident.
Has anyone responded to NHTSA opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin?
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 opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Verified · 3 sources (no primary) · last reviewed 2026-09-29

Verification posture

Verified

Medium confidence

Review state

Stable

Last reviewed 2026-09-29

Sources by quality tier

1
secondary-industry-publication
Industry publication
1
secondary-established-publication
Established publication
1
unclassified
Unclassified source

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

Methodology surface for NHTSA opens investigation into Tesla Cybercab deployment hours after steering-wheel-free robotaxi launches in Austin.

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 0f2c54f5-ef45-4827-83e8-f0476950946c