The HOS BASIC Isn't a Paperwork Score. It's a Fatigue Warning.

A carrier with 22 months of authority, a Satisfactory safety rating, and zero crashes in SAFER walked through every filter my colleague had. MC-1247893, DOT-3567102, operating 14 flatbeds out of a terminal in Mississippi. Everything checked out except one thing she didn't check.

Their Hours-of-Service Compliance BASIC was in the 91st percentile.

Six weeks after she tendered a $2,800 flatbed load on I-55, one of their drivers — running on falsified logs, already well past his 11-hour limit — drifted across the median. The cargo was a write-off. The litigation is ongoing. The first question the plaintiff's attorney asked in discovery: "Did your company have access to this carrier's FMCSA data before the load was tendered?" Yes. "Did you review their Hours-of-Service score?" Silence.

Here's what I've come to believe about the HOS Compliance BASIC: most brokers treat it like a compliance checkbox and look straight past it to the Crash Indicator. That's exactly backwards. The Crash Indicator tells you about crashes that already happened. The HOS BASIC tells you what's happening inside that carrier's daily operations right now — whether drivers are pushing past legal limits, whether logs are being falsified, whether the company has built a culture where hours violations are routine. The crash hasn't shown up in SAFER yet. That doesn't mean it won't.

What the HOS BASIC Actually Measures

The HOS Compliance BASIC compiles violations discovered during roadside inspections under 49 CFR Part 395. Every time a carrier's driver gets inspected and an officer finds an hours violation, it goes into FMCSA's SMS system and rolls into the carrier's percentile ranking against similar carriers.

The violations aren't all equal, and that matters.

49 CFR § 395.3(a)(1) is the one that should stop you cold: driving more than 11 hours after 10 consecutive hours off duty. That's not a paperwork problem. That's a driver who was behind the wheel when he should have been in the sleeper. § 395.3(a)(2) covers the 14-hour rule — a driver still operating after their daily on-duty window closes. Both of these mean a driver was genuinely fatigued and the carrier either didn't know or didn't care which is worse.

Then there's § 395.8, which covers failure to prepare or retain driver records of duty status. This one has teeth because § 395.8(e) — log falsification — sits under it. A § 395.8(e) violation means an officer found discrepancies between a driver's log and objective data: fuel receipts, toll records, GPS pings. That's not a paperwork error. That's intentional concealment of hours pushed.

§ 395.22(a) is the one I find most telling from a broker's perspective: the motor carrier obligation to ensure all drivers use a properly registered ELD. When this one gets cited in an inspection, the carrier itself is on the hook — not just the driver. A carrier racking up § 395.22(a) violations isn't dealing with a few rogue drivers. Their safety management is failing at the company level.

The BASIC score mixes severe and minor violations together into one percentile. A § 395.3(a)(1) violation — actually driving fatigued — sits in the same calculation as a § 395.8(k)(1) form-and-manner defect, which might be nothing more than a log entry missing a required field. If you can access the underlying inspection data through FMCSA's PIN portal, look at which violations actually built the score. A carrier whose HOS BASIC is driven by § 395.8(k) paperwork issues is a different situation from one whose score is built on § 395.3(a)(1) actual fatigued driving. The percentile doesn't tell you that. The inspection detail does.

Why This Predicts Crashes, Not Just Compliance Failures

FMCSA's large truck crash causation research has consistently found driver fatigue as a contributing factor in serious crashes. The 11-hour driving limit in § 395.3 isn't arbitrary — it reflects research showing that crash risk increases sharply as driving time extends past 8 or 9 hours and doubles in that final stretch before the limit.

A carrier in the 90th percentile for HOS violations isn't just generating paperwork problems. They're running a fleet where drivers routinely push past legal limits. Maybe dispatchers are building routes that require it. Maybe per-mile pay structures make drivers reluctant to log a 10-hour reset. Maybe safety managers aren't auditing logs until there's an inspection and it's already too late. Whatever the cause, you're looking at a carrier where fatigue is normalized — and normalized fatigue eventually produces a crash.

The Crash Indicator BASIC tells you what already happened. It measures crash rates and trends that signal elevated risk based on past events. But crashes take time to accumulate and enter SAFER. A carrier that started running its drivers hard six months ago won't have new crash data yet. It will have an HOS BASIC that's been climbing.

This is why, for a carrier with under two years of authority, I weight the HOS BASIC more heavily than the Crash Indicator. They haven't been on the road long enough for crash data to be statistically meaningful. But their HOS violations come from real inspections that happened last month.

The Percentile Thresholds Are FMCSA's Bar, Not Yours

FMCSA's alert threshold for the HOS Compliance BASIC is the 65th percentile — that's when carriers start appearing on their intervention radar. If you're a broker, the 65th percentile is not your green light. That's the point at which the federal government decides to pay attention. Your liability standard is different, and it's higher.

Here's how I actually think about it:

Below the 35th percentile: fine. For most carriers in this range, HOS compliance isn't a concern worth escalating.

35th to 64th percentile: worth a call. Not a hard stop, but I want context. How big is their fleet? How many inspections generated this score? I'll ask the dispatcher directly how they manage driver hours — do they use ELDs, paper logs, what's their system for flagging drivers running close to the limit? If they get defensive or vague about ELDs on a fleet doing interstate hauls beyond 150 air miles, that's a stop.

65th percentile and above: I need a documented reason to continue. Not a gut feeling — a documented reason. A declining trend in the last two measurement periods, a small fleet where one bad inspection cycle drove the score, a specific conversation with the safety director that I wrote down. If I can't articulate and document it, I don't tender.

80th percentile and above: I don't tender. I've made this a hard line. I can't justify it from a legal exposure standpoint and I can't justify it from a "what do I think actually happens inside this carrier's operation every day" standpoint.

The Small-Fleet Caveat

The HOS BASIC uses the same methodology as other BASICs — it weights violations against vehicle miles traveled. For a 3-truck carrier, a single inspection with two violations can spike the percentile dramatically. You have to factor that in.

I look at the inspection count, not just the percentile. If a carrier has 4 inspections over 18 months and 2 came back with HOS violations, that's a 50% hit rate on a tiny sample. It could mean nothing. It could mean something. It doesn't mean the same thing as 100 inspections with 40 HOS violations across a 300-truck fleet.

But even for small fleets: if the violations that appear are § 395.3(a)(1) — actual fatigued driving, not paperwork defects — I treat it seriously regardless of sample size. One inspection showing a drive-past-11-hours violation tells me something about how that carrier runs their operation, even if I can't statistically prove a pattern.

What This Has to Do With Montgomery

The Supreme Court's ruling in Montgomery v. Caribe Transport II, LLC, decided May 14, 2026, held that the FAAAA does not preempt state-law negligent-selection claims against brokers. Brokers can now be sued in state court. Plaintiff attorneys know this and they've been building their discovery playbooks accordingly.

When there's a fatigue crash, discovery reaches for the SAFER snapshot from the date of tender. If that snapshot shows an HOS BASIC in the 80th percentile, the first question is whether you documented that you saw it and what you did about it. "We check FMCSA data" is not an answer. A saved snapshot with the date, the HOS percentile recorded, and a note on what action you took — that's a record.

The carrier file you build either helps you or hurts you in discovery. There's no neutral file.

How I Document This

For every carrier relationship, first tender and every annual re-qualification, I record the following explicitly:

• Date of the SAFER/SMS pull
• HOS Compliance BASIC percentile, written out — not just "FMCSA: OK"
• If above the 35th percentile: note the trend (improving, worsening, or flat over the visible measurement periods in SMS)
• If above the 65th: a written note on what I'm relying on to proceed and who approved the decision to move forward
• If I called the carrier about it: who I spoke with, their title, what they said, date and time of the call

DOTScreener timestamps the snapshot automatically when you run a screen, which covers the "when did you check" question. The substantive note on what you decided and why — that's yours to write. The timestamp proves when you looked. The note proves you understood what you were looking at.

That distinction is what matters when you're sitting in a deposition two years later and an attorney is reading your carrier file back to you line by line.

A 91st-percentile HOS BASIC on a carrier with 14 trucks and 22 months of authority isn't ambiguous. It's a fleet running its drivers into the ground. The only question is whether you knew and documented it, or knew and didn't, or didn't know because you weren't looking at the right BASIC.

Start looking at the right one.

— Mason Lavallet

Founder, DOTScreener.com