EVIDENCE LIBRARY · VEHICLE DATA & CRASH FORENSICS

Vehicle / EDR & Telematics

A Citizen’s Guide to event data recorders, vehicle modules, connected-car systems, telematics, lawful access, preservation, download integrity, and what machine-generated vehicle evidence can — and cannot — prove after a crash.

Start with the factual question. “Vehicle data” may exist in several different systems. An EDR, an infotainment unit, an OEM connected-car account, a fleet telematics platform, and a phone paired to the vehicle are different evidence sources with different retention, access, and technical limits.

Preservation First

Preserve the vehicle and its data before ordinary handling changes the evidence.

After a serious crash, the vehicle may be towed, repaired, scanned, power-cycled, reprogrammed, salvaged, sold, or dismantled. Some crash-event data are locked against overwriting, but some non-deployment event buffers may be overwritten depending on the vehicle and event. Preservation should address both the physical vehicle and any remote systems that may hold related data.

1

Identify the vehicle

Record VIN, year, make, model, trim, odometer, plate, owner/lessee, tow location, repair facility, insurer, and current custodian.

2

Freeze destructive handling

Address repair, salvage, module replacement, unnecessary operation, reprogramming, disposal, and loss of power where relevant.

3

Map the systems

Determine whether evidence may exist in the EDR/airbag control module, infotainment, navigation, OEM telematics, fleet device, ELD, or connected app.

4

Preserve remote records

Connected-car, fleet, rideshare, dispatch, and cloud systems may have retention periods separate from the physical vehicle.

5

Use a qualified protocol

Preserve the native download, tool/version information, photographs, VIN/module identity, notes, and chain of custody.

Evidence Taxonomy

Separate the vehicle evidence sources.

The first technical mistake is treating every electronic record generated by a modern vehicle as “the black box.” Different systems answer different questions.

EDR

Event Data Recorder

Crash-triggered vehicle dynamics and safety-system data intended for post-crash retrieval. Often implemented within an airbag or restraint control module.

TEL

OEM Telematics

Connected-car services may create account, vehicle-status, location, emergency-response, diagnostics, or service records depending on manufacturer, subscription, configuration, and retention.

INF

Infotainment & Navigation

Paired-device history, recent destinations, calls, contacts, navigation artifacts, and system events may exist in the head unit or related modules, subject to model-specific forensic support.

FLT

Fleet / Employer Systems

Commercial vehicles may be tracked by GPS, dispatch, asset-management, ELD, camera, maintenance, or fleet telematics systems that are independent of the OEM EDR.

APP

Vehicle & Driver Apps

OEM mobile apps, rideshare, delivery, mileage, navigation, and employer apps can create a second evidentiary trail outside the vehicle.

DTC

Diagnostic & Module Data

Diagnostic trouble codes, freeze-frame data, module states, and service records may be relevant, but they should not automatically be described as EDR data.

Federal EDR Framework

Part 563 standardizes EDRs when covered vehicles are equipped with them.

49 C.F.R. Part 563 establishes uniform requirements for specified light vehicles that have an EDR; it does not itself require every vehicle to be equipped with one. For covered vehicles, the regulation standardizes defined data elements, data format, capture, survivability, owner-manual disclosure, and commercial availability of retrieval tools.

563

Who is within the federal Part 563 framework?

Part 563 applies to specified passenger cars, multipurpose passenger vehicles, trucks, and buses manufactured on or after September 1, 2012, if equipped with an EDR, subject to the regulation’s weight and vehicle-type limits and stated exceptions.

EDR is a defined crash-data function

The federal definition focuses on dynamic time-series data recorded just before or during a crash event for later retrieval. Audio and video are not part of the Part 563 EDR definition.

Commercial retrieval tools

For vehicles equipped with a Part 563 EDR, the manufacturer must ensure that a commercially available tool can access and retrieve the data required by the regulation.

What the EDR May Record

Core EDR data elements and the 2026 phase-in.

The exact record depends on the vehicle, model year, event, and regulatory phase-in. Current Part 563 includes longitudinal delta-V and timing, vehicle-indicated speed, accelerator/throttle, service-brake status, ignition-cycle information, driver belt status, airbag-related information, event count, and complete-file status. Additional elements are required under specified conditions when recorded by the vehicle.

Category Examples Why it may matter Important limitation
Pre-crash operation Vehicle-indicated speed, accelerator/throttle, service brake Can help reconstruct driver inputs and vehicle state before time zero. Recording duration and sample rate depend on compliance phase and vehicle implementation.
Crash severity Longitudinal and, where applicable, lateral delta-V; maximum delta-V and timing Can help describe change in velocity during the crash pulse. Delta-V is not the same as pre-impact travel speed and does not alone establish fault.
Restraint system Belt status, airbag warning, deployment timing Can help evaluate safety-system state and deployment chronology. Interpretation must match the exact module and vehicle configuration.
Event integrity Event count, time between events, complete-file status, ignition cycles Can help determine whether multiple events were recorded and whether the file is complete. Power cycles and later handling should be documented rather than assumed irrelevant.
Conditional elements RPM, ABS, stability control, steering input, lateral dynamics, roll angle where recorded May add important context in some vehicles. Not every vehicle records every optional/conditional field.
Ownership & Lawful Access

The Driver Privacy Act controls access to EDR data.

The federal Driver Privacy Act of 2015 provides that EDR data are the property of the vehicle owner, or the lessee of a leased vehicle. A person other than the owner or lessee generally may not access the data unless a statutory exception applies.

Owner / lessee consent

Written, electronic, or recorded-audio consent can authorize retrieval, including for diagnosis, service, repair, or other stated purposes.

Judicial authorization

A court or other judicial or administrative authority with jurisdiction may authorize retrieval, subject to the evidentiary standards of that forum.

Specified statutory exceptions

The Act also addresses designated safety investigations, emergency medical response, and traffic-safety research under stated conditions.

Forensic Acquisition

A defensible EDR download needs a documented protocol.

  1. 01
    Document the vehicle

    VIN, year/make/model, location, condition, odometer, damage, power state, keys, and relevant modules.

  2. 02
    Define authority

    Record owner/lessee consent, stipulation, order, or other lawful basis before access.

  3. 03
    Use qualified personnel

    Match the examiner and retrieval system to the vehicle and module.

  4. 04
    Photograph before access

    Preserve exterior/interior condition, module location where relevant, connectors, and tool setup.

  5. 05
    Acquire native output

    Retain the raw/native file, generated report, tool and software version, adapters, notes, and timestamps.

  6. 06
    Do not alter the source casually

    Avoid unnecessary driving, repair, reprogramming, or module replacement before collection.

  7. 07
    Record limitations

    Note warnings, unsupported fields, incomplete events, damaged systems, power loss, or model-specific constraints.

  8. 08
    Correlate independently

    Compare EDR time-series data with video, scene evidence, vehicle damage, phone/app records, 911/CAD, witnesses, and telematics.

Preserve the source vehicle, native output, acquisition method, and interpretation as separate parts of the evidentiary foundation.

Connected Vehicle Evidence

Telematics may extend far beyond the EDR window.

A modern vehicle may communicate with OEM, fleet, emergency-response, navigation, insurance, employer, or app systems. These records can be especially important when the question concerns location, route, work use, rideshare status, vehicle assignment, diagnostics, or events outside the short EDR window.

OEM Connected Services

Remote vehicle account

Depending on manufacturer and service, records may include vehicle association, account history, remote commands, diagnostic events, emergency-response events, location-related services, or service interactions.

Fleet / Employer

Dispatch and commercial telematics

Fleet systems may preserve GPS, ignition state, route, geofence events, driver assignment, job dispatch, speed alerts, maintenance, camera events, or electronic logging data.

Infotainment

Paired phones and navigation

Some systems retain paired devices, contacts, call artifacts, recent destinations, navigation history, or other user data. Availability and extraction support are highly model-specific.

Insurance / Usage-Based Programs

Driving-behavior data

Telematics programs can create separate records concerning trips, mileage, braking, acceleration, time of day, or driving events. The source, scoring method, retention, and raw-data availability must be verified.

Interpretation

What can vehicle data actually prove?

Question Potential evidence Important limitation
How fast was the vehicle traveling shortly before time zero? EDR vehicle-indicated speed Use the applicable recording interval, sample rate, accuracy, tire/vehicle context, and report limitations. It is not automatically impact speed.
Was the accelerator being requested? Throttle / accelerator field The field describes the recorded input or request under the vehicle’s definition; it does not by itself establish intent.
Was the service brake recorded as on? EDR brake status On/off status is not a complete braking-force measurement and may not describe ABS or all braking dynamics.
How severe was the crash pulse? Delta-V and timing Delta-V is change in velocity during the event, not a direct measurement of travel speed before impact.
Was the vehicle near a location earlier? OEM/fleet/app telematics Precision, retention, timestamp source, account/vehicle attribution, and gaps must be established.
Was the driver working or dispatched? Fleet GPS, dispatch, job records, vehicle assignment Digital status is evidence of activity; legal course-and-scope conclusions depend on jurisdiction and surrounding facts.

EDR data are strongest when the engineering proposition matches the field that was actually recorded — and when the result is compared with independent evidence.

Foundation & Reliability

Authentication and interpretation

VIN and vehicle identity
Module identity and location
Owner/lessee access authority
Tool and software version
Native/raw acquisition file
Generated report preserved
Photographs and examiner notes
Chain of custody
Field definitions and warnings
Time-zero and sampling interpretation
Model-specific limitations
Correlation with independent evidence

A report printout is only one layer. Preserve enough information for another qualified person to understand what was accessed, how it was acquired, and what assumptions were used.

Practical Tools

Vehicle-evidence action tools

Vehicle Preservation Checklist

VIN, custodian, tow yard, insurer, repair/salvage status, EDR, modules, telematics, keys, photographs, and no-alteration instructions.

Open preservation checklist →

EDR Inspection Protocol

Consent/order, examiner, tool, documentation, native files, photographs, handling limitations, and post-download custody.

Open EDR inspection protocol →

Vehicle Data Source Map

Separate EDR, infotainment, OEM connected services, fleet systems, apps, ELD, cameras, and diagnostic sources.

Suggested worksheet

Telematics Request Worksheet

Define provider, vehicle/account identifier, date range, record category, custodian, retention risk, and legal process.

Suggested worksheet

EDR Report Review Sheet

Normalize time zero, pre-crash samples, delta-V, pedal/brake fields, event count, file-complete status, warnings, and model notes.

Suggested worksheet

Correlation Timeline

Align EDR samples with video, 911/CAD, phone/app events, telematics, witnesses, vehicle damage, and scene evidence.

Open master chronology →

Continue in Evidence

Correlate vehicle data with the rest of the crash record.

Evidence Home

Return to the national Evidence Library

Use the six-step framework and move among evidence sources as the record develops.

Open Evidence Home →

Crash & Scene Evidence

Compare the physical record

Match vehicle data against impact evidence, roadway geometry, photographs, police information, witnesses, and scene chronology.

Open Crash & Scene Evidence →

Cell Phone Records

Compare the digital timeline

Correlate vehicle samples and telematics with calls, messages, device/app events, location records, and carrier timestamps.

Open Cell Phone Records →

Maintenance

Keep the page current

Legal / regulatory review:
October 2, 2026

Technical-source review:
October 2, 2026

Review triggers:
Part 563 amendment, Driver Privacy Act change, new retrieval standard, or material OEM/telematics process change.

Preserve the vehicle. Identify the system. Acquire lawfully. Keep the native data. Correlate the result.

Vehicle-generated evidence can be powerful when its source, access authority, acquisition method, regulatory limits, and relationship to independent crash evidence are understood.

Back to top ↑