Chameleon carrier detection

what reincarnation looks like on a desk

A chameleon (reincarnated) carrier is a new USDOT that continues the people, phone, address, or equipment of a company that was placed out of service, left unpaid bills, or drew an Unsatisfactory rating. FMCSA screens for this internally. Brokers still see it first as: same dispatch cell, new MC, “we rebranded.”

The public job is overlap, not a courtroom finding. You can match fields on SAFER and ask questions. You cannot declare them a chameleon in a public forum as if you were FMCSA.

New authority plus a rebrand story is the usual entrance. Run the new-entrant checks and this overlap check together. Clean paper is the point of reincarnation.

shared phone

A dispatch number on several USDOT records can mean a shared office, a dispatch service, or a reused identity. The phone itself is not a crime. Unexplained reuse with a new MC after an OOS or Unsatisfactory history is the pattern.

Call it. Ask for the legal name and DOT. If they recite the new docket and will not discuss the old one they just used in conversation, write that down. Search the number. Do not invent a “shared by 12 DOTs” statistic you did not count.

There is no public graph of every DOT that shares a phone. The accurate mechanism is the call plus a search plus whatever prior MC they admit. Do not fake a network count.

shared address

Physical address on SAFER is a strong field when it is a yard or a unique suite. It is a weak field when it is a registered-agent mill or a bookkeeper. Write which kind you think you have and why.

A move three days after you approved a related company, plus a new cell, is a re-check. MCS-150 updates are a signal, not a verdict.

Mailing address overlap is weaker than physical address overlap. Still record it. Do not treat a UPS Store as proof of reincarnation by itself.

shared officers and names

When officer names appear on the census or MCS-150 materials you can see, compare them to the prior company they mentioned or that the phone led you to. Same officer plus same phone plus a new USDOT after Unsatisfactory is a pile of facts. Any one of those is thinner.

Legal-name rhymes (“River Line LLC” after “River Line Freight Inc”) are a reason to open both files. Entity-type change is also how ordinary reorganizations look. Ask for documents. Do not skip the ask because the rhyme felt clever.

Equipment stories on social media are not FMCSA records. If you use them, label them as unofficial and still require the federal file to stand on its own.

what you can check without a private database

Compare officer names, physical address, and telephone on the new SAFER record to the old one. Google the phone. Ask for the previous MC if they volunteer a rebrand story. Open L&I on both dockets: rating history will not always travel, but insurance cancellations and authority revocations on the old file are worth reading.

A shared bookkeeper address is weak evidence. A shared dispatch cell plus the same trucks in photos plus an Unsatisfactory on the old MC is strong. Write down what you actually matched. Strength is the list, not a vibe.

You do not need a paid chameleon product to fail closed on unexplained overlap with an OOS carrier. You do need the old USDOT or MC to compare. If they will not give it and the phone search produced one, use the search result as a question, not as a press release.

do not publish accusations

Denied-carrier lists are your records. They are not FMCSA findings. Do not post “chameleon” plus a company name in a public broker group as if it were a government action.

A peer flag is a reason to open SAFER and L&I again. It is not the reason you tell a shipper. Tell the shipper the fields that did not match, or tell them you will not cover. Do not narrate a fraud novel.

Inside the load file, use plain sentences: phone on new USDOT equals phone on old USDOT 1234567 (example format only — use the real numbers you looked up); old snapshot showed Unsatisfactory; they declined to explain. That file holds up. A slogan does not.

worked desk: rebrand, same cell, old Unsatisfactory

The inbox said a new USDOT, granted recently, “we used to run under another name.” Dispatch cell matched the cell on a prior SAFER snapshot for a carrier with an Unsatisfactory rating that later showed out of service. Physical suite matched. Officer last name on the materials you could see matched.

They called it a rebrand. They wanted a dry-van load the same day. L&I on the new docket was Active with a BMC-91. Paper on the new file was clean. Paper on the old file was the reason the new file existed.

You can match phone, address, and officers. You cannot publish that they are a chameleon. Document the overlap. Do not cover until they put the prior MC in writing and the old file is something you can explain to a shipper without lying. An Unsatisfactory history that simply changed numbers is still an Unsatisfactory history for your risk, even if FMCSA issued a new USDOT.

what this is not

This is not a private investigator kit. It is not a license to defame. It is a field-comparison habit plus a fail-closed rule when overlap with OOS or Unsatisfactory is unexplained.

A shared dispatch service across legitimate owner-operators can look like a shared phone. Call the census number for each MC. Do not collapse every shared cell into reincarnation.

If someone pastes a screenshot from another network, still run the federal checks. Do not republish the accusation.

desk checklist

• If they admit a prior MC, that MC is looked up before cover.
• Phone, physical address, and officer fields compared to the prior record you found.
• Overlaps written as field matches, not as a public accusation.
• OOS or Unsatisfactory on the prior MC treated as material, not “old news” because the USDOT changed.
• Rebrand story required in writing when overlap is already visible.
• Census callback on the new DOT still performed.
• Shipper communication uses matched fields, not the word chameleon.

what belongs in the load file

• New and old SAFER/QCMobile snapshots side by side (phones, addresses, names).
• L&I on both dockets if you have the old MC.
• Written rebrand explanation, or a note that they refused.
• Internal overlap list: which fields matched.
• What you told the shipper, limited to facts on the snapshots.

fail closed

• Phone plus address plus officer overlap with an OOS or Unsatisfactory carrier, unexplained.
• They refuse to name the prior MC after volunteering a rebrand.
• You cannot describe the overlap without guessing.
• Someone already posted a public accusation from your desk — stop and keep the rest internal and factual.
• New docket is clean on L&I but identity still points at the old out-of-service office and they will not take a census call.