The Same Brake Violation Three Times in Six Months

A carrier showed up in my queue last spring — MC-1247893, DOT-3896441, 16 months of authority, Satisfactory rating from their new-entrant safety audit. Vehicle Maintenance BASIC said "Insufficient Data." That's the field FMCSA shows when a carrier has fewer inspections than the threshold for a reliable percentile. Seeing that empty slot, most brokers flag the authority age, confirm insurance is active, and move on.

I pulled their 90-day inspection history on SAFER anyway. Four inspections. Three had brake violations. Two of those three were identical: 49 CFR § 393.52(b) — brake adjustment out of tolerance, meaning the brakes weren't stopping the truck within the distance physics requires. The fourth inspection was clean.

The four inspections ran across 19 weeks. Brake violation. Brake violation. Clean (different driver on that one). Brake violation.

That's not bad luck. That's a carrier who knows exactly what's wrong with their trucks and has decided not to fix it.

I didn't tender to them. I've never been more glad of a call I didn't write up in an email.

Why Inspection History Tells You Something the BASIC Score Doesn't

The Vehicle Maintenance BASIC is a percentile score built on a rolling 24-month inspection database. FMCSA needs enough inspections to produce a meaningful number — under roughly three inspections in the window (the exact threshold isn't published cleanly), the system shows "Insufficient Data" instead of a percentile. Most brokers read that as "nothing to see here." What it actually means is "there's not enough data to rank this carrier against its peers." It says nothing about whether the data that does exist is alarming.

The SAFER inspection query is different from the BASIC. SAFER shows raw inspections — the actual records, not a normalized score. You can see what happened at each roadside stop: which violations were cited, which were Out of Service, which got the driver sent home on the spot. It's on the carrier's public company snapshot page, right there if you scroll to the Inspections & Crashes section and click through. FMCSA doesn't advertise this the way it should.

Go to safer.fmcsa.dot.gov, pull the carrier's DOT number, and look at the individual inspection records. You'll see violation codes, inspection dates, inspection type, and whether any violations triggered an OOS order. Four minutes. Free. One of the highest-signal checks I run on any carrier with a thin BASIC file.

What You're Actually Looking For

Three patterns that should stop a tender cold:

Repeating violation codes. When the same CFR section shows up across multiple inspections, you're not looking at random failures — you're looking at a maintenance culture. § 393.52 recurring three times in six months means a carrier who knows they have brake problems and keeps dispatching trucks anyway. § 393.75 hitting twice in 90 days is a fleet manager watching rubber wear down and hoping it holds through the next run. These aren't accidents. They're choices.

OOS violations followed by the same pattern. When a vehicle gets placed Out of Service, it's supposed to get repaired before it goes back on the road. Under § 396.9, a carrier must certify repairs were made before returning an OOS vehicle to service. Now look at what follows. If the next two inspections show the same violation type — not necessarily the same unit, but the same category — you're looking at a carrier who fixed one truck and ignored the pattern in the rest of the fleet.

Non-OOS violations repeated across many inspections. Counterintuitively, a long list of non-OOS violations can be worse than a single OOS. Non-OOS means the inspector found a problem but decided it wasn't dangerous enough to pull the truck right now. A carrier with eight inspections and six of them showing brake-lighting violations has a chronic problem they're just barely keeping above the pull-out threshold. That's the management strategy.

The Regulatory Floor They're Not Meeting

49 CFR § 396.3(a)(1) requires every motor carrier to "systematically inspect, repair, and maintain, or cause to be systematically inspected, repaired, and maintained, all motor vehicles subject to its control." The word "systematically" is doing real work in that sentence. It means a schedule, a record, a process — not hoping the truck makes it to the next weigh station.

Part 396 also requires drivers to complete a vehicle inspection report at the end of every duty period under § 396.11. If a driver finds defects, those go on the DVIR and the carrier is supposed to certify they've been repaired before the truck goes back to work. When the same brake violation shows up in SAFER three inspections in a row, it means one of three things: the driver didn't report it on the DVIR, reported it and no one fixed it, or fixed it and it broke again immediately. None of those options reflect a carrier with a functioning maintenance program.

Annual inspections are required under § 396.17, but those are a floor — a minimum. A carrier who passes their annual inspection and then fails three roadside brake checks in six months is skating between mandatory review points and betting they won't get pulled.

At load-tender time, here's what that means: if you tender to a carrier with a documented brake violation pattern and a catastrophic failure occurs, your vetting record now shows you found evidence of chronic brake problems and loaded them anyway. Under Montgomery v. Caribe Transport II, LLC — the unanimous Supreme Court decision from May 2026 holding that the FAAAA doesn't preempt state-law negligent-selection claims — a plaintiff's attorney doesn't need to prove you knew the carrier was dangerous. They need to prove you should have known. A repeat inspection pattern you could've found for free in four minutes is a hard fact to explain to a jury.

The Cargo Value Factor

This matters more on some loads than others. I wouldn't walk away from a carrier with one non-OOS citation on a standard $18,000 dry van load without other flags. Risk tolerance is part of the job.

I would walk away from any carrier with three brake citations in 24 weeks if I was moving electronics on a $290,000 declared-value shipment, or anything on a reefer that needed 72-hour temperature integrity across a multi-state run. The severity of potential loss scales the weight of the signal.

For high-value lanes, I now hold myself to a self-imposed standard: no OOS violations in the last 90 days for the vehicle type I'm tendering to, and fewer than two instances of the same violation code in any 24-month window. That's not regulatory. That's my documented carrier selection policy — and it exists specifically because I can articulate it under oath without sounding like I made it up after the fact.

When "Insufficient Data" Is Actually a Signal Itself

A carrier with "Insufficient Data" in the Vehicle Maintenance BASIC is often newer, smaller, or operating in a region with lower roadside enforcement. That's not a problem by itself. But it means the BASIC is giving you zero signal, not a clean signal. Those are different things.

The way I handle it: if a carrier has fewer inspections than the BASIC threshold, I pull the raw records on SAFER directly. Every time. If there are zero inspections, I weigh the authority age against the freight type. A 14-month carrier with zero inspections moving standard palletized freight is one conversation; the same carrier moving flatbed OD loads across mountain states in December is a different one.

"Insufficient Data" on the BASIC means shift your check. It doesn't mean skip it.

The other thing worth knowing: the BASIC score threshold isn't static by carrier. A carrier with nine inspections might show a percentile in one BASIC category while another category still says "Insufficient Data" because the violations that feed each BASIC come from different inspection types (driver-based vs. vehicle-based). So it's possible for a carrier to have a visible, unremarkable Crash Indicator score and still have "Insufficient Data" in Vehicle Maintenance. The two categories draw on overlapping but non-identical data sets. Don't assume that a visible score in one BASIC means all your signals are populated.

How I Document This

For every carrier where I pull SAFER inspection records as part of my vetting:

1. Screenshot the full inspection record table — all pages if it goes beyond one screen. Save to the carrier's file with the date pulled.

2. Note the specific violation codes, inspection dates, and OOS designations in a one-paragraph summary.

3. Record my decision with reasoning. "Carrier MC-1247893 / DOT-3896441 has three § 393.52 violations in 19 weeks across four inspections. Pattern consistent with deferred brake maintenance. Declining to tender."

4. If tendering despite a yellow flag: document what offset it — strong insurance position, long authority history, confirmed dedicated equipment with VIN verification, dispatch call where I asked direct questions about maintenance scheduling.

That note takes 60 seconds. It's timestamped. It's attached to a screenshot that shows exactly what public data said, at the moment I was deciding. If I'm ever deposed about why I made a particular carrier selection decision, that's the record I want — not a vague memory of checking "the usual stuff."

The documentation isn't just defensive. After a few months of writing these notes, you start to recognize patterns faster. The second time you see two § 393.52 violations in 90 days, you don't need to talk yourself through it. You already know what it means.

---

— Mason Lavallet

Founder, DOTScreener.com