DEPLOYDatabase

Safety record

TTS Bee-Bot safety record

DEPLOY has no incidents on file for TTS Bee-Bot. This rolls up incidents attached directly to TTS Bee-Bot, to its models, and to its deployments (operated or manufactured): the same graph as the company page's safety-record summary, shown here with full sourcing and exposure context.

← Back to TTS Bee-Bot

Machine-readable surfaces

Incidents

No incidents on record for TTS Bee-Bot. Absence of a recorded incident is not proof of a clean operating history; it reflects what DEPLOY has tracked and verified to date.

Exposure

DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for TTS Bee-Bot's 2 recorded deployments. This is a genuine data gap, not a rounding to zero: no incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators, and there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today. Where a company self-publishes a mileage figure, it is not independently audited and is not shown here as DEPLOY-verified data.

Common questions

What is TTS Bee-Bot's safety record?
DEPLOY has no incidents on file for TTS Bee-Bot. This reflects the incidents DEPLOY has tracked and verified to date, drawn primarily from NHTSA's Standing General Order crash-reporting program and press coverage; it is not a safety guarantee, and absence of a recorded incident is not proof of a clean operating history.
Is TTS Bee-Bot safer than a human driver?
DEPLOY does not have exposure data (miles driven or hours operated) on file for TTS Bee-Bot, so no per-mile or per-hour safety rate can be computed from this registry today. This is a documented industry-wide data gap, not unique to DEPLOY: NHTSA's own SGO dataset does not publish exposure denominators alongside crash counts. Any rate comparison you see elsewhere may rely on a company's self-published mileage figures, which are not independently audited.
Does DEPLOY redact or omit crash details for TTS Bee-Bot?
No. DEPLOY does not redact incident narratives. Where a source narrative is itself incomplete (for example, a NHTSA SGO filing redacted as confidential business information), DEPLOY states that plainly rather than filling the gap. See "A note on NHTSA's crash-reporting data" below.

Full company record: TTS Bee-Bot