The Carrier That Isn't New: How to Spot a Chameleon Before You Tender

A broker I know — good at his job, been in freight for twelve years — put a load of networking equipment on a carrier out of Memphis last fall. $380,000 of product. The MC number was eight months old. Clean snapshot. No BASICs in alert. Valid BIPD coverage confirmed through L&I. He ran his standard check and moved the load. The truck went dark for 32 hours.

When he finally reached the driver, it came out that the principal behind that carrier had already surrendered two previous MC numbers. One was revoked by FMCSA after a pattern of OOS violations. The other was abandoned after a crash that killed a family of three on I-40. Different LLC names. Different DBA. Same guy, same yard in Shelby County, half the same fleet.

That's a chameleon carrier. New paint, same snake.

What "chameleon" actually means

FMCSA uses the term to describe a motor carrier that closes down under one authority and reopens under a new MC number to escape a revoked or unsatisfactory safety record. The new entity typically has the same officers, owners, or managers in operational control; the same or overlapping equipment; the same physical address or terminal; and a clean new-entrant snapshot that tells you almost nothing useful.

FMCSA has tools designed to catch these situations during the new-entrant safety audit process under 49 CFR Part 385, Subpart D. The audit is supposed to flag carriers with problematic histories during their first 18 months. In practice, if the principals are sufficiently separated on paper — a spouse listed as sole owner, a business partner as the registered officer, a shelf LLC with a different name — the flag doesn't always fire. And by the time a broker is looking at the SAFER snapshot, the carrier has cleared audit and looks legitimate.

Most brokers stop right there. That's the problem.

The regulatory hook at tender time

When a carrier files its MCS-150 — required under 49 CFR § 390.19 — they list the name, title, and contact information for each principal officer and owner. That form is the data source. The officers on the current MC are public record. So are the officers on any prior MC they were associated with, including revoked ones.

The "so what" at tender time: if you pull MC-1187432 on SAFER and see the registered owner is listed as Tomás Reyes, your job is to check whether Tomás Reyes appears as a principal on any other MC — especially one that's been revoked or is sitting inactive with a bad history. You're not running a federal background check. You're doing a five-minute name and address cross-reference that most brokers skip entirely.

§ 390.19 also requires carriers to update their MCS-150 every two years and within 30 days of certain changes. A carrier that changed principals recently and hasn't updated the form is in violation — and that filing gap is itself a signal worth noting.

The four things I actually check

Officer names from the current MCS-150. Pull the carrier's company snapshot on SAFER. The MCS-150 data shows who filed it and when. Write down the principal names. You'll use them in the next step.

A SAFER carrier search on each principal name. FMCSA's system lets you search by carrier name. What I do: search the principal's full name as a DBA or company name component to see if any other entities are associated with it. It's imperfect — you won't catch everyone — but it surfaces the obvious cases. The guy who ran "Reyes Transport LLC" from Shelby County from 2019 through 2021 who now runs "RT Logistics Group LLC" from the same address will show up. Most chameleons aren't sophisticated enough to scrub this.

The physical address against other MC filings. The carrier's address is in SAFER. If two different carriers share an address — especially a non-terminal address like a residential street or a small rural industrial park — that's worth a call before tender. Two separate legitimate carriers can share a yard, but it's rare enough to ask about.

The Operating Authority history and L&I status on any prior entities you find. If a SAFER name search surfaces a prior entity with the same principal, check that entity's authority status. Revoked? Inactive after a fatal crash? Surrendered right before an enforcement action? That history doesn't disappear just because the MC number does. It's sitting right there in FMCSA's system, waiting for someone to look.

None of this is foolproof. A chameleon who uses a business partner as the listed officer and operates from a different address is harder to catch without deeper tools. But most of them don't go that far. Most are opportunistic, not methodical.

Why the authority age and OOS rate combination matters here

A brand-new authority with a zero OOS rate looks pristine. On a carrier that's been active for three months and run a handful of loads, zero inspections is completely normal. On a carrier that's supposedly been operating in the Southeast for 14 months — a region with active roadside enforcement — zero inspections should raise a question. Where have they been running?

Chameleon carriers often stay below the inspection radar early on. They route carefully, keep the profile low while rebuilding their book of business. A clean BASIC scorecard on a 12-month carrier with very few inspections is not a reassuring sign. It's a gap in the record.

Compare that to a 14-month carrier with 22 inspections logged and a 14% OOS rate. That's not great, but it's real operating history I can actually read. I know what types of violations are driving it. The zero-inspection carrier is a black box, and I have no idea what's inside it.

Authority age paired with inspection count tells you more than the percentile scores do. A carrier with eight months of authority and three inspections — all clean — is very different from one with eight months and zero. Ask yourself which one is easier to fake.

What changed after Montgomery

Before Montgomery v. Caribe Transport II, LLC, decided unanimously by the Supreme Court on May 14, 2026, the FAAAA preemption argument gave brokers some federal court cover against state negligent-selection claims. That argument is gone. State courts can now hear those claims, and plaintiff's attorneys know how to use SAFER.

If you tender a load to a chameleon carrier and something serious happens, the discovery question isn't "did the carrier have a valid MC number?" Of course they did. The question is: what did you check, when did you check it, and what would a reasonably diligent broker have found?

"I pulled the snapshot and it looked clean" is not an answer. It's the first sentence of an answer. The rest of the answer has to explain what you looked at behind the snapshot. If the answer is "nothing else," you're going to have a bad deposition.

A new authority, a high-value load, and a principal whose name you've never encountered — that combination is a reason to dig. MC-2219043 for a carrier out of an industrial park in north Memphis with DOT-4103882 registered two weeks ago under an LLC formed three weeks before that? Call them before you tender. Get a straight answer about who's been running freight and under what authority. Document the call.

How I document this

When I vet a carrier with authority under 18 months, I add one step to the standard check: I log the principal officer name from the MCS-150, run a manual SAFER name search, and record what I found — or what I didn't find. The note goes into the carrier file with a timestamp.

It looks something like this:

> *MC-1187432 (DOT-3842917) — authority 8 months. Principal on MCS-150: Tomás Reyes. SAFER name search: no other active or revoked entities found associated with that name or with registered address (2241 Industrial Blvd, Memphis TN 38109). L&I confirms valid BIPD at $1M and cargo at $100K with no lapses. No prior entity flagged. Approved for single load; re-verify on next use.*

That note costs me eight minutes. It also creates the paper trail that separates a defensible carrier file from one that reads like nobody looked past the green checkmark.

If I find a hit — same name, revoked prior authority, same address — the load doesn't move until I've talked to the carrier directly and gotten a clear answer. Sometimes it's innocent: two different people with the same name operating in the same region. More often it isn't. Either way, I've documented the question and the answer, and the file shows I asked.

One thing I had wrong for years

I used to treat the FMCSA new-entrant safety audit as a reliable filter. Carrier passed the audit, they're vetted, move on. I've corrected that. The audit checks for systems and processes. It doesn't reliably catch an officer who has a paper wall between himself and a revoked prior entity. FMCSA's own enforcement data shows that chameleon carrier detection is still inconsistent — cases get caught, but not all of them, and not always before a serious load or a serious accident.

The audit is a floor. It isn't a ceiling, and it isn't a substitute for the five minutes you spend looking at who actually filed that MCS-150.

The chameleon problem is one of the harder vetting issues to systematize because it requires pattern recognition — reading two or three data points together and asking whether they fit. That's still mostly a human job. Which means it's still your job.

— Mason Lavallet

Founder, DOTScreener.com