Retrofit driver-assist kits turn a familiar daily driver into something that can steer and pace traffic for long stretches on the highway. That promise sits on a windshield-mounted camera, a small dash computer, and software that was never part of the window sticker when the car left the factory. When federal safety regulators step in, the question on every commute is no longer whether the hardware works on your model—it is whether the system reliably sees the slow or stopped vehicle ahead in your lane.
What changed at NHTSA
On September 21, 2026, the National Highway Traffic Safety Administration’s Office of Defects Investigation opened a Preliminary Evaluation into devices sold by Comma AI and the open-source openpilot software they run. The agency says it received reports of five crashes in which vehicles equipped with comma hardware struck stopped or slowly moving vehicles in the same travel lane, with three fatalities and 11 serious injuries cited in the opening documents quoted by trade press. NHTSA notes that comma systems were powered on or engaged in multiple incidents and that early review suggests the setup may not have adequately detected or responded to the in-lane traffic ahead.
A Preliminary Evaluation is an early fact-finding step. It is not a recall, a civil penalty, or a final ruling that a defect exists. Investigators can request data from the manufacturer, pull crash records, and compare software versions before deciding whether to deepen the inquiry or close the file. You can follow active U.S. auto safety investigations through the agency’s public docket at NHTSA Investigations.
Which hardware and software are in scope
The probe covers Comma’s consumer devices—commonly referenced as comma 3, comma 3X, and comma four—and the openpilot stack loaded onto them. Because openpilot is open source, NHTSA also plans to look at modified forks built from the same codebase when those forks may have been running at the time of a crash. Reports in September 2026 pointed to at least one fatal incident involving a fork such as FrogPilot, which matters if you bought a used car and never asked what image was flashed onto the device.
Comma markets the product as hands-free highway assistance for cars people already own, not as a robotaxi service. The company’s own support materials list situations— including stationary lead vehicles in the lane—that can challenge adaptive cruise behavior. That is a different category from the factory robotaxi certification fight playing out separately over vehicles built without conventional pedals or mirrors, but the crash pattern NHTSA flagged here will feel familiar to anyone who follows automated driving news: traffic that is not moving at highway speed in your lane.
How this differs from the ADAS you ordered from the dealer
Lanes labeled “Full Self-Driving,” “ProPILOT,” or “BlueCruise” on a new-car brochure are integrated by the automaker, tied to that VIN, and updated through manufacturer channels. A comma device is an aftermarket accessory you (or a previous owner) install, often in under an hour, with compatibility depending on make, model year, and harness support.
Legally and practically, you remain the driver. openpilot expects an attentive person behind the wheel, ready to steer or brake. Marketing language about long stretches without intervention does not change state licensing rules or the fact that insurance policies vary on undisclosed modifications. Treat any hands-free claim as driver support with strict limits, especially around construction zones, emergency scenes, and stop-and-go queues where the car ahead may be at a standstill.
The crash pattern investigators are studying
All five reported incidents share a shape: the equipped vehicle continued in its lane toward traffic that was stopped or barely rolling. That is the scenario where human drivers lean on early visual cues—flashers, brake lights stacked ahead, cones narrowing a lane—and where camera-based assist can struggle if lead-vehicle tracking drops or speed control does not taper quickly enough.
NHTSA says it will verify system status crash by crash and review safeguards meant to keep operation within safe bounds. For owners, the takeaway is operational, not technical: never assume the device sees what you see when approaching a wall of brake lights, a disabled vehicle under an overpass, or a sudden backup behind a crash scene.
If you already run comma or openpilot
- Stay in the loop: Watch the NHTSA docket for requests, scope changes, or upgrades of the investigation. Software forks can matter; note the exact build on your device.
- Drive as if you are unassisted near stopped traffic: Cover the brake when closing on a queue, especially at night or in glare. Reduce speed early when lanes compress.
- Document installs and updates: Keep dates, device serials, fork names, and who performed the install. That paper trail helps with insurer questions and resale disclosure.
- Do not disable factory safety features without understanding the interaction: Some setups rely on the car’s stock radar or braking; changing settings without guidance can remove layers you did not know you had.
Logging the device model, software fork, and install date in CarDiary alongside ordinary service entries keeps that aftermarket history in one vehicle record instead of buried forum posts.
If you are shopping used in the next few months
A comma rig is easy to miss on a quick lot walk-around. Look for a wide-angle camera pod on the windshield, an extra USB or harness tucked under the trim, or telltale mount marks on the glass. Ask directly whether any driver-assist hardware was added after delivery and whether it is included in the sale.
Before money changes hands, run the CarDiary VIN check for open recalls and title flags on the underlying car—the investigation centers on the accessory, but you still inherit the base vehicle’s maintenance and paperwork story. If a seller removes the comma box before inspection, insist on written disclosure either way; undisclosed mods can complicate claims after a fender-bender.
What a Preliminary Evaluation does not do—yet
Federal probes can end without mandatory repairs, or they can expand into engineering analysis and coordinated remedies. Until NHTSA publishes a outcome, owners should assume status quo operation: no government order to unplug devices, but also no green light that the reported crash scenario is resolved. Comma may issue its own guidance or updates; treat those as manufacturer communications, not as a substitute for reading NHTSA’s public filings.
Meanwhile, keep doing the unglamorous work that prevents rear-end crashes in any car: scan far ahead, match speed to visibility, and leave space so a moment of inattention or a missed detection does not become a impact with zero closing distance. Aftermarket assist can reduce fatigue on open interstate miles; it does not remove the obligation to handle the messy, static obstacles that appear without warning in the lane you are already in.
