As a California personal injury attorney, I’ve watched the way we prove what actually happened in a car or motorcycle crash change dramatically over the past decade. Skid marks, eyewitness memory, and the officer’s best guess used to be the backbone of accident reconstruction. Today, one of the most powerful tools in my toolkit sits quietly inside the vehicle itself: the Event Data Recorder, or EDR.
If you’ve been in a serious crash, there’s a good chance your car — or the car that hit you — was already telling the story before your lawyer ever got involved. And most modern motorcycles have EDRs as well.
Most people know the aviation version of this technology as the “black box.” Cars have their own version, built into the airbag control module of nearly every vehicle manufactured after 2013 (and many earlier models too). The EDR continuously monitors a rolling window of vehicle data and, when it detects a crash-like event — a sudden deceleration, an airbag deployment, a specific change in velocity — it locks in and preserves a snapshot of what the vehicle was doing in the seconds before, during, and sometimes after the impact.
Depending on the make and model, that snapshot can include:
This is objective, machine-recorded data. It doesn’t get nervous on the stand, doesn’t misremember details six months after the fact, and doesn’t have a stake in the outcome of the case.
Liability disputes in car or motorcycle crash cases often come down to a battle of narratives. The other driver says they had a green light. My client says otherwise. The other driver says they weren’t speeding. My client’s medical bills and totaled vehicle suggest otherwise.
EDR data cuts through a lot of that noise. If the defendant’s own vehicle recorded that they were traveling 61 mph in a 35 mph zone with zero brake application in the final 2.5 seconds before impact, that’s not something a skilled defense attorney can easily argue away. I’ve had cases where the insurance company was prepared to fight liability hard — until we obtained the EDR download and the conversation changed within days. Our office just resolved a case where the offending driver said he was traveling within the speed limit; however, the EDR said that he was driving at 70 miles per hour, with no braking in the seconds before he rear-ended our client’s stopped car.
That kind of objective evidence sticks like Velcro to the minds of anyone evaluating a plaintiff’s case, both as proof of fault and also as proof of the severity of the injury sustained. It also works in reverse, and I say this because it matters for credibility with insurers, judges, and juries alike: EDR data can also protect defendants and even plaintiffs from inflated claims. If a plaintiff attorney tries to argue a client was rear-ended at high speed, causing catastrophic injury, but the EDR shows a delta-V of 4 mph, that data will surface — through defense discovery if not through us.
Being straightforward about what the data shows, good or bad, is part of maintaining credibility in every case we handle.
Here’s the part that keeps me up at night on new cases: EDR data isn’t permanent. Most modules only store a limited number of crash events before older data can be overwritten, and vehicles get repaired, totaled, sold, or scrapped — sometimes within days of a collision. If the vehicle goes to a salvage yard or gets crushed before anyone thinks to pull the module, that evidence is gone forever.
This is why sending a spoliation letter — a formal notice to preserve evidence — is one of the very first things we do when we take on a serious crash case. I want the vehicle preserved and the EDR downloaded before the insurance company’s total-loss process runs its course. When a client comes to my office within days of a wreck, one of my first questions is simple: where is the vehicle right now, and who has access to it?
Pulling EDR data isn’t something I do myself, and it isn’t something any attorney should attempt without proper training. The standard tool in the industry is the Bosch Crash Data Retrieval (CDR) system, which connects either directly to the airbag control module or through the vehicle’s diagnostic port. This work is typically handled by:
I retain a qualified reconstructionist early in cases where liability is contested, or injuries are severe, because the download itself has to be done correctly and documented carefully to survive a foundational challenge later if the case goes to trial.
California was actually ahead of the curve on this issue. Vehicle Code Section 9951 specifically addresses EDR data, and generally requires that a vehicle owner consent before EDR data can be retrieved and used — except in certain circumstances, such as pursuant to a court order, a valid warrant, or when the data is being retrieved for purposes of determining the need for or facilitating emergency medical response.
In practice, this means that in litigation, we typically need either the owner’s consent or a subpoena/court order to access data from a vehicle we don’t control. If it’s my client’s own vehicle, that consent piece is usually simple. If it’s the defendant’s vehicle, we often need to move through formal discovery, and timing matters enormously given how quickly vehicles get repaired or disposed of after a crash.
Once we have the download, the data doesn’t just sit in a file — it becomes part of building the case:
Reconstructing the sequence of events. Combined with the police report, photographs, roadway measurements, and sometimes nearby surveillance or dashcam footage, EDR data lets a reconstructionist build a scientifically defensible timeline of the collision.
Corroborating or contradicting witness statements. When a driver tells the officer at the scene “I was barely going 30,” but the EDR shows 52 mph with no braking, that gap becomes powerful cross-examination material. I have one case now where the reporting officer had the defendant’s EDR examined by a specialist as part of the preparation of the traffic collision report. Although the defendant told the officer that he was only doing 40 mph, the EDR data revealed that this driver was moving at 128 mph on the streets of Fremont right before he struck and permanently injured my client.
Establishing comparative fault. California follows a pure comparative negligence system, meaning a plaintiff’s recovery can be reduced by their own percentage of fault. Precise speed and braking data can be the difference between a defendant being found 100% at fault versus a jury assigning some percentage of fault to my client — which directly affects the value of the case. And with motorcycle cases, the defendant always says my motorcyclist client was speeding. That EDR data could well be the missing witness we need to combat the allegation of speeding against my biker client.
Supporting or challenging injury causation. Delta-V and crash severity data can help correlate the mechanism of injury with the forces involved, which matters when insurance companies try to argue that a low-speed impact “couldn’t possibly” have caused the injuries a client is reporting.
I want to be honest about this technology rather than oversell it. EDR data has real limitations:
I never present EDR data as the whole story. It’s one powerful piece of a larger reconstruction that includes physical evidence, medical records, and human testimony.
If you’ve been injured in a collision in California, here’s my practical advice:
Technology has fundamentally changed how car accident cases get proven in California courtrooms. As someone who represents injured people for a living, I’d rather have a dashboard full of hard data backing up my client’s account than rely solely on memory and mangled metal. It levels a playing field that, for a long time, favored whichever side could tell the more convincing story — rather than whichever side was actually right. You can contact Choulos, Choulos & Wyle at (415) 432-7290.
This post is for general informational purposes only and does not constitute legal advice. If you’ve been injured in an accident, consult a licensed California attorney about the specific facts of your case.
