Event data recorder: what vehicle data is worth when a crash is disputed

Published August 22, 2026

A crash record from an event data recorder is worth as much as the process that moved the data out of the vehicle and into the case file, and no more. An event data recorder, or EDR, is a system designed for one purpose: to record and store the parameters of a collision and of the moments immediately before, during and after the impact. Regulation (EU) 2019/2144 makes the device mandatory across the European Union and prescribes what it has to capture, yet it attaches no evidentiary presumption to the extract a technician later pulls out of it. The regulation governs the recorder. It says nothing about the document that reaches a courtroom.

So the contested question is rarely whether the car recorded the impact. It is whether anyone outside the organization that produced the extract can verify where the data came from, whether it has changed, and when it was fixed in its current state. In the UK the same material is often called black box data, though black box insurance means a telematics unit fitted by an insurer rather than the type-approved recorder built into the car. The evidentiary problem is identical either way.

What an event data recorder actually captures in a collision

An event data recorder captures a short window around a triggering event, not a continuous history of the journey. Article 6(4)(a) of Regulation (EU) 2019/2144 sets the minimum content of that window: vehicle speed, braking, the position and tilt of the vehicle on the road, the status and activation rate of all its safety systems, the 112-based eCall system and other relevant inputs from onboard active safety systems. The same article forbids deactivation and requires a closed-loop design protected against manipulation.

The recorded parameters: speed, acceleration, position and moment of impact

Anyone reading an EDR extract for the first time expects more than the device holds.

Retrieval is constrained too. Delegated Regulation (EU) 2022/545 requires recovery through the serial port of the standardized connector and rules out wireless access. Reading an EDR is a physical operation, carried out by somebody, on a given day, on a specific vehicle.

From sensor to report: how many hands touch the data before it reaches a courtroom

Between the sensor and the exhibit there is a sequence of custody transfers, none of them documented by the recorder itself:

1. The sensor writes the event to memory inside the vehicle.
2. A technician retrieves the record through the connector or module.
3. Proprietary software decodes the raw record into readable parameters.
4. The commissioning party stores the output on its own systems.
5. Weeks or months later, a report is exported from those systems.
6. The report is filed with a claim or produced as an exhibit.

Telematics policies stretch the chain further, since the device streams to the provider’s operations center long before any extract is requested. No handover leaves a trace an outsider can inspect. It is the weakness behind any export of footage from a third-party recording system.

Why an EDR report can be challenged

An EDR report can be challenged because nothing inside the document proves anything about itself. European law does guarantee that electronic evidence will not be rejected merely for being electronic: under Regulation (EU) 910/2014, Articles 35(1) and 41(1), an electronic seal or time stamp cannot be denied legal effect and admissibility solely because it is in electronic form or does not meet the requirements for the qualified versions. Admissibility is not weight, though, and no European instrument grants a plain EDR printout a presumption of accuracy. Its weight is decided case by case, on the process behind it.

The data arrives as an extract produced by a party with an interest in the outcome

The party filing the EDR extract is almost always the party that benefits from it: the insurer commissions the retrieval, the insurer’s provider holds the database, the insurer’s systems generate the document. That is procedural position, not bad faith. But one side controls the whole evidentiary path and the other cannot test it, so opposing counsel never has to prove tampering. It is enough to observe that the extract’s link to that recorder, that date and that vehicle rests on the assertion of the party producing it.

Three questions the report does not answer: origin, integrity, time reference

All three have the same shape: the document answers with its own authority, which is exactly what the other side is contesting.

Fraud screening and the suspended settlement offer

Weak provenance costs money long before anyone reaches a hearing. When a claims file holds a technical dataset nobody can verify independently, fraud screening does what it was built to do and puts the file on hold: the settlement offer is suspended, a second inspection is requested, and a claim that could have closed in days spends months in review. The honest claimant pays for that delay exactly as the fraudulent one does.

Anonymization sharpens the problem. Because Article 6(5) of Regulation (EU) 2019/2144 bars the recorder from storing anything that identifies the vehicle or its owner, the link between a record and a claim rests entirely on the retrieval process wrapped around it. Where that process is undocumented, the most precise evidence in the file is also the easiest to attack, and an unverifiable telematics extract joins the manipulated photographic evidence insurers already face.

What makes vehicle data trustworthy

Vehicle data becomes trustworthy when three properties can be demonstrated by someone with no access to the systems that generated it: where the data came from, whether it has changed, and when it was fixed in its current state. None of the three is created by the sensor, and none can be recovered later by inspecting a PDF. They have to be attached at the point of acquisition.

Qualified timestamp and electronic seal applied at the moment of capture

eIDAS provides two instruments for this, and they are frequently confused. Under Article 41(2) of the consolidated text of Regulation (EU) 910/2014, a qualified electronic time stamp enjoys the presumption of the accuracy of the date and time it indicates and of the integrity of the data to which that date and time are bound. Under Article 35(2), a qualified electronic seal enjoys the presumption of integrity of the data and of correctness of the origin of that data. The seal belongs to a legal person and speaks to where data came from, which is precisely the question an EDR extract leaves open.

Timing separates a useful seal from a decorative one. A seal applied to a PDF six months after retrieval proves that the PDF has not changed since that moment, and nothing about the six months before it. A qualified electronic time stamp and an electronic seal applied in the instant of acquisition close that window instead of documenting it. Regulation (EU) 2024/1183 carries the logic forward, adding qualified electronic archiving to eIDAS with a presumption of integrity and correct origin for the whole preservation period.

Chain of custody and third-party verifiability

ISO/IEC 27037:2012, the international standard on the identification, collection, acquisition and preservation of digital evidence, covers vehicle systems by its own terms: its scope note states that an automotive system may include a mobile navigation system, data storage and a sensory system. Clause 6.1 addresses chain of custody, and clause 5.3 sets the four properties any handling process has to satisfy, namely auditability, repeatability, reproducibility and justifiability. An EDR retrieval documented only by the retrieving party satisfies none of them from the outside.

ISO/IEC 27042:2015 then governs analysis and interpretation, and ISO/IEC 27041:2015 the assurance that the method was fit for purpose. Together the three describe a digital chain of custody a stranger can audit, which is the practical test when an extract is contested. This is what certification at the point of capture means, and it is the approach TrueScreen applies: seal and time stamp are bound to the acquisition itself, not to a document assembled from it later.

How is a vehicle data extraction certified at the moment of capture?

Certification at the point of capture is the practice of binding a qualified electronic time stamp and an electronic seal to digital content in the instant it is acquired, so that origin, integrity and time reference travel with the content instead of being asserted about it later. TrueScreen, the Data Authenticity Platform, applies that step inside the acquisition itself: photographs, videos, screen recordings and screen captures of a telematics console or a retrieval tool output are sealed and time stamped as they are taken, then preserved. The seals and time stamps are official, internationally recognized and carry legal value across jurisdictions. What changes is not the content of the evidence but who is able to check it, since a third party can verify the date and integrity of each item without access to the systems that produced it. The platform covers capture from mobile, desktop and web, and the same primitives are available through API for organizations certifying inside their own claims systems.

Picture a loss adjuster inspecting a vehicle the day after a rear-end collision. She photographs the damage, records the position of the vehicle and captures the readout of the retrieval tool, and each acquisition is sealed and time stamped at the moment of the shot rather than when the file is closed. Eight months later the other side argues that the damage is inconsistent with the declared impact, and the file holds evidence whose date and integrity a third party can confirm without querying the insurer’s systems. None of this removes judicial discretion, since any evidence can be challenged on its probative value, but the burden of argument moves onto the party contesting the record. TrueScreen documents the workflow in its certified car accident report and insurance claims certification use cases, part of its work in the insurance sector.

Two typical situations: the disputed rear-end collision and the fleet that must prove delivery times

Take the disputed rear-end collision first. Two drivers describe the same impact in incompatible terms, and the insurer retrieves an event data recorder output supporting its position on speed and braking. The other side does not dispute the physics, it disputes the paperwork: the extract was produced by the insurer, on the insurer’s equipment, on a date recorded by the insurer. Where the accompanying field inspection was certified at the point of capture, the photographs and the screen capture of the retrieval tool carry independent time stamps and seals, and the argument goes back to the physics.

The fleet case is the same problem without a collision. A logistics operator asked to demonstrate departure times, routes and stops to a client or a regulator can answer with telematics, but the answer comes from its own platform. Organizations in this position use TrueScreen to certify extractions and field evidence as they are produced, so the record is verifiable by the counterparty rather than merely asserted. Categories M2, M3, N2 and N3 face type approval requirements from 7 January 2026 under Delegated Regulation (EU) 2024/2220, so the question is about to reach every fleet in Europe.

FAQ: event data recorder and evidentiary value

Is event data recorder data admissible as evidence in court?
+

Event data recorder data is generally admissible in European proceedings, but admissibility is not evidentiary weight. Regulation (EU) 910/2014 provides that electronic evidence cannot be denied legal effect solely because it is electronic, while no European instrument grants a plain EDR extract a presumption of accuracy. Its weight depends on how the data was acquired, sealed and preserved.

Which vehicles must have an event data recorder in the European Union?
+

Under Regulation (EU) 2019/2144 and its Annex II, cars and light commercial vehicles in categories M1 and N1 needed an event data recorder for new vehicle types from 6 July 2022 and for all newly registered vehicles from 7 July 2024. Buses and trucks in categories M2, M3, N2 and N3 follow, with new types from 7 January 2026 and new registrations from 7 January 2029.

What does an event data recorder record?
+

Article 6(4)(a) of Regulation (EU) 2019/2144 requires an event data recorder to capture at least vehicle speed, braking, the position and tilt of the vehicle on the road, the status and activation rate of all safety systems, the 112-based eCall system and other relevant inputs from active safety systems, for the period immediately before, during and immediately after a collision.

Who can access event data recorder data?
+

Delegated Regulation (EU) 2022/545 requires retrieval through the serial port of the standardized connector, or a direct connection to the recorder when that port is unusable after a collision, and rules out wireless access. Regulation (EU) 2019/2144 lets national authorities obtain the data for accident research and analysis, subject to data protection law.

How can an EDR report be challenged?
+

An EDR report is usually challenged on its provenance rather than its physics, since the extract is produced by a party to the dispute, on its own systems, with a date generated by those systems. That line of attack can be addressed with TrueScreen, which seals and time stamps each acquisition as it is captured, so origin, integrity and time reference can be verified independently.