DEPLOYDatabase

Incident · Regulatory action

NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas

On March 3, 2026, the NTSB opened a safety investigation into Waymo ADS-equipped vehicles passing school buses stopped to load or unload passengers in violation of Texas state law. The NTSB identified a January 12, 2026 incident where a driverless Waymo Jaguar I-Pace on East Oltorf Street in Austin stopped for a school bus with active red lights and extended stop arms, then contacted remote assistance, received an incorrect No answer about whether it was a school bus with active signals, and proceeded to pass the bus. Austin ISD reported multiple similar incidents. NHTSA had earlier opened PE25013 in October 2025 and Waymo issued a December 2025 recall (25E-084) covering 3,067 vehicles.

Occurred 2026-03-03 · Waymo

How to read this record

Incident records on DEPLOY are compiled from public sources (regulatory filings, news reports, and operator disclosures) and reflect what has been reported and tracked to date. They are not legal findings, determinations of fault, or safety ratings, and may be updated as new information is verified. See the sources below for the underlying references.

Machine-readable surfaces

Sources (2)

  1. NTSB Investigation HWY26FH007 · https://www.ntsb.gov/investigations/Pages/HWY26FH007.aspx · 2026-03-03
  2. Reuters · https://www.reuters.com/technology/ntsb-says-waymo-robotaxis-illegally-passed-stopped-school-buses-new-incidents-2026-03-03/ · 2026-03-03

Status history

  • Active · 2026-07-17 · agent:recon

Common questions

What happened in NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas?
On March 3, 2026, the NTSB opened a safety investigation into Waymo ADS-equipped vehicles passing school buses stopped to load or unload passengers in violation of Texas state law. The NTSB identified a January 12, 2026 incident where a driverless Waymo Jaguar I-Pace on East Oltorf Street in Austin stopped for a school bus with active red lights and extended stop arms, then contacted remote assistance, received an incorrect No answer about whether it was a school bus with active signals, and proceeded to pass the bus. Austin ISD reported multiple similar incidents. NHTSA had earlier opened PE25013 in October 2025 and Waymo issued a December 2025 recall (25E-084) covering 3,067 vehicles.
When did this incident occur?
The incident is recorded as occurring on March 3, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
Who was involved in NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas?
The incident is recorded as involving Waymo on the DEPLOY registry. No specific robot model is linked to this incident in the registry.
Has anyone responded to NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas?
No responses to this incident are recorded on the DEPLOY registry. Operators, manufacturers, or affected parties can submit responses to the editorial team; absence is not a guarantee no response was issued.
What is the current status of NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas?
This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.
Methodology: Unreviewed · 2 sources (1 primary) · last reviewed 2026-07-17

Verification posture

Unreviewed

Low confidence

Review state

Stable

Last reviewed 2026-07-17

Sources by quality tier

1
primary-government-record
Government record
1
secondary-established-publication
Established publication

The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.

Methodology surface for NTSB opens investigation HWY26FH007 into Waymo robotaxis illegally passing stopped school buses in Austin, Texas.

Deploy Watch

Track this incident.

We notify you when the regulator updates the record, the remedy status changes, or a related incident surfaces.


Canonical ID fa5ef82c-415d-4901-8ea4-48f0da552f08