NHTSA's Cybercab FMVSS probe — what Utah operators should know

What NHTSA opened (AQ26002) — dated

As of Nov 2, 2026 (MT): The NHTSA ODI investigations flat file, file timestamp Nov 2, 2026, still lists AQ26002 as open (opened September 3, 2026; blank close date). Tesla's response was due Oct 30, 2026; not yet public as of Nov 2, 2026. The public PDFs are still the opening resume, the September 10 Special Order, and the September 29 memo. None is Tesla's response. Superseded: the Oct 30 vehicle-page read that the file was open and the response was not public as of Oct 30.

As of Oct 23, 2026 (MT): NHTSA's Office of Vehicle Safety Compliance opened Audit Query AQ26002 on Sep 3, 2026, with a public announcement on Sep 4, 2026. The opening resume, fetched again Oct 23, is still an open audit query. The inquiry looks at Tesla's FMVSS self-certification of the Cybercab: the process and technical data Tesla relied on, including how far certification depended on determinations that certain Federal Motor Vehicle Safety Standards are inapplicable to a vehicle without permanently attached conventional manual controls. Superseded Oct 30, 2026 on the open/closed point by the vehicle-page read above. The description of what the query examines is unchanged.

Context for the opening: Paid rides began Sep 3, 2026, with public hails from about Sep 4 in a limited Austin geofence. Agency materials and contemporaneous reporting put the population under review at about 1,000 Cybercabs.

Vehicles under review lack permanently attached conventional brake pedal, accelerator, steering wheel, and mirrors, according to the OVSC resume and NHTSA press summaries.

Sources: NHTSA OVSC resume (INOA-AQ26002); NHTSA press release Sep 4, 2026; Reuters Sep 4, 2026.

Self-certification vs “approval” in plain English

In the U.S., manufacturers generally self-certify that vehicles meet applicable Federal Motor Vehicle Safety Standards. NHTSA oversees that system and can investigate when certified vehicles appear not to adhere. That is different from a blanket, pre-market design approval for every vehicle configuration.

So when you see “NHTSA opened a probe into Cybercab self-certification,” read it as federal oversight of how the vehicle was certified, not as a Utah operating permit, ban, or finding that a local service is legal or illegal.

Educational framing only. We are describing the agency's stated purpose, not predicting outcomes.

Why no-controls Cybercabs raise FMVSS questions

Many FMVSS assume a human driver and related controls and equipment. A purpose-built Cybercab without permanently attached steering wheel, pedals, and mirrors forces a hard question: which standards still apply, which were treated as inapplicable, and what technical basis supports those determinations?

Trade reporting has pointed to examples such as FMVSS No. 135 (light vehicle brake systems / foot brake expectations) as one area of scrutiny. Treat that example as partial until you are citing the Special Order or primary NHTSA materials directly; the precise legal and engineering arguments belong to Tesla's response and NHTSA's record, not to a blog paraphrase.

Sources: OVSC resume; Reuters Sep 4, 2026; Electrek Sep 15, 2026 (partial on clause-level detail).

Special Order: response was due Oct 30, not yet public

As of Oct 6, 2026 (MT): Electrek reports that NHTSA issued a Special Order around Sep 10, 2026, requiring Tesla to answer under oath by Sep 30, 2026, with about 21 information requests. Secondary wires summarizing Reuters reporting describe question themes around temporary controls, human drivability, touchscreen movement controls, and operating limits.

Important: The sworn response was due Sep 30, 2026. CNBC reported on Oct 3, 2026 that an NHTSA spokesperson said Tesla obtained an extension. An NHTSA memo to file dated Sep 29, 2026 shows NHTSA granted Tesla a 30-day extension on Sep 22 (Tesla had asked for eight weeks, to Nov 20); the new due date is Oct 30, 2026. Tesla's response was due Oct 30, 2026; not yet public as of Nov 2, 2026. Superseded: not yet public as of Oct 30, 2026. The ODI flat file dated Nov 2 still has no close date. Reuters reported on Oct 21 that Tesla has until October 30 to respond. That is reporting of the deadline, not a filing of the response. Do not read this page as saying Tesla has replied in public, settled, recalled, been banned in Utah, or been approved in Utah.

Clause-level quotes from circulating Special Order PDFs hosted outside NHTSA/ODI are partial until a primary-hosted text is confirmed.

Sources: Electrek Sep 15, 2026; MarketScreener/Reuters wire Sep 15, 2026 (partial); CNBC Oct 3, 2026 (NHTSA spokesperson on the extension; Texas DMV counts as of Oct 2).

What this is not

Hold these separations firmly:

D.R. Autonomy is not running Tesla Robotaxi, Cybercab ride-hail, or any paid robotaxi fleet in Utah. We have no Tesla affiliation, partnership, or operator contract. This site is an invitation to partners interested in a Wasatch Front ops layer — depots, insurance, corridors, local relationships — as we form up. It is not proof of a live fleet.

Optimus is out of scope for this page.

Utah / Wasatch Front: state law and sightings ≠ federal probe outcome

Federal FMVSS certification oversight is not the same as Utah's state autonomous-vehicle framework.

As of TownLift's Sep 15, 2026 reporting: a gold Cybercab was spotted in Park City on Sep 11, 2026 in what that article describes as test conditions with a visible driver / temporary-controls style setup. That is local color, not paid Utah Robotaxi service, and it is not the same fact pattern as the no-controls commercial product under AQ26002.

TownLift also notes Utah testing themes under HB 101 self-certification and that Tesla does not operate Robotaxi ride-hail in Utah as of that article. Olympics-related interest in the local press is color only — not a D.R. Autonomy contract, UDOT pilot award, or launch commitment.

What local operators still prepare regardless of OEM headlines

Headlines about Austin, NHTSA letters, and Park City sightings do not replace ground work.

Independent local operators still have to get honest about:

• Depots and charging along real corridors
• Insurance and risk for the ops model you actually intend
• Relationships with campuses, municipalities, and partners
• Trip design on the Wasatch Front / I-15 geography you claim to serve

Those problems do not wait for Tesla's Special Order response to become public. They also do not get solved by implying a Tesla brand relationship you do not have.

If you want to talk depots, corridors, or partnership shape while everything is still early: drautonomy.com / hello@drautonomy.com.

Watch list + how we'll update this page

Watch next (no invented close dates):

1. Whether Tesla’s sworn response, or any NHTSA acknowledgment of it, becomes public. The original due date was Sep 30, 2026. CNBC (Oct 3, 2026) reported an NHTSA spokesperson said Tesla obtained an extension. The NHTSA memo to file dated Sep 29, 2026 sets the new due date at Oct 30, 2026. Tesla's response was due Oct 30, 2026; not yet public as of Nov 2, 2026. Superseded: not yet public as of Oct 30, 2026. The ODI flat file dated Nov 2 still has no close date. Trade coverage notes the answers may be held as confidential business information (The Auto Wire, Sep 30).
2. Whether NHTSA grants or denies defect petition DP26010. Opening the file is not that decision.
3. Any public NHTSA status change on AQ26002
4. Clear separation, in primary sources, between temporary-controls testing and no-controls commercial certification questions
5. Utah service geography facts: still no Tesla Robotaxi ride-hail in Utah. Tesla's Robotaxi page, read Nov 3, 2026, lists Austin, Dallas, Fort Worth, Houston, Miami, Orlando and Tampa, and its safety page lists coming soon Las Vegas, Jacksonville, Phoenix and San Antonio. Utah is not named. Superseded: the Oct 30 and Nov 2 reads of six cities, without Fort Worth. See our Utah status page.

We will date-stamp another refresh when Tesla's response or an NHTSA update is public. Until then, treat this page as current through Nov 2, 2026 (MT).

FAQ

Change log

• Nov 2, 2026 (MT): TxDMV public list for Tesla Robotaxi, LLC (AV8313426653583, status authorized) read directly about 7:58 AM MT: 671 Model Y and 573 Cybercab-prefix (1,244). Counted across 13 pages of 100 (last page 44); distinct VINs. API total 1,244 on every page. Authorization, not active rides, and not a city. This supersedes the Oct 30 and Oct 28 figure of 507 Model Y and 573 Cybercab-prefix (1,080). Startup Fortune on Nov 1 reported 1,204 on Oct 31 (631 / 573); reporting context only. AQ26002: ODI flat file dated Nov 2 still open, no Tesla response PDF found; Tesla's response was due Oct 30, 2026, not yet public as of Nov 2, 2026. Tesla Robotaxi page read: six ride cities unchanged, coming soon Las Vegas, Jacksonville, Phoenix and San Antonio, Utah not named. Cybercab support page: rides in limited areas of Austin. No D.R. Autonomy fleet, fares, or depot.
• Oct 30, 2026 (MT): AQ26002 vehicle page read: still an open investigation, September 3, 2026 – present. Public file has four documents and no Tesla response. Tesla's response was due Oct 30, 2026; not yet public as of Oct 30, 2026. DP26010 resume fetched again: still "Open Defect Petition." TxDMV re-read about 7:55 AM MT: still 1,080 (507 Model Y, 573 Cybercab-prefix). Tesla Robotaxi page read: six ride cities unchanged, coming soon Las Vegas, Jacksonville, Phoenix and San Antonio, Utah not named. Cybercab support page: rides in limited areas of Austin. No D.R. Autonomy fleet, fares, or depot. Superseded Nov 2, 2026 by the TxDMV read of 671 Model Y and 573 Cybercab-prefix (1,244), and by the Nov 2 finding that Tesla's AQ26002 response is still not public.
• Oct 28, 2026 (MT): TxDMV public list for Tesla Robotaxi, LLC (AV8313426653583, status authorized) read directly: 507 Model Y and 573 Cybercab-prefix (1,080). Counted across all 11 pages; distinct VINs. The Oct 23 operator URL now returns 404; this read used the current company page. Authorization, not active rides, and it does not assign a vehicle to a city. This supersedes the Oct 23 figure of 507 Model Y and 351 Cybercab (858). StockTwits/Yahoo on Oct 27 reported 1,051 (544 Cybercab + 507 Model Y); reporting context only, not this note's count. Utah still not live. Tesla city lists, AQ26002, and DP26010 were not re-fetched on this stamp. No D.R. Autonomy fleet, fares, or depot.
• Oct 23, 2026 (MT): TxDMV public list for Tesla Robotaxi, LLC (AV8313426653583) read directly: 507 Model Y and 351 Cybercab (858). The model field spells 30 of the Cybercabs in lowercase. Authorization, not active rides. This supersedes the Oct 16 figure of 349 and 420 (769). CNBC's Oct 21 report of 449 Cybercab and 362 Model Y (811) was not reproduced by this read. Tesla pages read the same day: six ride cities unchanged, coming soon Las Vegas, Jacksonville, Phoenix and San Antonio, Utah absent. Paid Cybercab still reported only in Austin. Oct 21 call: Dallas Cybercab next month (Tesla claim, not a launch). Moravy year-end customer-sale aim and Musk "vast majority" Tesla-owned are claims. AQ26002 resume and Sep 29 memo re-fetched: still open, response due Oct 30, not public. Superseded Oct 30, 2026: Tesla's response was due Oct 30, 2026; not yet public as of Oct 30, 2026. DP26010 resume re-fetched: still an open defect petition, not a recall. No D.R. Autonomy fleet, fares, or depot. Superseded Oct 28, 2026 by the TxDMV read of 507 Model Y and 573 Cybercab-prefix (1,080).
• Oct 16, 2026 (MT): Texas registry figure updated from public reporting. CyberCab.News (published Oct 15) says the TxDMV robotaxi registry as of Oct 14 lists 349 Cybercabs and 420 Model Y vehicles (769 combined). The registry is authorization, not active rides. This supersedes the Oct 13 tracker line of 319 and 739. Superseded Oct 23, 2026 by the TxDMV read of 507 Model Y and 351 Cybercab (858). Superseded Oct 28, 2026 by the TxDMV read of 507 Model Y and 573 Cybercab-prefix (1,080). Utah still not live. No D.R. Autonomy fleet, fares, or depot. AQ26002 and DP26010 were not re-fetched on this stamp.
• Oct 13, 2026 (MT): Defect-petition review DP26010 (opened Oct 9; resume fetched Oct 13) covers a school-zone speeding allegation against 2026 Model Y robotaxis and Cybercabs. It is a petition review, not a recall or a grounding. Tesla's Robotaxi account said Oct 10 that 300+ Cybercabs are serving Austin (Tesla claim). Ashok Elluswamy wrote "Dallas soon," with no date; paid Cybercab ride-hail still reported only in Austin. Texas-registry trackers checked Oct 13 list 319 Cybercabs and 420 Model Y (739). That supersedes the Oct 6 "no newer count" line and is not paid service. AQ26002 still open; Special Order response still due Oct 30 and not public. Superseded Oct 30, 2026: Tesla's response was due Oct 30, 2026; not yet public as of Oct 30, 2026. Utah still not live.
• Sep 23, 2026: Published.
• Sep 30 – Oct 2, 2026: Special Order due / not-public wording; Texas registry counts (attributed to public tracker reporting); Nevada NTA primary source.
• Oct 2, 2026, 8:20 PM MT: Re-checked NHTSA and news: Tesla’s Sep 30 response still not public; no recall, grounding or halt reported. Answer box, watch list and FAQ re-stamped; author byline added.
• Oct 10, 2026 (MT): NHTSA memo to file (dated Sep 29) shows Tesla's Special Order response extended 30 days on Sep 22, to Oct 30, 2026. Response still not public. No grounding, recall, or halt reported. Utah still has no Tesla Robotaxi service.
• Oct 6, 2026 (MT): CNBC (Oct 3, citing an NHTSA spokesperson) reported Tesla obtained an extension on the Sep 30 Special Order response. Response still not public; no new due date published. No grounding, recall, or halt reported. OVSC resume still an open audit query (fetched Oct 6). NHTSA vehicle page indexed Oct 5: 0 recalls, 1 investigation. Texas count updated to CNBC / Texas DMV as of Oct 2: 169 Cybercabs authorized and 420 Model Y (about 589). Registered or authorized is not paid service. Cybercab paid ride-hail still Austin only (CNBC).

Sources

Primary / official

1. NHTSA press release — “NHTSA Opens Investigation into Tesla Cybercab Self-Certification Following Austin Deployment,” Sep 4, 2026
   nhtsa.gov press release — CDN often returns Access Denied to automated fetch; confirm live text in browser.
2. NHTSA OVSC / ODI open resume — Investigation AQ26002, opened 09/03/2026, population ~1,000
   INOA-AQ26002 PDF

National press

3. Reuters — David Shepardson, “US opens probe into Tesla self-certification of Cybercab robotaxis,” Sep 4, 2026
   reuters.com
4. Electrek — Fred Lambert, “NHTSA orders Tesla to prove its Cybercab is legal to sell, under oath,” Sep 15, 2026
   electrek.co
5. Reuters / MarketScreener wire — “US agency orders Tesla to answer questions on Cybercab certification,” Sep 15, 2026
   marketscreener.com partial — prefer Reuters.com URL if available.
6. CNBC — Lora Kolodny, “Tesla’s Cybercab had a rocky first month in Austin. Now comes the hard part: expanding,” Oct 3, 2026. An NHTSA spokesperson told CNBC that Tesla obtained an extension. Texas DMV public records as of Oct 2: 169 Cybercabs authorized for commercial use; 420 Model Y vehicles in the Texas Robotaxi fleet. Austin is the only city where Tesla operates Cybercab ride-hail.
   cnbc.com

Special Order PDF

7. Circulating Special Order PDF (AQ26002) via trade press — treat clause-level quotes as partial until NHTSA/ODI primary host is confirmed.

Utah local color only

8. TownLift — “Tesla's self-driving Cybercab spotted in Park City,” Sep 15, 2026
   townlift.com

Nevada (Las Vegas) status

9. Nevada Department of Business & Industry — “Nevada Transportation Authority Approves Autonomous Vehicle Network Applications for Tesla, Waymo and Aviari,” Aug 21, 2026
   business.nv.gov

Oct 13, 2026 check

10. NHTSA ODI opening resume — Investigation DP26010, opened 10/09/2026, "Open Defect Petition." Products: MY 2026 Tesla Robotaxi (Model Y and Cybercab). Petition received Sep 23, 2026. ODI number 11766676. Fetched Oct 13, 2026.
    INOA-DP26010 PDF
11. Tesla Robotaxi account on X (@robotaxi), Oct 10, 2026: "One month after launch, we've scaled to 300+ Cybercabs serving Austin – an 8x increase in 30 days." Tesla claim, not an independent count.
    x.com/robotaxi
12. Ashok Elluswamy on X (@aelluswamy), Oct 10, 2026, quoting that post: "Two years since the 10/10 Cybercab WeRobot event, the cabs are everywhere in Austin now. Dallas soon." No date.
    x.com/aelluswamy
13. FSD Database, Texas Robotaxi page, fetched Oct 13, 2026: Tesla Robotaxi card read 420 Model Y and 319 Cybercab, 739 registered VINs. A tracker mirror of the Texas list, not the TxDMV credentialing screen and not paid service.
    fsddb.com/robotaxi
14. AI Shift robotaxi radar, fetched Oct 13, 2026: morning reads the same day still 319 Cybercabs and 420 Model Y across 739 VINs, up from an Oct 8 baseline of 169/420/589. Same caveat: tracker, not a TxDMV page opened here.
    aishiftnews.ca/robotaxi-radar

Oct 16, 2026 check

15. CyberCab.News, Jordan Hale, "Closing In: Tesla Adds 30 More Cybercabs, Texas Count Hits 349," published 15 October 2026. Read Oct 16, 2026. The article says Texas DMV records show the Cybercab count moved from 319 to 349, Model Y robotaxis held at 420, and the Texas Robotaxi fleet is 769. It says this is a state registration count, not a live tally of cars carrying paid riders. The registry is authorization, not active rides.
    cybercab.news

Oct 23, 2026 check

16. Texas DMV, TxMCCS public operator list for Tesla Robotaxi, LLC, authorization AV8313426653583, status authorized. Read Oct 23, 2026. Counted 858 vehicles: 507 model-year 2026 Model Y (VIN prefix 7SAYG) and 351 model-year 2026 Cybercab-prefix vehicles (VIN prefix 5YJA). The model field labels 321 Cybercab and 30 cybercab. Filing. Authorization, not active rides, and not a city assignment. The operator URL used that day later returned 404; the current company page is linked in the Oct 28 check. Superseded Oct 28, 2026 by the TxDMV read of 1,080.
    txmccs.txdmv.gov Tesla Robotaxi, LLC company page
17. CNBC, Oct 21, 2026 (updated 7:32 p.m. EDT), Tesla Q3 earnings. Citing the Texas DMV, CNBC reported 362 Model Y and 449 Cybercab authorized in Texas (811). This Oct 23 TxDMV read did not reproduce that figure. The same article quotes Musk: "the vast majority of the Cybercab stuff will be essentially Tesla-owned and transport-as-a-service." Tesla claim, via CNBC.
    cnbc.com
18. Tesla Robotaxi page, read Oct 23, 2026. Rides in Austin, Dallas, Houston, Miami, Orlando and Tampa. Utah not named.
    tesla.com/robotaxi
19. Tesla Robotaxi safety page, read Oct 23, 2026. Same six cities, plus coming soon Las Vegas, Jacksonville, Phoenix and San Antonio. Utah not named. Tesla page, not an independent census.
    tesla.com/robotaxi/safety
20. TechCrunch, Sean O'Kane, Oct 22, 2026, on the Oct 21 call: Cybercab expansion begins in Dallas next month and other cities by year-end; Tesla said it will start selling Cybercabs to fleet operators by year-end. Tesla claims, as reported.
    techcrunch.com
21. Reuters, Abhirup Roy, dateline Oct 21, 2026: Moravy said Tesla is trying to get Cybercabs to customers by the end of 2026, starting small. Elluswamy said Cybercab service expands to Dallas next month. Musk said the vehicle will mainly be Tesla-owned. Tesla claims, as reported. Reuters also reported Tesla has until October 30 to respond to NHTSA.
    reuters.com
22. Engadget, Mariella Moon, Oct 22, 2026: Moravy, "trying to get Cybercabs to customers by the end of this year, 2026," starting small, with current cars for Tesla's own fleet. Musk: the vast majority will be essentially Tesla-owned. Tesla claims, as reported.
    engadget.com
23. NHTSA OVSC opening resume, AQ26002, fetched Oct 23, 2026. Action line still "Open Audit Query."
    INOA-AQ26002 PDF
24. NHTSA memo to file, Sep 29, 2026, fetched Oct 23, 2026. Special Order response due October 30, 2026. No public response found on this check. Superseded Oct 30, 2026: Tesla's response was due Oct 30, 2026; not yet public as of Oct 30, 2026. See the Oct 30 check.
    IRSPO-AQ26002 PDF
25. NHTSA ODI opening resume, DP26010, fetched Oct 23, 2026. Action line still "Open Defect Petition." Not a recall.
    INOA-DP26010 PDF

Oct 28, 2026 check

26. Texas DMV, TxMCCS public company page for Tesla Robotaxi, LLC, authorization AV8313426653583, status authorized. Read Oct 28, 2026, about 7:50 AM MT. Counted 1,080 vehicles across all 11 pages, distinct VINs: 507 model-year 2026 Model Y (VIN prefix 7SAYG) and 573 model-year 2026 Cybercab-prefix vehicles (VIN prefix 5YJA). Filing. Authorization, not active rides, and not a city assignment. The prior operator URL (automated-vehicles/operators/AV8313426653583) returned 404 on this read.
    txmccs.txdmv.gov Tesla Robotaxi, LLC company page

Oct 30, 2026 check

27. NHTSA vehicle page for the 2026 Tesla Robotaxi (Cybercab), read Oct 30, 2026. AQ26002 listed as an open investigation, September 3, 2026 – present. Four associated documents, none a Tesla response. DP26010 listed as an open investigation. Filing.
    nhtsa.gov vehicle page
28. NHTSA OVSC opening resume, AQ26002, re-fetched Oct 30, 2026. Action line still "Open Audit Query (AQ)." Filing.
    INOA-AQ26002 PDF
29. NHTSA Special Order directed to Tesla, Inc., dated September 10, 2026, in the AQ26002 public file. Response to the Office of the Chief Counsel was due September 30, 2026. Filing. The September 29 memo moved that date to October 30, 2026.
    INIM-AQ26002-17090 PDF
30. NHTSA memo to file, September 29, 2026, re-fetched Oct 30, 2026. "The new due date for Tesla’s response to the Special Order is October 30, 2026." Filing.
    IRSPO-AQ26002 PDF
31. NHTSA ODI investigations flat file, FLAT_INV.zip, file timestamp Oct 30, 2026. AQ26002 row has open date 20260903 and a blank close date. Filing.
    static.nhtsa.gov FLAT_INV.zip
32. NHTSA ODI opening resume, DP26010, fetched Oct 30, 2026. Action line still "Open Defect Petition." Filing.
    INOA-DP26010 PDF
33. NHTSA ODI investigations flat file, FLAT_INV.zip, file timestamp Nov 2, 2026. AQ26002 row has open date 20260903 and a blank close date. Filing.
    static.nhtsa.gov FLAT_INV.zip
34. Texas DMV, TxMCCS public company page and vehicle API for Tesla Robotaxi, LLC, authorization AV8313426653583, status authorized. Read Nov 2, 2026, about 7:58 AM MT. 1,244 distinct VINs across 13 pages of 100 (last page 44): 671 Model Y (7SAYG) and 573 Cybercab-prefix (5YJA). Model field: 631 Model Y, 40 Modey Y, 543 Cybercab, 30 cybercab. Filing. Authorization, not active rides. This supersedes the Oct 30 read of 1,080.
    txmccs.txdmv.gov Tesla Robotaxi, LLC company page
35. Texas DMV, TxMCCS public company page and vehicle API for Tesla Robotaxi, LLC, authorization AV8313426653583, status authorized. Read Oct 30, 2026, about 7:55 AM MT. 1,080 distinct VINs across 11 pages of 100: 507 Model Y (7SAYG) and 573 Cybercab-prefix (5YJA). Model field: 543 Cybercab, 30 cybercab. Same count as Oct 28. Filing. Authorization, not active rides. Superseded Nov 2, 2026 by the TxDMV read of 1,244.
    txmccs.txdmv.gov Tesla Robotaxi, LLC company page
36. Tesla Robotaxi page and safety page, read Nov 3, 2026. Rides in Austin, Dallas, Fort Worth, Houston, Miami, Orlando and Tampa. Coming soon (safety page): Las Vegas, Jacksonville, Phoenix and San Antonio. Utah not named. Tesla page.
    tesla.com/robotaxi
37. Tesla Robotaxi page, read Nov 2, 2026. Rides in Austin, Dallas, Houston, Miami, Orlando and Tampa. Coming soon (safety page, same day): Las Vegas, Jacksonville, Phoenix and San Antonio. Utah not named. Tesla page. Superseded Nov 3, 2026: Fort Worth added.
    tesla.com/robotaxi
38. Tesla Cybercab support page, read Nov 2, 2026. "Cybercab rides are currently available in limited areas of Austin, Texas." Tesla page.
    tesla.com/support/robotaxi/cybercab
39. Tesla Robotaxi page, read Oct 30, 2026. Rides in Austin, Dallas, Houston, Miami, Orlando and Tampa. Coming soon: Las Vegas, Jacksonville, Phoenix and San Antonio. Utah not named. Tesla page. Same six cities on the Nov 2 read.
    tesla.com/robotaxi
40. Tesla Cybercab support page, read Oct 30, 2026. "Cybercab rides are currently available in limited areas of Austin, Texas." Tesla page.
    tesla.com/support/robotaxi/cybercab
41. Tesla Investor Relations quarterly disclosure, read Oct 30, 2026. Latest row is Q3, earnings date Oct 21, 2026, 10-Q. No newer Robotaxi terms document. Tesla page.
    ir.tesla.com
42. Reuters, Abhirup Roy, dateline Oct 21, 2026: "Tesla has until October 30 to respond to the agency." Reporting of the deadline, not a filing of the response.
    reuters.com