Truck accident cases hand you something car accident cases never do: a defendant legally required to keep records that prove their own negligence. The problem is those records vanish fast — and most solo PI attorneys don't know exactly what to request, how to read it, or how to use it in a demand letter before the trucking company's legal team gets there first.
Why FMCSA violations change the entire settlement math
When a commercial truck driver violates a Federal Motor Carrier Safety Administration regulation and causes a crash, you don't prove negligence the traditional way. The violation does it for you.
This is negligence per se. Under 49 CFR Part 395, the rules are specific enough that a documented violation — driver exceeded 11 hours behind the wheel, company falsified logs, carrier ignored a prior out-of-service order — constitutes an automatic breach of duty as a matter of law. Your job shifts from proving negligence to connecting the violation to the crash. That's a fundamentally easier argument in front of a jury and a fundamentally harder one for an adjuster to dismiss at the settlement table.
It gets better. When a carrier knowingly permitted or encouraged hours-of-service violations, you're not looking at compensatory damages only. You're looking at punitive damages. A driver who falsified ELD records to hide fatigue didn't make a mistake. That's deliberate fraud. Juries understand that difference. So do adjusters — which is why the settlement conversation changes completely the moment a federal violation appears in the first paragraph of your demand letter.
In 2023, FMCSA recorded over 882,000 out-of-service violations nationwide. The minimum insurance requirement for general freight carriers is $750,000 under 49 CFR Part 387 — and that floor is exactly where negotiations start when you haven't built the liability case properly.
Most solo PI attorneys understand FMCSA violations in theory. The problem is execution — knowing which records to request, how to read ELD output, and how to get everything preserved before it's legally destroyed. That's what this article is about.
The 72-hour window — and why missing it ends cases before they start
Send the spoliation letter within 72 hours of the crash. Not within a week. Not when you get the retainer signed. Within 72 hours.
Here's why. Federal law only requires trucking companies to retain certain records for limited periods. ELD data and Records of Duty Status must be kept for just six months under 49 CFR §395.8(k). Maintenance records expire after one year under 49 CFR §396.3. Drug and alcohol test results have even tighter windows. The trucking company's legal team — and they will have one on the phone within hours of a serious crash — knows every one of these deadlines by heart.
A spoliation letter is a formal written demand sent to the trucking company, their insurer, and any identified defense counsel requiring immediate preservation of all potentially relevant evidence. Once received, they cannot legally destroy it. Without it, records that would prove your case can be — and routinely are — legally destroyed before litigation ever begins.
- Send to the carrier's registered agent, their insurer, and any identified defense counsel simultaneously
- Demand preservation of ELD data, paper logs, fuel receipts, toll records, dispatch communications, drug test results, maintenance logs, and driver qualification files
- Reference 49 CFR §395.8 explicitly — it signals you know the retention rules and they do too
- Send via certified mail and email, keep proof of delivery on both
This isn't optional on truck cases. It's the first thing you do. Everything else depends on having the evidence to work with.
The exact records to request and what each one tells you
Once the spoliation letter is out, here's the complete list of what to request and why each record matters.
ELD data for the 14 days before the crash. Under 49 CFR §395.26, Electronic Logging Devices automatically capture date, time, geographic location, engine hours, vehicle miles, and driver identification. Request the originals plus the full edit history. Edits to ELD records are logged — a driver who retroactively changed their on-duty time is a driver who falsified federal records. That's your punitive damages argument right there.
Records of Duty Status for the 8 days before the crash. The 60/70-hour rule doesn't apply only to the day of the crash. A driver who was 68 hours into a 70-hour week when they hit your client was already running empty. The full 8-day picture matters — and most attorneys don't request it.
Supporting documents under 49 CFR §395.11. Fuel receipts, toll records, bills of lading, payroll records. These corroborate — or contradict — the ELD data. An ELD shows the driver parked in Ohio at 2pm. A fuel receipt puts them 200 miles away at 1:45pm. That discrepancy is a falsified log. Potentially a criminal matter, definitely a punitive damages argument.
Driver qualification file. CDL status, medical examiner certificate, pre-employment drug screen, prior violations, motor vehicle record. If the driver had a prior HOS violation and the company hired them anyway — or kept them on after a pattern of violations — you have a negligent hiring and retention argument stacked on top of everything else.
FMCSA Safety Measurement System data. This one is free and public. Go to ai.fmcsa.dot.gov and enter the carrier's DOT number. You get their full safety rating, violation history, and any prior out-of-service orders. A carrier with a documented pattern of HOS violations isn't just negligent in this case. They're a company that knew about a systemic safety problem and did nothing about it. That's punitive territory — and it's sitting in a public database waiting for you to find it.
Post-accident drug and alcohol test results. Federal law requires testing within 8 hours for alcohol and 32 hours for drugs after a crash meeting certain severity thresholds under 49 CFR Part 382. If the company failed to test — or if results came back positive — that goes in the first paragraph of the demand letter, not buried in an exhibit.
How to actually read ELD data — what you're looking for
Most PI attorneys have never worked through raw ELD output. It's not intuitive. Here's the framework.
ELD logs show driver duty status in 15-minute increments: driving, on-duty not driving, off-duty, or sleeper berth. The key limits under 49 CFR Part 395 for property-carrying drivers are:
- 11-hour driving limit: maximum 11 hours of actual driving after 10 consecutive hours off duty
- 14-hour on-duty window: the clock starts when the driver goes on duty and cannot be extended by rest breaks — once it closes, they cannot legally drive
- 30-minute break requirement: mandatory non-driving break after 8 cumulative hours of driving
- 60/70-hour weekly limit: no driving after 60 hours on duty in 7 days, or 70 hours in 8 days for carriers that operate every day of the week
When you get the ELD data, you're building a timeline. How many hours had the driver been on duty at the moment of impact? When did their 14-hour window open? Had they taken their mandatory 30-minute break? Were they within their weekly limit? If any of those questions has a bad answer for the defense, that answer belongs in the first paragraph of your demand letter — not buried in the liability section after three pages of medical history.
Take the James Okafor case — rear-ended by a FastRoute Logistics truck on I-10 in Houston. The driver had logged 11.4 hours of on-duty time at the moment of impact. Direct violation of 49 CFR §395.3(a)(3). That fact led the demand letter. Not the $34,560 in medical bills. Not the herniated disc. The federal violation. Because the violation reframes every other fact that follows it.
Where competitors fall short — and what the tools miss
EvenUp is the most well-funded AI demand letter tool in personal injury law. Their proprietary AI — trained on 250,000 verdict and settlement data points — is genuinely strong on medical record analysis and damages calculation. That's a real number worth respecting.
What EvenUp doesn't do — what none of the major AI legal tools do well — is walk a solo PI attorney through the FMCSA discovery process that makes truck cases worth taking in the first place. Their workflow assumes you already have all the evidence organized. It doesn't help you get the evidence before it disappears.
Clio's blog covers demand letter best practices. CasePeer covers workflow and case management. Neither tells the solo PI attorney in suburban Houston exactly which CFR sections to cite in a spoliation letter, which records to request on day one, or how to read ELD output for the specific violations that trigger negligence per se. That gap is real. And it costs attorneys settlements.
Tools like Jurovy can draft the demand letter in 60 seconds once you have the facts — with every citation verified against 7 million court opinions. But the facts have to come from you. Specifically: the ELD data you requested within 72 hours, the CFR violation you identified in the logs, and the negligence per se argument you built before anyone else got there.
How to structure the demand letter when FMCSA violations are present
The structure changes when you have a federal violation. Lead with it. Don't save it for the liability section.
The first substantive paragraph after your introductory sentence states the specific regulation, the specific violation, and when it occurred. Something like: "At the time of impact, defendant's driver had been on duty for 11.4 hours in direct violation of 49 C.F.R. §395.3(a)(3), which prohibits property-carrying drivers from operating a commercial motor vehicle beyond the 11th hour after coming on duty following 10 consecutive hours off duty." That sentence — in the opening paragraph — reframes everything the adjuster reads after it.
Then connect the violation to causation. An HOS violation doesn't help you if it's floating in space without a causal link to the crash. Fatigue impairment at extreme hours is well-documented — research puts severely fatigued driving on par with alcohol impairment. Make that connection explicitly, with accident reconstruction support if you have it.
Then go to medical and damages in your normal structure. By the time the adjuster reaches the damages section, they already know they have a federal violation problem, potential punitive exposure, and a plaintiff attorney who clearly understands FMCSA regulations. That combination changes their Colossus override calculation before they enter a single number.
- Opening paragraph: specific FMCSA violation with exact CFR citation and when it occurred
- Causation paragraph: how the violation — fatigue, regulatory non-compliance — caused or contributed to the crash
- Liable parties: driver, carrier, and any third parties (shipper, maintenance contractor) where applicable
- Medical section: injuries, treatment, current status, prognosis, future needs — using exact clinical language from the chart
- Damages section: itemized, specific, documented
- Closing: reference punitive damages exposure if violations involved falsified records or a documented pattern of carrier non-compliance
Do this on day one — not after you've built the rest of the case
Pull the FMCSA SMS data the same day you take the case.
It's free. Public. Five minutes. Go to ai.fmcsa.dot.gov, enter the carrier's DOT number — visible on the truck door or cab in accident photos — and look at their safety history. A carrier with a pattern of prior HOS violations, multiple citations, and a deteriorating safety rating makes the "isolated incident" defense impossible. That prior history belongs in your demand letter. It opens the door to punitive damages even if the driver's ELD data on the day of the crash looks relatively clean.
Day one. Not later. The SMS data is often the first indicator of whether this truck accident case is a standard PI matter or a case where the carrier's systemic negligence justifies pushing for policy limits from the opening demand. Know which one you're dealing with before you write a single paragraph.