{"schema":"sanctity-signal/0.2","record_type":"signal","id":"nhtsa-comma-pe26007-e031","domain":"safety","drop_id":"signal-e031","occurred_at":"2026-09-21","how_to_use":"This is a structured record of one real-world action and its competing interpretations, from Sanctity Signal. To build content from it (a reel script, a blog, a thread): open on the hook, ground the viewer with plain and observed, walk the dated trail, present the interpretations as live tension between named readings, and close on the before/after shift and what_to_watch. Hard rules: items under established are fact; items under unknown are never presented as fact; the evidence status (verified or reported) is stated, not dropped; sources are cited.","actor":"US National Highway Traffic Safety Administration","action_type":"defect investigation opened","observed":"Monday September 21, 2026. The National Highway Traffic Safety Administration's Office of Defects Investigation opened preliminary evaluation PE26007 into comma.ai. Products and population named on the agency's own resume: comma three, comma 3X, comma four and the openpilot software, an estimated 30,000 units. The summary states that ODI identified five crashes in which vehicles equipped with comma devices struck stopped or slow-moving vehicles in the same travel lane, with the systems reportedly powered on during multiple incidents; two of the crashes resulted in three fatalities and four resulted in injuries to eleven people. The resume records that the devices are aftermarket systems sold directly to consumers for self-installation, advertised to enable hands free driving, with openpilot described on the company's own site as an open source advanced driver assistance system that works on 325+ car models. At least one of the fatal crashes involved FrogPilot, a third-party modified build of openpilot rather than the official software: in a February 2026 crash in Louisiana a Toyota RAV4 running the forked software struck a stopped first responder vehicle and killed two rear-seat passengers. Comma.ai did not respond to requests for comment and its founder George Hotz did not respond either. A preliminary evaluation is the first of the agency's investigative stages and carries no finding; it either closes, or escalates to an engineering analysis, which is the stage that can lead to a recall demand. The date opened on the agency's resume is September 21, which was inside Edition 029's window, and it was not carded there; it reached us through coverage dated September 23. Under the clock law it is carded at September 21 and recorded as surfacing late.","corrections":[],"evidence":{"status":"verified","note":null,"sources":[{"role":"primary","label":"NHTSA Office of Defects Investigation, investigation resume PE26007, comma.ai, date opened Sep 21","url":"https://static.nhtsa.gov/odi/inv/2026/INOA-PE26007-17274.pdf"},{"role":"corrob","label":"TechCrunch: Comma's hands-off driving tech under investigation after 2 fatal crashes, Sep 23","url":"https://techcrunch.com/2026/09/23/commas-hands-off-driving-tech-under-investigation-after-2-fatal-crashes/"},{"role":"corrob","label":"Reuters via WBOW: US probes Comma.AI over crashes tied to aftermarket driver assistance devices, Sep 23","url":"https://1027wbow.com/2026/09/23/us-probes-comma-ai-over-crashes-tied-to-aftermarket-driver-assistance-devices/"}]},"strength":{"cost":"Medium","commitment":"Medium","reversibility":"Medium","persistence":"Years","rationale":"Cost is medium: opening a preliminary evaluation costs the agency staff time and a public commitment to look, which is real but small, and it costs comma.ai a legal problem it did not have on Sunday. Commitment is medium because a preliminary evaluation binds the agency to nothing; most of them close with no action. Reversibility is medium for the same reason, since closing a file is routine and unremarkable. Persistence is years, and that is what carries this card: the jurisdictional question the file raises, whether a regulator can reach the author of software somebody else modified, does not close when the file closes, and the answer will be cited long after the specific crashes are forgotten."},"shift":{"prior":"Federal defect investigations into driving automation had one shape: a named carmaker, a model year list, and a system the manufacturer alone controls and can change over the air.","action":"Monday September 21, 2026. The National Highway Traffic Safety Administration's Office of Defects Investigation opened preliminary evaluation PE26007 into comma.ai. Products and population named on the agency's own resume: comma three, comma 3X, comma four and the openpilot software, an estimated 30,000 units. The summary states that ODI identified five crashes in which vehicles equipped with comma devices struck stopped or slow-moving vehicles in the same travel lane, with the systems reportedly powered on during multiple incidents; two of the crashes resulted in three fatalities and four resulted in injuries to eleven people. The resume records that the devices are aftermarket systems sold directly to consumers for self-installation, advertised to enable hands free driving, with openpilot described on the company's own site as an open source advanced driver assistance system that works on 325+ car models. At least one of the fatal crashes involved FrogPilot, a third-party modified build of openpilot rather than the official software: in a February 2026 crash in Louisiana a Toyota RAV4 running the forked software struck a stopped first responder vehicle and killed two rear-seat passengers. Comma.ai did not respond to requests for comment and its founder George Hotz did not respond either. A preliminary evaluation is the first of the agency's investigative stages and carries no finding; it either closes, or escalates to an engineering analysis, which is the stage that can lead to a recall demand. The date opened on the agency's resume is September 21, which was inside Edition 029's window, and it was not carded there; it reached us through coverage dated September 23. Under the clock law it is carded at September 21 and recorded as surfacing late.","update":"Treat an open source driving system with modified forks in the field as something a federal regulator will open a file on, and watch whether the file ends up naming the fork or the original."},"inference":{"established":["NHTSA's Office of Defects Investigation opened preliminary evaluation PE26007 into comma.ai on September 21, 2026.","The products named are comma three, comma 3X, comma four and openpilot, an estimated population of 30,000 units.","The agency identified five crashes in which comma-equipped vehicles struck stopped or slow-moving vehicles in the same lane; two killed three people and four injured eleven.","At least one fatal crash involved FrogPilot, a third-party modified build of openpilot rather than the official software."],"unknown":["That the systems are defective. A preliminary evaluation makes no finding, most close without one, and the agency's own summary says the systems were reportedly powered on rather than confirmed so.","That comma.ai is responsible for the fork. Nothing in the file assigns responsibility, and the question of whether an author answers for a modified copy is unresolved in law.","That 30,000 is accurate. The agency's own resume marks the population as an estimate, because nobody registers an aftermarket device.","That a recall is available. The recall machinery is built around manufacturers and vehicle identification numbers, and no one has established it reaches a self-installed box running community software."]},"narrative":{"hook":"The federal car safety regulator opened an investigation into an aftermarket box that drives your car, after three deaths.","plain":"On September 21 the National Highway Traffic Safety Administration opened preliminary evaluation PE26007 into comma.ai, covering the comma three, comma 3X and comma four devices and the openpilot software, an estimated 30,000 units. The agency's own summary says it identified five crashes in which vehicles fitted with comma devices struck stopped or slow-moving vehicles in the same lane, with two crashes killing three people and four injuring eleven. Two caveats matter: at least one fatal crash involved FrogPilot, a third-party modification of openpilot rather than the official software, and the investigation opened on September 21 but only reached the public through coverage on September 23, so it is carded here at its true date and surfaced late.","story":["Every driving automation investigation this agency has run has had a company at the other end of it that could be ordered to fix something: Tesla, General Motors, Ford, each with a fleet it identifies by vehicle identification number and updates when told to. PE26007 does not have that shape. The thing under investigation is a 1,000 dollar box a consumer buys and installs, running software published openly for more than 325 car models, in an estimated 30,000 units the agency can only estimate because nobody registered them. The five crashes all share one failure described in the agency's own words, striking stopped or slow-moving vehicles in the same lane, which is the oldest failure mode in driver assistance and the one that killed three people here.","The fork is the part that makes this new. At least one of the fatal crashes, the February 2026 Louisiana crash in which a Toyota RAV4 struck a stopped first responder vehicle and killed two passengers in the back seat, involved FrogPilot, a modified build that comma.ai did not write and cannot recall. A regulator can order a manufacturer to fix its product. It has no mechanism at all to reach a third party who downloaded that product, changed it and gave it away, and no answer yet to whether the original author is responsible for what the copy does. That question has been theoretical in every open source licence argument for thirty years and it is now attached to three deaths and a docket number. Treat an open source driving system with modified forks in the field as something a federal regulator will open a file on, and watch whether the file ends up naming the fork or the original."],"trail":[{"d":"FEB 2026","t":"A Toyota RAV4 running FrogPilot, a fork of openpilot, strikes a stopped first responder vehicle in Louisiana, killing two rear-seat passengers."},{"d":"SEP 4","t":"NHTSA opens a file on Tesla's Cybercab hours after the first driverless rides. Carded in Edition 012."},{"d":"SEP 21","t":"ODI opens PE26007 into comma.ai: four products, 30,000 units, five crashes, three deaths, eleven injuries."},{"d":"SEP 23","t":"The investigation reaches the public through coverage. Comma.ai and George Hotz do not respond to requests for comment."},{"d":"Reacts","r":true,"t":"Comma.ai, a company with no press office facing a federal defect file; the maintainers of every openpilot fork, who now know a regulator is reading the commit history; the 30,000 people driving with one of these boxes fitted; Tesla, whose own driver assistance files use the same language about stopped vehicles in the same lane and whose lawyers will read this one closely; the insurers who have been quietly pricing aftermarket driver assistance without a category for it; the first responders whose stopped vehicles are the specific hazard in this failure mode; and every open source project whose licence says the author warrants nothing."}],"glossary":[{"term":"Preliminary evaluation","def":"The first stage of a federal defect investigation. It gathers information and makes no finding. It either closes or escalates to an engineering analysis, which is the stage that can lead to a recall."},{"term":"Aftermarket","def":"Equipment sold to the car owner rather than fitted by the manufacturer. It sits outside the recall and compliance machinery built around carmakers, which is the awkward part of this file."},{"term":"Fork","def":"A copy of open source software that someone else has modified and distributes under their own name. FrogPilot is a fork of openpilot, and the original author does not control what it does."},{"term":"Advanced driver assistance system","def":"Software that steers, brakes or accelerates while a person is still responsible for the car. It is a lower category than self-driving, and hands free is a claim about attention rather than about liability."}]},"judgment":{"prompt":"Which explanation do you believe?","interpretations":[{"id":"a","label":"Regulation has reached open source driving software.","text":"The first federal defect file naming an open source system and its forks is the moment this category stopped being outside the machinery, and everything downstream of it follows from that.","abstain":false},{"id":"b","label":"One small company with five crashes.","text":"Thirty thousand devices and five incidents is a narrow file about a narrow product. Reading a doctrine into it overstates what an early-stage evaluation is.","abstain":false},{"id":"c","label":"A deliberate move to establish jurisdiction over aftermarket systems.","text":"The agency chose a defendant with no lobbying operation and a product that is plainly aftermarket, which is how a regulator establishes reach before applying it to somebody larger.","abstain":false},{"id":"d","label":"The ordinary cadence of defect investigations.","text":"The agency opens dozens of preliminary evaluations a year, and stopped vehicles in the same lane is the most common driver assistance complaint it receives. Nothing here is new except the defendant.","abstain":false},{"id":"e","label":"Too early to call.","text":"The evidence cannot yet separate these.","abstain":true}],"distribution":{"status":"held back until you have made your call","calls":null}},"story_thread":null,"what_to_watch":[{"linked_interpretation":"a","direction":"strengthens","observable_event":"NHTSA escalates PE26007 to an engineering analysis, issues an information request naming a third-party fork, or demands a recall, by June 30, 2027.","window_end":"2027-06-30","state":"unresolved"},{"linked_interpretation":"a","direction":"weakens","observable_event":"NHTSA closes PE26007 with no action and no finding by June 30, 2027.","window_end":"2027-06-30","state":"unresolved"}]}