Bill
HB 1648
HB 1648 would shield TNCs from vicarious liability for driver-caused harm while the driver is logged into the network, unless the TNC is negligent, criminally liable, or fails stat
Status and jurisdiction
- Bill number: HB 1648 (multiple variants appear in the provided materials).
- Primary subject (from the provided text): creates a new section 387.435 in Chapter 387 (Missouri statutes) limiting vicarious liability of TNCs.
- Filing / status in the supplied record: prefiled (H); introduced 12/17/2024. (The record includes other HB1648 proposals in different states and mixed legislative actions; confirm the target state before relying on the procedural history.)
Purpose / intent
- To shield transportation network companies (TNCs) — i.e., companies that provide a digital platform connecting drivers and riders — from vicarious liability for harms caused by a TNC driver’s use of a motor vehicle while logged on to the TNC’s digital network, subject to stated exceptions. The intent is to make TNC civil exposure depend primarily on the company’s own negligence or criminal misconduct and on compliance with certain statutory obligations.
Key provisions (text summary)
- Adds section 387.435 to Chapter 387. Core rule:
- A TNC shall not be vicariously liable (under any law) by reason of owning, operating, or maintaining the digital network or by being the TNC affiliated with a TNC driver, for harm to persons or property that results from use, operation, or possession of a motor vehicle operating as a TNC vehicle while the driver is logged on to the digital network, if both:
1. There is no negligence (under sections 387.400–387.440) or federal/Missouri criminal wrongdoing by the TNC; and
2. The TNC has fulfilled all of its obligations under sections 387.400–387.440 with respect to the TNC driver.
- In short: absent the company’s own negligence/criminality or failure to meet statutory duties (the duties set out in sections 387.400–387.440), the TNC cannot be held vicariously liable for a driver’s motor-vehicle-related harm while the driver is logged into the network.
Who is affected
- Beneficiaries: TNCs (platforms), which would face reduced exposure to vicarious liability for driver-caused accidents when the two statutory conditions are satisfied.
- Potentially affected parties: individuals injured by TNC drivers (may have less ability to sue the TNC directly); TNC drivers (remain liable for their own conduct and remain subject to regulatory/insurance rules); insurers (might bear more of the claim burden depending on contract/statutory insurance requirements).
- Regulators and courts: will interpret whether a TNC “fulfilled” statutory duties and whether the company’s conduct amounts to negligence or criminal wrongdoing.
Practical and legal implications
- Shifts emphasis onto (a) proving TNC’s own negligence or criminal misconduct, or (b) demonstrating the TNC failed to meet statutory obligations (e.g., background checks, insurance, driver screening if those are part of 387.400–387.440).
- Likely to reduce direct TNC exposure in many vehicle-related claims, increasing reliance on drivers’ liability and required TNC insurance policies.
- May prompt litigation over (i) when a driver is “logged on,” (ii) what the statutory obligations precisely require, and (iii) whether the TNC’s operational decisions constituted negligence.
- Could incentivize legislative or regulatory updates to the referenced statutory duties (387.400–387.440), particularly insurance and safety requirements, since immunity is conditioned on fulfilling them.
Procedural / next steps
- The provided record shows mixed and state-specific actions for various HB1648 drafts. Confirm the bill’s exact state and session before tracking committee assignments or timelines. If this is the Missouri proposal, monitor the relevant chamber committee, floor readings, and any amendments clarifying (a) “logged on” scope, (b) the list of obligations in 387.400–387.440, and (c) interaction with private insurance and victim recovery mechanisms.
Compiled from official sources — confirm details with the bill’s official record.
Sign in to ask a question.
