Freight Broker Liability After Montgomery: Double-Brokering Controls

The AONE double-brokering case shows why freight brokers need carrier substitution controls, pickup verification, and load-level vetting evidence.

A freight broker may face a negligence case over a crash even when the broker did not select the driver or final motor carrier. An August 2026 federal order allowed claims against AONE Brokerage to continue where evidence indicated that its contracted carrier had reassigned loads before, turning unauthorized re-brokering from a payment and cargo-theft problem into a documented carrier-selection risk.

Direct Answer: What Does the AONE Double-Brokering Case Mean for Freight Brokers?

The AONE order does not make brokers automatically liable for a downstream carrier's crash and does not establish a nationwide legal standard. It shows that, after Montgomery v. Caribe Transport II, a broker's knowledge of prior load transfers, response to contract breaches, and proof of the carrier actually hauling each shipment can become central evidence in a negligence case.

Key Takeaways for Freight Brokers

  • On August 11, 2026, a Nevada federal judge denied summary judgment requests in a crash case involving AONE Brokerage, Lucky Transport, GRK Transport, and driver Bhupinder Singh.
  • The court found enough disputed evidence for claims to continue, including evidence that AONE knew Lucky had subcontracted loads before; the order is not a final finding that AONE was negligent.
  • The Supreme Court's May 14 Montgomery decision removed FAAAA preemption as a categorical defense to state negligent-selection claims tied to motor-vehicle safety.
  • FMCSA says a motor carrier cannot broker loads without separate property-broker authority, subject to the specific statutory rules governing carrier interchanges and agents.
  • Brokers should verify the dispatched carrier, truck, driver, authority, insurance, and pickup identity before release, then document any substitution or re-brokering exception.
  • ARK TMS is designed for growing freight brokerages and established 15-40-user teams that need carrier, load, document, and exception records without enterprise-software complexity.

What Changed in the AONE and J.B. Hunt Broker-Liability Cases

Two active federal cases reported on August 21 show how post-Montgomery broker-liability disputes are moving from preemption arguments toward fact-intensive questions about carrier choice, safety signals, contractual roles, and what a brokerage knew before a load moved.

AONE's Summary-Judgment Request Was Denied

In Hardy v. Singh, AONE tendered a hay load to Lucky Transport, which then placed the shipment with GRK Transport and driver Bhupinder Singh. The truck crossed into opposing traffic after skidding on a Nevada highway in July 2022, killing one passenger and injuring another.

FreightWaves and Overdrive reported that U.S. District Judge Anne Traum denied summary judgment requests on August 11. According to the reporting, the record included evidence that AONE continued doing business with Lucky despite knowing that Lucky had used third-party carriers on prior loads.

The judge did not decide at summary judgment that AONE caused the crash or is liable for it. The narrower development is that disputed facts—including prior knowledge of subcontracting and whether contracting with Lucky was reasonable—must continue through litigation rather than being resolved for the brokerage as a matter of law.

The Arizona Case Tests a Different Carrier-Selection Record

In Gee v. J.B. Hunt Transport, plaintiffs allege that J.B. Hunt negligently selected Borderlanders for a 2023 shipment before a Borderlanders employee driver was involved in a fatal Arizona collision. J.B. Hunt argues that Borderlanders was solely responsible for hiring, supervising, training, assigning, and dispatching its employee driver and has asked the court for summary judgment.

That motion remained undecided as of FreightWaves' August 21 report. The plaintiffs point to alleged safety alerts, crashes, inspection violations, and an English-proficiency issue, while J.B. Hunt disputes the legal basis for holding it responsible for the motor carrier's employee.

These are separate cases with separate facts. Their common operational lesson is that the brokerage's carrier-selection record, contract language, knowledge of red flags, and representation of its role can receive close scrutiny after a serious incident.

Why Montgomery Matters to Freight Brokers Now

The Supreme Court unanimously held on May 14, 2026, that the Federal Aviation Administration Authorization Act does not categorically preempt state-law negligent-selection claims against brokers when those claims concern motor-vehicle safety. The decision permits qualifying claims to proceed; it does not decide that a broker is negligent whenever a selected carrier crashes.

Before Montgomery, broker defendants often sought early dismissal under the FAAAA provision that preempts state laws related to broker prices, routes, or services. The Supreme Court held that the law's motor-vehicle safety exception can preserve negligent-selection claims, leaving courts to examine the applicable state law and the evidence in each case.

That distinction matters. A brokerage can ultimately prevail and still incur discovery, expert, insurance, and defense costs because the carrier-selection process must be reconstructed. Justice Brett Kavanaugh's concurrence expressly recognized that litigation, insurance, and more extensive carrier inquiries could impose significant costs on brokers even when they win.

Active FMCSA Authority Is a Baseline, Not a Complete Defense

FMCSA operating authority answers whether an entity is federally authorized for a stated role. It does not decide whether selecting that carrier for a particular load was reasonable under every state's negligence law, and Montgomery did not create a federal carrier-vetting checklist or safe harbor.

A defensible review can include active authority, insurance, safety-rating status, inspection and crash indicators, identity consistency, internal performance, equipment and commodity fit, customer restrictions, and unresolved fraud signals. The brokerage should define these checks with qualified counsel and its insurer rather than inventing different standards load by load.

Known Re-Brokering Can Become a Safety Fact

Unauthorized re-brokering breaks the connection between the carrier a broker approved and the carrier that actually arrives. In the AONE litigation, the reported evidence about earlier subcontracting mattered because it could support an argument that the original brokerage knew its carrier-selection controls were not reaching the final truck.

FMCSA describes double-brokering as a carrier accepting a brokered load and transferring it, without the shipper's or original broker's knowledge, to another carrier that performs the transportation. The agency also states that a motor carrier cannot broker loads without first obtaining separate broker authority, while federal law contains specific exceptions and rules for lawful carrier arrangements.

The operational issue is not the label alone. A broker needs to know whether the approved carrier will haul the load under its own authority, whether a requested substitution is contractually and legally permitted, and whether the final carrier receives a fresh review before freight is released.

What Freight Brokers Should Do Now

Freight brokers should treat undisclosed carrier substitution as a stop-work exception, not an administrative detail. The immediate objective is to connect the approved carrier record to the truck and driver at pickup and preserve evidence showing how every change was reviewed.

1. Define Carrier Transfer Rules in Writing

Carrier agreements should state whether subcontracting, trip leasing, interlining, co-brokering, or re-brokering is prohibited or requires advance written approval. The terms should identify who may approve an exception, what authority and insurance evidence is required, and when the load must return to the open market.

Contract language alone is insufficient if operations routinely tolerate contradictory behavior. Train carrier sales, dispatch, after-hours staff, and managers to use the same escalation path when a carrier says another truck, company, dispatcher, or authority will perform the move.

2. Verify the Actual Hauling Entity Before Pickup

Match the carrier name, USDOT number, operating authority, insurance, dispatch contact, truck, trailer, and driver presented for pickup against the approved load record. Use independently sourced contact information for material discrepancies; FMCSA specifically recommends checking the phone number posted in SAFER and calling that number when the contact does not match.

A clean certificate of insurance or familiar email thread does not resolve an identity mismatch. Pause release until the broker can explain and document the relationship among the approved carrier, dispatcher, driver, tractor, and any proposed replacement carrier.

3. Re-Vet Every Material Carrier Substitution

If a different motor carrier will transport the load, treat that carrier as a new selection unless counsel-approved procedures establish another lawful arrangement. Repeat the applicable authority, insurance, safety, identity, fraud, equipment, and customer-restriction checks before approving the change.

Do not rely solely on the first carrier's assurance that its subcontractor is safe. The AONE case illustrates why a broker may need its own evidence showing who performed the transportation and why the final selection was accepted.

4. Turn Prior Violations Into Structured Risk Signals

Record suspected re-brokering, unauthorized substitutions, pickup mismatches, identity discrepancies, payment disputes, and contract violations on the carrier profile. Define whether each event triggers a temporary hold, permanent block, management review, insurer notice, or heightened verification.

Free-text notes are easy to miss under coverage pressure. A structured reason, date, source, owner, disposition, and expiration rule lets the next representative see the prior event before tendering another load.

5. Preserve the Tender-Time Evidence

Store the exact evidence available when the brokerage made its decision, not only the carrier's current profile after an incident. Useful records include authority and insurance timestamps, safety data reviewed, customer requirements, internal history, approval or exception owner, rate confirmation, dispatch communications, tracking events, pickup verification, and changes in driver or equipment.

This record should show both what the broker knew and what it did. A screenshot without a decision, or a decision without its supporting data, leaves the process harder to explain.

6. Review Insurance and Incident Response With Counsel

Brokerages should confirm with qualified insurance and legal advisers how transportation-broker liability, contingent auto, general liability, cargo coverage, exclusions, retentions, and notice duties interact. Coverage names do not guarantee protection for every negligent-selection, vicarious-liability, fraud, or unauthorized-brokerage allegation.

The incident plan should identify who preserves records, contacts counsel and insurers, communicates with the shipper, and prevents routine retention schedules from deleting relevant data. Staff should avoid admissions or unsupported conclusions while facts are still being established.

Double-Brokering Control Checklist for Freight Brokers

This checklist connects carrier approval to the party that actually performs the transportation.

Control pointBroker actionEvidence to retain
ContractDefine permitted and prohibited carrier transfersSigned carrier agreement and current policy version
TenderConfirm carrier legal name, USDOT number, authority, and insuranceTimestamped source records and reviewer
DispatchMatch dispatcher, driver, tractor, trailer, and carrier identityVerified contact details and equipment record
SubstitutionStop release and re-vet the proposed carrierRequest, reason, new checks, and approval
PickupConfirm the arriving truck and driver before freight releaseCheck-in record, identity result, and exception status
Prior violationHold, block, or escalate under a defined ruleIncident type, source, date, owner, and disposition
DeliveryReconcile actual carrier and paperwork with the tenderPOD, tracking history, BOL, and carrier invoice
IncidentPreserve records and follow notice proceduresLegal hold, insurer notice, and communication log

Who This Matters For

Ideal reader:

  • Freight brokerages with 1-50 employees, especially growing 15-40-user teams.
  • Spot and mixed spot/contract teams that source capacity from small carriers or load boards.
  • Brokerages handling high-value, theft-targeted, urgent, cross-border, or after-hours freight.
  • Teams managing carrier approvals, substitutions, and compliance evidence in email or spreadsheets.

Who can likely deprioritize this:

  • Asset-based carriers with no brokerage operation; they still need their own lawful subcontracting and safety controls.
  • Businesses that do not arrange motor-carrier transportation.
  • Large enterprise brokerages with counsel-approved carrier governance, integrated identity verification, and mature litigation-hold processes, although the new cases remain relevant to their legal teams.

Manual Carrier Checks vs a Structured TMS Workflow

Manual carrier checks can confirm a single authority record, but they often fail to connect the selected carrier to later driver, truck, contact, or authority changes. A structured TMS keeps carrier evidence and exception decisions attached to the load so operations can identify when the party arriving at pickup differs from the party originally approved.

AreaEmail or spreadsheetStructured TMS workflow
Carrier approvalCurrent status copied into a threadTimestamped checks linked to the carrier
Prior violationsFree-text note or staff memorySearchable hold, block, and review reasons
SubstitutionPhone call or forwarded emailStop-work exception with owner and decision
Pickup identitySeparate message from facilityDriver and equipment check tied to the load
Decision recordResult without supporting contextEvidence, reviewer, reason, and timestamp
Incident responseRecords gathered after the eventPreserved tender, dispatch, tracking, and document history

How Modern Brokerages Handle Carrier-Selection Evidence

Modern brokerages use one repeatable carrier-approval policy, apply it at tender, and reopen the decision whenever the hauling entity or material risk information changes. They connect FMCSA authority, insurance, identity, safety signals, internal incidents, customer requirements, exception approvals, pickup verification, and delivery documents to the same load record.

Systems like ARK TMS are designed for growing freight brokerages and established 15-40-user teams that need fast spot-freight execution, carrier onboarding, compliance visibility, and searchable load records without enterprise-software complexity. ARK TMS is not a carrier, insurer, law firm, asset-management platform, custom development shop, or on-premise enterprise ERP.

What This Means Going Forward

Post-Montgomery broker-liability litigation will turn increasingly on evidence: which carrier was selected, which safety and identity signals were available, whether the broker knew about prior violations, who actually hauled the load, and how exceptions were handled. The AONE order is an early warning that a known pattern of unauthorized load transfers may be examined as more than a commercial dispute.

Brokers should not respond by rejecting carriers arbitrarily or treating allegations as proven facts. The durable response is a counsel-approved standard, consistent application, verified pickup identity, controlled substitutions, and a load-level record that can explain the decision years later.

Frequently Asked Questions

Did the court find AONE Brokerage liable for the crash?

No. The August 11 order denied summary judgment requests, allowing disputed issues to continue in the litigation. It was not a final judgment that AONE was negligent or legally responsible for the crash.

Does Montgomery make a freight broker liable for every carrier accident?

No. Montgomery held that FAAAA does not categorically preempt certain state negligent-selection claims tied to motor-vehicle safety. A plaintiff still must prove the required elements under the applicable law and facts.

Can a motor carrier re-broker a freight broker's load?

FMCSA states that a motor carrier cannot broker loads without separate property-broker authority. Lawful interchanges, leases, agents, co-brokering arrangements, and other structures can involve different rules, so brokerages should define permitted arrangements with qualified counsel and verify the authority actually used.

What should a broker do when a different truck or carrier arrives?

Pause freight release, verify the reason for the mismatch through independently sourced contacts, identify the actual hauling authority, repeat the required carrier checks, and document approval or rejection. A broker should not let pickup urgency bypass its substitution policy.

Is active FMCSA authority enough to defend a negligent-selection claim?

Active authority is an essential baseline but not a universal safe harbor. Brokerages should use a counsel-approved review that accounts for available authority, insurance, safety, identity, fraud, shipment-fit, customer, and internal-performance information.

Sources

Compliance Disclaimer

This article is for general informational purposes and does not provide legal, insurance, regulatory, safety, contract, or risk-management advice. Freight brokerages should review carrier-selection standards, contracts, authority rules, insurance, record retention, litigation holds, and incident-response procedures with qualified advisers based on their operations and jurisdictions.

Filed under
broker-liabilitydouble-brokeringmontgomery-v-caribecarrier-selectioncarrier-vettingfmcsafraud-preventionfreight-broker-complianceload-records

From reading to running

See the workflow with your freight.

Bring a representative load and the handoffs that slow your team down. We will map them in ARK.