Your Carrier's OOS Rate Is Green. That Doesn't Mean They're Not Out of Service Right Now.

Three weeks ago I got on a call with a broker who'd just received a litigation hold letter. His carrier had a 16% vehicle OOS rate — well below the national average, nothing alarming. That number never flagged on his dashboard. What he didn't know: eleven days before the accident, one of that carrier's drivers was placed out of service at a weigh station in Georgia for a logbook violation. The broker's monitoring tool had pulled the inspection data. It just never surfaced the individual event.

The OOS rate looked fine. The OOS order was sitting right there in the inspection records. He'd never looked.

These are two completely different things. Most brokers treat them as the same check.

What the OOS Rate Is (and Isn't)

The vehicle out-of-service rate is an aggregate. FMCSA calculates it by dividing the number of vehicle inspections that resulted in at least one OOS violation by the total number of vehicle inspections, over a rolling 24-month window. Same math for the driver OOS rate. Same window.

FMCSA feeds the vehicle OOS rate into the Vehicle Maintenance BASIC. The driver OOS rate shows up in HOS Compliance and Driver Fitness. National averages sit around 20–21% for vehicle OOS and roughly 5–6% for driver OOS. Cross those averages and you're in FMCSA's intervention threshold territory.

If a carrier's vehicle OOS rate is 38%, that's a pattern. This fleet consistently has equipment that fails badly enough to get parked at roadside. That signal is worth taking seriously — and worth documenting your response to.

But here's what the rate does not tell you: whether any specific inspection in the last few weeks resulted in an OOS event. The rate is a mean. Averages hide recent events, especially for carriers with low-to-moderate inspection counts. A carrier with 10 inspections over 24 months who got hit with two OOS violations three months ago has a 20% rate — right at the national average. Nothing to see here. Except maybe there's quite a bit to see in those two specific inspections.

The rate is a trend. It is not a status.

What an OOS Order Actually Is

An OOS order is a point-in-time enforcement action. A roadside inspector — state police, federal DOT enforcement officer, CVSA-certified examiner at a weigh station — reviews a vehicle or driver and determines they're too dangerous to continue operating. Under 49 CFR § 396.9, the inspector affixes an OOS sticker to the vehicle. That vehicle cannot move, except to a repair facility, until the defects are corrected and a qualified person certifies in writing they've been fixed. The driver logs the defects on the Driver Vehicle Inspection Report (DVIR) per §§ 396.11 and 396.13, and the next driver to operate the vehicle has to sign off that it was repaired before they roll.

Driver OOS orders work the same way but track differently. A driver put OOS for hours-of-service violations under § 395.8 — failure to maintain accurate records of duty status, which is the technical name for falsifying a logbook — has to take a mandatory off-duty period before continuing. A driver OOS for a lapsed medical certificate under § 391.41 can't operate a CMV at all until that's resolved. Neither of those events touches the vehicle OOS rate. The driver OOS rate may move, depending on inspection counts, but the BASIC data lag means the aggregate might not reflect it for weeks.

The point is this: an OOS order is binary, immediate, and attached to a specific inspection event with a specific date, location, and violation code. It's not a trend. It's a fact: this vehicle was grounded because it was unsafe to operate, or this driver was pulled because they were out of hours or had faked their logs.

Why Brokers Conflate These Two Things

The SAFER company snapshot shows both on the same page. The aggregate OOS rates and BASIC percentile summary are right at the top — easy to screenshot and file. The individual inspection records are one more click, buried under "Inspections" in the detail. Most carrier monitoring tools show you the aggregate stats: BASIC percentiles, vehicle and driver OOS rates, current authority status. Those numbers were green. Most brokers stop there.

There's also the data lag problem. FMCSA's BASIC system carries roughly a 30–60 day delay on incorporating new inspection data into the percentile calculations. An OOS event that happened two weeks ago might not have moved the needle on the BASIC at all yet. But the individual inspection record appears in SAFER faster — typically within a week or two of the inspection date.

That means the inspection records are actually more current than the BASIC aggregates your monitoring tool is showing you.

When plaintiff's lawyers build their case, they don't pull your monitoring tool's dashboard screenshot. They pull the raw inspection data from FMCSA. And they ask you, under oath, whether you looked at it.

A Scenario Worth Walking Through

MC-1589234 / DOT-4127803. Three-year-old authority. Eighteen power units, flatbed. Vehicle OOS rate of 17.2% — below national average. Driver OOS rate of 4.1% — also clean. No active BASIC alerts. SAFER shows a "Satisfactory" rating from an investigation 14 months ago. On paper, a reasonable carrier.

Broker books a $38,000 flatbed load of structural steel, Chicago to Charlotte. T-call was completed (box checked, no detailed notes). Carrier agreement on file. COI shows $1M BIPD, $100K cargo coverage, listed the broker's brokerage as an additional insured on the cargo line.

What the broker didn't check: the inspection detail. Ten days before the load tendered, DOT stopped one of this carrier's trucks on I-65 in Indiana. The vehicle passed. But the driver had been systematically falsifying his logbook — compressing real hours into shorter entries. Driver placed OOS under § 395.8. The carrier put a different driver on the Charlotte load. That driver — same company, same dispatch pressure, same culture — ran 14.5 hours before the wreck in Virginia.

In discovery, plaintiff's counsel printed the inspection detail from the FMCSA website. The logbook OOS event from ten days before load tender was right there, timestamped, with the specific violation code. The broker's file had a BASIC percentile printout. Nothing showed they'd looked at individual inspections.

The verdict was $2.3 million. The broker's exposure came down to one question: was their diligence reasonable? Stopping at the summary page was not reasonable, once opposing counsel showed the jury what was one click deeper.

What § 396.9 Tells You at Load Tender

The regulation requires that every CMV be "inspected, repaired, and maintained in safe and proper operating condition." The OOS order is the enforcement mechanism when that standard is visibly violated. An active OOS order means an inspector already looked at this carrier's equipment and concluded it did not meet that standard.

The practical implication at load tender: if a carrier has had any OOS events in the last 30 to 60 days, that's material. Not necessarily a hard pass — a brake adjustment OOS that was corrected the same day and documented is very different from a driver caught running 18-hour shifts on falsified logs. But it's something you need to know, and something you need to have an opinion about in writing.

You cannot get this from the BASIC summary. You have to look at the inspections.

How I Check for OOS Orders (Not Just the Rate)

SAFER's company snapshot has an inspections section with aggregate counts. Below the summary there's a link to the detailed inspection list — individual records, sorted by date, with inspection type, location, and violation codes listed.

I pull that detail. I look specifically at the last 90 days, not the 24-month window. I'm asking:

• Any vehicle OOS events in the last 90 days? What failed — brakes, tires, lighting? Is the same violation showing up on multiple trucks?
• Any driver OOS events? HOS falsification is a culture problem, not an individual driver problem. One driver caught faking logs is a signal about how that company is run.
• How frequent are the inspections overall? Carriers that get stopped constantly may be getting targeted by enforcement officers who've noticed something. That's worth knowing.

I also ask directly on the T-call: "Any of your trucks or drivers currently out of service or under a maintenance restriction?" Most carriers answer honestly. The ones who don't — and then something goes wrong — have now lied to you in a documented conversation. That matters in discovery.

How I Document This

This note goes in the carrier file, attached to the load record:

Pulled FMCSA inspection detail on [date]. Reviewed last 90 days: [X] inspections, [Y] vehicle OOS events, [Z] driver OOS events. [If any: describe what failed and when, whether it was resolved, and what evidence of correction was provided.] No active OOS orders identified as of [date]. T-call with [name] on [date] confirmed no vehicles currently OOS. Screenshot of inspection detail attached.

If you found something and still proceeded — a brake adjustment from 45 days ago, corrected same day, repair invoice on file — document your reasoning. Why did you still tender? What specifically satisfied you the issue was closed?

That judgment, in writing, is what separates a defensible decision from an unexplained one. A blank file just means the jury gets to decide what you were thinking.

The OOS rate tells you about the pattern. The OOS order tells you about right now. Check both.

— Mason Lavallet

Founder, DOTScreener.com