NHTSA make / model monitor
Comma.ai Comma Three: recalls, complaints and investigations.
US NHTSA records for Comma.ai Comma Three. Check the affected model years, then verify your exact vehicle with NHTSA.
No recent campaign in this snapshot. Check your VIN for current and older outstanding recalls.
We do not collect your VIN. A model-year match does not establish whether your individual vehicle is affected or has been repaired. Snapshot through 2026-10-11.
Evidence summary
- Evidence found
- 0 recent recall campaigns, 0 complaint rows, and 1 monitored investigation.
- Source coverage
- NHTSA complaint and current-action window 2024-08-24 to 2026-10-11; historical campaign count uses the complete official pre- and post-2010 recall files acquired for this release.
- What this means
- The records were matched to the NHTSA make/model identity “Comma.ai Comma Three”. Each evidence type is reported separately.
- What this does not mean
- Complaint reports are allegations, not defect findings or a safety score. Counts are not normalised for sales, registrations, mileage or exposure, and a zero does not prove safety.
Official recall campaigns
Recall campaigns in the monitoring window
No recall campaigns matched this model and selected year in this snapshot. The historical count above may still include earlier campaigns.
Consumer reports — allegations
Complaint aggregates by model year
Zero complaint rows matched this make/model in the monitoring window. That is not a safety clearance.
NHTSA says complaints are consumer reports. RecallRecall excludes narratives, VINs, names, contact details and locations. A crash, fire, injury or death flag is reported information, not an independently verified causal finding.
NHTSA defect investigations
Open or recently opened investigations
PE26007: Crashes involving comma.ai driving automation products open
The Office of Defects Investigation ("ODI") has identified crashes involving vehicles equipped with devices manufactured by comma.ai (“comma”) occurring under similar circumstances. ODI received notice of five (5) crashes in which vehicles with comma devices installed reportedly struck stopped or slowly moving vehicles within the same travel lane. ODI has confirmed that the systems were powered on or engaged in multiple crashes. Preliminary data reviewed by ODI suggests that the comma system may not have adequately detected or responded to the in-lane vehicles. Two crashes resulted in a total of three (3) fatalities. Four of the five crashes contributed to various non-fatal injuries, including serious injuries, to eleven (11) other individuals. The comma devices are after-market accessory systems intended to augment a vehicle’s driving automation capabilities. The devices are sold with wire harnesses that connect to existing vehicle systems and use the device’s cameras alongside stock vehicle sensors as a basis to provide sustained automated control of speed and vehicle heading with options for other enhanced features enabled by software loaded onto the devices. The devices are sold directly to consumers, and the company’s provided setup instructions are intended for consumer installation. The company advertises on its website that, with its “step-by-step guide,” a consumer can “[g]et set up in your car in 15 minutes.” According to the website, the devices provide “hands free driving for the car you already have,” and the software (openpilot) that comma develops to operate on the devices is described as “an open source advanced driver assistance system that works on 325+ car models” and “[c]an drive for hours without intervention.” The company’s website states that “openpilot requires the driver to be alert, pay attention, and be ready to take over at all times.” ODI is opening this Preliminary Evaluation to investigate further any incidents involving the comma devices and openpilot, particularly crashes involving slower or stopped vehicles or hazards in lane. The investigation will obtain data to verify system status for each incident and evaluate system performance and safeguards that are intended to ensure safe operation of vehicles equipped with comma devices. Additionally, to the extent that modified software based on openpilot (i.e., a “fork”) is involved in a crash or other incident, ODI will evaluate the incident and consider the shared components between openpilot and the fork. The SGO incidents cited in the Opening Resume are listed below by report ID and are available for download at NHTSA.gov/laws-regulations/standing-general-order-crash-reporting 30351-15888 30351-14668 30351-11961 30351-1807 62-14853