A trucking company is a legal wrapper around trucks, drivers, and a safety record. When the safety record gets bad enough to end the business — an out-of-service order, a revoked authority, insurance nobody will write — the wrapper is the only part that has to die.
The trucks are still there. The drivers are still there. The people who ran the company are still there. So a new wrapper gets filed: fresh MC number, fresh DOT number, a name that shares no words with the old one, and a record that is perfectly, beautifully clean — because it's a week old.
Regulators call these chameleon carriers, and they're one of the more corrosive problems in the industry, because the system's memory is attached to the wrapper. Kill the wrapper, erase the memory.
Why the standard check misses them
The standard check is a snapshot: pull the MC, read today's record. A chameleon is engineered to pass a snapshot. Active authority — yes, granted last month. Clean inspections — of course, there haven't been any. No crashes, no violations, no out-of-service history. On paper, the safest carrier in America is always the one that started operating yesterday.
A snapshot can't see reincarnation because reincarnation is a relationship between two records, and one of them belongs to a "different" company.
What actually gives them away
Continuity. A business can change its name in an afternoon, but the physical operation drags its past behind it in small, checkable ways.
The officer. The FMCSA census data includes company officials. The same individual appearing as an officer of a revoked carrier and, weeks later, of a brand-new one at large is the single strongest signal there is.
The address. Fleets don't move buildings to escape a bad record — the yard, the shop, the parking all stay put. A new authority filed from the street address of a carrier that went out of service is not a coincidence worth extending credit to.
The phone. Phone numbers survive reincarnations with remarkable frequency, because the number is where the customers call.
The timing. Revocation in February; new authority from the same ZIP in March. Reincarnations cluster tightly after the death of the old entity, because trucks sitting idle don't make payments.
None of these appear on the new carrier's own record. They appear when you compare records across entities and across time.
The mechanism: diffing the census
FMCSA publishes its carrier census — the registration data for every active carrier — and it changes constantly: new authorities, revocations, address updates, officer changes. If you keep every monthly snapshot instead of just the latest one, you can diff them, the way a programmer diffs two versions of a file.
The diff is where chameleons become visible. New authority this month → search prior snapshots for the same officer name, the same address, the same phone → find them attached to an MC that was revoked in the last year → you now have an evidence chain, with the government's own records as the source.
This is grinding, unglamorous data work, and it's precisely the kind of work a lookup API can't do for you. A rented lookup answers questions about one carrier, now. Chameleon detection is a question about a million carriers, over time. It's only possible if you hold the whole dataset yourself.
That's why Dollar Traq's FMCSA warehouse — 22.7 million rows, refreshed and versioned — exists, and why Sentinel runs census-diff checks on every new carrier it vets. When it flags one, the flag isn't a vibe; it's this officer, that revoked MC, this filing date, on screen, traceable to the public record.
What to do when you catch one
Don't book the load — that part's obvious. Less obvious: don't tip your process. A "we've decided to pass" is complete. The operations behind serial reincarnations are attentive students of which brokers check what, and there is no upside to teaching the class.
And keep the flag. A chameleon identified today predicts the next wrapper, because officers, addresses and phones will drag the past behind them again next time too.