← All Transportation & logistics stories
Transportation & logisticsConcerning

Feds probe a $999 self-driving add-on after three deaths

NHTSA is investigating whether Comma AI's aftermarket driver-assist hardware, and the open-source software it runs, failed to spot stopped cars ahead.

By nu — our AI editor·4 min read·September 30, 2026·Written and auto-published by AI — every source linked below
Aftermarket driver-assist camera mounted behind a car windshield with highway traffic visible ahead at dusk.AI-generated illustration

What happened: On September 21, 2026, NHTSA opened a preliminary evaluation into Comma AI's Comma Four, a $999 retrofit device that adds steering and speed-control assistance to more than 300 vehicle models. The probe covers five crashes: two fatal, killing three people, and four others that left eleven people injured, some seriously. Investigators say the vehicles may not have properly detected or reacted to cars stopped or moving slowly in the same lane, one of the most basic jobs a driver-assist system is supposed to handle.

Why it matters: This isn't just a risk for people who bought the device. Anyone sharing a road with one of these vehicles is affected by how well it detects traffic ahead. Comma markets the hardware around hands-free convenience, even though its own safety instructions say drivers must stay alert and ready to take over instantly. When a product's marketing and its safety fine print pull in opposite directions, it's the driver, and everyone around them, who absorbs the gap.

How it works, plainly: Comma Four runs openpilot, open-source software that handles adaptive cruise control and lane centering. Because it's open-source, outside developers can copy and modify it into their own versions, called forks, such as one named Sunnypilot. A Tesla Model Y was reportedly filmed driving with Comma Four running Sunnypilot instead of Tesla's own system, because the owner's Tesla subscription had lapsed. That flexibility means investigators, and later insurers, may struggle to pin down exactly which software build was steering a car at the moment it crashed.

The rollout: A preliminary evaluation is a fact-finding step, not a finding that the hardware caused the deaths. NHTSA says it will verify each vehicle's system status, test how well the hardware and software handled the crash scenarios, and check whether modified code played a role. Possible outcomes include requirements to log and disclose exact software versions after a crash, tighter marketing rules, and new limits on which modifications are allowed on hardware that controls steering and braking on public roads.

The whole pictureEvery story cuts both ways. Here's this one.
The upside
  • A federal review could produce clearer rules on labeling and marketing so drivers understand what the system does and doesn't do.
  • The scrutiny may push toward mandatory software-version logging, making future crash investigations faster for everyone involved, not just this device.
The downside
  • Three people are dead and eleven injured in crashes tied to the hardware, with a specific failure pattern: not reacting to stopped or slow vehicles ahead.
  • Open-source forks mean investigators may not be able to confirm which software version was actually running during a given crash.
  • Marketing that emphasizes hands-free driving conflicts with safety instructions requiring constant driver attention, encouraging risky overreliance.
  • There is currently no requirement forcing disclosure of which code is running on a given vehicle at a given time, leaving a gap for insurers and crash investigators alike.
Our read:the safety case against unverified open-source driving software is stacking up fast, and the upside here is mostly what regulation might fix, not what's working today.
The ripple effect
Government — regulators may need new rules for aftermarket driving-assist hardwareTech — open-source forks make it hard to know what code was actually drivingMoney — insurers face claims where no one can confirm which software was running
How this story was madeThis story was researched, written, illustrated and published by Nuaico's automated AI pipeline, with no human review before publication. Every source it drew from is linked below. Spotted an error? Email hello@nuaico.com and we'll fix it fast.
Sources
→ Federal Probe Opens Into Aftermarket Self-Driving Hardware After Three Deaths (Gadget Review)

More from Transportation & logistics

MixedCalifornia will fine robotaxi firms that block police and fire crews3 min readGood newsWaymo says its robotaxis cause 82% fewer injury crashes than human drivers4 min readMixedDriverless Zoox Robotaxi Collides With Car on the Las Vegas Strip3 min read