Products Liability Law Daily Wrap Up, CAUSATION—ELECTRONIC PRODUCTS—E.D. Mo.: Widow’s case proceeds against Lyft as court finds slain driver’s murder was foreseeable, (Oct 13, 2026)

By Molly Platnick

The court declined to dismiss negligence or products liability claims for lack of proximate cause.

The federal district court for the Eastern District of Missouri granted in part and denied in part Lyft’s motion to dismiss a case brought by the widow of a driver who was killed by a rider with a history of violent crime. The widow’s Sixth Amended Complaint accused Lyft of negligence and products liability, arguing the rideshare app’s defective design and the company’s failure to warn caused her husband’s death. Lyft denied liability because the murder was not the “direct result” of its conduct, as required under Missouri’s civil codes. The court clarified that “direct result” referred to proximate cause. It found the widow plausibly asserted that Lyft had proximately caused the driver’s death because its defective data collection and failure to warn about the dangerous rider made the murder foreseeable. The foreseeability also assigned Lyft a duty to protect the driver from criminal acts. The court only dismissed the widow’s negligent training claim, which is not a recognized cause of action in Missouri (Newman v. Lyft, Inc., No. 4:23-cv-853-MAL (E.D. Mo. Sept. 30, 2026)).

Background—from operative complaint. The decedent was murdered in April 2021 while working as a Lyft driver. The rider had carjacked another Lyft driver at “virtually the same location” a few weeks earlier. Lyft’s data systems track riders’ information and activity and collect publicly available crime data. The ridesharing company should allegedly have identified the driver as a “dangerous criminal” because his email address and account history suggested he had committed fraud and other carjackings before the murder. The rider also used an anonymous payment method “which often correlates to criminal behavior” on the platform. Despite possessing this information, Lyft did not deactivate or flag the rider’s account or warn the decedent a driver had recently been carjacked at the pickup location, the complaint asserted.

In her Sixth Amended Complaint, the decedent’s widow raised claims for (1) negligence, (2) negligent undertaking, (3) strict liability for defective product design, (4) negligent product design, (5) failure to warn, and (6) negligent training.

Lyft responded the claim must be dismissed for (1) lack of products liability causation, (2) lack of proximate causation due to an intervening criminal act, (3) lack of duty, (4) failure to allege key elements, and (5) failure to plead a recognized cause of action.

Design defect. The issue before the court was whether the widow plausibly alleged that a defect in the Lyft app’s design proximately caused the decedent’s death. Mo. Rev. Stat. § 537.760 codifies the elements of a common law strict liability design defect claim. The statute stipulates, in relevant part, a plaintiff must be “damaged as a direct result” of the product’s defect. Lyft contended the decedent was not “damaged as a direct result” of any defect in its app. The court disagreed, finding “direct result” meant proximate cause within the meaning of § 537.760. In State ex rel. Mo. Highway & Transp. Comm’n v. Dierker, the Missouri Supreme Court ruled “directly resulted from” means proximate cause in Mo. Rev. Stat. § 537.600. The court in this case deduced “because both sections belong to the same chapter of the Revised Statutes, the natural inference is that the phrase ‘direct result’ has the same meaning in both sections.” Proximate cause exists where a "foreseeable risk [is] created by the defendant’s acts or omissions.” In this case, the complaint asserted that Lyft defectively designed its app by omitting safety features to protect drivers from “dangerous riders.” The widow plausibly alleged that the omission was the proximate cause of the decedent’s death because a driver’s murder was a foreseeable risk from the app’s defective design.

The court denied Lyft’s motion to dismiss the negligent design claim under the same theory of proximate cause.

Failure to warn. The operative complaint asserted Lyft failed to warn the decedent of the dangers of picking up the rider because its app did not “incorporate adequate data collection and analysis technology to protect drivers from danger.” As with design defect, a plaintiff pleading failure to warn must show he sustained damages as a direct result of the defendant’s insufficient warning. The court again interpreted direct result to mean proximate cause, citing the Missouri Supreme Court’s decision in Moore v. Ford. Proximate causation for a failure to warn claim requires plaintiffs to prove they would have altered their behavior if given an adequate warning. Lyft argued the decedent would have picked up the rider, even if given an adequate warning. Missouri law, however, has a presumption that a warning will be heeded: “[i]f there is sufficient evidence from which a jury could find that the plaintiff did not already know the danger, there is a presumption that a warning will be heeded.” Here, there were no facts suggesting the decedent knew about the rider’s criminal history, and the court found a “fair inference” he would not have picked him up if the app had warned him. Because the decedent’s murder was the type of injury a warning was designed to prevent, the complaint plausibly alleged that Lyft’s failure to warn was a proximate cause of the decedent’s death.

Negligent conduct. The allegations in the widow’s Sixth Amended Complaint established Lyft’s negligent conduct “reasonably and probably caused” the decedent’s death.

Lyft responded it was not liable because the rider’s conduct was an intervening cause. An intervening cause will only cut off proximate causation if it is a “superseding cause.” Dierker, the Missouri Supreme Court case referenced above, held an event is a superseding cause “to the extent the damages are surprising, unexpected, or freakish.” Lyft claimed the murder was "the type of surprising, unexpected, or freakish act that cuts off proximate cause under Missouri law.” The court disagreed. It considered the rider carjacking another rideshare driver and the carjacking resulting in the driver’s death an “unsurprising, reasonably expected, and ordinary consequence of Lyft’s actions.” Lyft relied on DJ. by and Through R.J. v. First Student, in which the Missouri Supreme Court found “a driver’s various traffic law violations, without evidence of similar prior violations, was sufficiently ‘unexpected’ to constitute an intervening cause that broke the chain of causation.” The court here rejected the comparison because Lyft’s failure to respond to the rider’s previous crimes on rideshare drivers meant the decedent’s murder was not “sufficiently unexpected.”

The court denied Lyft’s “attenuation” and public policy arguments with little analysis.

Duty to protect. Lyft denied liability for general negligence and negligent undertaking (counts 1 and 2), asserting it did not have a common law duty to protect the decedent. Missouri generally does not recognize a duty to protect third parties from criminal acts. However, the court noted this is “not a categorical rule” and must be analyzed based on the foreseeability of the crime. The court analyzed Lyft’s third-party liability to that of a real property owner. Missouri courts may hold a property owner liable for another person’s criminal acts if the property owner knew or had reason to know the person was likely to be on the property. The court here came up with a novel legal theory: The rideshare app is Lyft’s personal property, which the killer rider was regularly “on,” and his criminal acts, as explained above, were foreseeable. Thus, the court declined to dismiss the widow’s claims for lack of common law duty.

Negligent training. Missouri does not recognize a specific cause of action for negligent training. Courts analyze negligent training claims under a negligent supervision theory. Negligent supervision occurs when “a ‘master’ [fails] to exercise reasonable care … [over] his servant while acting outside the scope of his employment as to prevent him from intentionally harming others or…creat[ing] an unreasonable risk of bodily harm to them.” A servant is “a person employed by a master to perform service in his affairs…[and] is controlled…by the master.” There was no indication the rider was Lyft’s “servant.” He was a mere app user, not subject to negligent training.

The case is No. 4:23-cv-853-MAL.

Judge: Lanahan, M.

Attorneys: Arielle Comer (Comer Law Group PLLC) for Lisa Newman. James F. Bennett (Dowd Bennett LLP) for Lyft, Inc.

Companies: Lyft, Inc.

MainStory: TopStory CausationNews ElectronicProductsNews DesignManufacturingNews WarningsNews MissouriNews