On July 10, 2026, the Federal Motor Carrier Safety Administration quietly handed Aurora Innovation a waiver that allows its autonomous trucks to operate on public highways without meeting standard warning-device requirements — and without a human in the cab. What the FMCSA did not do is equally significant: it provided no updated liability framework to govern what happens when one of those trucks crashes. That regulatory blind spot is not a minor technicality. It is a legal vacuum that leaves crash victims, shippers, logistics operators, and insurers exposed at precisely the moment driverless freight is scaling fastest.
The FMCSA July 2026 Aurora Waiver: What It Does — and What It Doesn’t
The FMCSA’s July 10, 2026 waiver grants Aurora Innovation the authority to conduct driverless commercial trucking operations while deviating from certain standard warning-device compliance requirements. In place of those requirements, Aurora has proposed “alternative means” of achieving equivalent safety outcomes — a flexible standard that reflects the agency’s recognition that legacy vehicle rules were simply not written with fully autonomous Class 8 trucks in mind.
Aurora has publicly targeted deployment of more than 200 driverless trucks in commercial operation by the end of 2026, according to its Q1 2026 shareholder letter released in May 2026. That is not a pilot program. That is a commercial fleet. Aurora’s Q4 2025 earnings report noted that the Aurora Driver system had already surpassed 250,000 driverless miles with zero Aurora-attributed collisions — a safety record the company cites as justification for rapid scaling. Independent data suggests autonomous fleets broadly have demonstrated an 85% reduction in police-reported crashes compared to human drivers. Those figures are meaningful, but they do not resolve the legal question of who pays when something does go wrong. To understand the scale of what is being authorized without a corresponding liability structure, consider the following summary of where autonomous trucking stands as of mid-2026:
| Factor | Current Status (2026) | Regulatory Coverage |
|---|---|---|
| FMCSA Aurora Waiver | Granted July 10, 2026 — driverless ops, alternative warning compliance | Operational only; no liability rules |
| Aurora Driverless Fleet Target | 200+ trucks by end of 2026 (Q1 2026 shareholder letter) | No federal liability framework |
| Aurora Driver Safety Record | 250,000+ driverless miles, zero Aurora-attributed collisions (Q4 2025) | No federal liability framework |
| Hirschbach Motor Lines DaaS Deal | 500-truck Aurora Driver-as-a-Service contract; delivery begins 2027 | No carrier liability rule for AI failure |
| FMCSA ADS Maintenance Rule | Proposed rule expected by May 2026; not yet finalized | Gap — state tort law only in the interim |
| AV Insurance Minimums (Kentucky) | SB 241 (2025) raises minimum to $5M for AVs over 62,000 lbs | State-level only; no federal standard |
| Uniform State Autonomous Liability Law | No federal standard; 50 states operate independently | Patchwork; no consistency |
| Federal Liability Preemption (FAAAA) | Shields brokers in transportation-service claims | Unclear scope for autonomous tech-failure claims |
The FMCSA has authority over motor carrier safety regulations under 49 U.S.C. Subtitle VI, but that authority has historically been exercised over human-operated commercial vehicles. The agency has issued guidance documents and waivers for autonomous vehicles, but it has not promulgated a single binding rule addressing product liability for autonomous systems, manufacturer duty of care for AI-driven decision-making, or operator responsibility when software — not a driver — causes a crash. The FMCSA has signaled it expects to propose a rule addressing inspection, repair, and maintenance standards for automated driving systems by May 2026, but a proposal is not a rule, and a rule is not yet law. In the meantime, victims of autonomous truck crashes are left navigating a liability landscape that was never designed for the technology now operating on American highways.
Traditional Truck Liability: A Framework Built for Humans
To appreciate how profoundly autonomous trucking disrupts existing legal structures, it helps to understand what those structures were built to do. Traditional commercial truck accident liability in the United States rests on several interlocking legal doctrines, each of which presupposes a human being somewhere in the chain of causation.
Respondeat superior holds employers liable for the negligent acts of their employees committed within the scope of employment. In a standard truck crash, this means the motor carrier is vicariously liable for its driver’s negligence. The driver is the proximate cause; the carrier is the legal target.
Negligent entrustment imposes liability on an owner who allows an incompetent or reckless person to operate a vehicle. The doctrine requires a human operator whose fitness can be evaluated.
Negligent hiring, retention, and supervision holds carriers liable when they knew or should have known that a driver posed a danger. Again, the entire doctrine is built around human behavior — hiring records, driving histories, training protocols, supervisor oversight.
Direct negligence against a carrier can arise from inadequate maintenance, faulty equipment, or improper loading — areas where human decisions created a dangerous condition.
All of these doctrines share a common architecture: a human acted, or failed to act, and that human action (or inaction) caused harm. Strip the human out of the cab, and the doctrinal scaffolding begins to collapse. Respondeat superior requires an employee-tortfeasor. Negligent entrustment requires a human entrusted with the vehicle. Negligent hiring requires a hire. When the “driver” is a software stack running on LIDAR, radar, and machine learning inference, courts and plaintiffs’ attorneys face a fundamental question that existing doctrine does not cleanly answer: who is the tortfeasor?
The Federal Motor Carrier Safety Regulations, codified at 49 C.F.R. Parts 300–399, impose specific duties on motor carriers, drivers, and vehicles. Those regulations address driver qualifications (Part 391), hours of service (Part 395), vehicle inspection and maintenance (Part 396), and accident reporting (Part 390). They were written with human drivers as the default assumption. The FMCSA has exempted autonomous vehicles from some of these requirements — including, now, certain warning-device rules for Aurora — but it has not replaced those exempted requirements with autonomous-specific liability standards. The result is a regulatory structure with holes precisely where the new technology operates.
The Federal Preemption Problem: FAAAA and the Autonomous Tech Gap
Any serious analysis of autonomous truck liability must grapple with the Federal Aviation Administration Authorization Act of 1994 (FAAAA), codified at 49 U.S.C. § 14501(c)(1). The FAAAA preempts state laws “related to a price, route, or service of any motor carrier.” That preemption language has been interpreted broadly by federal courts and, critically, has been used to shield freight brokers from state tort liability.
The U.S. Supreme Court’s 2023 decision in Westfall v. Luna declined to resolve the circuit split on whether the FAAAA preempts state negligence claims against freight brokers who negligently select motor carriers. That split remains unresolved as of 2026, meaning that whether a broker can be sued for contributing to an autonomous truck crash depends heavily on which federal circuit the crash occurs in.
The preemption problem deepens in the autonomous context. When an autonomous truck crashes because its software made a defective routing decision, is that a “service” of the motor carrier for FAAAA purposes? If Aurora’s Driver-as-a-Service platform is characterized as a transportation service rather than a technology product, FAAAA preemption arguments become available to shield Aurora from state tort claims. Conversely, if the Aurora Driver system is characterized as a product — software and hardware integrated into the truck — then product liability law applies, and preemption arguments weaken.
This characterization question is not academic. It will determine whether victims can sue in state court under familiar negligence and products liability theories, or whether they face a preemption wall that forces them into a narrower federal framework. Courts have not yet addressed this question in the autonomous trucking context because, as of 2026, no major autonomous truck crash litigation has produced a published federal appellate decision on FAAAA preemption scope for AI-driven systems. That gap in precedent is itself a form of legal exposure.
Who Is Actually Liable When a Driverless Truck Crashes?
In the absence of clear federal rules, liability for autonomous truck crashes in 2026 will be fought out under a combination of state tort law, existing federal motor carrier regulations, and contract law — with multiple potential defendants asserting multiple overlapping and conflicting theories. The following is a structured analysis of each potential liable party.
Driver Negligence and Vicarious Liability
In a fully driverless operation — which is precisely what the FMCSA’s July 2026 Aurora waiver authorizes — there is no driver in the cab. The traditional respondeat superior claim against a motor carrier for driver negligence is therefore unavailable. There is no employee-tortfeasor whose conduct can be imputed to the carrier.
Some Aurora deployments may retain a remote human monitor — sometimes called a “safety operator” — who can observe the truck but cannot physically intervene in the way a co-pilot could. Whether a remote monitor’s failure to detect and respond to an impending hazard constitutes actionable negligence is an open question. If it does, vicarious liability could flow to whoever employs that monitor — Aurora, the motor carrier, or a third-party safety services contractor. If courts hold that remote monitoring does not create a duty sufficient to support negligence liability, that avenue closes.
The practical implication: in driverless Aurora deployments, plaintiffs will need to look beyond traditional driver-negligence theories from day one. The litigation strategy shifts immediately toward product liability, carrier liability under FMCSA regulations, and negligence theories targeting the technology developer and system operator.
Negligent Selection and Operator Control
Motor carriers retain potential liability for negligent selection of the autonomous system itself. If a carrier chose to deploy an autonomous driving system that had known defects, an inadequate safety record, or unresolved technical problems — and a crash resulted — negligent selection arguments become available. This is an adaptation of the negligent entrustment doctrine to the technology-selection context.
Operator control liability is more complex. Aurora’s Driver-as-a-Service model involves Aurora maintaining substantial control over the driving system — route management, software updates, remote monitoring infrastructure, operational design domain parameters. If Aurora controls the system and the system causes a crash, Aurora’s control becomes a basis for direct liability. If the motor carrier customizes operational parameters — say, accepting loads that push the system outside its designed operational envelope — the carrier’s decisions create independent negligence exposure.
Aurora Innovation: Technology Manufacturer and System Operator
Aurora occupies a dual role that has no precise precedent in motor carrier law: it is simultaneously the manufacturer of the autonomous driving system and, under its DaaS model, the ongoing operator of that system in commercial service. That dual role creates layered liability exposure.
As a manufacturer, Aurora faces strict products liability claims under state law for design defects, manufacturing defects, and failure to warn. If the Aurora Driver system made a defective decision — failed to detect a hazard, misjudged a gap in traffic, executed an unsafe lane change — plaintiffs will allege that the system was defectively designed. Aurora’s response will be that its system met or exceeded the performance of human drivers, pointing to its record of more than 250,000 driverless miles with zero Aurora-attributed collisions. That safety record is a powerful defense, but it does not establish that any specific crash was not caused by a system defect.
As a system operator, Aurora has ongoing duties to maintain, update, and monitor the driving system. If a crash results from a software bug that Aurora knew about but had not patched, or from a sensor degradation that Aurora’s monitoring systems should have detected, operator negligence claims arise independently of product liability.
The FMCSA’s anticipated proposed rule on inspection, repair, and maintenance standards for automated driving systems — expected by May 2026 — will, if finalized, create a regulatory benchmark against which Aurora’s maintenance practices can be measured. Until that rule exists and takes effect, the standard of care for ADS maintenance is defined by expert testimony, industry practice, and Aurora’s own internal standards.
Motor Carriers: Operator Liability Without Operator Control
Motor carriers operating Aurora-equipped trucks face a peculiar liability position: they are the FMCSA-registered operators responsible for regulatory compliance, but they do not control the driving decisions made by the Aurora Driver system. Under 49 C.F.R. Part 390, the motor carrier bears ultimate responsibility for the safe operation of vehicles in its fleet. That regulatory responsibility does not disappear because the carrier has outsourced the actual driving to an autonomous system.
Carriers can therefore face liability on two tracks simultaneously: as the FMCSA-regulated operator responsible for ensuring the vehicle is safely operated, and as the entity that chose to deploy Aurora’s system under a DaaS contract. If the DaaS contract allocates risk back to Aurora for system-caused crashes, the carrier may have contractual indemnification rights — but those contract rights do not bind injured third parties, who can still sue the carrier directly under FMCSA regulations.
The insurance implications are significant. Kentucky’s Senate Bill 241, enacted in 2025, raises the minimum insurance requirement from $1 million to $5 million for autonomous vehicles weighing more than 62,000 lbs — a direct response to the higher liability exposure that autonomous freight operations create. That kind of state-level legislative action reflects a broader recognition that existing insurance minimums were calibrated for human-driven trucking and may be inadequate for autonomous operations. Carriers and their insurers operating in Kentucky and states that follow similar legislative paths will face substantially higher insurance costs, and victims will have access to larger minimum coverage pools.
Shippers, Brokers, and Logistics Platforms
Shippers who tender cargo to autonomous truck fleets and brokers who arrange those shipments occupy a potentially liable position that depends heavily on their level of involvement in carrier selection and operational oversight. The core negligent selection theory — that a broker or shipper knew or should have known that the carrier it selected was unsafe — applies in the autonomous context just as it does in traditional trucking.
The autonomous dimension adds a new wrinkle. If a broker or shipper selects an autonomous carrier knowing that the carrier’s system is operating outside its approved operational design domain — in weather conditions, geographic areas, or traffic environments for which the system was not validated — that selection decision could support a direct negligence claim. The FAAAA preemption issue discussed above will determine whether those state-law negligence claims survive in federal court.
As of 2026, NHTSA’s standing general order requires manufacturers and operators of autonomous vehicles to report crashes meeting certain thresholds. Data compiled through November 2025 showed 5,202 autonomous vehicle accidents reported in the United States — a figure that reflects the growing scale of AV deployment across all vehicle categories, not just heavy trucks. That reporting data creates a discoverable record: if a broker or shipper had access to crash data suggesting systemic safety problems with a specific autonomous carrier and selected that carrier anyway, that knowledge becomes evidence of negligent selection.
The Scale Problem: 200 Trucks Before the Rules Exist
Aurora’s Q1 2026 shareholder letter targets more than 200 driverless trucks in commercial operation by the end of 2026. The Hirschbach Motor Lines DaaS contract commits to 500 trucks with deliveries beginning in 2027. These are not speculative projections — they are contractual and investor-disclosed commitments made by a company that has already demonstrated the operational capability to execute them, having logged more than 250,000 driverless miles without an Aurora-attributed collision.
The scale problem is not primarily a safety problem in the narrow sense. Aurora’s safety record is genuinely impressive, and the 85% reduction in police-reported crashes that autonomous fleets have demonstrated compared to human drivers suggests that widespread deployment may ultimately make roads safer. The scale problem is a liability architecture problem: the legal and regulatory framework that will govern crashes involving these trucks does not yet exist at the federal level, and it is being assembled piecemeal at the state level as fleets grow.
Consider what happens when an Aurora truck crashes on an interstate highway in a state with no autonomous vehicle liability statute, injuring occupants of a passenger vehicle. The victims’ attorney faces the following simultaneous uncertainties:
- Whether the crash was caused by a system defect (product liability against Aurora) or operator error in route or load selection (negligence against the carrier or shipper)
- Whether FAAAA preempts state tort claims against the freight broker who arranged the load
- Whether the motor carrier’s FMCSA-regulated operator status creates non-delegable duties that override the DaaS contract’s risk allocation
- Whether Aurora’s remote monitoring personnel owed a duty of care to the crash victims
- What discovery is available from Aurora’s proprietary system logs, sensor data, and software version records — and whether Aurora will assert trade secret protections to limit disclosure
- Whether the state in which the crash occurred has enacted AV-specific liability legislation, and if so, whether that legislation favors or limits victim recovery
Each of these uncertainties represents a litigation risk for victims and a potential escape route for defendants. The absence of a unified federal liability framework means that outcomes will vary dramatically depending on jurisdiction, judge, and the specific contractual arrangements between Aurora, the motor carrier, and the shipper on that particular load.
What Crash Victims Need to Know Right Now
If you or someone you know is injured in a crash involving an autonomous truck in 2026, the legal landscape is more complex than a standard commercial truck accident — and the evidence preservation requirements are more demanding. Here is what matters most in the immediate aftermath.
The data window closes fast. Autonomous trucks generate extraordinary volumes of sensor data, system logs, and decision-record data. Aurora’s trucks operate with LIDAR, radar, cameras, and onboard computing systems that record detailed information about every second of operation before, during, and after a crash event. That data is the primary evidence in any autonomous truck crash case. It is also proprietary, stored on Aurora’s infrastructure, and subject to routine data retention policies that may result in its deletion if a litigation hold is not triggered quickly. An attorney experienced in autonomous vehicle litigation needs to send preservation demands to Aurora, the motor carrier, and any logistics platform involved within days of the crash — not weeks.
Multiple defendants, multiple theories. As the analysis above makes clear, a single autonomous truck crash can produce viable claims against Aurora (product liability and operator negligence), the motor carrier (FMCSA regulatory liability and negligent selection), the shipper or broker (negligent selection), and potentially remote monitoring personnel. Building a complete liability picture requires early investigation of all of these relationships — the DaaS contract between Aurora and the carrier, the broker agreement governing the load, the carrier’s insurance coverage and its adequacy given state minimums, and Aurora’s maintenance and update records for the specific truck involved.
Insurance coverage is a moving target. States are actively revising insurance requirements for autonomous heavy vehicles. Kentucky’s 2025 legislation requiring $5 million in minimum coverage for AVs over 62,000 lbs reflects a recognition that $1 million — the traditional federal minimum for large trucks — is inadequate for the liability exposure autonomous freight creates. Other states may follow. Knowing which state’s insurance requirements apply to the specific operation involved, and what coverage actually exists across all potentially liable parties, is essential early work in any autonomous truck crash case.
Expert testimony will be central. Autonomous truck crash cases will require experts in autonomous systems engineering, software architecture, LIDAR and sensor technology, machine learning decision systems, and FMCSA regulatory compliance — in addition to the accident reconstruction and medical experts standard in any serious truck crash case. Identifying and retaining qualified experts early is critical, because the technical complexity of these cases means that expert analysis must begin long before litigation deadlines arrive.
The regulatory record matters. Aurora’s NHTSA crash reports, FMCSA waiver filings, and any communications between Aurora and federal regulators about the specific system version involved in the crash are potentially discoverable. The NHTSA standing general order requiring AV crash reporting means there is a federal record of Aurora’s prior incidents. That record, combined with Aurora’s internal safety data, forms the evidentiary foundation for establishing what Aurora knew and when it knew it.
Frequently Asked Questions About Autonomous Truck Liability
Who is legally responsible when a driverless autonomous truck causes a crash in 2026?
Responsibility in a driverless truck crash in 2026 is not assigned to a single party by any federal rule — because no such rule exists. Liability will be determined under state tort law, existing FMCSA regulations, and the specific contractual arrangements governing the crash. Potential defendants include Aurora Innovation (as manufacturer and system operator), the motor carrier (as FMCSA-regulated operator), the freight broker or shipper (under negligent selection theories), and potentially remote monitoring personnel. Because no single federal liability framework governs these crashes, outcomes depend heavily on the jurisdiction, the specific facts of the crash, and the quality of early legal investigation.
Does the FMCSA’s July 2026 Aurora waiver affect crash victims’ legal rights?
The July 2026 waiver affects Aurora’s operational authority — it allows Aurora to run driverless trucks without meeting certain warning-device requirements. It does not create or eliminate any private right of action for crash victims. Victims’ legal rights are governed by state tort law and existing federal motor carrier regulations, not by the waiver itself. However, the waiver’s existence is legally significant in one respect: it means Aurora’s driverless operations were federally authorized, which Aurora will use to argue that its operations were not inherently negligent. Plaintiffs will counter that federal authorization does not insulate Aurora from state-law product liability or negligence claims.
Can a freight broker or shipper be sued when an autonomous truck causes a crash?
Yes, under state tort law negligent selection theories — but whether those claims survive in federal court depends on FAAAA preemption analysis, which varies by circuit. Brokers and shippers who selected an autonomous carrier knowing of systemic safety issues with its system face the strongest negligent selection exposure. As autonomous crash data accumulates in NHTSA’s reporting system — 5,202 AV accidents had been reported through November 2025 — the argument that brokers and shippers had constructive knowledge of autonomous system risks becomes stronger over time.
What evidence is most important to collect after a driverless truck crash?
The most critical evidence in a driverless truck crash case is the autonomous system’s own data: sensor logs, system decision records, software version and update history, operational design domain parameters at the time of the crash, and any pre-crash anomaly or error flags recorded by Aurora’s monitoring systems. This data is held by Aurora, not by the motor carrier, and it is subject to deletion under routine data retention policies. Preservation demands must be sent immediately. Physical evidence — the truck itself, tire marks, crash scene documentation — is also essential, as is early identification and interview of any witnesses to the crash sequence.
Will autonomous truck crash claims be handled differently than regular truck accident claims?
Yes, in several important respects. The defendants are different — Aurora Innovation as system manufacturer and operator is a defendant type that does not exist in traditional truck crash litigation. The evidence is different — autonomous system data replaces driver logs, hours-of-service records, and drug and alcohol testing results as the core technical evidence. The expert requirements are different — autonomous systems engineering expertise is essential. And the legal theories are different — product liability against the ADS manufacturer is a primary claim rather than a supplemental one. The fundamental goal is the same as in any serious truck crash case: full compensation for victims’ injuries, losses, and future needs. But the path to that compensation runs through a more complex legal and technical landscape than traditional commercial truck accident litigation.
Marcus Holloway is a commercial truck accident claims specialist with deep expertise in FMCSA regulations, trucking company liability, and high-value settlement negotiations across the United States. Marcus is not an attorney, and the information provided is for educational purposes only.