New Authority, Same Trucks, Same Problem: Spotting Chameleon Carriers Before You Tender

The load was $82,000 worth of consumer electronics, LTL consolidation on a Chicago-to-Phoenix lane. The broker who called me had already tendered to Summit Freight Partners LLC — MC-2047832, authority issued June 2026, zero inspections, zero crashes, nothing on SAFER to raise a flag. Clean company snapshot, active authority, insurance filed on time.

The truck that showed up had a DOT number on the door that didn't match. The driver, when pressed, said they ran freight under a different company name sometimes. It happens. What the broker didn't know until two days later, when the load went silent, was that Summit Freight Partners LLC was registered to the same officer — Robert Teal — who had controlled Peak Horizon Logistics LLC, MC-1891247, DOT-3892147. Peak Horizon got a Conditional safety rating in January 2026 after an audit flagged hours-of-service violations and two driver qualification failures. They stopped filing MCS-150 updates in February. Their authority was administratively revoked in April.

Summit Freight Partners was filed in May. Same terminal address in Fontana. Same phone number, different area code. Different name, same problem.

What a chameleon carrier is, in plain terms

Carriers don't lose their FMCSA record. But a company can. When an entity's authority is revoked — whether from an Unsatisfactory rating, an imminent hazard OOS order, or just unpaid fees — the carrier's officers can form a new LLC, file for new operating authority, and start fresh with a blank SAFER profile. FMCSA tracks individuals through their principal officer records and enforcement history, but that linkage isn't automatic on the carrier's public snapshot. The new MC number looks clean because it is clean — the company has no history.

The problem isn't that the system is broken. It's that most brokers only run the MC number. They pull SAFER on Summit Freight Partners and see what Summit Freight Partners has done. They never ask what Robert Teal has done.

FMCSA does have tools for this. Under the agency's enforcement authority, investigators can pierce through corporate structures and attribute prior conduct to related entities — particularly when the same principals control both. But that's an enforcement tool, not a vetting tool. It doesn't protect you before the load moves. Nothing in SAFER automatically links the new company to the old one.

You have to do that yourself.

The four tells that show up every time

I've seen this pattern enough to know it doesn't look like fraud from the outside. It looks like a new carrier who is eager for business and maybe a little rough around the edges. That's why it works.

The tells are consistent:

Authority age under six months. New companies start new. But genuinely new operations — someone who just got their CDL and is running their own authority for the first time — look different than a reincarnated operation. A new carrier usually has one or two power units, one or two drivers, and a fairly narrow radius. When a four-month-old carrier shows up with a ten-unit fleet, company vehicles with visible wear, and a preference for long-haul freight, that gap is worth explaining.

The same terminal address, different name. SAFER shows the carrier's principal place of business. Cross-reference the physical address of the new authority against any carrier you can find at that address. FMCSA's company search is filterable by state; a quick search for carriers in Fontana, CA near a specific zip code will sometimes surface the predecessor. It's tedious. It's also the exact thing a plaintiff's lawyer will do after the accident.

Officer name matches a prior carrier. This is the most reliable tell and the least-used check. Form MCS-150, filed under 49 CFR § 390.19, requires the carrier to identify its principal officer — president, CEO, or equivalent — by name. FMCSA stores this. When you pull a company snapshot on SAFER, the company officer is listed. If that name appears in your own records as the officer of a carrier you've previously screened, or if a search surfaces it attached to a prior entity with enforcement history, you're looking at a continuation, not a startup.

Equipment that doesn't match the authority age. A carrier whose authority is four months old and whose trucks show 2019 model years with 400,000 miles didn't buy those trucks after they filed. They inherited them, either from a related entity or because the principals already had equipment when they filed. This doesn't prove anything by itself. But it's a thread to pull.

The regulatory hook

49 CFR § 390.19 requires every motor carrier to file an MCS-150 within 90 days of beginning operations and to update it every two years. The form asks for the carrier's name, address, and the name and title of the principal officer or owner. FMCSA uses this information to maintain the carrier's SAFER profile, but it also creates a paper trail of who controlled what and when.

What that means at load-tender time: when you pull a carrier's snapshot and the authority is young, look at the officer name. That name can be cross-referenced against FMCSA's carrier search — it's a free, public tool at safer.fmcsa.dot.gov. If the same name appears as a principal officer on another entity with enforcement actions, an OOS order, or an Unsatisfactory rating, you have a direct line connecting the new authority to the old problem. The MCS-150 requirement exists precisely because FMCSA wants carrier responsibility to follow people, not just entities.

It doesn't happen automatically. But the data is there if you look.

Why this matters more after Montgomery

Before Montgomery v. Caribe Transport II, most brokers' chameleon-carrier exposure lived in the contract, not in tort. You tendered to a carrier with new authority, something went wrong, and you had the carrier agreement indemnification clause to fall back on. That indemnification is only worth something if the carrier has assets to satisfy it — which a four-month-old company that's really a continuation of a revoked one often doesn't.

After Montgomery, decided unanimously by the Supreme Court on May 14, 2026, you can be sued in state court for negligent selection. The plaintiff's theory in a chameleon-carrier case is exactly what you'd expect: "The broker failed to conduct adequate due diligence, and that due diligence, if conducted, would have revealed that the carrier's principal officer had prior enforcement history that made this carrier unsuitable." That argument works whether or not the broker knew about the connection. Not knowing isn't a defense — it's the negligence.

The standard isn't that you have to catch every chameleon. It's that a reasonably diligent broker would have taken steps that might have caught it. Checking the officer name against FMCSA's carrier database takes about four minutes. That's the standard you're measured against.

What DOTScreener does here

When you run a carrier through DOTScreener, the screen pulls the officer name from the MCS-150 record and flags it if the authority age is recent — under six months triggers a closer review. If the platform finds prior enforcement history for that officer under another entity, the screen surfaces it alongside the current carrier's file, with the prior entity's status, rating history, and any OOS orders.

This isn't magic. It's the same database lookup you'd do manually, executed automatically and surfaced in context so you're not doing it separately for every tender. On a day where you're booking 40 loads, manually cross-referencing every carrier's officer name isn't realistic. The screen makes it routine.

For carriers with Continuous Monitoring enabled, DOTScreener will also flag if a previously-approved carrier's authority status changes — which is how you catch the scenario in reverse: you've been using Peak Horizon for six months, their authority gets revoked, and the system alerts you before Summit Freight Partners shows up on the load board still advertising availability.

How I document this

When a carrier's authority is under six months old, I add one step to the standard screening process: I pull the officer name from the SAFER company snapshot and run it through FMCSA's carrier search filtered by that name. If I find prior entities, I document what I found — the company name, the MC number, the current status, and any rating or enforcement history — in the carrier file.

The note I write is: "Officer cross-check conducted [date]. No prior entities found." Or: "Officer cross-check conducted [date]. Principal officer [name] also listed on [Prior Entity LLC], MC-XXXXXXX, status [revoked/unsatisfactory], [effective date]."

If the prior entity has enforcement history, I don't approve that carrier. If it's something less concerning — say, the officer ran a prior company that voluntarily cancelled its authority and started fresh for legitimate business reasons — I document that context and make a judgment call, clearly noted. Either way, the check happened and I can show it.

That's what your carrier file needs to demonstrate: not that you never approved a bad carrier, but that you ran a process and made an informed decision. The difference between those two things is the difference between a defensible file and a deposition you lose.

How this fits the broader vetting standard

Most brokers have a checklist. Active authority, insurance on file, OOS rate below threshold, no Unsatisfactory rating. That checklist was adequate in a world where negligent-selection claims didn't reach state court. It's not adequate anymore.

New authority deserves deeper scrutiny, not less. The carrier has no history because they have no history — and that's either because they're genuinely new or because someone decided to start over. Your job is to figure out which. It's not that new carriers are bad or that you can't use them. I've approved plenty of young authorities. But I've seen what happens when you don't look past the MC number, and it's not a situation you want to be building a defense from.

The MC number is the starting point. The officer name, the terminal address, the equipment age — those are the threads you pull when the starting point doesn't tell you enough.

Four minutes. That's all this check takes. Every time.

How I document this

When I screen a carrier with authority under six months old:

1. Pull the SAFER company snapshot. Note the officer name and principal place of business address.

2. Run the officer name through FMCSA's carrier search at safer.fmcsa.dot.gov. Note any prior entities associated with that name.

3. For each prior entity found, note the company name, MC/DOT numbers, current authority status, safety rating if any, and any OOS orders or enforcement actions.

4. Document the finding in the carrier file: "Officer cross-check [date]: [name] — prior entity [name/MC], status [X], no disqualifying history" or "prior entity [name/MC] — Conditional rating [date], authority revoked [date], not approved."

5. Save the screenshot of the FMCSA search results alongside the carrier's SAFER snapshot.

DOTScreener runs this automatically on every screen and stores the result in the carrier file. If you're doing it manually, it's five steps and one screenshot. Either way, it needs to be in writing before you tender.

— Mason Lavallet

Founder, DOTScreener.com