What is a chameleon carrier?

A chameleon carrier is a trucking company that had its operating authority revoked — or was on track to have it revoked — and re-registered with FMCSA under a new name, new MC number, and often a new principal officer on paper, while the underlying equipment, drivers, and management stay the same. The word "chameleon" comes from FMCSA's own terminology; the broader trucking industry also calls them "reincarnated carriers."

For brokers, the practical problem is that chameleon carriers show up on your SAFER company snapshot looking like any other small fleet with a clean-ish record — because the MC is new. The compliance and safety history that would have flagged them is buried under a previous authority that you are not currently looking up. If you book one, you have meaningfully higher odds of a cargo-claim incident, a crash, or a late delivery than the base rate of booking the carrier pool at random.

Why chameleon carriers exist

FMCSA enforcement tools — out-of-service orders, conditional safety ratings, escalating civil penalties — all attach to a carrier's operating authority. When enforcement gets uncomfortable, some carriers calculate that it is cheaper to shut down the authority and spin up a new one than to fix the underlying safety issues. They file paperwork, re-register with a different principal officer (often a relative or a shell LLC), get a new MC, and resume operating.

The incentive structure is the problem. The cost of a new MC authority is low. The cost of an out-of-service order on an existing fleet is high. Until that math changes, the practice continues. FMCSA has multiple rulemaking efforts — including recent work around identity verification (MOTUS) and successor-authority analysis — aimed at raising the cost of reincarnation, but the loophole is not fully closed.

How big is the safety risk?

Multiple studies over the past decade have measured chameleon-carrier crash rates. The numbers vary by methodology and by how strictly "chameleon" is defined, but the consistent finding is that carriers identified as reincarnated have crash rates meaningfully higher than matched-fleet-size baselines — typically in the 2–3× range. The safety story is not that chameleons are universally dangerous; it is that the population is non-random. Carriers who reincarnate because of a safety-enforcement problem on their first authority are, unsurprisingly, more likely to have safety events on their second.

For a brokerage, that translates to: every time you book an unidentified chameleon, your probability of a cargo claim goes up meaningfully. Over a year, at enough volume, that stacks into real losses.

The three signals that identify a chameleon

1. New authority + established equipment

A 3-month-old MC claiming to run 50 trucks is not necessarily fraudulent, but it is not normal. Legitimate new carriers usually scale up equipment over time — a new authority with a handful of trucks is common; a new authority with a full mid-size fleet behind it is suspicious.

How to check: pull FMCSA's SAFER snapshot or QCMobile data. Look at the registration date versus the reported power unit and driver counts. A mismatch is the first signal.

2. Principal officer / address overlap with a revoked carrier

This is the highest-signal check. Pull the new carrier's principal officer, registered business address, and phone number. Search FMCSA's public records for other MCs with matching officer, address, or phone. If one of those matches is a carrier whose authority was revoked within the last 24 months, you are looking at a probable chameleon.

FMCSA does this analysis internally during successor-authority review. The public SAFER snapshot does not surface it as a flag, but the underlying data is in public records.

3. Insurance + equipment identifier overlap

The insurance certificate on a new MC that names the same policy holder as a previously revoked MC is a hard signal. VIN overlap on the truck list between old and new authorities is another. License-plate continuity is a third. Fraud investigators use all three; brokers can replicate the first two at the email stage with a bit of effort.

What this looks like at the broker inbox

Most brokers discover chameleon carriers retroactively — after a claim or a late delivery, during the post-incident investigation. That is too late. The goal is to catch them during the email-reply stage, before booking.

The practical check is a sequence of 90-second questions on any MC whose authority was granted within the last 12 months:

• Does the registered principal officer share a name, address, or phone with any revoked MC?
• Does the equipment count claimed in the carrier packet match what a 3–12 month old fleet would plausibly operate?
• Is the insurance carrier and policy number consistent with a genuinely new operation, or does it overlap with a historical authority?
• Does the quoting dispatcher have a history of representing this MC, or are they new to it too?

A "yes" to two or more of those questions is not proof of a chameleon — but it is enough of a red flag that you should either run the deeper verification or decline the load. See also Anatomy of a Fraudulent Carrier Email for the broader email-stage fraud taxonomy.

How Keelway handles this automatically

Keelway's carrier trust score surfaces chameleon-adjacent signals directly on the ranked list:

• Authority age: any MC with operating authority granted in the last 12 months gets a visible "new authority" pill next to the trust score.
• Equipment-vs-age mismatch: new MCs claiming large fleet sizes get an amplified flag on the same row.
• Principal officer overlap: when a new MC's principal officer matches an MC in FMCSA's revoked-authority history, the trust score drops sharply and the overlap is surfaced as a reason on the score.

None of this replaces a formal FMCSA successor determination or a thorough onboarding process. It is an inbox-level filter that catches the obvious cases before they get booked — which is where the economic damage of a chameleon-carrier incident actually happens.

For the full capability spec, see Carrier Email Automation or the TMS-specific integration pages (Tai, McLeod, Aljex).