SAFER Shows 3 Crashes. Their Accident Register Shows 7. Which Number Goes to the Jury?

MC-1337492. Lancer Transport Solutions LLC, out of Canton, Ohio. DOT-4012678. Two and a half years of authority. Crash Indicator BASIC at the 61st percentile — inside the alert threshold at 65, but not over it. SAFER showed three crashes in the prior 24 months. Insurance clean on L&I. I approved the carrier.

Fourteen months later, one of their flatbeds rear-ended a passenger car on I-71 near Columbus. Forty-three thousand pounds of boxed appliances. Two people in the car. One of them didn't make it. The other spent four months in a rehab facility.

In discovery for the $2.4 million wrongful death action that followed, plaintiff's counsel asked for two things: the SAFER printout dated the day of carrier approval, and Lancer's accident register maintained under 49 CFR § 390.15. The SAFER printout showed three crashes. The accident register showed seven — covering the same 24-month window.

The broker on that load had to explain to a jury why the number she relied on was three when the carrier's own records said seven. I wasn't that broker. But I've thought about that gap every time I've approved a carrier since.

---

What the Accident Register Is

Under 49 CFR § 390.15, motor carriers operating commercial motor vehicles are required to maintain an accident register for at least three years from the date of each recorded accident. Not optional. Not for large carriers only. Every carrier hauling freight on your loads is covered.

The register has to document every accident that meets the FMCSA definition under § 390.5: a fatality, a bodily injury requiring medical treatment away from the accident scene, or disabling damage to any involved vehicle requiring tow-away. For each qualifying accident, the carrier records the date, location (city and state), the driver's name and license number, the number of injuries and fatalities, whether hazardous materials were released, a brief description of the cargo, and the registration state and plate number of the vehicle involved.

That's it. No editorializing. No safety conclusions. Just the facts of every FMCSA-reportable crash, logged in order, maintained for three years.

Most brokers have never seen one. That's the problem.

---

Why SAFER Doesn't Tell You the Same Story

SAFER's crash data doesn't come from the carrier. It comes from two independent pipelines: state crash databases that states submit to FMCSA on their own reporting schedules, and carrier MCS-150 biennial update filings. Both introduce lag.

State reporting to FMCSA is not standardized in timing. Some states transmit crash data within 60 days. Others run six to twelve months behind. If Lancer Transport had two rear-end collisions in October, and you're approving a load for them in February, those crashes might not show up in SAFER until the following spring. You're looking at a Crash Indicator percentile built on an incomplete dataset, and you don't know it.

There's also the DataQ challenge factor. Carriers can dispute individual crash entries through FMCSA's DataQ system, arguing a crash was "not preventable." During the challenge period, the crash is still visible in SAFER but flagged. If the challenge succeeds, the crash can be removed from the Crash Indicator calculation. Some carriers actively use DataQ to clean their SAFER record. The accident register still documents every crash regardless of DataQ outcomes — because the underlying obligation under § 390.15 isn't tied to FMCSA's calculation. The crash happened. It goes in the register.

For Lancer Transport, four of the seven crashes in the accident register simply hadn't hit SAFER yet because of state reporting lag. All four were legitimate FMCSA-reportable events — injuries requiring off-scene treatment, one tow-away. They were real. They just weren't visible on the screen I was looking at when I approved them.

---

The Pattern Hidden Inside the Percentile

Here's the thing about the Crash Indicator BASIC: it tells you how a carrier compares to similar carriers on crash rate. It does not tell you what type of crashes they're having.

That distinction matters more than most brokers realize.

Rear-end collisions at highway speed are a specific failure mode. They almost always involve following distance — too close, too fast for conditions, or both. The root causes are fatigue, distraction, and a driver culture that pushes against hours-of-service limits under 49 CFR § 395.3. When you see multiple rear-end collisions in a carrier's crash history, you're seeing a signal about how that carrier manages its drivers on long hauls.

Intersection collisions are different. Many are other-party fault — red-light runners, left-turn-across-path situations. They're bad, but they don't necessarily tell you something about the carrier's driver management practices.

Single-vehicle rollovers on curves suggest speed management issues, often combined with load shift or insufficient securing. Backing accidents are usually a yard or dock problem.

A carrier with six rear-end collisions and a 58th-percentile Crash Indicator is a categorically different risk than a carrier with six intersection collisions and the same percentile. The SAFER number doesn't show that. The accident register does.

With Lancer Transport, five of the seven crashes were rear-ends. Two were on interstates in Ohio and Pennsylvania, all between 2 a.m. and 6 a.m. That's a fatigue signature. And a plaintiff's expert witness can connect that fatigue pattern to the specific crash on I-71, because the fatal accident happened at 4:17 a.m.

---

What Montgomery Does With the Gap

In Montgomery v. Caribe Transport II, the Supreme Court held that the FAAAA does not preempt state-law negligent selection claims against freight brokers. That decision opened the door to state court liability for brokers who select unsafe carriers.

State negligence law asks a simple question: did you know, or should you have known, that this carrier was unsafe? "I checked SAFER" is a starting point. But if the accident register shows a pattern that predates your load tender — crashes that hadn't hit SAFER yet, crash types that cluster in a way SAFER can't show — then "I checked SAFER" becomes a floor, not a ceiling.

A plaintiff's lawyer who knows what to subpoena will get the accident register. They'll put it next to your SAFER printout. They'll have an expert testify about what the register shows that the SAFER printout misses. And they'll ask the jury: was it reasonable to rely only on the public database when the carrier's own private record told a different story?

Most juries think that asking the question was worth the five minutes it would have taken.

---

What You Can Actually Do

You can't compel a carrier to hand over their accident register. It's their internal record and there's no regulatory obligation to disclose it to a broker. But you can ask for it, and you should build that ask into your standard carrier onboarding flow.

A well-run carrier with a clean accident history will usually provide a copy without much resistance. They know what's in it. The carriers who refuse to provide it are telling you something — not necessarily that they have a bad record, but that they're not willing to be transparent. That unwillingness is a factor. Carriers who claim they don't maintain an accident register are telling you they're out of compliance with § 390.15, which is a different category of concern.

When you get the register, don't just count the crashes. Look at:

Total count vs. SAFER count. If the register shows six crashes and SAFER shows three, the difference is probably reporting lag. Understand the gap, don't assume the SAFER number is the real number.

Crash type concentration. Five rear-ends in 36 months is not the same as five crashes spread across five different types. Type concentration is a pattern. Patterns suggest a systemic problem.

Recency weighting. Two crashes in the last eight months are a worse signal than two crashes in the last 36. Frequency trending up is worse than frequency holding steady.

Driver concentration. If the same driver name appears in three of five accidents, that's a carrier management failure — they kept the driver hauling after two events. That's documented negligence at the carrier level, which has implications for your negligent selection exposure.

Night and early morning concentration. Crashes between midnight and 6 a.m. cluster with fatigue-related incidents. This is especially important for long-haul carriers.

DOTScreener's carrier onboarding packet gives you a structured place to collect and timestamp carrier-submitted documents — insurance certificates, agreements, and any supplemental records you want in the file before you approve a carrier. Building the accident register into your standard document request means you're creating a record that you asked. Whether the carrier complies or refuses, that interaction and its timestamp is part of your vetting file.

---

How I Document This

My onboarding document request now includes a standing line:

"Copy of accident register as required by 49 CFR § 390.15, covering the prior 36 months. If no qualifying accidents occurred in that period, written attestation signed by an authorized company officer."

If the carrier provides the register, I upload it to the carrier file, note the total crash count versus the SAFER count for the same period, flag any crash-type concentration for review, and log it as part of the carrier approval record. If the counts match, that's reassuring. If they don't, I want to understand why before I approve the carrier.

If the carrier refuses to provide it, that goes in the file too. Reason: carrier declined to provide accident register on request. Vetting decision made with that noted.

If the carrier says they don't have one, that's a § 390.15 compliance gap and it goes in the file as: carrier represented no accident register is maintained. I treat that as a higher-risk flag and make an individualized decision about whether to proceed.

The timestamp on that interaction is what matters. If this carrier is ever in a serious accident after you onboarded them, you want the record to show that you asked, not just that you looked at SAFER and clicked approve.

---

— Mason Lavallet

Founder, DOTScreener.com