Autonomous Vehicle Recording Devices and Crash Evidence

Separate the legal requirements

Section 545.455 lists recording equipment among the conditions for automated operation. Section 547.615 addresses the defined recording device, disclosure, access, and exceptions. Section 545.457 connects collision response to Chapter 550. Each provision should be applied to its actual subject rather than combined into a fictional all-purpose black-box rule. [1; 2]

An authorization holder should identify the installed device and the information it records. A vendor's general telemetry service may have different capabilities, access rights, and retention. Compliance with the device requirement does not automatically establish that every desired reconstruction record exists.

Federal event data recorders

Part 563 addresses covered EDR requirements, defined data elements, and related conditions. It does not mean that every vehicle records every camera feed or that every ADS decision is an EDR field. The actual vehicle and recorder need examination. [3]

The Driver Privacy Act of 2015 supplies separate ownership and access rules with specified exceptions. Consent, legal process, safety investigation, emergency, and other statutory conditions should be identified for the actual request. A crash alone does not automatically make all vehicle data publicly available. [4]

Identify the broader evidence

Potential evidence includes software version, configuration, calibration, maps, sensors, remote assistance, maintenance, alerts, dispatch, and responder communications. The inventory should identify where each record resides and how quickly it is overwritten. The vehicle, manufacturer, fleet, cloud vendor, and support contractor may hold different parts.

Recommended collection records include device identity, time settings, extraction method, original format, metadata, and known limitations. An exported summary should not silently be treated as the complete raw record. Aligning clocks and configurations can be essential to determine what happened before and after contact.

Preservation and legal holds

Brookshire Brothers v. Aldridge states Texas preservation principles involving reasonable anticipation of a claim and material, relevant evidence. The duty is not an instruction to retain every ordinary fleet record forever. The actual incident, knowledge, possession or control, and relevance determine the scope. [5]

Federal Rule 37(e) addresses specified loss of ESI, reasonable preservation steps, restoration or replacement, prejudice, and intent. Discovery scope and production under Rules 26 and 34 are separate. A hold should therefore identify relevant custodians, systems, overwrite cycles, and vendor cooperation rather than preserve only the most convenient video export. [6]

Access, contracts, and privacy

The deployment agreement should address prompt preservation, usable exports, documentation, technical assistance, fees, and survival after termination. A fleet should know whether it can obtain data or merely view a dashboard. Contractual access does not itself override statutory privacy, privilege, confidentiality, or lawful process requirements.

Personal data and confidential technical information may need protective handling during investigation and litigation. A record can be relevant without being suitable for unrestricted public release. Government-held records require their own Chapter 552 and other statutory analysis where applicable.

Reporting and reconstruction

NHTSA's crash-reporting order imposes its own duties on served entities and qualifying events. The order is distinct from EDR ownership, Texas collision response, recall reporting, and civil discovery. The incident plan should track each obligation by actor and trigger. [7]

Reconstruction should separate observed facts from inferred behavior. A later software version, a successful reenactment, or a missing stream does not by itself establish the earlier configuration or cause. The record should preserve uncertainty and explain what each source can and cannot show.

Hypothetical crash record

A driverless vehicle stops after contact while remote support later sends a maneuver instruction. The investigation should align event times and distinguish the ADS's preceding actions from the later remote command. A single dashboard timeline without its assumptions may conceal that distinction. The legal analysis needs competent evidence of the relevant conduct, not simply a system label.