Research Note
Research Note: A Matched Protocol for Robotaxi Safety Claims
The safety guide needs a method that can test crash, injury, intervention, disengagement, or mileage claims without converting unlike records into a ranking.
Research Note: A Matched Protocol for Robotaxi Safety Claims
Question
The safety guide needs a method that can test crash, injury, intervention, disengagement, or mileage claims without converting unlike records into a ranking.
Federal data boundary
NHTSA's Standing General Order page publishes reported ADS and Level 2 ADAS incidents and a detailed limitations section. The third amended order became effective June 16, 2025. NHTSA says reporting requirements differ between ADS and Level 2 ADAS, reporting entities have different access to crash information, duplicate reports can occur, and the public data should not be assumed to represent all crashes statistically.
The third amended order defines the current reporting threshold and timing. A report is evidence that an incident met the reporting rule as understood by the reporting entity. It is not by itself a fault finding, a fleet exposure record, or a safety rate.
Raw report counts cannot compare operators unless the analyst also has compatible exposure, operating conditions, event definitions, and reporting completeness.
Comparison fields
Every claim should disclose the following fields.
| Field | Required question |
|---|---|
| System and version | Which ADS, vehicle platform, software version, and operating mode produced the data? |
| Numerator | What event counts, who determines it, and does it include minor contact, alleged injury, police report, airbag deployment, or serious injury? |
| Exposure | Miles, trips, hours, vehicles, passenger miles, intersections, or another denominator? |
| Domain | Which cities, roads, speeds, weather, lighting, traffic, and time periods are represented? |
| Human role | Was there a safety driver, remote assistance, direct remote driving, or rider-only operation? |
| Baseline | Which human or competing fleet is used, and is its exposure matched to the same domain? |
| Reporting rule | What threshold, knowledge standard, update process, duplicate treatment, and exclusions apply? |
| Severity and fault | Does the result include all involvement, responsibility, injury level, vulnerable road users, and secondary events? |
| Uncertainty | Are confidence intervals, zero-event limitations, and sample-size constraints reported? |
Intervention and disengagement require an additional definition. A company can count human steering takeover, high-level route guidance, a safety-driver precaution, a system-requested handoff, or a simulation event differently. "Miles per intervention" has little meaning until the event definition and supported domain are visible.
A useful study and its limits
A 2025 Waymo-affiliated retrospective study compared 56.7 million rider-only miles with human benchmarks matched by vehicle type, road type, and location. It used NHTSA incident records, company mileage, crash-type groups, severity outcomes, and statistical intervals. The authors reported statistically lower rates for several outcomes.
The study is useful because it demonstrates better comparison design. It still studies one operator, a defined period, selected locations, specific outcomes, and company-supplied exposure. It does not prove every robotaxi, every Waymo software version, or every city is safer than every human driver.
Waymo's living Safety Impact hub provides downloadable methods and current company analysis. Its July 2026 time-and-location research summary argues that roadway, city, day, and time materially change the human baseline. Both remain operator-affiliated sources and should be labeled that way.
Decision rule
If the numerator, denominator, domain, baseline, reporting rule, severity, and uncertainty cannot be matched, the correct result is "not comparable from the disclosed evidence." That is not the same as saying the systems are equally safe. It is a statement about the evidence.
Editorial use
The public guide should show how to build a matched claim table and when to stop. It should not rank Tesla and Waymo from raw NHTSA counts or repeat the transcript's 10,000-versus-444-mile comparison.
Sources
Follow the evidence.
- statutes.capitol.texas.gov: IN.1954statutes.capitol.texas.gov
- rosap.ntl.bts.gov: 56823rosap.ntl.bts.gov
- nhtsa.gov: automated vehicles safetynhtsa.gov
- nhtsa.gov: national av safety forumnhtsa.gov
- statutes.capitol.texas.gov: OC.2402statutes.capitol.texas.gov
- rosap.ntl.bts.gov: dot 88518 DS1rosap.ntl.bts.gov
- open.spotify.com: 59g3xZ2WunOCIOrju8FTKSopen.spotify.com
- saemobilus.sae.org: j3016 202104 taxonomy definitions terms related driving automation systems road motor vehiclessaemobilus.sae.org
- daltonanderson.ghost.io: teslas robotaxi pilot hype vs reality in austindaltonanderson.ghost.io
- nhtsa.gov: standing general order crash reportingnhtsa.gov
- capitol.texas.gov: SB02807Fcapitol.texas.gov
- waymo.com: impactwaymo.com
- txdmv.gov: AVprogramtxdmv.gov
- nhtsa.gov: third amended SGO 2021 01 2025nhtsa.gov
- tesla.com: robotaxitesla.com
- tdi.texas.gov: auto insurancetdi.texas.gov
- arxiv.org: 2505arxiv.org
- rosap.ntl.bts.gov: 79800rosap.ntl.bts.gov
- youtu.be: K3Nj92fDh3wyoutu.be
- tdi.texas.gov: cb020tdi.texas.gov
- nhtsa.gov: automated driving systems 20 voluntary guidancenhtsa.gov
- waymo.com: time geo crash risk effectwaymo.com
- nhtsa.gov: av public meeting 2026nhtsa.gov
- tesla.com: TSLA Q2 2025 Updatetesla.com
- tesla.com: robotaxitesla.com