Chameleon carriers — how to spot one before the deal funds

The pattern

A “chameleon carrier” is a motor carrier that has either (a) had its operating authority revoked or placed Out of Service, or (b) accumulated a poor enough safety record to make ongoing operation difficult, and then reincorporated under a new legal entity with a new USDOT and a new MC number, often with substantially the same equipment, drivers, and principals.

The pattern is widely understood by FMCSA enforcement. The agency has published multiple advisories — most recently a series of reports under the Office of Inspector General between 2018 and 2024 — documenting chameleon-carrier activity. FMCSA’s New Entrant Program is the primary regulatory response: new carriers face heightened scrutiny in the first 18 months specifically because of the chameleon pattern.

For a commercial-finance processor underwriting a trucking deal, the chameleon pattern is the highest-impact verification issue. You’re being asked to finance equipment for an operation that may have a hidden history of safety violations or unpaid liabilities.

The signals that show in the data

A new MC with chameleon characteristics typically shows several of the following:

1. Recent MC issuance, but principals with prior trucking history.

The new MC was issued in the last 12-24 months. The credit application discloses a principal who has been “in trucking” for 10, 15, 20 years. The discrepancy invites the question: under what MC was the prior decade?

2. The same physical address or phone number as an older closed carrier.

FMCSA registers each carrier’s principal place of business, mailing address, and contact phone. When a new MC’s principal address matches the address of a recently-revoked or out-of-service carrier — visible by reverse-searching the address in the FMCSA SAFER database — the relationship is likely.

3. The same officer name on both records.

A search of the FMCSA Licensing and Insurance database by individual officer name returns all MCs that named the individual as principal, officer, or contact. When the same individual appears on a revoked older MC and a brand-new one, the relationship is direct.

4. The same equipment.

VIN matches on the equipment list between the old and new MC are dispositive. The Vehicle Identification Number is unique to each truck; the same VIN cannot legitimately be operated under two unrelated MCs at the same time. If the new MC’s recently-acquired equipment matches VINs that were operated by the revoked MC, the relationship is the same.

5. The same Safety Measurement System (SMS) violation pattern.

A new MC accumulating CSA violations in the same categories at the same rates as a recently-closed MC operated by the same principals is statistically distinctive. The pattern is rarely coincidence.

What FMCSA does about it

FMCSA’s primary enforcement tool is the New Entrant Safety Assurance Program. Every new motor carrier is subject to an 18-month new-entrant safety audit during which the carrier must complete a safety audit and pass without serious findings. Failure of the new-entrant audit can result in revocation of the new MC before the chameleon pattern matures.

In addition, FMCSA has the authority under 49 CFR 385.337 to deny operating authority to a new carrier if the agency determines the application is a “reincarnated motor carrier” — a successor to a previously-revoked operation. Determinations under 385.337 are uncommon (the agency has to substantiate the relationship) but they do happen and they are public.

For a processor, the practical takeaway: a new MC at the new-entrant stage carries some FMCSA enforcement risk that older MCs don’t. If the new-entrant audit is still pending, the financing carries the risk of MC revocation during the loan term.

The cross-state legal-name lookup

The most useful single check for a chameleon pattern is a cross-state SOS lookup of the carrier’s legal name against the principal’s name. The workflow:

1. Pull the FMCSA SAFER record for the carrier. Note the legal name as filed with FMCSA.
2. Pull the SOS record in the state of formation. Note the principals.
3. Search every state SOS for entities formed by the same principals. Note the entity names, formation dates, and states.
4. Cross-reference the entity names against the FMCSA Licensing and Insurance database. If any of the matching entities also have a USDOT or MC number, you have the principal’s prior trucking history.

This is exactly what a chameleon would try to hide. The legal-entity name on the new MC is fresh, but the principal’s history goes back through every legal entity they’ve ever operated.

What VerifySOS shows for trucking deals

A verification packet for a trucking deal includes:

• The current SAFER record with USDOT, MC, operating-authority status, BASIC scores.
• The legal name as filed with FMCSA cross-referenced against the SOS in the state of formation.
• A cross-state officer search: every SOS record where any of the carrier’s principals appear as officers.
• For each prior entity found, an FMCSA lookup against that entity’s name to detect prior USDOTs / MCs.

When the cross-state officer search returns prior FMCSA-registered entities — particularly any with revoked or out-of-service status — the packet flags the deal for human review. Some of these will be legitimate (an owner-operator with a long history may have operated under multiple LLCs over the years without any safety issue). Some will be true chameleons. The flag is a starting point for review, not an automatic decline.

What this means for you

If you finance trucking, build the chameleon check into every new-MC underwrite. The FMCSA data is public, the SOS data is public, and the cross-reference is the work. A clean SAFER record on a 6-month-old MC isn’t a clean trucking history; it’s a clean recent history. The processor’s job is to confirm that recent history is also the carrier’s actual history.

A VerifySOS lookup on a trucking deal cross-references the carrier’s principals against SOS records nationally and against the FMCSA L&I database. Prior MCs operated by the same principals appear in the packet automatically. Developers get the same cross-reference on /api/v1/lookup.