Incident · Fatality
First recorded Tesla Semi fatal crash kills two people in Nevada
A Tesla Semi electric truck struck two passenger vehicles stopped at a red light on US-50 near Dayton, Nevada, killing two people and sending one to the hospital. The driver reportedly fell asleep at the wheel. This is the first known fatal crash involving a Tesla Semi.
Occurred 2026-06-28 · Semi · Tesla · Trucks · 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
- Markdown mirror: /incidents/fatality-2026-06-28-tesla.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/a813a3ed-f192-4239-a5e6-c8ed820bdd77
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Status history
- Active · 2026-07-03 · agent:depth
Common questions
What happened in First recorded Tesla Semi fatal crash kills two people in Nevada?
When did this incident occur?
What robot was involved in First recorded Tesla Semi fatal crash kills two people in Nevada?
Has anyone responded to First recorded Tesla Semi fatal crash kills two people in Nevada?
What is the current status of First recorded Tesla Semi fatal crash kills two people in Nevada?
Methodology: Verified · 1 source (no primary) · last reviewed 2026-07-22
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-22
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for First recorded Tesla Semi fatal crash kills two people in Nevada.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 a813a3ed-f192-4239-a5e6-c8ed820bdd77