Documents › 61c8fcfaabe8b9b5ec965444f8f05cea6c8983dd:38-43

Ventura PD Crash Data Retrieval Report GO# VE 2019-90723

Agency records police reportcriminal case 2020-01-01 Ventura Police Department 6 pages (file pages 38–43) original file
About this document
Layer
agency record: part of a file an agency produced
Type as titled
general offense report (kind from doc_type)
Produced as
ventura-police-department/ROOT/GOVE_2019-90723_Redacted.pdf
File
61c8fcfaabe8b9b5ec965444f8f05cea6c8983dd application/pdf
Cases
agency:C-f2f6703e85 · Gabrielle Root (concern)

About: Gabrielle Root (case)

Page 1 · file page 38 larger image
Image of page 1; its text is alongside
Text: OCR figure: some text describes an image

Figure: the OCR model's description, not text on the pageVentura Police Department logo

VENTURA POLICE DEPARTMENT

GENERAL OFFENSE HARDCOPY

PRA

GO# VE 2019-90723

5401-1 TRAFFIC- HIT & RUN- NO INJURY

20-2229

Figure: the OCR model's description, not text on the pageBosch logoFigure: the OCR model's description, not text on the pageCDR CRASH DATA RETRIEVAL logo

IMPORTANT NOTICE: Robert Bosch LLC and the manufacturers whose vehicles are accessible using the CDR System urge end users to use the latest production release of the Crash Data Retrieval system software when viewing, printing or exporting any retrieved data from within the CDR program. Using the latest version of the CDR software is the best way to ensure that retrieved data has been translated using the most current information provided by the manufacturers of the vehicles supported by this product.

CDR File Information

User Entered VIN1FM5K8AR7HGC14364
UserGomez #322 / Bevan #463
Case Number19-00000
EDR Data Imaging Date01/01/2020
Crash Date01/01/2020
Filename1FM5K8AR7HGC14364_ACM 19-00000.CDRX
Saved onWednesday, January 1 2020 at 12:24:50
Imaged with CDR versionCrash Data Retrieval Tool 18.0.2
Imaged with Software Licensed to (Company Name)Ventura Police Department
Reported with CDR versionCrash Data Retrieval Tool 18.0.2
Reported with Software Licensed to (Company Name)Ventura Police Department
EDR Device TypeAirbag Control Module
ACM Adapter Detected During DownloadNo
Event(s) recoveredNone

Comments

Image Method- DTM
Power Type- Cig Lighter
Tire Size Recommended-245/55/R18
Tire Size Actual-245/55/R18
Connector- Fook108-287
Adaptor- Fook108-784
Authority- Police Vehicle Involved in incident
19-00000

Gomez #322/ Bevan #463

The retrieval of this data has been authorized by the vehicle's owner, or other legal authority such as a court order or search warrant, as indicated by the CDR tool user on Wednesday, January 1 2020 at 12:24:50.

Data Limitations

Data Imaging:

CAUTION: When imaging data directly from the RCM on a bench top, make sure the RCM is placed on a flat surface without any movement (static) while connected to and powered by the CDR interface. Not following the above guideline for bench top imaging could risk inducing new events to be recorded in the RCM and possibly overwriting a Non airbag deployment.

Note that the RCM Adapter Detected during Download parameter equal to " Yes" indicates that the EDR data was collected directly from the RCM. When equal to "No", it indicates that the EDR data was collected through the OBD II from the vehicle.

Restraints Control Module (RCM) Recorded Crash Event(s):

The RCM can store up to two crash events. Event types are categorized as follow:

    1. Non deployment trigger event is an event in which EDR recording trigger threshold is met or exceeded (minimum of 5 mph (8kph) Accumulated Delta Velocity within 150ms interval), but no device(s) have deployed. The data from such event can be overwritten by subsequent events.
    1. Airbag deployment event is an event in which frontal, side or curtain airbags have deployed. Note that such event cannot be overwritten or cleared from the Restraints Control Module (RCM). Once the RCM has deployed any airbag device(s), the RCM must be replaced.
    1. Some RCM may also categorize Non airbag deployment event. This type is an event in which non airbag devices such as pretensioners, knee bolster etc... have deployed. Note that such event can be overwritten given a subsequent "deployment" event.

"Time zero" or Event Beginning of any event (First Record or Second Record) is defined as the first Algorithm wake up during that event. So all the Pre-Crash, At Event, Delta V Data, deployment times etc... are relative to "Time zero".

It is possible that conditions in a crash may result in an incomplete event data record.

Keys: ← → or j k turn pages; / finds.