Seat-Belt and Event Data After a California Crash: What to Preserve

This guide is for a California vehicle owner, injured occupant, family member, or authorized representative trying to preserve seat-belt and crash-event evidence after a collision. It gives a practical workflow for identifying the vehicle, documenting the physical restraint system, separating diagnostic records from event data, confirming lawful access, and preserving the acquisition record.

It does not decide whether a belt was worn, whether a pretensioner should have fired, whether a restraint failed, how fast a vehicle was traveling, who caused the crash, whether an injury was caused by a particular mechanism, or what a claim is worth. Those questions may require vehicle-specific engineering, medical evidence, qualified analysis, and other sources. The seat-belt failure service guide explains the possible legal lane; this article is the narrower evidence-preservation task.

Address medical care and immediate safety first. Do not enter an unsafe vehicle, reconnect damaged electrical systems, drive a vehicle that should not be driven, test a restraint on a person, cut webbing, pull trim, dismantle a retractor, energize a pretensioner, or attempt a module download without appropriate training and authority. If a tow yard, repair shop, insurer, or salvage operator has the vehicle, send a narrow written preservation request promptly and keep delivery proof.

Start with the exact vehicle rather than a general description. Record the year, make, model, trim, body style, registered owner, current custodian, tow or stock number, and the private VIN. Photograph the VIN plate and certification label for the private file, but redact the VIN from anything public. Record the collision date, approximate time, each impact, whether any air bag deployed, whether the vehicle was driven or towed, and every place the vehicle has been stored.

Ask the current custodian not to repair, scan, clear codes, cycle ignition unnecessarily, disconnect or replace modules, remove seats or trim, cut belts, replace restraint parts, scrap, auction, crush, or release the vehicle until preservation and inspection arrangements are resolved. This is a preservation request, not a declaration that every listed act would destroy evidence. Record what had already happened before the request and who supplied that information.

The tow and storage record guide explains how to track release authority, photographs, inventory, access, and custody. The repair-estimate guide helps separate preliminary estimates, supplements, authorizations, invoices, parts, photographs, scans, and total-loss records. Preserve those source families before they are compressed into one insurer or shop summary.

Photograph the full occupant position from several angles. Then document the belt webbing from upper anchor to lower anchor; D-ring or height adjuster; latch plate; buckle and buckle stalk; retractor area; anchor bolts; seat track; seat position; surrounding trim; air bags; and any visible pretensioner-related component that can be photographed without disassembly. Include wide context images and close details with consistent file names.

Record condition without diagnosing it: “webbing folded near latch plate,” “buckle button returned when pressed,” “upper anchor trim displaced,” or “retractor function not tested.” Avoid “belt failed,” “pretensioner did not fire,” or “occupant was unbelted” unless a qualified source supports that conclusion. A photograph shows a post-crash condition at a particular time; it does not automatically reconstruct the pre-crash state or explain how an injury occurred.

Keep each seating position separate. Driver and front-passenger EDR fields, belt hardware, air bags, pretensioners, and occupant classifications can differ. Do not infer rear-seat information from a front-seat field. If an occupant moved after impact, first responders cut a belt, a rescuer changed a seat, or a custodian handled components, record that event and its source rather than attempting to recreate the original position.

Use the car accident checklist for scene photographs, witnesses, police information, and fast-changing facts. Use the broader injury evidence checklist to connect the vehicle file with medical, communication, insurance, and loss records without mixing those sources.

The federal December 2024 Part 563 final rule describes EDRs as vehicle devices that capture technical information immediately before and during a crash about vehicle-system status and operation. Depending on the vehicle and event, fields may concern pre-crash dynamics, driver inputs, crash severity, restraint use or deployment, and automatic collision notification. It is crash-event data, not a substitute for the complete scene, vehicle, witness, and medical record.

The federal December 2024 Part 563 final rule explains that Part 563 is an “if equipped” standard for covered light vehicles; it standardizes core data, format, retrievability, and survivability when a covered vehicle has an EDR. It does not mean every vehicle has the same module, every collision creates a stored event, every possible field is recorded, or every report will be complete.

Core Part 563 fields include items such as longitudinal change in velocity, indicated speed, accelerator or throttle, service brake, driver safety-belt status, air-bag warning and deployment information, event count, time between events, and whether the complete file was recorded. Other fields—including some lateral, steering, stability-control, right-front-passenger, side-air-bag, and pretensioner information—depend on whether the vehicle records or is equipped for them. Preserve “not recorded,” “not supported,” “not applicable,” and “no event found” as different report outcomes.

The same 2024 rule expanded certain pre-crash capture requirements from five seconds at two samples per second to twenty seconds at ten samples per second. The later May 2026 final rule moved that expansion into a phase-in beginning September 1, 2028, reaching general full compliance for EDR-equipped applicable vehicles on and after September 1, 2031, with later dates for specified small-volume, limited-line, altered, and multi-stage vehicles. For a crash today, never assume the report has twenty seconds of data; identify the vehicle and read the actual output.

California Vehicle Code section 9951 requires an owner-manual disclosure for covered manufacturer-installed recording devices and defines covered functions to include speed or direction, travel history, steering, braking, driver-seat-belt status, and crash transmission. For vehicles within the statute, subdivision (c) generally bars retrieval by someone other than the registered owner unless an identified exception applies.

The statutory routes include registered-owner consent; a court order; specified safety or medical research without disclosing owner or driver identity; and retrieval by a licensed new-motor-vehicle dealer or automotive technician for diagnosis, service, or repair. The section separately addresses subscription-service recording or transmission disclosures. It applies to motor vehicles manufactured on or after July 1, 2004.

Do not convert those categories into blanket permission. Identify the registered owner from current records, the person requesting access, the legal basis being used, the vehicle custodian, the technician or examiner, and the scope of the proposed work. A repair-diagnosis exception is not automatically an evidence-distribution agreement. A subscription provider’s data is not automatically the same as the on-vehicle EDR. If ownership, consent, insurer authority, police custody, court process, rental status, or a deceased owner creates uncertainty, obtain case-specific advice before retrieval.

A practical request can say: “Please preserve the vehicle and restraint modules without scan, clearing, repair, replacement, sale, or disposal. Before any download, please identify the registered owner, proposed examiner, tool and software, module, access authority, scope, date, and deliverables. This request does not authorize alteration or waive objections.” Keep the request, delivery record, response, consent or order, and final scope together.

Layer 1—physical restraint: webbing, latch plate, buckle, retractor, anchors, pretensioner hardware, seat, trim, and air bags. It can document visible post-crash condition and location. It cannot by itself prove pre-crash use, deployment timing, causation, or fault. Preserve photographs, measurements by a qualified person, components, and custody.

Layer 2—diagnostic and repair records: diagnostic trouble codes, pre-scan, post-scan, module identification, calibration, repair procedure, parts, and technician notes. They can show what a system reported or what work occurred at a stated time. They are not automatically a crash-event record and may change as the vehicle is powered, scanned, repaired, or cleared. Preserve native and rendered outputs plus tool, software, operator, time, and vehicle identity.

Layer 3—EDR event output: event status, ignition cycles, speed or pedal samples, change in velocity, belt status, air-bag or pretensioner fields, and report limitations actually produced for the vehicle. It can preserve recorded system data around a qualifying event. It does not identify a person, diagnose an injury, prove the sensor was physically correct, or decide legal responsibility. Preserve the native file, full report, export, photographs of setup, acquisition notes, and hash.

The same official Part 563 rule explains that EDR requirements are intended to support effective crash investigation and analysis of safety-equipment performance. That is the right model for a private evidence file too: compare physical, electronic, scene, witness, and medical sources and document conflicts; do not elevate one field above the entire record.

Before download, create one ledger entry with these fields:

• Authority: registered owner, written consent, court order, or other identified statutory basis; scope and date.
• Vehicle identity: year, make, model, trim, VIN in the private file, mileage or odometer source, tow or stock number, custodian, and storage location.
• System identity: module name, module part number if obtained, physical location, and whether acquisition uses the vehicle connector, direct-to-module method, or another documented method.
• Acquisition identity: examiner, organization, date, start and end time, tool make and model, adapter or cable, software and data version, power source, and photographs before and after.
• Vehicle state: battery condition, ignition state, prior scans, repairs, module replacement, air-bag deployment, tow handling, and known power cycles.
• Result: event found or not found, locked or unlocked status if reported, event count, event type, ignition cycles, complete-file status, supported and unsupported fields, warnings, and errors.
• Deliverables: native acquisition file, unedited full report, PDF or print rendering, screen captures only when needed, notes, exported data, checksums, copies supplied, and storage location.
• Custody: who possessed the vehicle and files before, during, and after acquisition; every transfer; read-only master; working copy; and final component disposition.

Example: “Vehicle identified from VIN plate and registration; registered owner consent dated July 28 limited to EDR imaging. Vehicle stored at named facility; no repair authorized. Examiner photographed connector, module context, odometer display, and tool setup. Tool and software versions logged. One report exported; native file and PDF hashed and copied to read-only storage. Report listed driver-belt status and frontal-air-bag fields, marked right-front pretensioner field not recorded, and contained a completeness flag. No interpretation of occupant identity, sensor accuracy, fault, or injury mechanism entered in acquisition ledger.”

• Private VIN, registration, year, make, model, trim, body style, custodian, tow or stock number, storage locations, and key dates.
• Written hold request and proof sent to tow yard, repair shop, insurer, owner, lessor, salvage operator, or other relevant custodian.
• Wide and close photographs for each seating position, belt path, webbing, latch plate, buckle, retractor area, anchors, seat, trim, air bags, and visible damage.
• Police information, scene originals, tow inventory, access log, estimate versions, pre-scan, post-scan, technician notes, repair procedures, invoices, parts, and total-loss records.
• Registered-owner identity, consent or court order, examiner, scope, tool, software, adapter, module, acquisition method, power state, and photographs.
• Native EDR file, unedited full report, rendered copy, supported and unsupported fields, warnings, event classification, ignition cycles, and complete-file status.
• SHA-256 or equivalent hashes for preserved electronic masters; read-only master location; working-copy location; copy and transfer log.
• Medical records and qualified medical opinions kept in a separate lane from vehicle data and restraint condition.
• Conflicts ledger linking each disputed statement to its exact source, time, author or system, and unresolved question.

The digital evidence guide explains original files, metadata, exports, hashes, and working copies. The California injury proof guide shows how to connect these records with duty, event, causation, harm, and loss without claiming that one source proves every element.

1. Handle safety and care. Do not delay emergency response or medically appropriate evaluation to gather evidence.
2. Locate and hold the vehicle. Identify the current custodian and send a precise preservation request with delivery proof.
3. Photograph before alteration. Capture vehicle identity, every relevant seating position, restraint components, air bags, damage, and existing changes.
4. Collect custody and repair sources. Get tow, access, scan, estimate, parts, repair, release, and total-loss records.
5. Confirm access authority. Identify the registered owner and exact statutory or court-authorized route before retrieval.
6. Set the acquisition protocol. Agree on examiner, scope, tool, module, power state, observers, photographs, native files, report, hashes, and component handling.
7. Acquire once, preserve fully. Keep the read-only native master and full output; analyze a copy.
8. Reconcile sources. Compare physical inspection, diagnostic records, EDR output, scene evidence, witness accounts, and medical evidence without forcing agreement.
9. Track other deadlines separately. A preservation request or planned inspection does not extend insurance, court, public-entity, discovery, or other deadlines.

• Waiting until after repair or salvage transfer: module, belt, trim, battery, and access history may change.
• Authorizing a general scan: define whether the task is diagnosis, EDR acquisition, or both, and preserve every output.
• Assuming an EDR exists: check the exact vehicle, owner’s manual, module support, and actual acquisition result.
• Assuming every crash creates a report: event thresholds, memory, crash type, module condition, and vehicle design can affect availability.
• Assuming today’s rule means twenty seconds in today’s vehicle: the expanded federal capture requirements phase in later; read the actual report.
• Equating belt status with occupant identity: a system field does not name the occupant or automatically validate every sensor and physical fact.
• Reading “not recorded” as “did not happen”: unsupported, unavailable, not applicable, error, no event, and recorded-no are different outcomes.
• Keeping only a PDF: preserve the native acquisition file, full unedited report, tool and software details, setup photographs, and hash.
• Letting one expert keep the only copy: maintain an owner-controlled read-only master and a documented copy log.
• Publishing private identifiers: keep VIN, registration, precise location, medical details, and access documents in the private file.

1. Confirm where the vehicle is and send a narrow written hold request.
2. Build the vehicle, custody, impact, repair, scan, and restraint-system identity record.
3. Photograph every relevant seating position and component before alteration.
4. Identify the registered owner and the lawful access basis before any download.
5. Use a written acquisition protocol and require native data, full report, photographs, tool details, and hashes.
6. Keep physical, diagnostic, EDR, scene, witness, and medical sources separate, then reconcile them in a conflicts ledger.
7. If the vehicle is about to be repaired, released, sold, auctioned, scrapped, or crushed—or if ownership, consent, court process, product condition, or serious injury is disputed—seek qualified advice promptly.

Hurt Advice is a lawyer-referral and legal-information service, not a law firm. You may use the contact page to request an intake review. Any attorney-client relationship requires a separate written agreement with a participating attorney, and no outcome is promised.