The Date Nobody Checks in the SAFER Snapshot — and What a Stale One Actually Tells You

I was vetting a flatbed carrier — MC-2847193, DOT-4183026 — for a $186,000 structural steel coil load out of Birmingham last February. Good rate, equipment available, they ran that corridor regularly. SAFER looked solid: zero crashes in the past 24 months, 21 inspections, four driver violations (one seat belt, three ELD), no equipment OOS, Satisfactory rating. Insurance was current. Driver Fitness BASIC at the 41st percentile. Nothing jumped out.

I was about two-thirds through the review when I caught something I almost never see brokers flag: the MCS-150 last update date said 38 months ago.

The legal requirement is 24.

This carrier was 14 months past the deadline for a mandatory federal filing, and they were still operating, still had active authority, still had the Satisfactory rating sitting there like a gold star.

Nobody had flagged it. The carrier certainly hadn't mentioned it. And if I'd been moving fast — if I'd been on load four of the day and running through the checklist quick — I'd have missed it too.

What 49 CFR § 390.19 Actually Requires

Every motor carrier that operates commercial motor vehicles in interstate or foreign commerce is required to file the MCS-150 (Motor Carrier Identification Report) to receive a USDOT number, and then update that filing biennially. The update schedule runs on a rolling calendar based on the last two digits of the carrier's USDOT number — FMCSA staggers the deadlines so they're not all hitting at once. Miss your window and you're technically in violation.

The civil penalty under § 390.19(g) can reach $1,000 per violation per day. In practice, FMCSA rarely sends a carrier a penalty notice for a late MCS-150 alone — they have bigger fish. Carriers generally don't lose their authority over this in isolation. But here's the thing: that low enforcement rate is exactly why a stale filing is useful information. It's not a trap FMCSA set. It's just a form the carrier couldn't be bothered to file.

The MCS-150 isn't trivial paperwork. It covers: the number of power units operated, the number of drivers, whether the operation is for-hire or private, interstate or intrastate, the commodities hauled, and whether the carrier handles hazardous materials. These fields feed into FMCSA's data for the Crash Indicator and other SMS BASICs — the underlying denominators that turn inspection counts into percentile scores. When a carrier's fleet count in the MCS-150 is 18 months out of date, the data FMCSA is using to calculate that carrier's relative performance might be wrong.

The Filing as a Proxy

Here's where I get more interested than the reg itself warrants.

A carrier that's 14 months past a routine biennial filing has told you something real about how they manage compliance. Not through a violation or a crash — just through an omission. The MCS-150 is not a complex form. It takes maybe 20 minutes to update online if everything's the same as last time. There's no third-party inspection required. The carrier just has to log in and confirm their information or update what changed.

That's it. That's the entire ask.

If that's too much — if amid all the other things a trucking company does, maintaining a current federal registration slips by for 14 months — then what I want to know is: what else is slipping? Pre-trip inspection records under 49 CFR § 396.11? Driver qualification file updates under Part 391? Drug testing program files under Part 382? The administrative discipline that makes you update a 20-minute form on a two-year cycle is the same discipline that makes you maintain a systematic driver file and sign off on pre-trip reports every day.

I'm not saying a stale MCS-150 means the carrier is running an unsafe operation. I'm saying it's a data point. And it clusters with other data points. A carrier with an overdue filing who also has a spotty maintenance BASIC and whose drug testing program shows no queries in the clearinghouse for the past 18 months is a different risk than a carrier who's 38 months stale on the MCS-150 but has had zero OOS violations across 40 Level I inspections. Context matters. But the date matters too.

What Changes in the Filing Tell You

Here's the angle most brokers never consider even if they do catch the update date: what DID the carrier file when they last updated, and what changed from the time before?

The SAFER snapshot shows you the current MCS-150 data. It doesn't show you the filing history in most web views. But there are patterns you can sometimes detect: a carrier whose current MCS-150 shows 8 power units but whose historical crash data includes incidents spread across what looks like a 30-unit operation is worth a call. A carrier who went from "for-hire, interstate" to "private, intrastate" on their last update and then started showing up on load boards as for-hire is somebody who changed their registration to move outside federal oversight and then didn't fully follow through.

The commodity change is the one that spooks me most. A carrier who started as general freight, switched to household goods (a commodity class with a whole separate federal overlay under the Surface Transportation Board's tariff requirements), and is now quoting you on automotive parts — that's a lot of operational pivoting, and the MCS-150 trail is the only footprint of it.

When a carrier updates their filing right after a compliance review, that's also a signal. Not always a bad one. Sometimes a compliance review finds the carrier has added trucks and drivers and they update to reflect reality. But sometimes a carrier downsizes on paper — files a reduced power unit count — right after a bad CSA period, which changes their exposure denominators in SMS and can pull percentile scores down even if nothing about their actual operation changed. You're not going to catch that from SAFER alone. But if you know when the last MCS-150 was filed and you look at the timing against the carrier's BASIC score trajectory, it can sharpen the picture.

The Load I Didn't Take

Back to MC-2847193.

I called the carrier's dispatcher to run through the load details. Routine call. About four minutes in I mentioned the MCS-150 and asked if they were aware it was overdue. The answer was a long pause followed by "I'm not sure who handles that" and then a redirect to the rate confirmation.

That was enough for me.

Not because an unanswered question about a form is a disqualifying offense. It's because of what it suggests about the carrier's internal organization. Who does handle regulatory filings at this operation? If nobody knows, who's watching the drug testing calendar? Who's tracking driver medical certificate renewals under § 391.45? Who's making sure the pre-trip records under § 396.11 are getting signed and filed?

I documented the call, noted the overdue MCS-150 date, noted the dispatcher's response, and declined the load.

The rate was competitive. The SAFER profile was clean on the surface. But a $186,000 load is not a load where "probably fine" is good enough. I sent it to a carrier I'd screened four months earlier with a current MCS-150, 31 Level II and III inspections, one violation, and a dispatcher who answered my question about their drug testing program by pulling up the date of their last third-party audit.

That carrier charged me $180 more to run the lane.

Worth every dollar.

The Montgomery Angle

Since May 2026, freight brokers can be sued in state court for negligently selecting an unsafe carrier. The Supreme Court's decision in Montgomery v. Caribe Transport II settled the preemption question. What's left is the merits question: what did you know, when did you know it, and what did you do about it?

A plaintiff's attorney working a post-crash discovery request is going to pull every bit of SAFER data that existed on the day you approved the carrier. If they find that the carrier's MCS-150 was 14 months overdue on that date, the question is simple: did you check it? If the answer is no — if your screening record shows an insurance check and a BASIC score pull but nothing about the MCS-150 update date — the follow-up question is why not. That's a question you don't want to answer on a deposition transcript.

You don't need to make it complicated. You just need to check the date, document what you found, and note whether it's within the 24-month window or not. If it's outside, note that you saw it, and note what (if anything) it changed about your decision.

How I Document This

In every carrier screening record, I add a line for the MCS-150 last update date pulled from SAFER. If it's within 24 months, I note the date and move on. If it's past 24 months, I note the specific overage — e.g., "MCS-150 last updated [date], 29 months ago, 5 months past the § 390.19(b) biennial deadline" — and add a brief notation of whether I followed up with the carrier and what they said. If I asked and got a substantive answer (they know who handles it, they're aware it's late, they've filed the update and it's pending), I log that. If I asked and got a redirect or a blank stare, I log that too.

The whole thing takes about 90 seconds. But it's on the record. If the carrier moves the load and something goes wrong, I can show exactly what I checked and what I knew.

The MCS-150 date isn't the most dramatic thing in a carrier's file. But it's a free data point sitting in plain sight in every SAFER profile, it takes seconds to find, and it tells you something real about how the carrier runs their operation when FMCSA isn't watching. After Montgomery, you want every free signal you can get.

— Mason Lavallet

Founder, DOTScreener.com