Secure Autonomous
FeedbackGet alertsCheck a deployment
Cases / REG-0016

Benavides v. Tesla: a jury assigns a third of the responsibility for a 2019 Autopilot crash to the maker of the system, Miami, 1 August 2025

Ended in harmMachines · Road vehiclesHuman supervisesProduction
REG-0016Updated 2026-10-286 sources, 6 linkedPublic regulatory

Disclosure: The editor owns shares in Tesla, a long-term holding from before the Register began. See Independence.

What happened

According to trial reporting, a 2019 Tesla Model S on Autopilot, with the driver pressing the accelerator, ran through a Key Largo T-intersection into a parked Tahoe that was pushed into two pedestrians, killing one and seriously injuring the other. On the record, Autopilot could be engaged on a road its manual said it was not meant for. A federal jury held Tesla 33% responsible, and Tesla has appealed.

A plain summary of the typed record below; where they differ, the record governs.

Verification: 6 of 6 checks complete
✓ Structured and checkedevery claim typed and sourced, then checked by the Register's automated checker for missing sources and mistyped claims
✓ Sources linked6 of 6 sources link to the record (5 to a primary record)
✓ Sources checked claim by claimevery claim checked against its source on 2026-10-20
✓ Interpretation checked statement by statementeach statement of the Register's interpretation checked against a source on 2026-10-21
✓ Reviewed by the editorreviewed 2026-10-28
✓ Reply offeredTesla: offered
Corrections · 17, latest 2026-10-20

Changes to what this case says, with the reason. Every earlier version is kept.

  • 2026-10-20: Sources: cc: title. Found in the editor's source re-check of 19-20 october 2026: the page's headline is 'miami tesla autopilot trial: $329 million jury verdict', by david a. wood, dated august 1, 2025, with 'the original story is below' dated july 23, 2025; the old title was a paraphrase without the author.
    Show the change
    Before: CarComplaints, 'Miami Tesla Autopilot trial: jury verdict', August 2025 (trial reporting)
    After: CarComplaints, 'Miami Tesla Autopilot Trial: $329 Million Jury Verdict', David A. Wood, 1 August 2025 (first published 23 July 2025 during the trial)
  • 2026-10-20: Controls: c-v1. Found in the editor's source re-check of 19-20 october 2026: 'eventually produced' implied tesla produced the data, which the record does not show. tesla's post-trial reply (ecf no. 603) says the plaintiffs' experts acknowledged 'nothing's really deleted' from the autopilot computer in mcgee's vehicle, that the court found no bad faith and no prejudice 'by the delay in getting the data', and that a tesla technician 'accidently deleted this file' from tesla's own servers; the court's order (ecf no. 612) refers to 'data-related evidence obtained from the vehicle'. bucket and confidence unchanged.
    Show the change
    Before: Vehicle data capture (eventually produced)
    After: Vehicle data capture (the data survived on the car's Autopilot computer and was obtained for trial after a dispute over whether Tesla had withheld it)
  • 2026-10-20: Outcome: cost. Found in the editor's source re-check of 19-20 october 2026: $242.57 million is the judgment against tesla after the 33% apportionment (final judgment, ecf no. 538; order, ecf no. 612); the jury's verdict itself was $129 million in compensatory damages ($59 million and $70 million, ecf no. 612 footnote 1) plus $200 million in punitive damages, so 'verdict' was the wrong word for the $243 million figure.
    Show the change
    Before: ~$243M verdict against Tesla (appeal pending)
    After: ~$243M judgment against Tesla (appeal pending)
  • 2026-10-20: Fields: recovery: automated fallback. Found in the editor's source re-check of 19-20 october 2026: 'none; no stop or hand-off' was cited to the final judgment, which says nothing about the car's behaviour, and stated the plaintiffs' side only. carcomplaints reports the allegation that the car gave no alert and never engaged its emergency brakes and that mcgee drove through the intersection; tesla's post-trial reply (ecf no. 603) says the car 'continuously warned him that he had deactivated cruise-control braking' and gave a '[t]ake over immediately' warning 1.5 seconds before impact. both accounts stated, marked disputed, confidence lowered to medium.
    Show the change
    Before: {"value": "None; no stop or hand-off at the road's end", "confidence": "high", "disputed": false, "source_ids": ["SDFL"]}
    After: {"value": "No automatic stop: the car did not stop before the intersection. Whether it signalled a hand-off is disputed: plaintiffs allege it gave no alert and never braked; Tesla says it continuously warned that cruise control would not brake while the accelerator was pressed and gave a take-over warning 1.5 seconds before impact", "confidence": "medium", "disputed": true, "source_ids": ["CC", "ECF603"]}
  • 2026-10-20: Fields: evidence: interpretation: source ids. Found in the editor's source re-check of 19-20 october 2026: the final judgment (sdfl) says nothing about evidence; tesla's post-trial reply (ecf no. 603) records that the plaintiffs told the jury tesla 'deleted ... the file', and the court's order (ecf no. 612) records tesla's challenge to 'the improper admission of data-related evidence obtained from the vehicle', which it denied.
    Show the change
    Before: ["SDFL"]
    After: ["ECF603", "ECF612"]
  • 2026-10-20: Fields: outcome: source ids. Found in the editor's source re-check of 19-20 october 2026: the final judgment (sdfl) gives the amounts but not the injuries; the court's order of february 2026 (ecf no. 612) states the crash killed benavides leon and caused 'significant injuries to angulo' and confirms the $242,570,000.00 judgment.
    Show the change
    Before: ["SDFL"]
    After: ["SDFL", "ECF612"]
  • 2026-10-20: Fields: envelope: basis: source ids. Found in the editor's source re-check of 19-20 october 2026: carcomplaints does not say that restricting engagement was itself litigated; tesla's post-trial reply (ecf no. 603) does: the plaintiffs' design-defect claim rested on three theories, 'operational design domain, driver monitoring system, and automatic emergency braking/forward collision warning', and their expert 'faulted tesla for not geofencing autopilot'. cited for the claim as worded.
    Show the change
    Before: ["CC"]
    After: ["CC", "ECF603"]
  • 2026-10-20: Fields: decision. Found in the editor's source re-check of 19-20 october 2026: the field gave the plaintiffs' allegation of no warning without tesla's answer to it; tesla's post-trial reply (ecf no. 603) says 'his vehicle continuously warned him that he had deactivated cruise-control braking by pressing the accelerator' and describes a '[t]ake over immediately' collision warning 1.5 seconds before impact. both accounts are now stated; the field stays disputed.
    Show the change
    Before: {"value": "Plaintiffs alleged the car detected the stop sign and obstacles but gave no warning and never braked; Tesla's position is that the driver was pressing the accelerator, which overrode Autopilot", "source_ids": ["CC"]}
    After: {"value": "Plaintiffs alleged the car detected the stop sign and obstacles but gave no warning and never braked; Tesla's position is that the driver was pressing the accelerator, which overrode Autopilot, and that the car continuously warned him that pressing the accelerator had turned off cruise-control braking and gave a take-over warning 1.5 seconds before impact", "source_ids": ["CC", "ECF603"]}
  • 2026-10-20: Fields: actor: source ids. Found in the editor's source re-check of 19-20 october 2026: the final judgment (sdfl) does not mention autopilot or the model s; the court's order of february 2026 (ecf no. 612, new source) says mcgee owned 'a 2019 tesla model s' 'equipped with automatic driving features, one of which tesla termed "autopilot"', so the fact is cited to that court record.
    Show the change
    Before: ["SDFL", "CC"]
    After: ["ECF612", "CC"]
  • 2026-10-20: Fields: mandate: principal. Found in the editor's source re-check of 19-20 october 2026: no source mentions 'terms of use'; carcomplaints reports the owner's manual warnings ('the model s owner's manual clearly warns that autopilot ...'), and the jury verdict form (ecf no. 534) asks whether 'tesla place[d] the 2019 model s on the market with a defect'. the final judgment (sdfl) does not mention the driver or the manual, so it is no longer cited.
    Show the change
    Before: {"value": "The driver, under Tesla's terms of use; Tesla as designer and seller", "source_ids": ["SDFL"]}
    After: {"value": "The driver, under the owner's manual's warnings; Tesla as designer and seller", "source_ids": ["CC", "ECF534"]}
  • 2026-10-20: Inference: source ids. Found in the editor's source re-check of 19-20 october 2026: the verdict form (ecf no. 534, new source) carries the apportionment between tesla and the driver and the punitive-damages finding; the notice of appeal (ecf no. 616) carries the appeal.
    Show the change
    Before: ["SDFL"]
    After: ["SDFL", "ECF534", "ECF616"]
  • 2026-10-20: Inference: value. Found in the editor's source re-check of 19-20 october 2026: the second sentence ('with the boeing case, it is one of two cases where accountability reached the maker of the automation') is contradicted by the register's own records: accountability also reached the makers of the automation in the cruise case (reg-0003: nhtsa consent order and civil penalty, deferred prosecution agreement with the us attorney's office and criminal fine, dmv permit suspension, cpuc penalty) and the knight capital case (reg-0007: sec penalty, censure and cease-and-desist), as well as the boeing case (reg-0009: department of justice deferred prosecution agreement). a search of every object in objects/ (reg-0001 to reg-0037) and objects/withdrawn for 'jury', 'verdict' and 'punitive' finds them only in this case, so the replacement sentence is checked against the register: the other makers were reached by regulators or prosecutors, and the air canada tribunal (reg-0010) and the workday ruling (reg-0020) were decided by a tribunal and a judge, not a jury. the jury verdict form (ecf no. 534) apportions 33% to tesla and 67% to the driver, george mcgee, and awards punitive damages; it records answers and amounts, not reasons. tesla's notice of appeal (ecf no. 616) shows the judgment is under appeal. the interpretation was signed by the editor on 2026-10-19; signed_by and signed_on are set to null and the editor must sign the new wording.
    Show the change
    Before: Here a jury held the maker of a driver-assistance system partly responsible, with punitive damages, not only the driver. With the Boeing case, it is one of two cases where accountability reached the maker of the automation
    After: Here a jury held the maker of a driver-assistance system partly responsible, with punitive damages, not only the driver. It is the Register's only case so far in which a jury, rather than a regulator or prosecutor, placed responsibility on the maker of the automation. The judgment is under appeal, and the verdict form does not show the jury's reasons
  • 2026-10-16: Inference: value. Found in an outside review of the published record on 16 october 2026: the interpretation implied this was the first case to reach a maker, overlooking the boeing case (reg-0009).
    Show the change
    Before: With this case, accountability reached the maker of the automation, not only the operator or the person supervising it
    After: Here a jury held the maker of a driver-assistance system partly responsible, with punitive damages, not only the driver. With the Boeing case, it is one of two cases where accountability reached the maker of the automation
  • 2026-10-16: Controls: c-e2: confidence. Found in an outside review of the published record on 16 october 2026: the register has not seen the trial evidence on this point and the verdict is under appeal.
    Show the change
    Before: high
    After: medium
  • 2026-10-13: Fields. Independent check against the linked records before right-of-reply letters.
    Show the change
    Before: decision, design-domain basis and jury reasoning stated without a source; 'about 60 mph' striking two people; driver's share 'two thirds'; data claim without Tesla's side
    After: plaintiffs' allegation and Tesla's position both recorded; manual wording quoted; driver's accelerator input and the Tahoe recorded; driver settled; court's bad-faith ruling noted
  • 2026-10-13: Fields and sources. Claims aligned to what each linked record says, found on review.
    Show the change
    Before: crash facts, design domain, and data-recovery claim cited to the final judgment; 'first jury verdict against Tesla over Autopilot in a wrongful-death case'; appeal pending
    After: judgment linked for the verdict only; crash facts typed as press-reported assertions; data claim recorded as contested at trial; 'first verdict' removed (not in the record); post-trial motions denied and appeal filed, from the docket
  • 2026-10-13: Controls: c-e2. A control has one state per case; entries in two states merged into the state the record supports.
    Show the change
    Before: failed: Design-domain restriction (engagement allowed off-domain); absent: Hard geofence to the design domain
    After: failed: Design-domain restriction (engagement allowed off-domain); Hard geofence to the design domain (absent)
Record history · 8 entries
  • 2026-10-28: No statement from Tesla within 14 days of the offer.
  • 2026-10-20: Source added: Order on Amended Renewed Motion for Judgment as a Matter of Law or, Alternatively, Motion for New Trial, Benavides v. Tesla, Inc., No. 21-cv-21940-BLOOM/Torres (S.D. Fla.), ECF No. 612 (signed 19 Feb 2026, entered 20 Feb 2026).
  • 2026-10-20: Source added: Jury Verdict Form, Benavides v. Tesla, Inc., No. 21-cv-21940-BLOOM/Torres (S.D. Fla.), ECF No. 534, 1 August 2025.
  • 2026-10-20: Source added: ECF616.interest.
  • 2026-10-20: Source added: ECF603.interest.
  • 2026-10-16: Interpretation reworded for readers before sign-off; its meaning is unchanged.
  • 2026-10-14: Right of reply offered to Tesla.
  • 2026-10-14: Checked by the editor against the linked records.

Controls that address what went wrong

3 controls missing or failed; 1 in place and worked. The line under each is the concrete form it would have taken in this case.

Machine-enforceable scope
Driver attention as the envelope
Failed · Mandate layer
Halt and hand off on uncertainty or refusal
Stop at end-of-road
Absent · Decision layer
Hard domain restriction
Failed: Design-domain restriction (engagement allowed off-domain). Absent: Hard geofence to the design domain.
Failed · Envelope layer
Independent audit log
Vehicle data capture (the data survived on the car's Autopilot computer and was obtained for trial after a dispute over whether Tesla had withheld it)
Worked · Evidence layer

New cases like this, once a week. A short email when a case, signal or rule touches machines. Free; unsubscribe in one click.

Get the weekly email

How it unfolded, layer by layer

MandateWhat it was told to do
Who deployed it: The driver, under the owner's manual's warnings; Tesla as designer and seller. The task: Driver assistance with cruise control; the owner's manual warned that Autopilot was primarily intended for highways and freeways. Disclosed to supervisor: Warnings existed in the owner's manual; the jury nonetheless assigned a third of the responsibility to Tesla. The Register does not know the jury's reasons.
ActorWhat acted
Autopilot on a 2019 Model S
InputsWhat it could see
A T-intersection at the end of Card Sound Road in Key Largo; the driver had dropped his phone and was looking for it
DecisionHow it chose
Plaintiffs alleged the car detected the stop sign and obstacles but gave no warning and never braked; Tesla's position is that the driver was pressing the accelerator, which overrode Autopilot, and that the car continuously warned him that pressing the accelerator had turned off cruise-control braking and gave a take-over warning 1.5 seconds before impact
EnvelopeWhat it was allowed to do
Limits in place: The owner's manual said Autopilot is primarily intended for highways and freeways and should not be used on city streets; it could nonetheless be engaged on this road. Basis: Whether engagement should have been technically restricted to the intended roads was at issue in the case; the Register has not seen the trial evidence on it.
ActionWhat it did
With the driver pressing the accelerator, the speed rose to about 62 mph, overriding the 45 mph cruise setting; the car went through the intersection and hit a parked Tahoe, which was pushed into two pedestrians
OutcomeWhat happened
Ended in harm. Severity: fatality and serious injury.
EvidenceWhat can be proven
Record of the event: What crash data existed and when Tesla held it was contested at trial; Tesla's post-trial brief says the court ruled the data was not withheld in bad faith. Interpretation: The evidence question (what data existed and who held it) was part of the case at trial; the Register records it as contested, not as an established fact or intent.
RecoveryWhat could be stopped, undone, answered for
Automatic fallback: No automatic stop: the car did not stop before the intersection. Whether it signalled a hand-off is disputed: plaintiffs allege it gave no alert and never braked; Tesla says it continuously warned that cruise control would not brake while the accelerator was pressed and gave a take-over warning 1.5 seconds before impact. Accountability: Judgment against Tesla on a 33% share; the driver settled separately and was not a defendant. Tesla's post-trial motions were denied on 20 February 2026 and it appealed to the Eleventh Circuit on 16 March 2026.

The same gap in other cases

Cases where the same control was missing or failed. Those in another world are the cross-domain comparisons the Register exists to make.

ControlSame worldOther worlds
Machine-enforceable scope·PocketOS 2026 (software agents), Replit and SaaStr 2025 (software agents), The DAO 2016 (agents moving money)
Hard domain restrictionWaymo construction zones 2026, Tesla FSD reduced visibilityReplit and SaaStr 2025 (software agents)

Cost and accountability

Severityfatality and serious injury
Affectedone pedestrian killed; one injured
Cost~$243M judgment against Tesla (appeal pending)
Regulatory or legal consequencejury verdict with punitive damages
Technical recoveryAutomatic fallback: No automatic stop: the car did not stop before the intersection. Whether it signalled a hand-off is disputed: plaintiffs allege it gave no alert and never braked; Tesla says it continuously warned that cruise control would not brake while the accelerator was pressed and gave a take-over warning 1.5 seconds before impact.
AccountabilityJudgment against Tesla on a 33% share; the driver settled separately and was not a defendant. Tesla's post-trial motions were denied on 20 February 2026 and it appealed to the Eleventh Circuit on 16 March 2026
InterpretationWhy it matters beyond its domain. Here a jury held the maker of a driver-assistance system partly responsible, with punitive damages, not only the driver. It is the Register's only case so far in which a jury, rather than a regulator or prosecutor, placed responsibility on the maker of the automation. The judgment is under appeal, and the verdict form does not show the jury's reasons. Signed by Saurabh Bhatnagar on 2026-10-21.

Right of reply

Named partyStatus
TeslaOffered 2026-10-14; no statement as of 2026-10-28Respond for Tesla

Help shape the Register

A person reads every answer; changes it leads to are logged in the methodology. To dispute a claim or reply for a named company, use Respond, dispute, or submit.

Did this page help with what you came to do?