What Cars Can’t Say, the Data Will: The Value of Objective Analysis in Accident Reconstruction

When I walk into a joint vehicle inspection, everyone has a story.

“I slammed on the brakes, but the car would not stop”
“The steering locked up.”
“My car was hit in the rear causing it to go forward and hit the car in front.”

Sometimes it’s honest confusion. Other times, not so much.

Working in Los Angeles brings a high volume of cases—not just because of the traffic, but also because of the fraud. I’ve seen it all:

• Pre-damaged vehicles insured as pristine.
• Drivers claiming theft, only to have their own phone data prove they were behind the wheel.
• Staged accidents, phantom vehicles, and recycled claims from the same bad actors.

As an accident reconstructionist, my job is to cut through that fog and deliver one thing: objective analysis. And that starts with pulling data from the vehicle itself. Tools like crash data retrieval kits are incredibly helpful in separating fact from fiction.

What the Vehicle Tells Us (If You Know Where to Look)

Most people don’t realize the car they drive every day is already tracking a surprising amount of information. Embedded inside is something called an event data recorder (EDR)—basically a black box. In the event of a crash, it stores key moments: speed, throttle, brake application, steering inputs, and more.

This isn’t new technology, but it’s still underutilized by people unfamiliar with the value of the data. As a mechanical engineer, I don’t just download this data—I combine it with physical inspection of the vehicle to create a clear, defensible picture of what actually happened. I want to know: Do the digital records and vehicle condition line up with the statement the vehicle driver provided? That’s where real insight happens.

When Brakes Fail—or Don’t

One of the most common claims I hear is brake failure. Sometimes it’s true—brakes do fail. Other times, it’s what’s known as pedal confusion—a driver mistakenly presses the accelerator, thinking it’s the brake. I’ve seen it happen more than you'd think, and the results can be tragic.

In one case involving a Tesla in Los Angeles, the driver insisted the car accelerated on its own. But when I downloaded the EDR data? It showed 94% throttle and 0% brake. That wasn't a mechanical issue, it was human error. That data was critical in protecting the insurer from a wrongful claim.

The Process: More Than Just a Plug-In

People sometimes imagine my job as plugging a laptop into a car and letting it spit out the answer. But the process is far more involved:

• Vehicle data download. I connect to the car’s OBD-II port and extract the crash data.
• Review supporting documents. Examine driver statements, vehicle damage estimates, and scene photographs.
• Physical inspection. I photograph the vehicle from every angle, document crush patterns, and may remove components for mechanical inspection with prior consent.
• Scene review. If possible, I visit the crash site, though often by the time I’m called in, any markings or physical evidence have disappeared.
• Report synthesis. The final product includes photos, data interpretations, and, when needed, expert testimony.

It’s a mix of engineering know-how and detailed investigative work to determine causation for the event.

From Big Rigs to Burnouts: Every Case Is Different

While much of my work is on passenger vehicles, I also inspect commercial vehicles—what I call the “big rigs.” These vehicles carry massive insurance policies, which often lead to claims where the stakes are high. In those cases, I may be called out just to preserve the data, even before a formal claim is filed.

Other cases involve a claim that two vehicles collided, resulting in damage and occupant injuries. However, vehicle inspections—and in some instances, laboratory analysis of paint samples—can show that the contact between vehicles was not consistent with the reported collision.

Accidents are messy. Stories conflict. Details get lost. But the vehicle? It usually remembers everything.

I’ve spent decades working on vehicles—from RVs to passenger cars to manufacturing transmissions at Daimler-Chrysler. That hands-on mechanical experience gives me an edge many reconstructionists don’t have. While others may rely heavily on software, I also understand the hardware. That balance, between mechanical fundamentals and digital insight, is where the truth usually lives.

Whether it’s a fraud case, a disputed liability claim, or a potential defect, I approach each assignment the same way: gather every scrap of evidence, evaluate it objectively, and deliver a report that helps the client make a clear, confident decision.

About the Author

Paul Saedler, P.E., ACTAR, is a mechanical engineer and accident reconstructionist at EDT Engineers. With over two decades of hands-on experience in vehicle systems, manufacturing, and forensic consulting, Paul specializes in delivering objective, data-driven analysis in complex motor vehicle cases.