All articles
Broker Guides September 15, 2026 9 min read

Your Carrier's OOS Rate Looks Fine. Their Maintenance Program Is a Different Story.

A low out-of-service rate doesn't mean a carrier has a functional maintenance program. After Montgomery v. Caribe Transport II, plaintiffs' attorneys know to subpoena inspection records and look for patterns in 49 CFR § 396.3 violations — and most brokers have no idea what that citation even means.

Three months after the accident, a plaintiff's attorney called my contact at a mid-size brokerage for a deposition. The broker had done their homework: MC number pulled, insurance verified, safety rating checked (Satisfactory), OOS rate below the national average. Clean file on paper.

Then the plaintiff's attorney showed them a printout. Fourteen inspections on the carrier's equipment over the preceding 18 months. Seven of them had the same violation code: 396.3(a)(1). The attorney asked, simply: "Were you aware that this carrier had been cited seven times for failing to systematically maintain their vehicles before you tendered MC-1384729 a load on September 8th?"

The broker didn't know what 396.3(a)(1) was. That was the problem.

What 49 CFR § 396.3 Actually Says

Most brokers in my world know 49 CFR § 396.13. That's the pre-trip inspection requirement — the one that shows up in FMCSA's Vehicle Maintenance BASIC and means a driver has to verify their vehicle is in safe operating condition before every trip. It's the citation that generates the most BASIC alerts for smaller carriers.

Section 396.3 is different, and it's upstream of all of that.

Under 49 CFR § 396.3(a), every motor carrier "must systematically inspect, repair, and maintain, or cause to be systematically inspected, repaired, and maintained, all motor vehicles and intermodal equipment subject to its control." The word that matters is systematically. It's not enough to fix things when they break. The regulation requires a carrier to have a maintenance program — scheduled intervals, documented records, a process that runs whether or not a driver files a DVIR complaint.

Section 396.3(b) says the carrier has to keep records of inspections, maintenance, and repairs for a minimum of 14 months (or 30 days on a vehicle no longer in their possession). Those records have to be available for inspection by FMCSA.

The "so what" at load-tender time: when you see repeated 396.3(a)(1) violations in a carrier's inspection history, you're not looking at a driver failing a pre-trip. You're looking at an organization that doesn't have a functional maintenance system. That's a categorically different risk.

Why It Shows Up in Discovery More Than Most Brokers Expect

After Montgomery v. Caribe Transport II, LLC was decided unanimously in May of this year, state-court negligent selection claims against brokers are viable everywhere in the country. Plaintiffs' attorneys have been updating their playbooks. The good ones have always known to subpoena FMCSA inspection data; now they're doing it more aggressively and they know exactly what to look for.

Here's what they find useful about 396.3: it's organizational evidence. A § 396.13 violation tells a jury a driver didn't complete a pre-trip checklist. A § 396.3(a)(1) violation tells a jury the carrier didn't have a system in place to make sure that happened consistently. Multiple § 396.3(a)(1) violations over 12-18 months tell a jury the carrier knew about the problem, got cited for it, and didn't fix their processes.

That's the pattern that makes juries angry. Not a single brake violation. A broken culture, documented by FMCSA's own field inspectors.

I've sat across from brokers who looked at a carrier's 18% driver OOS rate, compared it to the 34% national average, and called it a clean carrier. Nobody ever asked what the underlying violations were. Seven 396.3(a)(1) citations in 14 inspections is an 87% rate on that specific systemic failure. But if you only look at the aggregate OOS percentage, you miss it completely.

Reading § 396.3 Violations in SAFER Inspection Records

SAFER's inspection data doesn't categorize violations by section in the summary view — you get total inspections, total violations, and OOS percentages for driver and vehicle categories. To see the specific citation, you have to pull the inspection detail.

The shortcut: go to the carrier's SMS Inspection history and sort by vehicle violations. Download the CSV if you're doing this seriously. Carrier with, say, DOT-4129876 — you're looking at the "Violation Code" column. 396.3 violations will appear as 396.3A (maintenance system generally), 396.3A1 (the specific failure to systematically inspect and maintain), or occasionally 396.3A1A, 396.3A1B as subcategories.

A single 396.3 violation among 40 inspections over two years isn't alarming on its own — these things happen. What flags the systemic problem is repetition: same violation code, multiple inspections, spread over time. If FMCSA's roadside inspectors are finding this on your carrier's trucks every few months, that's not bad luck. That's a carrier that doesn't have a maintenance program that works.

The other thing to look for: 396.3 violations combined with brake violations (393.45, 393.48) or brake adjustment violations (393.47). Brake defects are the most common cause of truck fatalities in the data I've seen cited in NTSB reports. When you see § 396.3(a)(1) on the same carrier alongside repeat brake violations, that combination is what a plaintiff's expert witness is going to stand up in court and call a predictable failure.

The OOS Rate Isn't Wrong — It's Just Incomplete

I want to be clear: the vehicle OOS rate is still useful. A carrier at 45% vehicle OOS on 40 inspections is a hard no and should be. But the OOS rate tells you about violations that were serious enough to take a vehicle out of service at the roadside. It doesn't tell you about the pattern of systemic failures that might produce a catastrophic accident six months from now.

Section 396.3 violations often don't generate an OOS order. A carrier can get cited for inadequate maintenance records — failing to keep the documentation required under § 396.3(b) — without any vehicle being pulled from service. That violation doesn't move the OOS needle at all. But when those records get subpoenaed in litigation, their absence is devastating. The regulation required them. The carrier didn't have them. Discovery proves it.

This is why I tell brokers: the OOS rate is your first screen. The underlying violation codes are your actual vetting. If you're looking at a carrier with 20+ inspections and you're only reading the OOS percentage line, you're missing half the picture.

What § 396.3 Tells You About Safety Culture

When a carrier gets cited for § 396.3 violations, it usually means one of a few things:

The carrier doesn't have a written maintenance schedule or can't produce it. FMCSA inspectors doing a compliance review often ask for the carrier's maintenance policies as part of the safety management controls assessment. "We fix things when drivers complain" is not a maintenance system under § 396.3.

The carrier has a maintenance program on paper but doesn't follow it. Written policy, no records to back it up. This is the version that looks the worst in discovery — the carrier told FMCSA and told brokers they had a program, the records prove they didn't follow it.

The carrier has outsourced maintenance to owner-operators who aren't compliant. Under § 376.12(j), motor carriers using leased owner-operators are still responsible for vehicle safety. A carrier who "inspects" vehicles by accepting the O/O's self-attestation and then gets cited under § 396.3 has a paper trail that says they knew what the regulation required and substituted a weaker process anyway.

None of this shows up in a quick MC pull.

Connecting It to DOTScreener

When I built DOTScreener, I wanted the Carrier Selection Record to capture not just whether a carrier was authorized and insured, but what the specific risk signals were on the day you tendered the load. That means recording Vehicle Maintenance BASIC percentile, inspection count, and — where we surface it — the pattern of underlying violations.

The inspection data in the SAFER snapshot is the raw material. A broker who looks at MC-1384729 and notes only "Vehicle Maintenance BASIC: 34th percentile — below intervention threshold" has technically checked the box. A broker who records "Vehicle Maintenance BASIC: 34th percentile, 14 inspections, 7 citations for 396.3(a)(1) systematic maintenance violations, pattern consistent, last citation 23 days ago" has built a record that shows they understood what they were looking at.

When Continuous Monitoring catches a new inspection with a 396.3 citation on a carrier you're using actively, that's the trigger to re-file the Carrier Selection Record. Not because one new inspection changes everything, but because the pattern either gets worse (and you need to act) or you've documented that you noticed and reassessed.

How I Document This

When a carrier's vehicle inspection history shows 396.3 violations, here's what goes in the file:

  • Screenshot of the SAFER inspection CSV filtered to show all inspections in the last 24 months
  • A note identifying the specific violation codes present and how many times each appeared
  • A plain-English assessment: "Carrier has 7 citations for failure to systematically maintain vehicles under 49 CFR § 396.3(a)(1) in 14 inspections (50% hit rate on this violation). No OOS orders, but pattern indicates inadequate maintenance program at the organizational level. Carrier approved conditional on re-verification in 60 days."

If the violation count is high enough that I wouldn't approve the carrier, that goes in the file too, with the specific citation count and threshold. "Declined — 396.3(a)(1) pattern across 7 of 14 inspections, consistent with broken maintenance system. MC-1384729 removed from approved carrier list."

Both of those records are useful under deposition. One shows why you used the carrier anyway and what safeguards you put in place. The other shows you applied real judgment, not just a checkbox.

The absence of any such record — which is what most brokers have — is the one thing no explanation can fix after an accident.

The Part Nobody Wants to Hear

Most broker-carrier vetting processes don't actually look at violation codes. They look at the OOS rate. They look at the BASIC percentile. They pull insurance. They collect a carrier packet. And then they assume that if the OOS rate is below the intervention threshold, the carrier is safe enough to tender.

That assumption worked out fine in many jurisdictions before May 14, 2026. Post-Montgomery, it's an open question whether it works anywhere.

The plaintiff's attorney in that deposition I mentioned didn't ask the broker to have been perfect. They asked the broker to have looked. To have seen the pattern. To have formed any judgment at all about what those seven violations meant.

The broker hadn't looked. They'd checked a box.

I started building DOTScreener because I watched brokers I respected get blindsided in exactly this way — not because they were negligent, but because the tools they had didn't surface the signal. The § 396.3 pattern is in FMCSA's public data. It costs nothing to access. Most brokers just don't know to look for it.

Now you do.

How I Document This

When a carrier has Vehicle Maintenance BASIC violations in my screening, the file shows:

1. The SAFER inspection count and date range pulled (I capture this at the time of vetting, not retroactively)

2. The specific violation codes from the inspection detail — 396.3(a)(1), 393.45, etc. — and how often each appears

3. My actual reasoning for approval or decline, in plain English, with the data that drove it

4. If approved despite elevated Vehicle Maintenance violations, the specific compensating factors (high inspection count with low OOS rate, recent corrective action evidence, etc.)

That note is dated, timestamped by the system, and tied to the load tender record. It's not a perfect shield. But it's the difference between "we relied on a BASIC score" and "we reviewed the underlying inspection data and made a documented, reasoned judgment."

The first answer doesn't survive a deposition. The second one gives you a fighting chance.

— Mason Lavallet

Founder, DOTScreener.com

DOTScreener

Automate your carrier vetting

DOTScreener runs every check in this article automatically — live FMCSA data, documented decisions, tamper-evident audit trail.

Go deeper

Related Articles