Fourteen Trucks on the MCS-150. Three in the Inspection Record. What That Gap Is Telling You.

A carrier I screened last fall reported 14 power units on their MCS-150. MC-1693847, Opal Transport LLC, DOT-4388121, twenty-two months of authority out of Chattanooga. Clean SAFER snapshot in most categories. OOS rate at 6.1%, respectable. No BASIC alerts. Insurance current. I'd been about to add them to our approved list and move on.

Then I looked at their inspection history.

Eighteen months of FMCSA inspection data. Three VINs, total. The same three trucks appearing repeatedly across the Southeast. Not 14 trucks. Three. The other eleven existed on an MCS-150 form filed with the federal government. In the actual world of roadside inspections — Level I full-vehicle checks, weigh stations, post-accident reviews — eleven of this carrier's reported trucks had never appeared.

I called dispatch. "The others are leased to owner-operators." Reasonable answer. Completely unverifiable from the data I had. And eleven trucks' worth of safety history I had no access to.

That was the moment I stopped treating fleet count as a number and started treating it as a question.

What the MCS-150 Fleet Count Actually Is

Every active motor carrier files an MCS-150 — the Motor Carrier Identification Report — with FMCSA. Under 49 CFR § 390.19, carriers are required to file or update their MCS-150 at least once every 24 months. The form asks for the number of power units the carrier operates, the number of drivers, the type of freight hauled, and the states where they operate.

The number they put in the "power units" field is self-reported. FMCSA doesn't send an auditor to count the trucks. They don't cross-reference the answer against inspection records or VIN registrations. The carrier writes a number. The number goes into SAFER. Brokers see it and treat it like a fact.

It isn't. It's a disclosure, and disclosures are only as accurate as the party making them.

The other thing to understand about MCS-150 data: it's a snapshot, and the snapshot can be two years old before the carrier is required to update it. A carrier who had 14 trucks in April 2024 and sold six of them by October 2024 might not file an updated MCS-150 until April 2026. Their SAFER profile will show 14 power units for two years after the sale. The carrier you're looking at may not be the carrier you're seeing.

Why the Inspection-Confirmed VIN Count Tells a Different Story

Every time one of this carrier's trucks goes through a roadside inspection — a Level I North American Standard check, a weigh station pull-over, a post-accident inspection — the inspector records the vehicle identification number. That VIN gets tied to the carrier's DOT number in the federal inspection database.

The result, over time, is an inspection record that shows you which trucks have actually been operating under this carrier's authority. Not what they told the government they had. What the government actually caught on the road.

Under 49 CFR § 390.21, every commercial vehicle operating under a carrier's authority must be permanently marked with the carrier's legal name and their USDOT number. A truck operating under this carrier's authority and getting stopped at a roadside inspection will have that DOT number on it. If the VIN shows up in inspections under this carrier's DOT, it's real.

When the reported fleet is 14 trucks and the inspection record shows 3 VINs, eleven trucks are either:

1. Leased to independent owner-operators who operate under their own authority (not this carrier's)

2. Leased to owner-operators who operate under this carrier's authority but haven't been inspected

3. Inactive equipment — trucks the carrier owns but doesn't run

4. Equipment the carrier recently sold or returned

5. A filing the carrier never updated

Each of those scenarios has a different risk profile, and from the MCS-150 number alone, you can't tell which one you're looking at.

Why the Scenario Matters Before You Tender

Leased O/Os under their own authority. This is the most common explanation, and it's not automatically a problem. But it means the carrier's SAFER snapshot doesn't reflect those trucks or those drivers at all. Their OOS rate, their BASIC scores, their crash history — none of it applies to the majority of their operating fleet. You have safety data on three trucks and no data on eleven.

Leased O/Os under this carrier's authority. Now it's a different problem. Those trucks are running under the carrier's DOT number, which means their inspections should be appearing in this carrier's record. If they're not showing up after 18 months, that raises questions about how the trucks are marked, whether the carrier's supervision and dispatch is actually what it looks like on paper, or whether those O/Os have been running under a different DOT to avoid connecting their inspection history to this carrier's record.

Inactive equipment. A carrier with 14 trucks on the MCS-150 who's only running three of them is either managing their fleet down or struggling to find loads. Neither is a disqualifying fact, but fleet contraction in a carrier that's less than two years old warrants a conversation. Why are you running three trucks when you told FMCSA you had fourteen?

Stale filing. A carrier who hasn't updated their MCS-150 in the last two years legally doesn't have to. But a carrier who's actively operating and hasn't updated basic fleet information is showing you something about their administrative culture. FMCSA has specifically flagged MCS-150 non-updates as a risk indicator — not because the non-update is dangerous, but because it correlates with carriers who aren't paying attention to their compliance obligations in other areas either. Under the hours-of-service rules, the drug and alcohol testing requirements, the DQ file maintenance in Part 391 — all of it involves paperwork and systems. A carrier who doesn't keep their basic federal filing current may not be keeping those systems current either.

The point isn't that a fleet discrepancy means the carrier is dangerous. It means you don't actually know what you're approving when you look at the MCS-150 number.

The Follow-Up Question You Should Be Asking

Before you approve a carrier whose inspection-confirmed VIN count is materially lower than their MCS-150 power unit count, ask one question: "Which unit will be on this load, and what can you tell me about its inspection history?"

That question does three things. It tests whether the carrier can actually answer it — a carrier running a well-organized fleet knows their equipment. It identifies whether the specific truck that will move your freight has appeared in inspections at all. And it creates a documentation record showing that you specifically asked before you tendered.

If the carrier answers with a VIN, you can cross-reference that VIN in the FMCSA inspection database. You can see whether that specific unit has OOS violations, whether its inspection rate matches what a professionally operated truck should look like, and whether it's been maintained. That's a materially better vetting record than looking at the carrier's overall BASIC percentiles and moving on.

If the carrier can't answer — "we'll assign a driver closer to pick-up time" or "I'll have to check on that" — document that too. The absence of information before tender is part of your selection record under 49 CFR § 371.3.

What a Fleet Count Discrepancy Means After Montgomery

Before Montgomery v. Caribe Transport II, LLC — the Supreme Court's unanimous May 2026 decision holding that the FAAAA does not preempt state-law negligent-selection claims against freight brokers — the fleet count discrepancy was an interesting data point. After Montgomery, it's a gap in your documentation that a plaintiff's attorney can drive a verdict through.

Here's how it looks in discovery: the plaintiff asks what due diligence you did on the carrier before tendering the load. You produce your carrier file: the SAFER printout showing 14 power units, clean BASIC scores, valid insurance. Plaintiff's counsel then shows the inspection record: three VINs, 18 months of data. "You relied on safety statistics derived from these three trucks to make a decision about all fourteen?" If the answer is yes — if you never asked which specific unit was on the load — you're describing a vetting process that covered 21% of this carrier's reported fleet and assumed the other 79% was fine.

That's not a negligent selection argument. That's a negligent selection argument that already has the math in it.

How I Document This

When a carrier's inspection-confirmed VIN count is more than 20-25% below their reported MCS-150 fleet count, I treat that as a flag that goes into the carrier file before approval. My documentation includes:

• The MCS-150 power unit count at the time of review, with the screenshot date-stamped
• The number of unique VINs appearing in the FMCSA inspection history for that carrier and DOT
• The gap between those two numbers, noted explicitly
• The follow-up question I asked the carrier about the discrepancy and their answer (or non-answer)
• If they named a specific VIN for the load, the VIN and any inspection history I was able to pull for that unit specifically

DOTScreener's carrier screening shows the inspection-confirmed VINs from the FMCSA database — you can see at a glance which trucks have actually been stopped under this carrier's DOT. When I'm reviewing a new carrier, I check that number against the MCS-150 fleet count before I decide whether to ask any follow-up questions or add them to the approved list.

A carrier where the numbers match is not automatically safer than one where they don't. But a carrier where the numbers match is one whose operational reality I can see. That's where I start.

---

— Mason Lavallet

Founder, DOTScreener.com