Skip to main content

Commercial vehicles · evidence holders

Preserve the right system through the right record source

A serious truck crash can involve carrier records, driver accounts, tractor and trailer systems, vendors, brokers, shippers, roadway parties, responders, medical providers, businesses, and devices. One letter rarely reaches them all.

Printable matrix · federal applicability and ownership review required

Start with the parties, posture, evidence, and current source

The words truck and carrier do not identify every party or decide which federal rules apply.

Keep the operative papers, orders, chronology, evidence record, and unresolved legal question together before choosing the next step.

|

The procedural record

The facts that can change the litigation or evidence analysis

Separate the parties, current posture, decision-maker, evidence sources, governing rules, and timing before relying on a label.

01

The parties and decision-makers

Photographs of markings, plates, unit numbers, trailer numbers, cargo labels, and equipment configuration.

02

The procedural stage

Police identifiers, exchange cards, insurance data, shipping papers, dispatch references, and tow or storage records.

03

The evidence and record sources

Full legal names and registered agents for each business or government party, verified against current official records.

04

The legal and timing question

System vendors and account relationships for logging, telematics, cameras, tolling, fleet maintenance, and communications.

Printable matrix · applicability review required

Oklahoma Truck Crash Evidence Matrix

Use the matrix to identify possible evidence sources, record categories, preservation questions, and lawful access paths.

  1. 1

    Carrier and driver identity

    Capture legal and doing-business-as names, United States Department of Transportation number, authority, insurer, driver relationship, and registered agents. Which official record verifies each role rather than a logo?

  2. 2

    Tractor, trailer, and trip

    Record unit and serial numbers, ownership, lease, cargo, weight, route, origin, destination, dispatch, and event time. Which facts determine scope and remain unresolved?

  3. 3

    Duty-status and logging records

    Identify duty-status records, logging account, edits, supporting documents, unidentified driving, time zone, vendor, and exports. Does the rule apply, and who controls native data and the audit trail?

  4. 4

    Qualification and safety records

    Map driver qualification, training, prior inquiries, accident register, safety management, testing, and policy records by category and holder. What retention provision actually covers the record and event date?

  5. 5

    Inspection and maintenance

    Identify maintenance systems, repair vendors, inspection reports, defects, parts, recalls, post-crash work, and unit histories. Who created each record, and has equipment been moved, repaired, downloaded, or altered?

  6. 6

    Electronic vehicle and vendor data

    Name each module, camera, telematics service, phone, account, software version, clock, overwrite risk, and extraction method. What protocol preserves native information without changing the source?

  7. 7

    Cargo and transaction

    Identify broker, shipper, loader, carrier, consignee, bills of lading, rate confirmation, seal, scale, securement, and hazardous-material records. What role did each party perform, and what preemption or scope issue remains?

  8. 8

    Roadway and public records

    Map agencies, dispatch audio, body or dash video, signals or work zones, roadway owner, tolling, weather, and responder records. Which open-records, preservation, notice, immunity, Tribal-law, or subpoena path applies?

  9. 9

    Medical, witness, and business sources

    Identify ambulance, hospital, coroner, pharmacy, employer, nearby camera, witness device, tow, storage, repair, insurer, and claim-file material. What privacy, authorization, privilege, ownership, retention, or authenticity issue affects access?

  10. 10

    Delivery and follow-up log

    Record each source, verified address, preservation text, delivery proof, response, production path, timing analysis, and follow-up owner. What source remains at risk, and what lawful next step is assigned today?

Identify the operation

Start with entities, equipment, trip, cargo, and regulatory scope

The words truck and carrier do not identify every party or decide which federal rules apply.

Record the motor carrier's legal and doing-business-as names, United States Department of Transportation number, authority, insurer, safety vendor, tractor and trailer owners, driver relationship, broker, freight forwarder, shipper, loader, consignee, maintenance and leasing parties, dispatch, logging-device and telematics vendors, and any public, Tribal, or federal party. Bills of lading, leases, dispatch, markings, registrations, insurance filings, police material, and corporate records may show different roles. A logo does not prove ownership, control, agency, or responsibility.

Identify power-unit and trailer numbers, weight, cargo, hazardous-material status, interstate or intrastate movement, passengers, specialized use, route, origin, destination, and event time. Federal Motor Carrier Safety Regulations use defined terms, exceptions, and limited scopes. A rule governs a carrier, driver, commercial vehicle, or record only when its definitions and scope are met. Even an applicable safety or recordkeeping rule does not automatically create a civil standard, negligence finding, deadline, or private remedy.

  • The parties and decision-makers

    Photographs of markings, plates, unit numbers, trailer numbers, cargo labels, and equipment configuration.

  • The procedural stage

    Police identifiers, exchange cards, insurance data, shipping papers, dispatch references, and tow or storage records.

  • The evidence and record sources

    Full legal names and registered agents for each business or government party, verified against current official records.

  • The legal and timing question

    System vendors and account relationships for logging, telematics, cameras, tolling, fleet maintenance, and communications.

Section 1

Rule-defined categories

Retention rules do not prove a complete file

A cited record period still requires proof of applicability and compliance.

For qualifying carriers and events, §390.15 addresses investigation assistance and accident registers. Sections 395.8, 395.22, and 395.30 cover duty-status records and electronic logging within scope. Section 391.51 covers driver qualification files; §§396.3 and 396.11 cover inspection, repair, maintenance, and certain driver inspection reports. Section 382.401 sets different periods for specified drug- and alcohol-testing records. Read each citation with definitions, incorporated provisions, effective dates, exceptions, and event facts.

A retention period does not establish creation, storage, possession, vendor copies, compliance, or a longer litigation duty. Systems may retain more than a rule requires. Requests should identify category, date range, driver, unit, account, native format, metadata, edits, audit trail, backup, vendor, and legal basis. Review production for gaps, flattened exports, missing attachments, altered time zones, and absent sources.

  • Do not turn recordkeeping into civil liability

    A regulation may identify a record or obligation. Separately analyze applicability, violation, admissibility, civil effect, causation, and remedy under law and facts.

Section 2

Volatile systems

Identify sources by module, account, vendor, and clock

Black box is a conversational label, not a single technical device or legal category.

Heavy vehicles may use engine, logging, telematics, camera, collision, brake, transmission, location, dispatch, mobile, or cloud systems. Events, rates, clocks, rollover, formats, and remote data differ. Section 563.3 covers specified light-vehicle event data recorders, not a universal heavy-truck data rule.

Identify tractor, trailer, component, serial number, software or firmware, data owner, administrator, vendor, credentials, remote commands, clocks, backups, and competent extraction. Physical custody may not preserve a cloud account; an account hold may not preserve a repaired, powered, moved, or overwritten module. Inspection protocols should address safety, custody, notice, expert roles, imaging, alteration risk, confidentiality, and every owner's or possessor's rights. Do not casually connect to or operate equipment after a serious crash.

  • The parties and decision-makers

    Which device or service could hold the data, and what event makes it record?

  • The procedural stage

    Who controls the hardware, account, subscription, export, credentials, and derivative report?

  • The evidence and record sources

    Which retention, overwrite, synchronization, clock, edit, and vendor-support conditions apply?

  • The legal and timing question

    Which neutral or party protocol preserves native data without altering the source?

Section 3

Separate record sources

Separate roadway, cargo, broker, business, medical, and public records

The carrier cannot preserve another party's systems.

Cargo evidence may involve shipper, loader, carrier, driver, consignee, seal, scale, warehouse, and securement equipment. Sections 392.9 and 393.100 have defined scopes and do not establish who loaded every shipment or caused a crash. Section 371.3 broker records may identify covered transactions. Brokerage status, actual role, contractual allocation, preemption, agency, control, negligent selection, and current law require separate review. A rate-confirmation name prompts investigation, not liability. A rate-confirmation name prompts investigation, not liability.

Other sources may include police, road owners or contractors, emergency communications, tow and repair facilities, hospitals, ambulances, coroners, toll operators, businesses, property owners, insurers, witnesses, and phone providers. Open-records law, agency policy, privilege, health privacy, law-enforcement exceptions, subpoenas, authorization, and discovery are distinct paths. Public or Tribal entities add notice, immunity, jurisdiction, and records questions. One request does not satisfy every path.

  • Preservation is not production

    Oklahoma nonparty subpoenas and Federal Rule of Civil Procedure 45 use court authority with objections and protections. Authorization, open-records, inspection, and discovery serve different purposes.

Section 4

Preserve and verify

Send source-specific notices; prove delivery

A letter still needs a recipient, delivery record, follow-up, and lawful production plan.

Record source, verified delivery, notice date, event and equipment identifiers, categories, time range, systems, metadata, destruction hold, confirmation, response, and follow-up. Overbroad demands may obscure volatile sources; narrow ones may miss an account, trailer, phone, vendor, camera, or shop. Prioritize volatility and legal significance while preserving original physical and electronic evidence.

Spoliation and remedies depend on forum and facts. Analyze duty timing, required preservation, control, reasonable steps, loss, restoration or replacement, fault, prejudice, and governing authority. Missing records do not automatically prove misconduct or liability. Retention periods are not civil filing deadlines. Document evidence state and current law, avoid outcome language, and promptly review claim, notice, limitation, discovery, and subpoena clocks.

Section 5

Legal-information boundary

The matrix identifies questions, not duties or proof

The matrix does not determine carrier or driver status, rule scope, ownership, control, preservation duty, subpoena power, spoliation, standard of care, causation, liability, damages, or outcome.

Data can change quickly; notice or filing periods can be short. Serious crashes require prompt source-specific preservation and current-law timing analysis.

Section 6

FAQ

Truck-evidence questions

Does every truck have a single data recorder?

No universal device answers that. A tractor or trailer may have modules or vendor systems with different data, triggers, clocks, retention, access, and ownership. Equipment-specific technical review is required.

How long must a carrier keep logging data?

Federal rules set retention provisions within scope. Applicability, exemptions, record type, supporting documents, event dates, vendor copies, and litigation preservation duties require exact review. Regulatory periods are not civil deadlines.

Will a preservation letter produce records?

No. Preservation prevents loss; production may require consent, authorization, open-records procedure, discovery, subpoena, inspection agreement, or court order. Objections and protections may apply.

Are federal carrier rules the negligence standard?

No. Definitions, scope, exemptions, operation, responsible party, jurisdiction, and the relationship between a regulation and civil law all require analysis. A recordkeeping or safety rule is not universal proof of liability.

Who else may hold evidence?

Possible holders include the driver, equipment owners, electronic vendors, broker, shipper, loader, consignee, maintenance and tow providers, responders, roadway parties, medical providers, businesses, insurers, witnesses, and device or account providers.

Related litigation guides

Truck Crash PracticeUnderstand the parties, regulatory questions, evidence, and injury issues that distinguish serious commercial-vehicle matters.Heavy-Vehicle Electronic DataReview module, vendor, extraction, ownership, clock, and retention issues without treating black box as one device.Preservation FrameworkBuild a source-specific evidence hold and distinguish preservation from compulsory production.

Primary law and official guidance

These sources frame this guide. Reachability does not establish governing version, applicability, interpretation, evidence, jurisdiction, timeliness, standard of care, liability, damages, or a particular outcome.

View every source used for this guide

Addison Law Firm is based in Oklahoma City. This guide provides general legal information, not advice for a particular matter. It does not create an attorney-client relationship, select a court or tribunal, calculate a deadline, instruct testimony, authorize a filing, preserve evidence, compel records, establish a federal motor-carrier duty, prove causation or liability, value damages, or promise an outcome.

Review the record and next step

Bring the vehicle and source map.

A responsible review identifies the actual parties, vehicles, vendors, public agencies, records, retention conditions, and lawful preservation paths.

Request a Truck-Crash Evidence Review