Start hereprofessional & technical guide

What professional users can obtain

• Field retrieval through the CrashScan mobile workflow on supported vehicles.
• Contextual EDR report organized for rapid technical review.
• Raw / discoverable evidence outputs on request where applicable.
• Engineering support for vehicle-specific questions, report interpretation and troubleshooting.
• Direct-to-module and specialist processing routes for damaged, inaccessible or removed modules.
• Training, OEM interpretation material, validation studies, legal resources and expert-witness support through the Master Resources library.

Common data categories

• Event chronology and event type, including deployment and non-deployment records where supported.
• Pre-crash vehicle data such as indicated speed, brake status, accelerator/throttle input, engine speed, steering and other driver/vehicle state parameters.
• Crash-severity information, including longitudinal and/or lateral delta-V or acceleration-derived information where recorded.
• Restraint and occupant information such as buckle status, deployment commands and occupant classifications where supported.
• Ignition/key-cycle, odometer, date/time or other recency indicators on certain platforms.
• Additional diagnostic or vehicle-state data when the applicable vehicle architecture supports it.

Jaguar Land Rover and international coverage

For Jaguar Land Rover, CrashScan uses the manufacturer's EDR process. Other tools may return JLR data through a Chinese Universal Data Record (UDR) process; those are different retrieval paths and can produce different outputs when a China-market process is applied to a vehicle sold elsewhere. The professional question is therefore not whether a competing report exists, but which process was run, for which market, and what the resulting data actually represents.

For some international Ford, Mazda, Hyundai, Kia and GM applications, support and access can differ from North-American-only tool coverage. Confirm the exact VIN, module and market rather than assuming that a domestic support chart applies internationally.

Contextual information

Depending on the vehicle and report, contextual reporting may organize event order, severity, direction, pre-crash driver inputs, calculated or derived quantities, diagnostic information and clearly defined loss indicators. Inferential indicators should remain qualified and tied to their underlying data definition; they are not substitutes for an expert's ultimate opinion on fraud, liability or causation.

Limited preview availability

In selected international markets and approved trial programs, Collision Sciences may provide limited preliminary information following a successful acquisition. Preview availability, content and timing vary by vehicle, market and program and should not be relied upon as the final evidentiary result. The completed CrashScan report and associated source data, following applicable processing and quality review, remain the authoritative deliverables.

Sample report views

Crash event summary

Example contextual presentation of event sequence, severity, delta-V and related event information.

Pre-crash data table

Example presentation of recorded vehicle-state data before an event. Available parameters vary by vehicle and event.

Example CrashScan report / acquisition result screen

For technical, claims or litigation use, derived values should be checked against the original recorded parameters, units, sampling intervals, coordinate/sign conventions and any OEM limitations before they are relied upon as reconstruction or evidentiary conclusions.

Recommended integrity controls for litigation work

• Preserve the CrashScan report, report/case identifier, VIN and scan date/time.
• Retain raw/discoverable output where the assignment requires independent review or production.
• Preserve screenshots, connection photographs and any warnings or vehicle-specific limitations shown during acquisition.
• Compare the retrieved event structure and recorded parameters with the vehicle, physical evidence and case circumstances before relying on them.
• If acquisition integrity is specifically challenged, request engineering review and consider a repeat acquisition or independent comparison where the vehicle/module condition and applicable process make that appropriate.
• Do not treat a completed scan with “No Crash Data” or a missing parameter as an automatic acquisition failure; evaluate event thresholds, power state, OEM recording logic and report limitations.

Authorization

In the United States, the Driver Privacy Act of 2015, enacted as part of the FAST Act, establishes EDR data as the property of the vehicle owner or lessee and restricts access by others except in defined circumstances, which include owner/lessee consent, certain court or administrative orders, specified NTSB/DOT investigations, emergency medical response and anonymized traffic-safety research. State law may add requirements. Investigators should confirm the law that applies to the assignment and preserve the authorization basis.

Chain of custody

For a removed module, document who removed it, when and from which vehicle; label the module with the vehicle identifier; photograph its condition and connectors; record each transfer; and use the Collision Sciences evidence-tracking form when shipping the module for processing.

Admissibility

EDR evidence has been accepted by courts since the 1990s, but admissibility is not automatic. It depends on the jurisdiction, applicable evidentiary rules, authentication, the foundation for the retrieval and interpretation, expert qualifications, and the facts of the case. Collision Sciences maintains separate legal and evidentiary resources for counsel and experts.

Insurer / SIU application

For insurers and SIU investigators, the same underlying EDR evidence can help test reported loss circumstances, identify inconsistencies that merit further investigation, prioritize files for specialist review, and document objective vehicle-state information. Examples can include recorded speed, brake status, accelerator input, steering, event chronology, restraint data, diagnostic information and other available vehicle-state parameters. The significance of any indicator depends on the OEM definition, vehicle condition, event timing and the remaining case evidence.

Reconstruction / forensic application

For reconstruction experts and forensic engineers, CrashScan provides a practical acquisition route together with source data, contextual organization, OEM interpretation resources, validation material, advanced module-processing options and expert support. The original EDR data remains the technical foundation; reconstruction conclusions should integrate it with scene evidence, vehicle damage, measurements, witness information and applicable scientific methods.

Reconstruction software integration

CrashScan/EDR data can be imported into PC-Crash and Analyzer Pro workflows to reduce manual transcription and support comparison of recorded speed, delta-V and other EDR-derived values with trajectories, scene evidence and reconstruction hypotheses. Integration does not replace source-data review: verify units, time base, coordinate/sign convention and the original EDR evidence before using values in a simulation or calculation.