The Date on That MCS-150 Is Telling You Something. Are You Reading It?

The Number Nobody Reads

Imagine this: you tender a load — electronics, $340,000, Memphis to Louisville, March 2024. Carrier is MC-1583247 / DOT-4182936. Satisfactory rating. Insurance active on FMCSA's L&I database. Bond current. Two BASIC scores in yellow, neither near the intervention threshold. You print the SAFER snapshot, attach it to the load in your TMS, and move on. Nine months later there's a serious accident. A plaintiff's attorney files in Tennessee state court under the negligent-selection theory the Supreme Court unanimously blessed in Montgomery v. Caribe Transport II, LLC — and discovery starts.

Among the exhibits your attorney gets a call about is that SAFER screenshot. Third block of data on the snapshot, under "ID/Operations Info," is a line that reads:

MCS-150 Form Date: 11/08/2019

You tendered the load in March 2024. The carrier hadn't updated their FMCSA filing in four and a half years.

Nobody on your team noticed. Plaintiff's counsel very much did.

---

What the MCS-150 Is and What the Update Requirement Actually Says

The MCS-150 — the Motor Carrier Identification Report — is the foundational registration document a carrier files when they get operating authority. It captures who they are and what they do: how many trucks, how many drivers, what commodities they haul, whether they're authorized-for-hire or private, and whether they carry hazardous materials.

The filing requirement is in 49 CFR § 390.19. Subsection (a) says carriers must file before beginning operations. Subsection (b) is the part almost nobody quotes: every carrier must update their MCS-150 every 24 months, following a schedule based on the last two digits of their USDOT number. Subsection (c) requires an updated filing within 30 days any time material information changes — new address, different operation type, new hazmat authority.

That biennial update isn't a technicality. The MCS-150 is how FMCSA knows the size, scope, and nature of a carrier's operation. When the data is four years old, FMCSA doesn't actually know what this carrier looks like anymore. Neither do you.

Enforcement against carriers for late MCS-150 updates is minimal. FMCSA has bigger things to do than chase down paperwork. So a lot of small carriers let the biennial update slide six months, nine months, sometimes much longer. I'm not saying a three-month-late update is disqualifying. I'm saying four years is a different story — and I want to explain why.

---

Three Things Go Stale on a Four-Year-Old MCS-150

Fleet count. The number of power units is self-reported on the MCS-150. A carrier that had 5 trucks in 2019 might have 25 now, or might have gone down to 2 leased units and one company truck. The number on a stale form doesn't tell you what they're actually running.

Here's the cross-check I use: pull the carrier's FMCSA SMS inspection history — it's public, available through the FMCSA SMS website or any decent vetting tool — and count the distinct VINs across the last 24 months of inspections. If the MCS-150 says 5 power units and the inspection history shows 31 inspection events spread across 19 different VINs, those numbers don't reconcile. A 5-truck carrier doesn't accumulate 19 distinct VINs worth of inspection history in two years through normal operations. That discrepancy is a question, and the question deserves an answer before you tender.

To be clear about what that discrepancy might mean: the carrier could have swapped out equipment and MCS-150 just shows older count; they could have grown significantly without updating their filing; or they could be running equipment they don't control, moving loads on capacity they didn't disclose. The last scenario is what keeps me up at night. A broker's carrier agreement is with MC-1583247. If MC-1583247 is moving freight on a truck owned by MC-4382091 using a driver MC-4382091 hired, your vetting of MC-1583247 covered none of the equipment or personnel actually involved in the loss.

Commodity codes. The MCS-150 includes an "Operation Information" section where the carrier identifies what they haul. A carrier who checked "general freight" and "building materials" in 2018 and is now doing temperature-controlled pharma or electronics hasn't updated their operational profile with FMCSA. This matters most with hazmat. Hazmat authority requires a separate registration and specific safety permit requirements under 49 CFR Part 385 for certain materials. If a carrier's stale MCS-150 doesn't show hazmat authority and you're tendering a hazmat load, that's a mismatch you need to resolve before the truck rolls — not after.

Driver count. Also self-reported. A carrier running 8 drivers in 2019 might be running 40 now, which means 40 drivers whose qualification files you've never thought to ask about, in a post-Montgomery world where reasonable care is the legal standard for broker due diligence.

---

Why This Shows Up in Discovery

Montgomery doesn't create a new legal standard. It just removes the preemption defense that kept state negligent-selection claims out of court in the 7th and 11th Circuits. The standard has always been reasonable care — did you act as a reasonably careful broker would act when selecting this carrier? The content of that standard is now getting litigated in state courts all over the country.

Reasonable care means you checked what was there to check. SAFER is public. The MCS-150 Form Date is on SAFER. It costs nothing to read it. If you printed a SAFER snapshot on the day of tender and that snapshot shows a 2019 MCS-150 date, that date was in your hands. The question plaintiff's attorney is going to ask your 30(b)(6) witness isn't exotic:

"Did you look at the MCS-150 Form Date on this snapshot?"

"Do you know how many trucks this carrier was operating on the date of tender?"

"Is the answer to that question somewhere in your file?"

If the answer to all three is "no," you've handed opposing counsel three consecutive answers that add up to "this broker didn't look at publicly available information." That's not negligence per se. But it's a building block.

The other thing that shows up in discovery: the discrepancy between reported fleet count and actual inspection history. If plaintiff's attorney can show that the carrier's SAFER inspection history is inconsistent with a 5-truck operation — and your file doesn't show that you noticed, or asked, or noted your assessment — that's a gap in your due diligence that becomes part of the negligent-selection narrative.

---

What I Actually Do at Tender

When I pull a SAFER snapshot, I look at the MCS-150 Form Date first. The math takes five seconds:

• Form date more than 24 months before today: the carrier is out of compliance with § 390.19(b). Not automatically disqualifying, but noted.
• Form date more than 30 months old: I call the carrier and ask directly. When did you last update your FMCSA registration? How many trucks are you running right now? The call takes three minutes.
• Form date more than 48 months old: that's a hard look. Not a hard no by itself, but I need a good explanation.

The fleet count cross-check I run every time, stale filing or not. Inspection history is public and the VIN count is right there. If the reported power units don't match what the inspection history implies, I note the discrepancy in the file and document my assessment of it. Sometimes there's a simple explanation: the carrier just swapped from older equipment. Sometimes there isn't.

If the MCS-150 commodity codes don't match what they're being tendered — general freight carrier getting a hazmat load, household goods carrier doing LTL electronics — that's a call. Not because the carrier is necessarily doing anything wrong, but because I want to know whether their authority actually covers the freight type, and I want that conversation in the file.

I'm not a lawyer. I'm not giving legal advice. But I know what's on a SAFER snapshot and I know what "reasonable care" means in plain English.

---

How I Document This

In the carrier record for each load, I log:

• MCS-150 Form Date (the actual date from SAFER)
• Months since last update (calculated, not approximated)
• Whether the fleet count on MCS-150 is roughly consistent with inspection history VINs
• If I called the carrier about a discrepancy, who I spoke with, what they said, and whether the answer was satisfactory

If the MCS-150 is current and the fleet count is consistent, a single line in the file covers it. If there's a discrepancy, I write two or three sentences explaining why I tendered anyway, or why I didn't. That note is my decision record. It shows that I looked, I thought about it, and I made a judgment call — which is all anyone can ask of a broker.

The carriers who can't answer "how many trucks do you run?" in 90 seconds don't make it to tender. That question is not a trick.

---

The Bottom Line

A four-year-old MCS-150 doesn't make a carrier unsafe. What it tells you is that this carrier hasn't paid attention to their FMCSA compliance housekeeping in four years. That's a data point about organizational discipline — not a verdict, but not nothing either. Combine it with a fleet-count discrepancy and commodity codes that don't match the load, and you've got a pattern worth asking about.

The check takes 30 seconds. The MCS-150 Form Date is on the SAFER snapshot you're already pulling. Read it.

After Montgomery, the publicly available information is your file from the plaintiff's perspective. Act accordingly.

---

— Mason Lavallet

Founder, DOTScreener.com