Incident · Collision
Daxbot sidewalk robot struck by vehicle in Tyler Texas
A newly deployed Daxbot sidewalk accessibility robot was struck by a vehicle in Tyler Texas on June 12 2026. The city is investigating the incident but said the robot deployment project remains on track. The Daxbot fleet had just begun scanning 90 miles of sidewalks for ADA compliance.
Occurred 2026-06-12 · Dax Security at United States (multiple hotel chains) · Daxbot · United States (multiple hotel chains)
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/collision-2026-06-12-daxbot.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/8ed9b786-47cd-4e46-a909-b9e4336c9723
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (1)
Status history
- Active · 2026-07-04 · agent:depth
Common questions
What happened in Daxbot sidewalk robot struck by vehicle in Tyler Texas?
When did this incident occur?
What robot was involved in Daxbot sidewalk robot struck by vehicle in Tyler Texas?
Has anyone responded to Daxbot sidewalk robot struck by vehicle in Tyler Texas?
What is the current status of Daxbot sidewalk robot struck by vehicle in Tyler Texas?
Methodology: Verified · 1 source (no primary) · last reviewed 2026-07-14
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-14
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Daxbot sidewalk robot struck by vehicle in Tyler Texas.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 8ed9b786-47cd-4e46-a909-b9e4336c9723