Cybercab rollout under federal audit (NHTSA FMVSS self-certification)
- The thread: NHTSA's Office of Defects Investigation opened AQ26002 on Sep 3 — an audit of Tesla Cybercab FMVSS self-certification (population ~1,000, controls-free robotaxis operating in Texas). The regulator is examining the certification process, not a defect — the first federal look at how a steering-less robotaxi fleet cleared safety rules. Entered our feed Sep 11 via MSN mirror, 8 days late.
- 2026-09-11: opened from the robots digest. Primary: NHTSA.gov press release + OVSC resume (AQ26002, opened 09/03/2026). CNBC/NYT carried Sep 4.
- Watch for: audit scope/requests to Tesla, whether self-certification of controls-free vehicles survives the review, Houston/Nevada expansions proceeding meanwhile, precedent value for every following controls-free deployment.
- 2026-09-30: the fleet math splits — the Austin Cybercab fleet quietly doubled to 100+ units over the weekend (Teslarati), while the active robotaxi count had fallen back to ~8 vehicles (Electrek tracker, Sep 22 re-run; ~15 months in, no public-road net growth) — deployment optics vs service reality, mid-audit.
-
2026-10-03 (the night-hours explanation): Musk explains why robotaxi stays daytime-limited (operating hours moved 10pm→11pm): the holding-back factor is seeing pets in the dark — "grey kittens on grey tarmac"; Electrek notes that's the textbook weakness of cameras and the exact job of lidar/radar — sensors Musk spent years calling a "crutch" and a "fool's errand." An on-record low-light detection limit, self-quantified, with no sensor change announced. Link: electrek.co/2026/10/03/tesla-robotaxi-pets-night-musk-lidar/
-
2026-10-12 (the second federal front): NHTSA opened a file on a Tesla Robotaxi school-zone-speeding defect petition — the audit thread's first docket-adjacent movement since the self-certification finding. Watch: NHTSA's response, whether the petition's scope grows past school zones.
-
2026-10-15 (~12:39 PM ET, Electrek): the federal-audit thread's crash-data layer quantifies — Tesla's latest crash reports to federal regulators add two more Robotaxi crashes in which a remote operator, not the car's autonomous system, was driving when it hit something, bringing that count to five, and every remote takeover that has shown up in a Tesla crash report has ended in a collision. Development of the federal fronts on file (the FMVSS self-certification audit of the controls-free Texas fleet; the Robotaxi file opened October 12): the first count of remote-takeover failures inside the regulator's own data stream. Watch: NHTSA's use of the tally, remote-operator methodology disclosure, audit-scope expansion. https://electrek.co/2026/10/15/tesla-remote-operators-crashing-robotaxis/