Event data recorders are no longer a frontier topic in auto-accident practice. They are routine, and the discipline of pulling clean data has moved into the same checklist territory as preserving 911 audio or subpoenaing cell records. What changed in 2026 is the regulatory backdrop. NHTSA published a final rule on May 18 that delays the expanded pre-crash data capture mandate to a phased compliance window beginning September 1, 2028, with the rule itself effective June 17. The practical effect is that vehicles on the road today still operate under the older 15-element data set for most makes, with manufacturer-specific extensions for ADAS-equipped models. If you assumed the bigger pre-crash window was already standard, recalibrate the spoliation letter.
The preservation problem has not improved
EDR data is volatile. Many modules overwrite a non-deploy event the next time the ignition cycles through a similar threshold, and a totaled vehicle that sits at a salvage yard for thirty days can lose its evidence to a buyer's tow, a battery disconnect, or a routine inspection. Send the preservation letter the same week as the loss, addressed to the registered owner, the insurer, and the salvage yard if the vehicle was already towed. The letter should identify the VIN, demand that the airbag control module remain in place, prohibit ignition cycles, and put the recipient on notice that the carrier's insured may face spoliation sanctions if the module is damaged or downloaded by a non-qualified technician.
If the vehicle is in the defendant's possession, layer a Rule 34 inspection request on top of the preservation letter. Specify that the inspection will use a Bosch CDR tool, name the operator, and reserve the right to image the module with the defense expert present. For ADAS-equipped vehicles, expand the request to the forward-camera module, the radar control unit, and any cellular-connected telematics service the OEM offers under brand names like OnStar, BlueLink, or Uconnect.
Authentication after the carve-out
The doctrinal question for 2026 is no longer whether EDR data is admissible. It is whether the proponent can authenticate the chain from module to printout. Defense experts increasingly attack the chain on three pressure points. First, the imaging tool itself: was the CDR software version current and certified for the model year? Second, the cable and adapter: did the operator use the OEM-specified DLC connector or a generic substitute that may have altered metadata? Third, the post-image handling: was the .cdrx file hashed at the moment of capture, and does the production copy match the hash?
Build the foundation by deposing the imaging technician with the manufacturer's own service bulletin in hand. Confirm the software version, the cable serial number if relevant, and the sequence of steps. If the technician printed a hash on the cover page of the report, mark that exhibit at the deposition and ask the technician to confirm it matches the file you produce at trial. This is the same routine a cell-site analyst follows for call detail records, and it carries the same evidentiary weight when done correctly.
ADAS data is the new fault accelerant
Most 2024-and-newer vehicles carry forward-camera and radar modules that retain video clips, target-track logs, and alert histories independently of the EDR. The data does not live in the airbag control module, and a CDR pull will miss it. The OEM service tool, used by a manufacturer-affiliated technician, is the path. For plaintiffs in low-impact-defense cases, an alert history showing a forward-collision warning fire two seconds before impact often resolves the disputed-speed argument before the defense has time to retain a reconstructionist. Coverage of recent appellate decisions on EDR and ADAS admissibility shows trial courts increasingly granting motions in limine to exclude defense expert reconstruction that contradicts the OEM-pulled data.
Telematics, at the right altitude
Connected-vehicle telematics is its own deposition target. The OEM cloud retains GPS breadcrumbs, hard-braking events, and ignition logs, often for ninety days or longer, but the data is held by the OEM, not the owner. A subpoena to the manufacturer is the route, and the response time on those subpoenas has stretched into the four-to-six-month range as legal departments triage volume. Send the subpoena the week you confirm the vehicle is connected-services enabled, not the month before trial. For commercial-vehicle work, the same principles apply on the ELD side, where trucking practitioners have been litigating data preservation for years.
The defense playbook
Defense counsel has gotten better at attacking EDR foundation in the past two years. The most common arguments to expect:
- The module was damaged in the crash and the data is internally inconsistent.
- The CDR software was not certified for that VIN and the values are extrapolated.
- The vehicle was driven post-impact, contaminating the rolling buffer.
- The technician's qualifications fall short of the Daubert reliability factors.
Each of these is a fact-driven dispute the plaintiff can win on direct examination if the preservation chain was clean. The losing scenario is the one in which the plaintiff's expert is the first witness ever to touch the module, with no documented chain of custody from the date of loss. The cure is the boring documentation, in real time, on day one.
Where this lands for your file rotation
For practitioners running auto files at volume, the preservation letter and the inspection request should be templated and triggered by intake, not by the lawyer's calendar. Track which vehicles have connected services enabled, log the subpoena issue date, and calendar the OEM's typical response window. Firms that have moved EDR and telematics workflow into case management automation are turning around cleaner foundational records and pushing carriers into earlier reserve decisions. The science of the data has not changed. The operational discipline around capturing it has.