# Enidine (ITT Inc.) safety record

DEPLOY has no incidents on file for Enidine (ITT Inc.). This rolls up incidents attached directly to Enidine (ITT Inc.), to its models, and to its deployments (operated or manufactured).

[Back to Enidine (ITT Inc.)](/companies/enidine.md)

## Incidents (0)

_No incidents on record. Absence of a recorded incident is not proof of a clean operating history._

## Exposure

DEPLOY does not have exposure data (deployment-hours, miles driven, or rides given) on file for Enidine (ITT Inc.). No incident count above can be turned into a defensible rate without it. NHTSA's SGO dataset itself does not publish exposure denominators; there is no standardized, regulator-verified nationwide source for AV fleet mileage or ride counts today.

## Common questions

**What is Enidine (ITT Inc.)'s safety record?**

DEPLOY has no incidents on file for Enidine (ITT Inc.). 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 Enidine (ITT Inc.) safer than a human driver?**

DEPLOY does not have exposure data (miles driven or hours operated) on file for Enidine (ITT Inc.), 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 Enidine (ITT Inc.)?**

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.


_API: GET /v1/safety/companies/c1ae5dad-e550-490d-a754-d3daf856ab6f/profile (bearer-gated) · canonical URL: /companies/enidine/safety-record_