The BASIC Score Plaintiff Lawyers Pull First Is Not the Crash Indicator

The Wrong BASIC Is Getting All the Attention

A claims attorney I know — works plaintiff freight cases out of Nashville — told me once that when he files a negligent selection case against a broker, the first BASIC he looks at is Unsafe Driving. Not the Crash Indicator. Not Vehicle Maintenance. Unsafe Driving.

I asked him why. His answer was simple: "Crash history tells me what happened. Unsafe Driving tells me what the carrier was doing habitually. That's negligence. That's a pattern."

I've thought about that a lot since Montgomery came down. After the Supreme Court's May 2026 ruling in Montgomery v. Caribe Transport II, LLC that FAAAA preemption doesn't protect brokers from state-law negligent-selection claims, the standard of care conversation in this industry got real fast. Every broker is now looking at their carrier files and asking: would this hold up? And when they do, they reach for the Crash Indicator BASIC because it literally says "crash" in the name.

That's the wrong instinct. Let me explain why.

What the Crash Indicator Actually Measures

The Crash Indicator BASIC is a percentile ranking of carriers based on their crash frequency relative to vehicle miles traveled, adjusted for inspection opportunity. It's useful, it matters, and a carrier in the 80th percentile on Crash Indicator is a genuine red flag.

But here's the thing: that percentile is built from crash records reported to FMCSA. Which means it's counting what already happened. And because crash data comes with a 60-day lag — the time between a reportable accident and it showing up in SAFER — you're always looking backwards. A carrier that had a bad twelve months of crashes eighteen months ago might be cleaning up. A carrier that started sliding three months ago might still look clean.

More importantly, a crash record doesn't prove the carrier was negligent. It proves they were involved in an accident. Crashes happen to good carriers on black ice. Plaintiff lawyers know this. They need something that shows habitual, pattern-of-practice dangerousness — and the Crash Indicator alone doesn't give them that.

Why the Unsafe Driving BASIC Is Different

The Unsafe Driving BASIC is built from moving violations captured during roadside inspections: speeding, reckless driving, failure to obey traffic control devices, following too closely, improper lane changes, using a handheld device. These are things a driver was actively doing wrong behind the wheel when an inspector was watching.

Every violation that feeds into this BASIC is a documented instance of a driver making a bad choice on the road. It's not a crash that could be explained by road conditions or another driver. It's a driver who was going 78 in a 65 at 2 AM and got tagged for it.

From a negligence standpoint, that's different. A carrier with a 75th percentile Unsafe Driving BASIC has multiple documented instances of their drivers operating unsafely — caught by law enforcement, recorded in the federal inspection database. That's what pattern-and-practice looks like. That's what a plaintiff's expert witness puts on a timeline that runs from "broker tendered load" to "driver drove unsafely" to "crash happened."

The Crash Indicator tells a jury something bad happened. The Unsafe Driving BASIC tells a jury the carrier was already operating unsafely. For negligent selection purposes, the second story is harder to defend against.

The Violation Codes That Actually Matter

Within the Unsafe Driving BASIC, not all violations carry equal weight. The violations that get measured are coded under Part 392 of the FMCSR — operation of commercial motor vehicles. The heavy ones:

§ 392.2 — violating state or local traffic laws. This catches everything: speeding, running lights, lane violations. It's the volume violation, and carriers with high Unsafe Driving percentiles often have a lot of these.

§ 392.3 — operating while fatigued. This one bleeds into the Hours of Service BASIC too, but an inspector who writes this up during a roadside is documenting a driver they believed was impaired by fatigue in real time. That's serious.

§ 392.16 — using a handheld mobile telephone. Texting or calling while driving. FMCSA takes this seriously enough that a single citation can result in disqualification at certain thresholds. At load-tender time, a carrier with multiple § 392.16 violations is telling you their drivers are habitually distracted.

§ 392.71 — radar detectors prohibited in CMVs. Not the most severe by itself, but it tells you something about operating culture. A driver running a radar detector is trying to speed without getting caught.

The pattern of underlying codes matters as much as the overall percentile. Two carriers might both be at the 68th percentile on Unsafe Driving. One gets there mostly on § 392.2 state traffic law violations logged at scale — annoying, worth noting. The other gets there with a cluster of § 392.3 fatigued operation and § 392.16 handheld device citations — that's a carrier with a distraction and fatigue culture problem.

A Scenario Worth Taking Seriously

MC-1247893 / DOT-3567102. Flatbed carrier, 22 trucks, authority issued 29 months ago. When you pull their SAFER snapshot, the Crash Indicator BASIC shows them at the 44th percentile. Below the intervention threshold. Clean-looking.

But the Unsafe Driving BASIC is sitting at the 71st percentile. Dig into the inspection history and you find 14 Unsafe Driving violations over the past 24 months: nine § 392.2 speeding citations, three § 392.16 handheld device violations, and two § 392.3 fatigued operation citations.

Would you tender a $180,000 steel coil load to this carrier? Maybe you would — plenty of brokers would see a Crash Indicator under 50th percentile and move forward. But if that load ends up in an accident six weeks later, and a plaintiff lawyer pulls this carrier's SAFER history during discovery, you're going to explain why you tendered a $180K load to a carrier with 71st percentile Unsafe Driving and two documented fatigued-operation citations in the past two years.

Your documented answer better be better than "the Crash Indicator looked okay."

The Percentile Threshold That's Widely Used (and Why It Isn't Enough)

FMCSA flags carriers for intervention when they hit the 65th percentile on most BASICs (75th on Crash Indicator and Hazmat Compliance because the denominator is different). That's where you start hearing about "threshold" violations.

A lot of carrier vetting procedures use that threshold as a hard stop: 65th percentile or above is a reject; below is a pass. That's a reasonable starting point, but it's not a vetting procedure. It's a filter.

A carrier at the 62nd percentile on Unsafe Driving — three points under threshold — still has a meaningful unsafe driving history. The percentile measures relative standing within the carrier population, not absolute risk. Being below the intervention threshold doesn't mean the carrier is driving safely. It means FMCSA hasn't prioritized them for an intervention yet.

And critically, the Unsafe Driving BASIC has a data window issue too. Violations from inspections drop off after 24 months. A carrier that was getting hammered on speeding violations eighteen months ago might show clean now even if nothing in their operation actually changed. You need to cross-reference the percentile with the actual inspection history — look at when the violations were logged, not just whether the score is under threshold today.

How I Read This at Load-Tender Time

Here's my practical workflow when a carrier's Unsafe Driving BASIC is above 50th percentile:

First, I pull the full inspection history from the FMCSA SAFER system and look at the underlying violations, not just the aggregate. I want to know what's driving the score — high-volume § 392.2 traffic violations spread across many drivers, or concentrated § 392.3 and § 392.16 violations on fewer drivers. The second pattern is worse.

Second, I look at the trajectory. Are the violations clustered in one window two years ago and then trailing off? Or are they recent and consistent? A carrier working to fix a problem looks different from a carrier still operating the same way.

Third, I compare against the Crash Indicator. A carrier with high Unsafe Driving and high Crash Indicator is a double-red situation — they drive unsafely and they've had crashes. A carrier with high Unsafe Driving and low Crash Indicator might just be statistically unlucky, or might be one load away from the crash data catching up to the violation history.

Fourth, I think about load type. High Unsafe Driving carriers are a bigger concern on loads with longer transit windows, overnight runs, and time-sensitive appointments — situations that incentivize speeding and create fatigue pressure. A local delivery run is a different risk profile than a 1,800-mile OTR run with a receiving appointment.

How I Document This

When Unsafe Driving BASIC is a factor in my carrier decision:

I pull and save the SAFER snapshot with the BASIC percentile visible and the date-stamped. I note the specific percentile and whether it's above the 65th threshold. If I'm approving a carrier that's between 50th and 65th percentile on Unsafe Driving, I document the reason — typically a review of the underlying inspection violations showing no concentrated fatigued-operation or handheld-device pattern.

If the carrier is above 65th percentile on Unsafe Driving, I document the reason I approved them anyway or record the rejection and find a different carrier. "Above threshold, rejected" is a complete record. "Above threshold, approved because single driver / isolated incident / trajectory improving" is also a complete record if I can support it with inspection history.

What's not a complete record: "pulled SAFER, looked okay." That's not going to hold up.

DOTScreener flags BASIC percentiles automatically and timestamps the pull. That timestamp matters. If my vetting pulled a carrier's BASIC on a Monday and the load moved on Thursday, the record shows I checked with appropriate lead time. That's the kind of specificity that separates documented diligence from a retroactive claim.

The Takeaway

After Montgomery v. Caribe Transport II, the question every broker has to answer in discovery is: what did you know, when did you know it, and what did you do with what you knew? The Unsafe Driving BASIC is where the answer to that question gets uncomfortable fast, because it documents what a carrier's drivers were doing on the road before your load moved.

The Crash Indicator tells you who's had crashes. The Unsafe Driving BASIC tells you who drives like they're going to. If you're only checking one of them, you're checking the wrong one.

— Mason Lavallet

Founder, DOTScreener.com