Loading…
A reincarnated carrier is an operator whose previous authority was revoked — usually for unpaid penalties, an unsatisfactory safety rating, or an out-of-service order — who has re-emerged under a fresh MC number to leave the enforcement record behind. The new entity looks clean because the revocation is attached to the old number. This guide explains how the revocation flip works, which public records expose it, and the broker workflow for catching it before tender.
A reincarnated carrier is an operator who had a prior authority revoked and is now hauling under a new MC number to escape that record. The flip is detectable because the federal regulator publishes the revocation reason (involuntary vs. voluntary) and the served date for every revoked docket, plus any active out-of-service order. An involuntary revocation — pulled by the regulator for non-compliance — paired with the same officer, phone, address, or email re-appearing on a freshly granted carrier is the core reincarnation signal. Voluntary revocations (the carrier surrendered authority) are far weaker signals.
Carrier reincarnation is closely related to the chameleon pattern, but the trigger is specific: the prior carrier's operating authority was formally revoked, and the operator re-registered to escape that revocation. Where the textbook chameleon escapes a bad safety rating or unpaid claims, the reincarnated carrier escapes a hard enforcement action — a revoked docket, an active out-of-service order, or both. The new MC carries none of that record because revocations attach to the specific docket number, not to the human behind it.
From a broker's seat, the danger is that the revocation never shows up on the carrier the broker is actually looking at. The new MC was granted recently, has a clean authority status, and no revocation history. The revoked docket sits on a different number the broker has no reason to pull. The join that exposes the flip is the identity edge — officer name, phone, email domain, or physical address shared between the revoked carrier and the freshly granted one.
A Conditional safety rating means the carrier has problems but is still legally operating. A revoked authority means the regulator pulled the carrier's right to haul. When an operator re-emerges under a new number after a revocation — rather than fixing the issues on the existing one — that choice itself is a signal worth scrutiny.
The single most important field on a revocation record is the reason code: involuntary or voluntary. The federal regulator publishes this for every revoked docket, and the distinction changes the weight of the signal entirely.
An involuntary revocation is pulled by the regulator — typically for failure to maintain insurance on file, failure to pay civil penalties, failure to designate a process agent (BOC-3), or an unsatisfactory safety rating that was never upgraded. It is an enforcement event. A voluntary revocation means the carrier asked to surrender its authority, which happens routinely when an operator retires, sells the business, or restructures. Voluntary revocations are common and benign on their own.
Knowhaul ingests the federal revocation file weekly and stamps each carrier with its most recent revocation reason and date. When a reincarnation pattern crosses a freshly granted MC with an involuntary revocation on a linked identity, that combination surfaces on the carrier card.
Reincarnation often rides alongside an out-of-service (OOS) order. An OOS order is an enforcement action that prohibits a carrier from operating until the underlying issue is resolved — distinct from a revocation, which removes the authority entirely. A carrier under an active OOS order cannot legally haul, period. If the operator keeps soliciting freight, they are doing so under a new entity that does not carry the OOS flag.
The federal regulator publishes OOS orders with the order date and a rescind date (blank while still active). A carrier whose old MC sits under an active OOS order, with a new MC freshly granted and soliciting the same lanes, is exhibiting the reincarnation pattern at its clearest. The OOS order is the strongest single enforcement signal because it is a present-tense prohibition, not a historical mark.
Never tender to a carrier under an active out-of-service order — there is no judgement call. If the carrier you are evaluating is clean but shares an officer, phone, or address with a carrier under an active OOS order, treat the new carrier as high-risk and require written attestation about the relationship before proceeding.
The reincarnation check folds into the standard new-carrier vetting workflow. First, confirm the carrier you are looking at is not itself under a revoked authority or active OOS order — that is a hard fail. Second, for any carrier granted in the last 12 months, run the identity edges (officer, phone, email domain, address) against the carrier universe to find linked entities. Third, for any linked entity, read the revocation reason and OOS status. An involuntary revocation or active OOS order on a linked carrier turns the new carrier into a require-attestation case.
The manual version of this check requires pulling the federal revocation file and OOS-order list and cross-referencing them against the carrier's contact record. Tools that pre-join the revocation and OOS data against the identity graph collapse the workflow to a single card — the linked-carrier revocation history surfaces alongside the new carrier's clean record, so the broker sees both numbers at once.
As with all identity-graph signals, a linked revocation is a flag, not a verdict. The common false positives:
The pattern becomes actionable when the revocation was involuntary, recent, and paired with multiple shared identity edges to a freshly granted MC. That combination warrants written attestation before tender. A single voluntary revocation on a loosely linked carrier is noise.
A revocation removes the carrier's operating authority entirely — the docket is no longer valid and the carrier must re-register to operate. An out-of-service order prohibits the carrier from operating until a specific deficiency is corrected, but the authority itself can remain on file. A carrier can be under an active OOS order without being revoked, and a revoked carrier is by definition not operating legally. Both are enforcement actions; both are reincarnation triggers when an operator flips to a new MC to escape them.
The federal regulator publishes the revocation reason for each revoked docket. Involuntary revocations are regulator-initiated (insurance lapse, unpaid penalties, missing process agent, unresolved unsatisfactory rating); voluntary revocations are carrier-requested surrenders. Knowhaul ingests the federal revocation file weekly and stamps each carrier with its most recent revocation reason and served date, so the involuntary/voluntary distinction is visible on the carrier card without pulling the raw file.
Not inherently. An operator can legally register a new motor carrier after a prior one is revoked or surrendered. What is illegal is misrepresenting on the new registration — for example, providing false officer information or denying a successor relationship when the regulator determines the new entity exists to evade the prior enforcement. The federal regulator has successor-liability authority to attach a prior carrier's enforcement actions to a reincarnated entity, but the legal threshold is high. Most reincarnation operates in the gap between technical compliance and enforcement.
Yes, and reinstatement is the legitimate path. A carrier whose authority was revoked for a fixable reason — an insurance lapse, for example — can resolve the issue and have the authority reinstated on the SAME docket number. When that happens, the revocation history stays attached and visible; nothing is hidden. Reincarnation is specifically the choice to abandon the revoked docket and start a fresh one, which is what leaves the enforcement record behind.
There is no bright line, but most reincarnation flips show a new authority granted within roughly 12 months of the prior carrier's revocation or OOS order. The tighter the gap between the old carrier's enforcement event and the new carrier's grant date — and the more identity edges the two share — the stronger the signal. A new grant years after an old voluntary surrender, with only a common-name officer link, is weak; a new grant weeks after an involuntary revocation, sharing officer, phone, and address, is strong.
Paste an MC, DOT, or VIN to verify a carrier in one card. Free, no signup.
Free, no signup. Paste a DOT, MC, or VIN — verify right away.
Chameleon carriers are the same operators running new MC numbers to escape bad safety, fraud, or financial history. The strongest detection signal is officer reuse — the same principal name appearing on multiple distinct carrier records. This guide explains the pattern and how to detect it.
Authority history is the single strongest fraud-detection signal in the public record. This guide explains how to read the granted/revoked/reinstated timeline and how to spot the identity-flip pattern that drives modern double-brokering scams.
An out-of-service order is a federal enforcement action that prohibits a whole carrier from operating until it fixes a serious deficiency. Learn how it differs from a revocation, how to read its status, and why it's a hard stop.
Step-by-step checklist for vetting any motor carrier before tendering a load — operating authority, insurance, safety scores, inspection history, and identity flags.
Open one of these profiles in a new tab to see how the checklist applies to a live carrier record.
Knowhaul stamps every carrier with its revocation reason, served date, and OOS-order status — and links them across the identity graph.