You will be provided with a research report. The body of the report will contain some citations to references.

Citations in the main text may appear in the following forms:
1. A segment of text + space + number, for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels 15"
2. A segment of text + [number], for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels[15]"
3. A segment of text + [number†(some line numbers, etc.)], for example: "Li Qiang constructed a socioeconomic status index (SES) based on income, education, and occupation, dividing society into 7 levels[15†L10][5L23][7†summary]"
4. [Citation Source](Citation Link), for example: "According to [ChinaFile: A Guide to Social Class in Modern China](https://www.chinafile.com/reporting-opinion/media/guide-social-class-modern-china)'s classification, Chinese society can be divided into nine strata"

Please identify **all** instances where references are cited in the main text, and extract (fact, ref_idx, url) triplets. When extracting, pay attention to the following:
1. Since these facts will need to be verified later, you may need to look for some context before and after the citation to ensure that the fact is complete and understandable, rather than just a simple phrase or short expression.
2. If a fact cites multiple references, then it should correspond to two triplets: (fact, ref_idx_1, url_1) and (fact, ref_idx_2, url_2).
3. For the third form of citation (i.e., where the citation source and link appear directly in the text), the ref_idx should be uniformly set to 0.
4. If the main text does not specify the exact location of the citation (for example, only the reference list is listed at the end of the article, without specifying the citation point in the text), please return an empty list.

You should return a JSON list format, where each item in the list is a triplet, for example:
[
    {
        "fact": "Text segment from the original document. Note that Chinese quotation marks should use full-width marks. And add a single backslash before the English quotation mark to make it a readable for python json module.",
        "ref_idx": "The index of the cited reference in the reference list for this text segment.",
        "url": "The URL of the cited reference for this text segment (extracted from the reference list at the end of the research report or from the parentheses at the citation point)."
    }
]

Here is the main text of the research report:
# Liability Allocation in Shared Human–Machine Driving: A Multi-Jurisdictional Analysis of ADAS Accident Responsibility

## TL;DR

- **Liability at SAE Levels 1–2 remains anchored to the human driver**, but the wall between "driver fault" and "manufacturer defect" is crumbling: the August 2025 Florida federal jury verdict against Tesla (33% fault to Tesla) is the first to hold an ADAS maker liable in a third-party death, signaling that design choices, ODD non-enforcement, and marketing can override the "attentive driver" defense.
- **The decisive legal fault line is SAE Level 3**, where liability shifts from human to machine: Mercedes-Benz publicly accepts responsibility for its Drive Pilot when engaged; the UK (Automated Vehicles Act 2024) and Germany (StVG §§1a–1d) have built statutory regimes around this shift, while the US has no federal statute and relies on a patchwork of state law, NHTSA recalls, and product-liability litigation.
- **The single most effective reform lever is not liability rules but system design**: mandatory camera-based driver monitoring (already required in the EU), enforced Operational Design Domains, standardized "black box" data (EDR/DSSAD), and honest nomenclature. Jurisdictions that mandate these (EU, UK) convert vague fault fights into evidence-based determinations; jurisdictions that don't (US) are resolving the questions through unpredictable jury verdicts.

## Key Findings

1. **The SAE J3016 framework governs the entire debate.** Levels 1–2 are "driver support"; the human is always the driver and legally responsible. Levels 3–5 are "automated driving systems" (ADS) that perform the entire dynamic driving task within an Operational Design Domain (ODD). Level 3 is the pivot point — the system drives, but a "fallback-ready user" must resume control on a takeover request.
2. **Level 2 is where most real-world crashes and litigation occur** because these systems (Tesla Autopilot/FSD, GM Super Cruise, Ford BlueCruise) are widely deployed and marketed aggressively while legally requiring constant human supervision. This creates the "mode confusion" and "automation complacency" that recur in nearly every fatal case.
3. **The US relies on litigation and recall, not statute.** NHTSA's engineering analysis EA22-002, closed April 25, 2024 after reviewing 956 crashes, found a "critical safety gap" and produced the December 2023 recall of about 2.03 million Teslas; the Office of Defects Investigation identified "at least 13 crashes involving one or more fatalities and many more involving serious injuries, in which foreseeable driver misuse of the system played an apparent role." NHTSA then opened a query into whether the recall remedy itself was adequate.
4. **Mercedes-Benz Drive Pilot represents the cleanest liability model**: at Level 3, when the system is properly engaged within its ODD, the manufacturer accepts responsibility. But Mercedes's acceptance is narrower than press coverage suggests — it accepts product-defect responsibility, not liability for driver negligence or out-of-ODD misuse.
5. **Europe has built an integrated regulatory-liability stack**: UNECE R157 (type approval for Level 3 ALKS), the General Safety Regulation (mandatory driver monitoring), the revised Product Liability Directive 2024 (strict liability now covers software/AI with burden-shifting presumptions), and mandatory DSSAD "black boxes." The proposed AI Liability Directive, however, was withdrawn in 2025.
6. **The UK Automated Vehicles Act 2024 is the most comprehensive statutory scheme in the world**, creating the "user-in-charge," "no-user-in-charge," and "Authorised Self-Driving Entity" (ASDE) roles and shifting criminal and civil accountability away from the human when a self-driving feature is engaged.
7. **Criminal law consistently falls on the human operator, not the machine or maker** — Kevin Riad (Tesla, probation) and Rafaela Vasquez (Uber, probation) both illustrate Madeleine Elish's "moral crumple zone": the nearest human absorbs blame the automated system structurally deflects.

## Details

### I. Technical Foundations

**SAE J3016 levels.** SAE International's J3016 standard (first issued 2014, revised 2021) defines six levels of driving automation, 0 through 5, and is the de facto global taxonomy, adopted by NHTSA and incorporated into an increasing number of legal frameworks. The critical conceptual line runs between Levels 1–2 ("driver support features," where the human remains the driver and must constantly supervise) and Levels 3–5 ("automated driving systems," which perform the entire dynamic driving task, or DDT). At Level 1 a single system performs either longitudinal control (adaptive cruise control) or lateral control (lane-keeping assist); at Level 2 the vehicle performs both simultaneously but the human "is required to monitor the driving environment" and remain ready to take control. Level 3 ("conditional automation") means the system performs the entire DDT within a limited ODD "with the expectation that the driver is receptive to requests to intervene." Level 4 ("high automation") removes that expectation — the system must reach a "minimal risk condition" on its own if the ODD limit is reached — but is still ODD-limited. Level 5 is unconditional. Notably, discrete features like automatic emergency braking and electronic stability control are *not* classified above Level 0 because they do not provide *sustained* lateral/longitudinal control.

**How the systems work and who deploys them.** Adaptive cruise control (ACC) and lane-keeping assist (LKA) are the Level 1 building blocks; combined, they constitute Level 2. Currently deployed Level 2 systems include Tesla Autopilot and "Full Self-Driving (Supervised)," GM Super Cruise, and Ford BlueCruise — all of which, despite their names, legally require a fully attentive driver. Mercedes-Benz Drive Pilot is the only Level 3 system certified for consumer sale in the US (California and Nevada); Mercedes launched it in Germany via a press release dated May 6, 2022 (sales from May 17, 2022, priced at €5,000 on the S-Class), operating on approved motorways initially up to 60 km/h. It uses LiDAR, cameras, microphones, and a road-wetness sensor, with redundant steering, braking, and electrical systems so the vehicle "remains manoeuvrable even if one of these systems fails."

**ODD, DMS, and the handoff problem.** The Operational Design Domain defines the conditions (road type, speed, weather, geography) under which a system is designed to function. ODD *enforcement* — whether the vehicle prevents activation outside its design envelope — is a central liability question, as the Tesla cases show. Driver monitoring systems (DMS) range from torque sensors ("hands on wheel") to camera-based gaze tracking. "Mode confusion" (the driver misunderstands which automation is active) and "automation complacency" (over-trust leading to disengagement) are well-documented human-factors failures. The "handoff" or takeover problem is acute at Level 3: when a driver is "out of the loop," regaining situational awareness takes time. Human-factors research finds that takeover request (TOR) lead times of 6–14 seconds produce degraded situational awareness, with performance improving and leveling off around 16–30 seconds; drivers achieve driving-related stabilization (steering, speed) in roughly 8–10 seconds after takeover, but physiological stabilization (heart rate, skin conductance) takes considerably longer. Per Mercedes-Benz USA's own Drive Pilot documentation, "if a user does not respond to the takeover request within the maximum allotted time of ten seconds… the vehicle's emergency stop procedure will begin." These findings expose the core dilemma: a system that requires a distracted human to re-engage in seconds is designing the human into the "moral crumple zone."

### II. Existing Legal Frameworks — Comparative Analysis

**United States.** There is no comprehensive federal AV statute. NHTSA regulates under the Motor Vehicle Safety Act, treating both ADS and ADAS as "motor vehicle equipment." Its principal oversight tools are the Federal Motor Vehicle Safety Standards (FMVSS), defect investigations/recalls, and the **Standing General Order 2021-01 on Crash Reporting**, issued June 29, 2021, which requires manufacturers and operators to report crashes involving Level 2 ADAS or Levels 3–5 ADS. For Level 2, a crash is reportable if the system was engaged within 30 seconds of a crash that involved a fatality, a hospital transport, a vulnerable road user, an airbag deployment, or a tow-away. NHTSA announced it would propose a rule to codify the Order, which was otherwise scheduled to expire in April 2026. [Honigman](https://www.honigman.com/alert-2693) Substantive liability is overwhelmingly state law: product liability (design defect, manufacturing defect, failure to warn — under the Restatement (Second) of Torts §402A and the Restatement (Third) of Products Liability), negligence, and comparative fault. States lead on operational regulation — California (DMV permitting), Nevada, and Arizona are the principal AV jurisdictions.

**European Union.** The EU integrates type-approval and liability. The **General Safety Regulation (EU) 2019/2144 (GSR)** mandates advanced safety systems for new vehicles, including Driver Drowsiness and Attention Warning (DDAW, mandatory for new types from July 6, 2022 and all new vehicles from July 7, 2024) and Advanced Driver Distraction Warning (ADDW, from July 7, 2024 for new types and July 7, 2026 for all new vehicles), plus mandatory Event Data Recorders. **UNECE Regulation No. 157** provides binding type-approval requirements for Level 3 Automated Lane Keeping Systems (in force January 22, 2021; [Wikipedia](https://en.wikipedia.org/wiki/Automated_lane_keeping_systems) the 01 series of amendments raised the maximum operating speed from 60 km/h to 130 km/h for systems with lane-change capability), [Interregs](https://www.interregs.com/articles/spotlight/252/updated-un-ece-regulation-on-automated-lane-keeping-systems-published-) and requires a DSSAD "black box." The **revised Product Liability Directive (EU) 2024/2853** (in force December 8/9, 2024; transposition deadline December 9, 2026) expressly brings software and AI systems within strict product liability [Pinsent Masons](https://www.pinsentmasons.com/out-law/analysis/revised-eu-product-liability-regime-expands-ai-software-providers) and, critically, introduces rebuttable presumptions of defectiveness and causation that shift the burden toward the manufacturer where the claimant faces excessive technical/scientific complexity. The proposed **AI Liability Directive** (proposed September 28, 2022, procedure 2022/0303(COD)) — which would have harmonized fault-based AI liability by easing the claimant's burden of proof — was listed for withdrawal in the European Commission's 2025 Work Programme (adopted February 11, 2025) on the stated ground of "no foreseeable agreement," with the withdrawal formalized and published in the Official Journal (C/2025/5423) on October 6, 2025. AI-related liability in the EU therefore now rests on the revised PLD plus national tort law, raising fragmentation concerns.

**United Kingdom.** The **Automated and Electric Vehicles Act 2018** established a first-party insurance model: for listed automated vehicles, the insurer is directly liable to the victim when the vehicle is driving itself, then may pursue recourse against manufacturers. The **Automated Vehicles Act 2024** builds a full framework on the Law Commissions' recommendations. It creates the "user-in-charge" (UiC) — a person in the driving seat who is *not* legally the driver while a self-driving feature is engaged, but must respond to a "transition demand" — and the "no-user-in-charge" (NUiC) vehicle overseen by a licensed operator. Legal accountability shifts from the person in the seat to the **Authorised Self-Driving Entity (ASDE)**, which must be authorized (good repute, financial standing) and bears ongoing responsibility for the vehicle's safe and legal operation throughout its life. The Act reserves self-driving terminology and criminalizes misleading marketing. Full implementation was pushed from 2026 to the second half of 2027.

**Germany.** Germany was the first country to legislate comprehensively. A 2017 amendment to the Road Traffic Act (StVG) permitted Level 3 systems and clarified (§1a(4)) that a person who activates an automated function remains the "driver." The **2021 Autonomous Driving Act** (in force July 28, 2021) added Level 4 operation without a human fallback in approved operational areas, introducing the "technical supervisor" (§1d(3)) — a natural person who can deactivate the vehicle. Strict liability of the vehicle keeper (Halterhaftung) is preserved throughout; Level 3 drivers face presumed-fault liability (§18(1)(1) StVG) with the burden on the driver. The Kraftfahrt-Bundesamt (KBA) serves as the national type-approval authority for automated driving functions.

**Japan and China.** Japan amended the Road Transport Vehicle Act and Road Traffic Act in 2019 (in force April 1, 2020) [Lexology](https://www.lexology.com/library/detail.aspx?g=f84441bd-758d-475c-a1b2-8f48ca68102a) to permit Level 3, and added a permit regime for Level 4 "specified automated driving" (in force April 1, 2023). Civil liability is governed by the **Automobile Liability Security Act (ALSA)**, under which the vehicle owner/operator bears near-strict liability for third-party injury (subject to three narrow exemptions — no negligence by owner or driver, no vehicle defect, and causation by a third party or victim), covered by compulsory insurance; even where a vehicle defect causes the accident, the owner remains liable to the victim and the insurer pursues recourse against the manufacturer. This owner-centric model was deliberately retained to ensure prompt victim compensation. China's **Shenzhen Special Economic Zone Intelligent Connected Vehicle Regulations** (adopted June 23, 2022; in force August 1, 2022) were the first comprehensive Chinese ICV law; they adopt a "driver-priority liability" model — for a vehicle with a driver (including engaged L3), the driver bears compensation liability, with recourse against the manufacturer for defects; for fully driverless L4/L5, the owner/manager bears liability. Shanghai's Pudong provisions (in force February 1, 2023) follow a parallel structure. A national pilot scheme (MIIT and three other ministries, November 17, 2023) permits L3/L4 on restricted roads via a "manufacturer + operator" joint application, and MIIT conditionally approved the first L3 production models (Changan, BAIC) in December 2025.

### III. Case Law and Incidents

**Tesla Autopilot — the litigation wave.** The landmark development is the **Benavides Leon/Angulo case** (S.D. Fla.). On April 25, 2019, George McGee's Tesla Model S on Enhanced Autopilot ran a stop sign and a flashing red light at about 62 mph on Card Sound Road in Key Largo — a road outside Autopilot's intended controlled-access-highway ODD — killing 22-year-old Naibel Benavides Leon and severely injuring Dillon Angulo. On August 1, 2025, a Miami federal jury found Tesla liable, assigning 33% of fault to Tesla and 67% to McGee (who was not a defendant), and awarded $129 million compensatory plus $200 million punitive damages. Tesla's 33% share of compensatory damages was about $42.6 million. It was the first third-party wrongful-death Autopilot case to reach a jury verdict and the first jury finding that Autopilot was defective. In February 2026, U.S. District Judge Beth Bloom denied Tesla's motion to overturn the verdict, ruling that the evidence "more than supported" it; Tesla has said it will appeal. Plaintiffs' counsel argued "Tesla designed Autopilot only for controlled-access highways yet deliberately chose not to restrict drivers from using it elsewhere," combined with Musk's public statements that Autopilot drove better than humans.

**Banner v. Tesla (Florida).** On March 1, 2019, Jeremy Banner's 2018 Tesla Model 3 struck a semi-trailer crossing US Highway 441 near Delray Beach at about 68 mph, shearing off the roof and killing him; Autopilot had been engaged about 10 seconds before impact. The NTSB (Highway Accident Brief HAB2001) found the "Autopilot vision system did not consistently detect and track the truck," forward collision warning did not alert, automatic emergency braking did not activate, and the crash occurred outside Autopilot's ODD (US 441 is not a limited-access highway) — closely paralleling the 2016 Joshua Brown fatality. On February 26, 2025, Florida's Fourth District Court of Appeal, in *Tesla, Inc. v. Kim Banner* (No. 4D2023-3034, opinion by Judge Kuntz), reversed a trial-court order allowing a punitive-damages claim, holding that Florida requires gross negligence "so egregious that it is equivalent to criminal manslaughter" and that the record did not support it, noting the evidence indicated Tesla's Autopilot features were "state-of-the-art" and complied with industry and regulatory standards. This ruling was subsequently invoked by Tesla as persuasive authority in its (unsuccessful) post-trial motion in the Benavides Leon case.

**Huang v. Tesla (California).** Apple engineer Walter Huang died on March 23, 2018 when his Model X, on Autopilot for nearly 19 minutes, veered into a highway barrier at about 71 mph near Mountain View. The NTSB found Tesla's driver-assistance system, driver distraction (Huang was likely playing a game on his phone), and highway-barrier/road-marking issues all contributed, and faulted Tesla's ineffective monitoring of driver engagement, finding that the forward collision warning did not alert and automatic emergency braking did not activate. Tesla settled the wrongful-death suit for an undisclosed, sealed amount in April 2024, on the eve of trial.

**Riad (California — manslaughter).** Kevin George Aziz Riad was the first person in the US charged with a felony for a fatal crash involving a widely used partial-automation system: on December 29, 2019, his Tesla Model S on Autopilot ran a red light in Gardena at about 74 mph, killing Gilberto Alcazar Lopez and Maria Guadalupe Nieves-Lopez. He pleaded no contest to two counts of vehicular manslaughter and received probation. The criminal charging documents did not mention Autopilot — underscoring that criminal law targets the human driver's conduct, not the technology.

**Uber ATG / Elaine Herzberg (Tempe, Arizona).** On March 18, 2018, an Uber test vehicle (a development ADS with a human safety driver) struck and killed Elaine Herzberg as she crossed with a bicycle — the first pedestrian fatality involving a fully autonomous test vehicle. The NTSB concluded the main cause was safety driver Rafaela Vasquez's failure to monitor the road (she was streaming a TV show), with contributing factors including Uber's inadequate safety culture and Arizona's insufficient oversight. Prosecutors declined to charge Uber; Vasquez was charged with negligent homicide and, in July 2023, pleaded guilty to endangerment and received three years' probation. This is the paradigmatic "moral crumple zone" case.

**NHTSA EA22-002 and the December 2023 recall.** NHTSA opened its Autopilot engineering analysis (EA22-002) in 2021–2022 after a series of crashes, including Teslas striking stationary emergency vehicles. Closing the analysis on April 25, 2024, the Office of Defects Investigation reviewed 956 crashes and identified "at least 13 crashes involving one or more fatalities and many more involving serious injuries, in which foreseeable driver misuse of the system played an apparent role." On December 12, 2023, Tesla had filed recall 23V-838 covering roughly 2.03 million vehicles (model years 2012–2023, all Autopilot-equipped models), conceding the "prominence and scope of the system's controls may not be sufficient to prevent driver misuse" and deploying an over-the-air remedy to strengthen driver-engagement warnings and reduce mode confusion. NHTSA subsequently opened a recall query in 2024 to assess whether the remedy was adequate, noting crashes after the update and that part of the remedy could be reversed by the driver.

**Mercedes Drive Pilot liability statements.** Mercedes-Benz publicly stated (2022) it accepts legal responsibility for Drive Pilot when the Level 3 system is properly engaged. This is genuinely significant but frequently overstated in coverage: Mercedes's own statements make clear it accepts responsibility for *product defects* while the system drives within its ODD, not for driver negligence or for use where the driver "failed to comply with their duty of care" (e.g., activating outside approved conditions). Thatcham Research's Matthew Avery aptly called liability "complex and nuanced… there will be times when an accident is and isn't the carmaker's responsibility."

**Cruise robotaxi (San Francisco, October 2, 2023).** Although a Level 4 system (useful here for contrast), the Cruise incident crystallizes the data/transparency dimension of liability. After a human-driven hit-and-run threw a pedestrian into the path of a Cruise robotaxi, the Cruise vehicle braked but struck her; per the California DMV's October 24, 2023 Order of Suspension, the robotaxi then "attempted to perform a pullover maneuver," dragging the pedestrian about 20 feet at up to 7 mph. The DMV suspended Cruise's permits, finding the vehicles unsafe and that Cruise had withheld the full footage of the dragging. NHTSA's October 2024 consent order imposed a $1.5 million penalty for Cruise's failure to fully report the crash under the Standing General Order. The episode shows that at higher automation levels, liability turns heavily on the manufacturer's control over — and candor about — the evidentiary record.

### IV. Responsibility Boundaries

**The driver's continuing duty at Level 2.** Under every current framework, the Level 2 driver remains fully responsible. Tesla, GM, and Ford all instruct drivers to remain attentive and hands-ready. This is why criminal and civil fault still lands primarily on drivers (Riad; McGee at 67%). But the Benavides Leon verdict shows the "attentive driver" doctrine is not an absolute shield: when a manufacturer designs a system that can be engaged outside its ODD, monitors drivers ineffectively, and markets the system as more capable than it is, a fact-finder can assign substantial fault to the maker.

**The "moral crumple zone."** In "Moral Crumple Zones: Cautionary Tales in Human-Robot Interaction" (*Engaging Science, Technology, and Society* 5 (2019), pp. 40–60), Madeleine Clare Elish articulates "the concept of a moral crumple zone to describe how responsibility for an action may be misattributed to a human actor who had limited control over the behavior of an automated or autonomous system." As she puts it, "just as the crumple zone in a car is designed to absorb the force of impact… the human in a highly complex and automated system may become simply a component… that bears the brunt of the moral and legal responsibilities when the overall system malfunctions." Vasquez and Riad exemplify how the nearest human absorbs blame the system structurally deflects.

**Manufacturer duties.** Manufacturers face potential liability for design defects (including inadequate ODD enforcement and driver monitoring), failure to warn, defective over-the-air software updates (now squarely "products" under the EU PLD), and marketing that induces foreseeable misuse. The distinction between *user misuse*, *foreseeable misuse*, and *system defect* is doing enormous work: NHTSA's finding that Autopilot did not prevent "foreseeable driver misuse" reframes what manufacturers had treated as pure user error into a design responsibility.

**The role of DMS in shifting liability.** Robust, camera-based driver monitoring is becoming the fulcrum. If a manufacturer can prove (via DMS logs) that a properly warned driver ignored escalating alerts and disengaged, fault shifts to the driver; conversely, weak monitoring (Tesla's torque-based system, which NHTSA found inadequate) exposes the manufacturer. This is why the EU's GSR mandate for DDAW/ADDW is as much a liability instrument as a safety one.

**Data and evidence.** Event Data Recorders (EDR) capture crash-moment vehicle data; the Data Storage System for Automated Driving (DSSAD), mandated under UNECE R157 and the draft UN Global Technical Regulation, records the crucial who-was-driving question — when the ADS was activated, when transition demands were issued, and when the human resumed control — stored in read-only form and retrievable by authorized investigators. Access to and control over this data is decisive: the Cruise episode (withheld footage) and Tesla data disputes show that whoever controls the black box shapes the liability outcome.

**Marketing and nomenclature.** The naming controversy is now a live liability issue. Following a 2022 complaint, a California administrative law judge (Juliet Cox of the Office of Administrative Hearings), in a November 20, 2025 proposed decision adopted by the DMV on December 16, 2025, ruled that Tesla's "Full Self-Driving" name is "actually, unambiguously false and counterfactual" and that a "reasonable consumer likely would believe that a vehicle with Full Self-Driving Capability can travel safely without a human driver's constant, undivided attention." The DMV gave Tesla 60 days to fix its marketing or face a 30-day suspension of its dealer license; Tesla sued the DMV in February 2026 to reverse the ruling even after altering its language to "Full Self-Driving (Supervised)." Deceptive naming featured centrally in the Benavides Leon jury's reasoning, tying marketing directly to liability exposure.

### V. Analysis: Where the Law Is Heading

The jurisdictions divide into two camps. The **EU and UK have chosen ex ante structural regulation** — mandatory driver monitoring, ODD-bounded type approval (R157), statutory role definitions (ASDE, user-in-charge), first-party insurance, and burden-shifting product liability. These convert the human-vs-machine question into an evidence-driven determination made largely before litigation. The **US has chosen ex post adjudication** — no federal statute, reliance on NHTSA recalls and state tort law, and resolution through jury verdicts. The result is the volatility now visible: a Florida jury imposing a nine-figure verdict on Tesla while a Florida appellate court simultaneously bars punitive damages in a factually similar case under a manslaughter-equivalent standard. Germany and Japan occupy a middle position, preserving traditional keeper/owner strict liability while layering statutory recognition of automated functions on top. The convergence point across all systems is the Level 3 shift and the recognition — via Mercedes's model, the UK's ASDE, and the EU PLD's software coverage — that once the machine is driving within its ODD, responsibility should migrate to the entity that designed and deployed it.

## Recommendations

**Stage 1 — Immediate (regulatory actions available now):**

1. **Standardize nomenclature and restrict marketing.** Adopt the UK model of reserving "self-driving"/"autonomous" terminology for genuinely authorized systems and criminalizing misleading claims. The evidence that this matters is overwhelming: ALJ Juliet Cox found "Full Self-Driving" to be "actually, unambiguously false and counterfactual," [Electrek](https://electrek.co/2026/02/23/tesla-sues-california-dmv-reverse-fsd-false-advertising-ruling/) and the Benavides Leon jury tied liability directly to Musk's capability claims. *Benchmark to escalate:* any manufacturer marketing that a regulator or court finds misleading should trigger mandatory renaming and corrective advertising.
2. **Mandate camera-based driver monitoring for all Level 2+ systems**, as the EU GSR already does through DDAW/ADDW. Torque-based "hands-on" detection is demonstrably insufficient (per NHTSA's EA22-002 findings). *Benchmark:* systems unable to detect driver gaze/attention should be prohibited from combined lateral+longitudinal (Level 2) operation.
3. **Require ODD enforcement (geofencing).** Systems should refuse to engage, or should degrade gracefully, outside their design domain. The Benavides Leon and Banner deaths both occurred with Autopilot active outside its intended controlled-access-highway ODD. *Benchmark:* any fatal crash where the system was engaged outside its stated ODD should be presumptively a design defect.

**Stage 2 — Near-term (statutory):**
4. **Enact clear statutory liability allocation at each SAE level.** The absence of a US federal statute forces courts to improvise, producing unpredictable "nuclear verdicts." Adopt the emerging consensus: driver responsibility at Levels 1–2; a rebuttable shift to the ADS/manufacturer/ASDE at Level 3 when the system is engaged within its ODD; and manufacturer/operator responsibility at Levels 4–5.
5. **Adopt the ASDE / manufacturer-certification model** (UK AV Act 2024) so that a legally accountable, financially sound entity is identifiable for every authorized automated feature.
6. **Reform insurance toward first-party/no-fault for automated modes** (UK AEV Act 2018 model): the insurer compensates the victim directly and pursues manufacturer recourse, ensuring prompt victim relief without litigating the human-vs-machine question at the point of claim. Japan's ALSA achieves a similar effect through owner near-strict liability plus insurer subrogation.

**Stage 3 — Structural/international:**
7. **Uniform data-sharing and black-box standards.** Mandate EDR + DSSAD with standardized formats, tamper protection, and guaranteed access for investigators and litigants. Whoever controls the data controls the liability outcome; neutral access is essential.
8. **Adopt burden-shifting judicial doctrines**, following the EU PLD 2024's rebuttable presumptions of defect and causation where technical complexity makes proof excessively difficult for the claimant.
9. **Harmonize internationally through UNECE WP.29** (R157, the draft UN Global Technical Regulation on ADS, DSSAD) to prevent regulatory arbitrage.
10. **Embed human-factors requirements**: minimum takeover-time budgets calibrated to out-of-the-loop research (16–30 seconds for planned transitions), graceful degradation to a minimal-risk condition, and design that does not rely on an unrealistically rapid human re-engagement.

## Caveats

- **This is a fast-moving field and several key items are unsettled.** The Benavides Leon verdict (variously reported around $243M when netting the compensatory apportionment and $329M including full punitive damages) is on appeal; its precedential force is not yet fixed, and the *Banner* appellate ruling shows Florida courts remain reluctant to permit punitive damages absent manslaughter-level egregiousness.
- **Mercedes's liability acceptance is narrower than commonly reported** — it covers product defects during proper Level 3 operation, not driver negligence or out-of-ODD use. Treat "Mercedes takes 100% liability" claims with caution.
- **The US regulatory trajectory is uncertain.** The Standing General Order faced a 2026 expiration and a possible codification rulemaking, and a new federal AV framework was announced by the Department of Transportation in 2025; reporting on the latter comes from law-firm client alerts rather than final rules.
- **Some data points come from secondary/industry sources** (trade press, law-firm alerts) rather than primary texts, particularly for China's 2025 commercialization milestones and the exact dollar breakdown of the Tesla verdict; these are reliable for the fact of the event but specific figures should be verified against primary records before citation in formal work.
- **Human-factors takeover-time figures are drawn from driving-simulator studies**, which may not fully replicate real-world behavior; the numbers indicate ranges and trends rather than universal thresholds.
- **NTSB findings** establish probable cause for safety purposes and are not binding in civil or criminal litigation, though they carry substantial persuasive weight.


Please begin the extraction now. Output only the JSON list directly, without any chitchat or explanations.