Broker liability for carrier accidents: what Montgomery v. Caribe Transport actually held

Can a freight broker be sued when a carrier it arranged crashes?

A plaintiff can name a broker as a defendant. That was true before May 2026, it is true now, and being named is not what changed.

What changed is one defense, and the change is procedural. In Montgomery v. Caribe Transport II, LLC, decided May 14, 2026, the Supreme Court held that a state negligent-hiring claim against a freight broker is saved from FAAAA preemption by the statute's safety exception. For interstate shipments, preemption is no longer available to end a negligent-hiring claim at the threshold. More such cases reach discovery and the merits.

That is the change. It is not a ruling that brokers are liable, and the sections below keep the two apart.

Verified as of August 30, 2026, and offered as general information rather than legal advice. Everything below describes the decision as issued. We assert nothing about what has happened on remand, because we have not verified it.

What actually changed on May 14, 2026?

Montgomery v. Caribe Transport II, LLC was decided May 14, 2026. The decision was unanimous. Justice Barrett wrote the opinion. Justice Kavanaugh filed a concurrence, joined by Justice Alito. The Court reversed the Seventh Circuit, 124 F.4th 1053 (7th Cir. 2025).

The holding: a state negligent-hiring claim against a freight broker is saved from FAAAA preemption by the statute's safety exception.

The practical consequence, stated exactly: for interstate shipments, preemption is no longer available to end a negligent-hiring claim at the threshold, so more such cases reach discovery and the merits.

Three phrases in that sentence carry the weight, and they are worth having in plain words. “At the threshold” means at the very start of a case, before the facts are developed. “Discovery” is the stage where both sides have to hand over documents and answer questions under oath. “The merits” is where the question of who was actually at fault gets decided.

That sentence is the entire practical delta, and it is worth noticing how procedural it is. A preemption holding answers whether a federal statute blocks a state-law claim from being heard at all. This one answered no, for this category of claim. What happens to those claims once they are heard is a separate question, governed by separate law, and this decision did not reach it.

Which readings of Montgomery are wrong?

Five statements about this decision are easy to encounter, and the opinion supports none of them. No example is named on this page — we are correcting readings, not naming culprits, and we have not catalogued who said what, which is also why nothing here claims how common any of them is. Each is taken up in its own section below.

• “The Supreme Court ruled that brokers are liable for carrier crashes.” It did not. Montgomery is a preemption decision. The judgment below was reversed and the case remanded — “remanded” means sent back down to the lower courts for further proceedings — and no one in that case has been found negligent.
• “The Court created a duty to vet carriers.” It did not. The decision creates no duty of any kind; whether a broker owes one is a question of state law, and the decision left that where it found it.
• “The Court now requires brokers to check authority, insurance and safety history before tendering a load.” Nothing in the holding does that work. It sets out no list, no documentation standard and no verification requirement.
• “State-law claims against brokers are no longer preempted.” Too broad twice over. Purely intrastate arrangements sit under a different subsection, which has no safety exception. And claims that are not about safety — cargo loss and damage, for instance — are untouched.
• “The Court said brokers who vet reputable carriers are protected.” No opinion in the case says that. The language behind that reading comes from a concurrence — two Justices, not the Court — which noted that the plaintiff's own counsel accepted that brokers “should be able to successfully defend” if they acted reasonably and arranged transportation with reputable trucking companies. Being able to defend a suit is not being protected from one. A concurrence is not the holding and binds no lower court. It is not a safe harbor.

Does this mean brokers are now liable for carrier accidents?

No.

Four reasons. The first is what a preemption ruling is: it settles whether a claim may be heard, not whether it wins — and Montgomery is a preemption decision, not a liability decision. The other three are on the face of the decision. The Court reversed and remanded, so no one in that case has been found negligent. The Court did not hold that brokers are liable, and nothing in the holding does that work. And whether a broker owes a duty at all, and what care is required if one is owed, remains a question of state law that varies from state to state; the decision leaves that untouched.

What the ruling changes is which door a case comes through. A negligent-hiring claim arising from an interstate shipment can no longer be ended at the threshold on preemption grounds. But surviving preemption is not the same as surviving the case: a plaintiff still has to prove a claim under whatever the law of the relevant state actually requires, and a claim that clears preemption can still fail for reasons that have nothing to do with it.

What is FAAAA preemption, and what is the safety exception?

The FAAAA — the Federal Aviation Administration Authorization Act, which despite its name is the statute at issue for motor carriers and brokers — is the federal law brokers have invoked to argue that state-law claims about their selection of a carrier are barred. Preemption is a threshold defense: where it applies, the claim is blocked before the facts are developed, and the case can end before discovery.

The statute contains a safety exception. Montgomery held that a state negligent-hiring claim against a freight broker, on an interstate shipment, is saved from preemption by that exception. That is the mechanism of the ruling, and the two limits described further down follow from it — the holding runs through the safety exception, so it reaches what the safety exception reaches and no further. That last step is an inference from the mechanism of the ruling rather than a separate holding.

Beyond the statute's name, this page does not gloss what it preempts and does not cite subsection numbers; the verified record we work from is the decision itself. Where the intrastate carve-out comes up below, it is described as a different subsection, unnumbered, for the same reason.

What is a negligent hiring claim against a broker?

It is the name of a theory a plaintiff pleads: that the broker was careless in selecting the carrier it arranged. That is as far as a page like this one can honestly take it.

What the theory actually requires is a question of state law, and it varies by state. Montgomery did not define the claim, did not set out its elements, and did not decide whether the broker in that case met them. It decided that the claim is not preempted, and sent the case back.

Listing “the elements of negligent hiring” as though there were one national formulation would state as settled something that differs across jurisdictions. It is not something we are in a position to state at all.

One more piece of housekeeping, flagged so the sources you read afterwards do not confuse you: the terminology drifts. Negligent hiring, negligent selection and negligent entrustment all appear in writing about this area. This page uses “negligent hiring” because that is the phrase attached to the claim in the decision; it does not rank the terms, define them, or assert that they mean the same thing.

Does this apply to every load a broker arranges?

No. The decision has two stated limits.

The first is interstate versus intrastate. The holding concerns interstate shipments. Purely intrastate arrangements sit under a different subsection of the statute, one that has no safety exception.

The second is safety versus everything else. The holding runs through the safety exception. Claims that are not about safety — cargo loss and damage being the obvious example — are untouched by this decision.

Because the holding runs through the safety exception, the reasoning that saved the claim in Montgomery does not carry across to either category in the same way. That is an inference from the mechanism of the ruling rather than a separate holding, and it is marked as one here.

Said the other way round: a summary that renders the holding as “state-law claims against brokers are no longer preempted” overshoots on both axes at once.

Neither limit is reassurance, and this page will not turn it into any. “So intrastate freight is safe” would be a legal conclusion about a particular reader's arrangements, and drawing it would first require deciding which side of that line a given movement falls on — itself a legal test we have not verified and will not paraphrase. That belongs with a lawyer who can look at the actual contracts and the actual movement.

What does the Kavanaugh concurrence add?

A summary of this case that stops at the word “unanimous” leaves something out.

Justice Kavanaugh, joined by Justice Alito, wrote separately. In that concurring opinion, he said the decision “should not be read to mean that brokers will routinely be subject to state tort liability in the wake of truck accidents.” He also noted that the plaintiff's own counsel accepted that brokers “should be able to successfully defend against state tort suits if the brokers have acted reasonably and arranged transportation with reputable trucking companies.”

Two labels belong on that passage every time it is quoted. It is a concurring opinion, not the Court's holding, and it binds no lower court. And the second quotation is a characterization of a position the plaintiff's counsel accepted — it is not a holding at all, by anyone.

The more important thing is what the passage is not. It is not a safe harbor. It does not say that a broker who checks a carrier is protected, and no rule of that kind appears anywhere in this decision. Two Justices described how they expect these cases to go; an expectation about how cases should go is not a defense, and converting it into one — “vet your carriers and you are covered” — reads a rule into a passage that contains none.

It is also the reading that sells software. We sell carrier vetting software, and we are telling you the concurrence does not say that.

Did the Court say what a broker has to check before booking a carrier?

No. The decision did not create a duty to vet, and nothing in the holding does that work — it sets out no list, no documentation standard, no verification procedure, and no requirement that a broker review anything in particular before tendering a load.

No list of checks can be traced to this decision. Attaching one to the holding — a set of features, a documentation standard — implies a demand the opinion does not make.

What can be said without any legal content at all is a fact about public data: FMCSA publishes a record on every registered carrier, it is free, and anyone can read it before a load is tendered. That was true before May 14, 2026, and it is true after. The ruling neither created that record nor said anything about what to do with it. The next two sections describe what is in it — and, just as usefully, what is not.

What is actually in the public FMCSA record on a carrier?

All of it is public and free. FMCSA's SAFER system and its Licensing and Insurance system are both linked at the bottom of this page, and either can be searched by anyone. What follows is that record field by field, as our own tool renders it, because that is the version we can vouch for line by line.

• Identity and status: legal name, any DBA, USDOT status, entity type, physical address, phone, and power units against drivers.
• Allowed to operate — a yes or no flag, and the field that answers whether a carrier can haul right now.
• Operating authority carried as separate statuses rather than one summary word: common authority, contract authority and broker authority, each active, inactive or none, alongside the docket number.
• What the carrier is authorised to haul: property, passengers, household goods.
• Insurance from FMCSA's licensing system — BIPD liability, cargo insurance and the surety bond (BMC-84/85) — with dollars on file shown against dollars required. FMCSA sometimes reports the requirement itself as unknown; the honest rendering of that is to say so rather than guess in either direction, so ours prints “Requirement unknown per FMCSA.”
• An out-of-service date, called out at the top of the report when one is present rather than buried in a field.
• FMCSA's own safety rating, as a field. It is frequently absent from the record, and an absent field is not a finding about anything.
• The date of the last MCS-150 filing, and how long ago that was.
• Twenty-four months of roadside record: driver and vehicle out-of-service rates against the national average, and crash counts split into total, fatal and injury.
• Census signals stated as counts, never as a score: how old the operating authority is, how many other FMCSA registrations list the same phone number, and how many share the same street address.

CarrierVet is our product. It reads those systems and renders that record for freight brokers, and it is free to look up any carrier. The boundary is the product's own, stated the same way there as here: it reports what the record says, it is not a recommendation, and vet reports and fraud signals are never scored. A flagged signal is a reason to look closer, not an accusation — a shared street address can be a registered agent or an office park, and a young operating authority can be a perfectly legitimate new business.

We are not FMCSA and we are not affiliated with any government agency. We are also not a consumer reporting agency, and the record is presented for business due diligence on motor carriers only — those last two are commitments in the CarrierVet terms, not just assertions on this page.

None of this is a response to Montgomery. The record existed before the decision, the decision prescribes nothing about it, and reading a public file is not a legal position.

What does the public FMCSA record not show?

Enough to be worth its own section. The gaps are less discussed than the fields, and they are the part a reader is most likely to be wrong about.

• It is a filing record, not a live feed. It reflects what has been filed and published, not what is true at this minute.
• Insurance “on file” is a filing. It is not a certificate of insurance for a specific load, and it does not say what a policy actually covers or excludes.
• Identity is not a field. The record describes a registered entity. It cannot confirm that the person sending an email, or the driver who arrives, is that entity.
• There is no claims history, no service history and no payment history in it. Whether a carrier pays, communicates, or turns up is not in the federal record at all.
• There is nothing in it about the specific driver on a specific load, or the specific equipment.
• Counts are counts. None of these figures is a prediction, and two carriers with identical public records are not two identical companies.

We sell access to a record with those limits, which is the reason to state them on the page rather than only in the terms.

Who can say what this means for a particular brokerage?

Not us. This is where the page stops, and it is a limit on what we can do rather than a disclaimer protecting us.

We are not lawyers and this is not legal advice. What this page does is report what one published decision says and, just as carefully, what it does not say. It cannot be applied to a particular brokerage, a particular contract or a particular load, and any page that offers to do that for a national readership is inventing a uniform rule the decision did not create.

Because duty and the standard of care remain questions of state law that vary by state, the person who can answer a specific question is the brokerage's own counsel, working from the actual file.

There is a second conversation, separate from the legal one. A broker-liability policy is a contract with its own terms, and the insurer that wrote it will have its own reading of a decision like this one — of what the policy covers and what it asks of the insured. That is a conversation with the insurer, and it is not one a page can have on anyone's behalf.

If something on this page turns out to be wrong, we would like to know: support@cdlels.com. Corrections to a page about a court opinion are worth more to us than traffic to it.

Where can I read the ruling myself?