The Carrier That Was Shut Down Last Year — and You Didn't Know It

I got a call from a claims adjuster two years ago. She wanted to know about a carrier we had used — MC-1478362 / DOT-3891047 — a dry van outfit out of Laredo. Clean SAFER pull. Satisfactory rating. Eight months of authority. We had tendered a produce run to them without a second thought.

Turns out the owner of that company was also the principal officer of MC-1029847 / DOT-2744190, which had been shut down fourteen months earlier under a federal OOS order after a fatality in Tennessee. Different company name. Different MC number. Same guy. Same trucks, VINs and all, re-registered under the new entity. The injury plaintiff's attorney had matched them in about forty-five minutes.

That's the chameleon carrier problem. And it doesn't show up on a standard SAFER pull.

What FMCSA Enforcement Actually Does — and Doesn't Do

When FMCSA determines a carrier is unfit, it issues an Out-of-Service order under 49 CFR § 385.105. The carrier is prohibited from operating. They cannot tender loads, they cannot move freight, they're done.

But "done" is not permanent and it's not always tracked to the principals. The order attaches to the MC number and the DOT number. It does not attach to the names, social security numbers, or EINs of the officers who ran the operation. If those same people go file new authority — different company name, new MC number, new DOT number — they get a clean sheet in the FMCSA system. The only thing FMCSA might flag is if the applicant discloses prior authority, which they're supposed to do on the OP-1 application. People sometimes don't.

The enforcement history under the old number sits there, accessible to anyone who knows to look. The problem is most brokers are checking the new number and never think to look for the old one.

The Pattern Has a Name

The trucking industry calls it a chameleon carrier. FMCSA has been aware of the pattern for years. A carrier accrues violations, BASIC scores climb, enforcement takes action. The principals dissolve the entity, file new authority, buy the same equipment, hire back the same drivers, and start fresh. From the outside — from a broker's SAFER pull on the new MC — they look like an eight-month-old company with no violations and no crashes. The reality is they're a ten-year-old safety nightmare wearing a new name.

Some variations are more sophisticated. They'll park the trucks for sixty days, run a couple of clean inspections under the new authority to establish a baseline, and then go back to operating exactly as before. By the time the BASIC scores start climbing again, they've moved another few thousand loads.

The tell isn't on the new record. It's in the gaps between records.

What You Should Be Looking For

The principals. That's where it starts. If an owner, officer, or director of the carrier you're looking at also appears on another MC number that's now inactive or under enforcement action, you have a red flag. The SAFER database lists the legal name and address of the carrier, but it does not surface the officers' other affiliations automatically.

The physical address. Chameleon carriers often operate out of the same yard, same address, sometimes the same phone number. When the new MC shares an address with a revoked or OOS-ordered carrier, that's not a coincidence.

The equipment. If you can get the power unit VINs on file with FMCSA for the old entity and compare them to what the new entity is running, and they overlap significantly, that's a strong indicator. The trucks didn't go anywhere. Just the paperwork changed.

The timing. A carrier that filed for authority shortly after a related entity received an OOS order or enforcement action is worth additional scrutiny. Eight months of authority with a strong operational pattern from day one sometimes means they weren't actually new to the business.

None of this is conclusive on its own. You're pattern-matching, not prosecuting. But when multiple indicators line up, you're looking at a carrier you shouldn't touch until you can explain each one.

The FMCSR Problem for Brokers

Here's the regulatory bind. 49 CFR § 385.107 lays out the criteria FMCSA uses to determine a carrier is unfit. The determination is carrier-specific. FMCSA doesn't track enforcement across related entities in a way that automatically surfaces on the new MC pull.

The negligent selection standard doesn't care about that limitation. Montgomery v. Caribe Transport II confirmed what most plaintiff's attorneys already knew: brokers can be held liable in state court for negligent selection of a carrier. The question the jury asks isn't "did FMCSA's system flag this?" It's "did you do what a reasonably careful broker would do?"

A reasonably careful broker, under cross-examination, who never checked whether the principals of MC-1478362 had run a prior company, is in a rough spot. The plaintiff's attorney will show the jury the OOS order on the prior entity. They'll show the jury the overlapping VINs. They'll ask why a freight broker whose job is to select safe carriers never checked whether the people running this company had already been shut down once for killing someone.

I don't have a good answer to that question if I didn't run the check.

A Real Scenario, Fictional Numbers

Imagine this: it's October. You're booking a high-value electronics shipment — $380K of gear — from Memphis to Atlanta. The carrier pulls up clean. MC-2218947, DOT-4127831, Satisfactory rating, authority active eleven months, zero crashes in SAFER, one Level I inspection passed. You book it.

Six weeks later you get a litigation hold letter. There was an accident outside Birmingham. The driver ran a red at 2 AM, fell asleep at the wheel. Two people in a sedan died.

The plaintiff's attorney does what plaintiff's attorneys do now. They pull the principals of MC-2218947 and find they match the principals of MC-1841054 / DOT-3782993, which received a federal OOS order seventeen months ago after a series of driver fitness violations under Part 391. The trucks listed under the new MC include four VINs that were on the old MC's equipment list. The attorney subpoenas your file and asks why you didn't know.

At that point, "the SAFER pull looked fine" is not a defense. It's evidence that you didn't look hard enough.

This Is Exactly What Reincarnation Screening Is For

This is one of the specific checks DOTScreener runs on every carrier. The screen compares principals, addresses, and equipment against known enforcement actions and revoked authority on related entities. When a new MC is associated with a principal officer who also appears on a prior carrier with OOS orders, enforcement actions, or a revocation, the screen flags it.

It's not foolproof — the quality of the underlying data is only as good as what FMCSA has, and carriers that are genuinely careful about separating their identities can sometimes slip through a first pass. But for the most common pattern — same person, same address, new name filed shortly after a shutdown — it catches it.

Most brokers don't run this check at all. They run a SAFER pull, look at the BASIC scores, verify the insurance certificate, and move on. That's the minimum floor. It's not due diligence anymore.

The Minimum Is Not the Standard Anymore

Post-Montgomery, the regulatory floor on broker due diligence is exactly that — a floor. Verifying active authority, checking a valid insurance certificate, looking at BASIC scores if they're accessible. That's what FMCSA requires brokers to document under 49 CFR § 371.3.

That's not what a jury or a plaintiff's attorney means by due diligence. They mean: did you actually check whether this company and the people running it had a history of operating unsafe trucks? A 14-month-old OOS order on a related entity is not obscure information. It's in the public FMCSA database. The question is whether anyone looked.

Chameleon carriers exist because the barrier to filing new authority is low and the incentive to escape a bad safety record is high. Some of them go on to operate safely under the new structure. Some don't. The reincarnation screen doesn't automatically disqualify a carrier — it flags something that needs a second look. That's the whole point.

Run the check. Document what it showed. If something came up, document how you evaluated it. That file is your defense if something goes wrong — and given where federal negligent selection law sits right now, assuming it won't go wrong is not a strategy.

How I Document This

When a carrier passes the reincarnation check, I log it. Not just "reincarnation check run" — that's meaningless in a deposition. I log the date of the check, what data sources were checked, and the result: no flagged principals, no overlapping addresses on OOS or revoked entities. The screen ID goes in the Carrier Selection Record so there's a timestamp and a trail.

If the check surfaces a concern — overlapping address, a principal who appears on a revoked entity — I document the follow-up. I note what I looked at to evaluate whether it's the same operation, what I concluded, and why I made the decision I made. If I still tendered after flagging something, I document the business rationale and who approved it.

A carrier you approved with a documented red flag and documented follow-up is in a very different litigation position than a carrier you approved with a red flag you never noticed. Every carrier approval in DOTScreener generates a Carrier Selection Record that timestamps this entire sequence. The reincarnation flag result is part of that record: pass or flag, check date, entity references evaluated. The record exports as a PDF, signed with the approver's identity and timestamp.

When the litigation hold letter comes, you want to be the broker who can produce that file in forty-eight hours — not the one still searching email threads trying to reconstruct what you thought you checked.

— Mason Lavallet

Founder, DOTScreener.com