Sunday 4 October 2026
Afternoon EditionRSS
ZOTPAPER

News without the noise

ZOTPAPER
AI

Comma.ai under federal investigation after fatal crashes involving driver-assist tech

NHTSA probes five crashes — two fatal, leaving three dead — with the startup's aftermarket 'openpilot' system, some possibly running modified software

By LineZotpaper
Published
Updated
Read Time2 min
Sources3 outlets
The National Highway Traffic Safety Administration has opened a federal investigation into Comma.ai, the startup founded by hacker George Hotz, after five reported crashes involving its hands-off driver assistance technology caused three deaths and 11 injuries, the agency disclosed this week.

The NHTSA’s Office of Defects Investigation said the crashes involved Comma devices failing to detect or respond to slow or stopped vehicles in the same lane. Two of the crashes were fatal, resulting in three deaths. Across four of the incidents, as many as 11 people were injured, some seriously.

Some of the crashes — including at least one fatal — may have involved “forked” or modified versions of Comma.ai’s software, according to the agency. One fatal crash occurred in February 2026 in Ascension Parish, Louisiana, where a 2022 Toyota RAV4 running FrogPilot, a third-party fork of Comma’s openpilot software, struck a stopped first responder vehicle. Two rear-seat passengers died.

Comma.ai makes aftermarket devices that can tap into a car’s adaptive cruise control and automated lane centering systems, providing functionality similar to Tesla Autopilot or GM Super Cruise. The company warns drivers that they “must always be capable to immediately retake manual control of the vehicle” and uses a camera-based driver monitoring system to watch for distraction.

Comma.ai could not immediately be reached for comment. George Hotz, who stepped away from daily operations in 2022, did not return a request for comment.

§

Analysis

Why This Matters

  • The investigation raises questions about the safety of aftermarket driver-assistance systems that operate outside automaker-controlled, tightly integrated platforms.
  • The involvement of modified (“forked”) software highlights the challenge regulators face when open-source or third-party code can alter safety-critical vehicle functions.
  • With three confirmed deaths, the outcome could set a precedent for how NHTSA treats retrofitted autonomy systems — potentially affecting hobbyists, startups and the broader ADAS aftermarket.

Background

Comma.ai was founded in 2015 by George Hotz, a well-known hacker, with the goal of democratizing advanced driver-assistance. Its openpilot software runs on a smartphone-sized device that plugs into compatible vehicles, providing lane-keeping and adaptive cruise features. Hotz distanced himself from day-to-day operations in late 2022 to work on a separate AI project. The company has long warned that its system is not fully autonomous and requires constant driver attention, but the recent crashes suggest that warning may not be sufficient in all scenarios.

Key Perspectives

NHTSA (Office of Defects Investigation): The agency is treating the crashes as a potential safety defect, specifically citing failures to detect stopped vehicles. It is investigating both Comma’s official software and known third-party forks. Comma.ai: The company has not yet responded publicly. Its website stresses driver responsibility and its device uses driver monitoring, but the crashes raise questions about system reliability when the driver is not attentive. Critics/Skeptics: The use of modified forks like FrogPilot — which may change safety parameters — points to a broader risk: that open-source ADAS code can be altered without the same validation as OEM systems, potentially increasing danger for occupants and other road users.

What to Watch

  • NHTSA’s preliminary evaluation (PE26007) timeline: whether it escalates to an engineering analysis or recall request.
  • Comma.ai’s public response and any software updates or usage restrictions it may issue.
  • The extent to which regulators distinguish between official openpilot usage and third-party forks when assigning responsibility.

Sources

Zotpaper

Written by software from the reporting listed above, scored by an automated standards desk, and published without a person reading it first. If something here is wrong, tell the editor and it will be put right.

How we workReport an errorSubscribe