After a serious truck crash, a family may hear that the trucking company has video, that GPS proves the driver was not speeding, or that the truck’s “black box” will explain everything. None of those statements should replace a careful investigation.
Dashboard cameras, fleet GPS, electronic logging devices, and engine computers are different systems. Each may capture part of what happened. Each also has limits. A short clip can omit the approach to a collision. A location reading can describe a different moment from impact. A driver’s electronic log can document driving hours without recording braking or steering.
The practical priority is to identify the relevant sources, preserve them before they change or disappear, and compare them with the physical evidence. This guide explains what families should know after a commercial truck collision involving serious injury or death.
The short answer: can truck video and GPS help prove what happened?
Yes, when the records exist and are properly obtained and interpreted. They may help establish a truck’s route, a traffic signal, vehicle movements, a driver’s recorded work history, or particular operating conditions. They do not automatically prove fault, establish every person’s injuries, or guarantee compensation.
Keep these points in mind:
- Do not treat every electronic record as the same “black box.” Ask what equipment and data actually exist.
- Preserve the complete relevant material, not just a favorable clip. Context may support or undermine an initial explanation.
- Do not assume a universal deletion deadline. Ordinary retention settings differ, and specified driver-log retention rules do not cover every video system.
- A preservation request is not a subpoena. Keeping evidence and obtaining access to it are separate steps.
- Protect your own evidence, too. Save relevant recordings, messages, photographs, and vehicles even when they may be unfavorable.
What each type of truck evidence can show
| Evidence source | What it may help explain | Important limits |
|---|---|---|
| Forward-facing, side-view, or rear-view cameras, when installed | Traffic signals, surrounding vehicles, lane movements, visibility within the recorded view, and the approach to impact | Field of view, blind spots, lighting, recording gaps, and whether a visible signal controlled the relevant lane |
| Driver-facing camera, when installed | Visible movements inside the cab and where the driver appears to be looking | A movement does not by itself establish distraction, impairment, or what the driver could see outside the frame |
| Fleet GPS and telematics | Recorded locations, route history, and available speed or event information | Sampling intervals, time settings, positioning accuracy, and how a value was measured or calculated |
| Electronic logging device, or ELD | Duty-status records and data used to evaluate hours-of-service compliance | Required ELD information is not a second-by-second braking, steering, or speed history |
| Engine control module or other crash-related recorder, where available | Certain vehicle-operation or event records, depending on the equipment | Recorded fields, triggering conditions, overwriting, and download procedures differ |
| Business, roadway, residential, or witness cameras | An independent view of the approach, collision, or aftermath | A camera may not record, may face elsewhere, or may no longer retain the relevant period |
These are investigative possibilities, not a statement that every commercial truck carries every device.
NHTSA’s event-data-recorder overview distinguishes short-duration crash-related technical records from audio/video recordings and truck hours-of-service logs. That overview includes historical research; it should not be read as a current requirement that all heavy trucks have identical recording equipment. [1][2]
ELDs, GPS, and engine data are not interchangeable
An ELD primarily addresses driving-hour compliance
FMCSA explains that required ELD information includes date, time, location, engine hours, vehicle miles, and identification information for the driver, vehicle, and carrier. Location is recorded at specified events and at 60-minute intervals while the vehicle is moving. FMCSA also expressly states that ELD specifications do not require recording vehicle speed, braking action, steering, or other detailed performance parameters. [1]
That distinction matters when a company says, “The electronic log shows what happened.” A duty-status record may help investigate work and rest history. It may not show when the driver reacted to a stopped vehicle.
FMCSA describes ordinary on-duty ELD location accuracy as approximately within a one-mile radius, with lower precision during personal conveyance. That information is not the same as a precise reconstruction of a vehicle’s position within an intersection. A separate fleet GPS product may operate differently. [1]
A fleet platform may collect additional information
A company may purchase video, tracking, dispatch, and ELD services through one platform. That does not make every feature federally required or mean every dataset has the same retention settings.
The investigation should identify the actual equipment, account holder, vendor, available data fields, and export options. A speed value displayed on a map should be traced to its source: what does it measure, when was it recorded, and how does it relate to the collision?
An engine computer is not necessarily a complete crash recorder
“ECM,” “EDR,” and “black box” are often used loosely. The useful questions are more specific: which module recorded an event, what caused the event to be saved, what time period is available, and what procedures are necessary to retrieve it without changing relevant information?
Do not assume that starting a truck always erases its data—or that data will remain indefinitely. Counsel and a qualified specialist can assess the equipment and arrange an appropriate preservation and inspection plan.
Why a complete recording matters more than a short clip
A clip may begin after a vehicle entered a lane or after the driver first had an opportunity to react. It may show only one camera channel. A recording of someone else’s screen can omit file information and reduce the detail available for review.
Where reasonably available and relevant, investigators may seek the original or native recording, associated metadata, and a usable export covering an appropriate period before and after the crash. Depending on the system, useful supporting information may include camera-channel identification, timestamp settings, export history, and the software needed to view the files.
This is an evidence-quality preference, not a rule that every copy is legally worthless. Federal Rule of Evidence 1003 generally permits duplicates unless authenticity is genuinely disputed or admitting the duplicate would be unfair. The full context and applicable evidence rules still matter. [3]
A family that receives only a short clip should keep it, preserve how it was received, and tell counsel what the sender said it represents. Do not discard available evidence merely because a better version may exist.
What investigators should check before relying on video or GPS
Are the records about the same vehicle and trip?
A tractor, trailer, driver, dispatch account, and fleet unit number may not all use the same identifier. A route history should be connected to the actual equipment involved, rather than accepted simply because it bears the company’s name.
Do the clocks agree?
A displayed time should be compared with other reliable references. Time zones, device settings, or clock differences may explain an apparent disagreement. Preserve the original values; document any correction used in analysis rather than changing the source file to make it fit.
Does the speed value describe the relevant moment?
A reading before impact is not automatically impact speed. The interval between readings matters. So does whether a number reflects a measurement, a calculation, or a software display.
What is outside the camera’s view?
A forward-facing recording may not show a vehicle approaching from the side. A cab camera may not show the road. Missing visibility is a reason to seek additional evidence, not proof that an unseen event did or did not occur.
Does an event label prove a cause?
A platform’s “hard braking” or similar label, if present, should be evaluated with its underlying data and system settings. A label is not itself a legal finding that the driver acted negligently or avoided a collision.
The goal is a defensible timeline that accounts for the recordings, vehicle damage, roadway evidence, witnesses, and other available records—not a single screenshot presented without context.
A real court decision shows why the method matters
In Pemberton v. Liberty Ashes Inc., 2026 NY Slip Op 06255, decided October 27, 2026, New York’s Appellate Division, First Department, affirmed summary judgment dismissing a cyclist’s claim against a truck driver and company. [4]
The court described dashboard footage showing that the truck had a green light and the cyclist entered against a red light. Video and deposition testimony also established that the cyclist was traveling against one-way traffic.
The court rejected an opinion that the driver was smoking marijuana because the claim lacked supporting forensic evidence or witness testimony. It also rejected an expert’s substantially higher speed estimate where the expert did not explain the methodology. The defendants’ admissible GPS evidence registered between three and nine miles per hour right before the accident. That wording should not be converted into a claim that GPS conclusively measured impact speed. [4]
The lesson is not that trucking companies always win when they have video. It is that evidence can support either side, and an expert’s conclusion needs an explained evidentiary basis. This was a New York decision applying that state’s law; it does not control every truck case in Texas, Tennessee, Missouri, or Wisconsin.
What families can preserve immediately
Medical care and roadside safety come first. Do not enter traffic, climb onto a damaged truck, or handle another person’s equipment to gather evidence.
When it is safe and lawful, preserve:
- Vehicle identification. Photographs of the tractor and trailer, license plates, company markings, USDOT number, and visible unit numbers.
- The scene. Existing photographs or recordings of lanes, signs, signals, roadway marks, debris, sight obstructions, and surrounding camera locations.
- Witness information. Names and contact details, with notes distinguishing what you personally observed from what someone else reported.
- Your own electronic records. Original dashcam files, relevant phone photographs, messages, and recordings you lawfully possess.
- Official and claim information. Police incident numbers, towing and storage paperwork, insurer correspondence, and available reports.
- Vehicle-disposition notices. Any request to approve repairs, salvage, disposal, or transfer.
Keep an untouched original where possible and use a separate copy for everyday viewing. Record where a file came from, when it was received, and what changes or conversions were made to a working copy. Tell counsel before deleting relevant material or authorizing a device reset.
If storage charges are accumulating or an insurer wants an immediate decision about a totaled vehicle, raise the issue promptly. Evidence preservation and financial decisions may need coordination; simply ignoring the notice can create other problems.
Who may have the evidence?
Relevant records may be held by the carrier, driver, tractor or trailer owner, fleet-technology provider, towing company, repair facility, or another person or business with a useful recording.
Possession and control are not always the same. A carrier may have contractual access to records stored by a vendor. Conversely, a vendor may not have the footage a family assumes was uploaded. The correct approach is to identify the likely custodian and available copies.
Independent sources deserve early attention. A nearby store might show the approach even if the truck’s camera failed. Another driver may have saved a recording. Police may possess some evidence, but families should not assume investigators collected every camera channel, dataset, or vehicle module relevant to a civil claim.
What a focused preservation request should address
A lawyer can tailor a preservation request to the crash and the systems reasonably likely to contain relevant information. Useful identifying details include the date, approximate time, location, vehicles, driver or unit numbers when known, and a relevant time window.
Depending on the circumstances, the request may address:
- Relevant camera channels and the period before and after impact.
- Native recordings, available exports, metadata, and software needed for review.
- GPS or telematics history and the meaning of relevant recorded fields.
- Duty-status records, related supporting documents, and available change histories.
- Dispatch communications tied to the trip.
- Relevant engine or event records and the physical equipment.
- Planned repairs, disposal, or other changes that could affect inspection.
- Applicable retention settings, deletion processes, and steps taken to preserve identified information.
A focused request should not demand unrelated personal information or unlimited access to a company’s systems.
A letter does not create an automatic right to production, and it does not guarantee that evidence will survive. It can document notice and identify what needs attention. Whether a legal duty to preserve existed, when it arose, and what steps were reasonable depend on the applicable law and facts. Urgent situations may require more than correspondence.
How can a family obtain the footage or data?
A company or witness may voluntarily provide relevant material, but a request alone does not compel disclosure.
In federal litigation, Rule 34 provides a process for requesting documents, electronically stored information, and inspections within the discovery rules. A request may specify the desired production format. Rule 45 provides a subpoena process for nonparties, subject to protections including privilege and undue burden. Neither rule creates unrestricted pre-suit access to a carrier’s equipment or a vendor’s account. [5][6]
State courts use their own procedures. Available pre-suit preservation or inspection options also depend on the jurisdiction and circumstances. Counsel can assess an appropriate agreement, request, subpoena, or court application.
Do not use another person’s login, enter restricted property, connect to the truck’s equipment, or try to retrieve data without authorization. Preserving evidence should not create an access or privacy problem.
How long must trucking records be kept?
For covered records, 49 CFR § 395.8(k)(1) requires a motor carrier to retain duty-status records and required supporting documents for at least six months from receipt. 49 CFR § 395.22(i)(1) separately requires a six-month backup copy of ELD records on a device separate from the one holding the originals. [7][8]
Those provisions are not a universal six-month retention guarantee for dashcam video, every GPS record, or every engine-event file.
Different recording systems can have different settings and storage arrangements. A particular recording may be stored locally, saved as an event clip, uploaded, or never captured. The actual arrangement must be investigated rather than assumed.
Routine retention rules and litigation-preservation duties are also different questions. Information that should be preserved for anticipated litigation may require attention beyond ordinary deletion settings. Conversely, a retention rule does not guarantee that a specific camera recorded the crash.
Do not wait for a supposed video-retention deadline or the end of an insurance investigation. Ask who has the relevant information and what is being done to preserve it.
What if the trucking company says the footage is gone?
Missing evidence does not automatically prove fault, intentional destruction, or entitlement to compensation. Ask first what is actually missing:
- Was the equipment installed and functioning?
- Was a recording made but not uploaded?
- Was the wrong vehicle, date, time zone, or camera channel searched?
- Is there another copy with a vendor, investigator, insurer, or recipient?
- Was a shorter clip saved even though the full recording is unavailable?
- When was the information lost, and what preservation steps had been taken?
In federal court, Rule 37(e) addresses electronically stored information that should have been preserved for anticipated or ongoing litigation, was lost because reasonable preservation steps were not taken, and cannot be restored or replaced through additional discovery. [9]
The rule distinguishes measures necessary to address prejudice from more severe consequences. Presuming unfavorable content, instructing a jury to do so, dismissal, or default under Rule 37(e)(2) requires a finding of intent to deprive another party of the information’s use.
State law and the treatment of physical evidence may differ. An ordinary retention policy does not automatically excuse a loss; an accusation of “spoliation” does not automatically establish it.
Can electronic evidence be used in court?
Potentially, but obtaining a file does not resolve every admissibility issue.
Federal Rule of Evidence 901 requires sufficient evidence to support a finding that an item is what its proponent claims it is. Depending on the situation, that may involve a knowledgeable witness, the recording’s characteristics, or evidence about the system that produced it. [10]
Accurate identification, documented handling, and preservation of available metadata can help support review. Technical specialists may use integrity checks, such as file hashes, to document whether a collected copy later changed. A hash alone does not prove that the original recording accurately depicts the crash.
Authentication is only one issue. Relevance, hearsay questions, expert reliability, privacy protections, and other rules may also matter. State-court requirements can differ. No one should promise that a recording will be admitted merely because it exists.
Practical example: when a low speed reading does not answer every question
Hypothetical example—not an actual Dunk Law Firm case: A family receives a route screenshot showing a low speed value before a truck struck a passenger vehicle near an intersection. An adjuster says it proves the truck driver could not have caused the crash.
A careful review would ask which time the reading represents, whether it belongs to the correct truck, how often values were recorded, and what happened between that reading and impact. It would compare available video, lane assignments, traffic controls, physical damage, and witness accounts.
A low speed does not by itself resolve right-of-way or every other potential issue. A serious injury does not prove the truck driver was negligent, either. The evidence may support the company’s explanation, reveal a different sequence, or remain inconclusive. The purpose of preservation is to make a reliable evaluation possible.