Comma’s hands-off driving tech under investigation after 2 fatal crashes
The investigation stems from five incidents where Comma.ai’s plug‑in hardware, which commandeers a vehicle’s adaptive cruise control and lane‑centering functions, failed to recognize slow‑moving or stopped traffic in the same lane. Across four of those events, 11 people were injured, with two crashes proving fatal. One lethal accident involved a 2022 Toyota RAV4 equipped with “FrogPilot,” a community‑maintained fork of openpilot, which slammed into a parked police cruiser in Ascension Parish, Louisiana, killing two rear‑seat passengers. The NHTSA notes that at least one of the fatal crashes may have involved modified software, raising questions about the liability of both the original developer and independent coders.
This probe arrives as regulators tighten scrutiny on advanced driver‑assistance systems that struggle with stationary obstacles—a weakness previously flagged in Tesla’s Autopilot and Ford’s Co‑Pilot. Comma.ai’s business model—selling a retrofit kit that can be installed on a broad range of modern cars and relying on an open‑source codebase—differs sharply from OEMs that integrate hardware and software in‑house. While the company advertises “hands‑off” convenience, it also warns users to stay ready to intervene, yet its own documentation admits that openpilot’s ACC deceleration limits can hamper abrupt braking. The presence of community forks like FrogPilot amplifies the challenge: modifications can diverge from the safety assumptions baked into the original code, yet they remain marketed under the same brand umbrella.
If the NHTSA concludes that the hardware or software design is defective, Comma.ai could face mandatory recalls, fines, or restrictions on sales, which would reverberate through the niche market of aftermarket ADAS solutions. The case also pressures the open‑source community to adopt stricter testing and certification standards, lest fragmented forks become liability traps. Stakeholders should monitor forthcoming NHTSA findings, any recall notices, and whether Comma.ai releases a firmware patch or tighter controls on third‑party distributions. The outcome will likely shape how regulators treat retrofit autonomy and could influence OEMs’ strategies toward open‑source collaborations.
Key Takeaways
The NHTSA’s defect investigation targets Comma.ai’s inability to detect stopped vehicles, a flaw that contributed to five crashes and three deaths.
At least one fatal crash involved a third‑party fork, FrogPilot, suggesting that unofficial software variants may exacerbate safety risks.
Comma.ai’s open‑source model differentiates it from OEM‑integrated systems but also complicates regulatory compliance and liability.
Future regulatory actions or recalls could curb the growth of aftermarket driver‑assist kits and force stricter oversight of community‑maintained forks.
About the Source
This analysis is based on reporting by TechCrunch. Here is a short excerpt for context:
The investigation involves at least some crashes where it appears drivers were using "forked" versions of Comma's software.Read the original at TechCrunch
