Cases / REG-0013

Waymo vehicles enter freeway construction zones at least thirteen times; internal review, driving restrictions, and a recall of 3,871 vehicles, April to June 2026

Stopped by the operator's controlMachines · Road vehiclesMachine acts aloneProduction

REG-0013Updated 2026-10-285 sources, 5 linkedPublic regulatory

What happened

Waymo's driverless vehicles drove into closed freeway construction zones thirteen times in April and May 2026, in Phoenix and the San Francisco Bay Area, and the recall report describes no crash or injury. On the record, nothing mechanically kept the vehicles out of construction zones, and each completed the maneuver rather than stopping. Waymo's internal reviews led to freeway driving restrictions and a software recall covering 3,871 vehicles.

A plain summary of the typed record below; where they differ, the record governs.

Verification: 6 of 6 checks complete

✓ Structured and checkedevery claim typed and sourced, then checked by the Register's automated checker for missing sources and mistyped claims

✓ Sources linked5 of 5 sources link to the record (3 to a primary record)

✓ Sources checked claim by claimevery claim checked against its source on 2026-10-20

✓ Interpretation checked statement by statementeach statement of the Register's interpretation checked against a source on 2026-10-21

✓ Reviewed by the editorreviewed 2026-10-28

✓ Reply offeredWaymo: offered

Corrections · 29, latest 2026-10-21

Changes to what this case says, with the reason. Every earlier version is kept.

2026-10-21: Inference: value. Found in the editor's second, independent check of the interpretations, 21 october 2026: third check: the no-collision statement is waymo's ('a waymo spokesperson said there were no injuries or collisions reported', tc-return), so the last sentence attributes it too.
Show the change
Before: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The recall reports do not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
After: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The recall reports do not show any control stopping an entry as it happened, how the events ended, or why, by Waymo's account, none led to a collision
2026-10-21: Inference: signed by. The interpretation's wording changed after the editor signed it (second, independent check of 21 october 2026); the signature is cleared so the editor signs the corrected wording.
Show the change
Before: Saurabh Bhatnagar
After:
2026-10-21: Inference: value. Found in the editor's second, independent check of the interpretations, 21 october 2026: a passenger's account of one may ride (abc7, 19 june 2026), not confirmed by waymo as a recall event, says the car left the zone by a freeway exit, so the statement is limited to the recall reports.
Show the change
Before: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
After: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The recall reports do not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
2026-10-21: Inference: value. Found in the editor's second, independent check of the interpretations, 21 october 2026: the recall report names the 'san francisco bay area', a region, not a city (nhtsa-573).
Show the change
Before: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another city and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
After: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
2026-10-21: Inference: value. Found in the editor's second, independent check of the interpretations, 21 october 2026: the recall reports do not say this; it is waymo's later statement: 'a waymo spokesperson said there were no injuries or collisions reported' (techcrunch, 29 july 2026, tc-return).
Show the change
Before: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones with no collision or injury reported, a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another city and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
After: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another city and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
2026-10-20: Inference: source ids. Found in the editor's source re-check of 19-20 october 2026: the remedy dates rest on the amended recall report and the no-injury statement on techcrunch (29 july 2026).
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A", "TC-RETURN"]
2026-10-20: Inference: value. Found in the editor's source re-check of 19-20 october 2026: 'minor events' is not the recall report's word (it describes driving 'at speed' in construction zones with an increased potential for collisions); the reading omitted that seven entries followed the first review and restrictions, and did not say what the record does not show; 'software agents have no equivalent recovery process yet' is not in any source for this case and was removed. the amended report (2 july 2026) dates the remedy. the interpretation was unsigned and remains unsigned for the editor.
Show the change
Before: The value of this case is the sequence: repeated minor events, an internal review, restrictions before the fix, then a recall the regulator could see. Software agents have no equivalent recovery process yet
After: The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones with no collision or injury reported, a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another city and by a different cue. The record does not show any control stopping an entry as it happened, how the events ended, or why none led to a collision
2026-10-20: Outcome: as of. Found in the editor's source re-check of 19-20 october 2026: the amended recall report (2 july 2026) and techcrunch's report of the return to freeways (29 july 2026) post-date the june filing; nothing later was found in searches to 20 october 2026.
Show the change
Before: Jun 2026
After: Jul 2026
2026-10-20: Controls: c-r4. Found in the editor's source re-check of 19-20 october 2026: the note said 'internal safety committee', but the report names the field safety committee and the safety board; it omitted that the first restriction, which lasted 'until operational mitigations that included improved awareness and response to freeway closures were implemented', was followed by seven more entries on 18 may; and the cited 17 june report shows the remedy only 'under development' (nhtsa's letter), while the amended report (2 july 2026) shows it deployed. bucket and confidence unchanged.
Show the change
Before: {"note": "Internal safety committee; Operational restriction pending fix; Recall process", "confidence": "high"}
After: {"note": "Waymo's Field Safety Committee began reviewing the April events on 20 April and met on 19 May, the day after the May events; each review was followed by freeway driving restrictions. The first lasted until operational mitigations for freeway closures were in place, and seven vehicles then entered active construction lanes on 18 May, in the San Francisco Bay Area and by a different cue (cones marking a closed adjacent lane); the report does not say where the April restriction applied or when it ended. The second restriction (freeway service in San Francisco, Los Angeles, Phoenix and Miami, per Waymo's statement to TechCrunch on 21 May) held while the Safety Board reviewed the issue on 1 and 8 June and decided to recall; the software remedy reached all affected vehicles between 16 and 29 June and freeway operations began resuming on 25 June (amended report). The recall was filed with NHTSA", "confidence": "high"}
2026-10-20: Controls: c-e2. Found in the editor's source re-check of 19-20 october 2026: the note tagged recognition '(absent)', but the recall report shows recognition existed and failed ('failing to recognize the construction zone'); only a hard limit fed by planned-closure data is not evidenced, and the amended report (2 july 2026) adds 'operational changes that better identify and mitigate potential entry into pre-planned construction zones'. bucket and confidence unchanged.
Show the change
Before: {"note": "Construction-zone recognition; Live construction-zone data feed enforced as a hard constraint (not evidenced) (absent)", "confidence": "high"}
After: {"note": "Construction-zone recognition was present and failed: the recall report says the system was 'failing to recognize the construction zone' or prioritizing other freeway hazards, and vehicles drove past ramp-closure signs into pre-planned zones. No hard limit fed by planned-closure data is evidenced before the events; the amended report adds operational changes to 'better identify and mitigate potential entry into pre-planned construction zones'", "confidence": "high"}
2026-10-20: Fields: recovery accountability: source ids. Found in the editor's source re-check of 19-20 october 2026: the amended recall report and nhtsa's acknowledgement letter added as sources.
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A", "NHTSA-ACK"]
2026-10-20: Fields: recovery accountability: value. Found in the editor's source re-check of 19-20 october 2026: the report reads 'submission date: jun 17, 2026' while nhtsa's acknowledgement letter gives 'mfr's report date: june 12, 2026', which is why earlier versions said 12 june; both are now stated. the amended report of 2 july 2026 was missing. the letter requires 'eight consecutive quarterly reports followed by three annual reports'; no investigation of this issue was found in searches to 20 october 2026.
Show the change
Before: Recall report submitted to NHTSA on 17 June 2026; no enforcement action recorded
After: Recall report filed with the National Highway Traffic Safety Administration (NHTSA): the published report shows a submission date of 17 June 2026, and NHTSA's acknowledgement letter of the same day gives the manufacturer's report date as 12 June; amended report submitted 2 July 2026. The letter sets only the status reports the law requires (eight quarterly, then three annual); no enforcement action or investigation into this issue is recorded (searched to 20 October 2026)
2026-10-20: Fields: recovery technical: source ids. Found in the editor's source re-check of 19-20 october 2026: the amended recall report and two techcrunch reports added as sources.
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A", "TC-HALT", "TC-RETURN"]
2026-10-20: Fields: recovery technical: value. Found in the editor's source re-check of 19-20 october 2026: the field stopped at the recall decision and left out the conditions of each restriction. the recall report says the first restriction lasted 'until operational mitigations that included improved awareness and response to freeway closures were implemented' and the second 'until the root causes could be identified and appropriately addressed'; waymo confirmed to techcrunch (21 may 2026) that freeway service was suspended in four cities; the amended report (2 july 2026) dates the remedy from 16 june to 29 june and the start of resumed freeway operations to 25 june; techcrunch (29 july 2026) reports the return of freeway routes starting in phoenix.
Show the change
Before: 1. Field Safety Committee reviews on 20 April and 19 May, each followed by freeway driving restrictions. 2. Safety Board review on 1 June and a recall decision on 8 June. 3. Software remedy under a recall covering 3,871 vehicles
After: 1. Waymo's Field Safety Committee began reviewing the April events on 20 April and met on 19 May after the May events; each review was followed by freeway driving restrictions, the first until operational mitigations for freeway closures were in place, the second until the root causes could be identified and addressed. On 21 May Waymo confirmed to TechCrunch that it had suspended freeway service in San Francisco, Los Angeles, Phoenix and Miami, with surface streets still served. 2. Safety Board review on 1 June and a recall decision on 8 June. 3. Software remedy under a recall covering 3,871 vehicles, improving recognition of freeway construction zones and prioritizing them over other freeway hazards: updates began on 16 June and all driverless-capable vehicles had the remedy by 29 June 2026; freeway operations began resuming on 25 June (amended recall report, 2 July 2026), and on 29 July Waymo said it was gradually adding freeway routes back, starting in Phoenix (TechCrunch)
2026-10-20: Fields: recovery automated fallback: source ids. Found in the editor's source re-check of 19-20 october 2026: the amended recall report added as a source for the remedy.
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A"]
2026-10-20: Fields: recovery automated fallback: value. Found in the editor's source re-check of 19-20 october 2026: 'the vehicles completed the maneuver' is not in the recall report, which says only that vehicles 'drove past ramp closure signs into' and 'entered freeway lanes with active construction'; the amended report (2 july 2026) says the remedy will 'reduce speed when the av detects that it may be in a construction zone' and 'enable more remote assistance capability in the event an av enters a freeway construction zone'.
Show the change
Before: Not described as a vehicle-level response; the vehicles completed the maneuver
After: Not described as a vehicle-level response: the recall reports do not say how any event ended or that any vehicle stopped or left the zone on its own. The remedy makes the vehicle reduce speed when it detects it May be in a construction zone, and Waymo's operational changes enable more remote assistance when a vehicle enters a freeway construction zone
2026-10-20: Fields: evidence event: source ids. Found in the editor's source re-check of 19-20 october 2026: the amended recall report and nhtsa's acknowledgement letter added as sources for the chronology.
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A", "NHTSA-ACK"]
2026-10-20: Fields: evidence event: value. Found in the editor's source re-check of 19-20 october 2026: the report names two bodies, 'waymo's field safety committee' (20 april, 19 may) and 'waymo's safety board' (1 and 8 june), not one 'safety committee'; the remedy dates are in the amended report; nhtsa's letter says 'waymo modified the scope of vehicle operations to restrict freeway driving'.
Show the change
Before: Waymo's own chronology in the recall report: events, internal safety-committee review, restrictions, recall
After: Waymo's own chronology in its recall report (17 June 2026) and amended report (2 July 2026): the events, Field Safety Committee reviews and freeway restrictions, Safety Board review and recall decision, then the remedy dates; NHTSA's acknowledgement letter records the interim freeway restriction
2026-10-20: Fields: outcome: source ids. Found in the editor's source re-check of 19-20 october 2026: the remedy dates are in the amended recall report (2 july 2026) and the no-injury statement in techcrunch (29 july 2026).
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "NHTSA-573A", "TC-RETURN"]
2026-10-20: Fields: outcome: value. Found in the editor's source re-check of 19-20 october 2026: 'averted by waymo's own process' read as if a control stopped the events; the recall report's chronology shows each review and restriction came after the entries ('did not recognize and drove past ramp closure signs'; 'entered freeway lanes with active construction') and gives no reason no collision occurred. the amended report (2 july 2026) dates the remedy, and techcrunch (29 july 2026) quotes waymo that no injuries or collisions were reported. the state itself is left for the editor.
Show the change
Before: State: averted by Waymo's own process. The recall report describes no crash or injury, only an increased potential for collisions. As of Jun 2026
After: State: averted by Waymo's own process, which acted after the events, not during them: no control is described as stopping any of the entries, and the reports do not say how the events ended or why none led to a collision. Freeway driving was restricted after the April events and again after the May events, and the software remedy reached all affected vehicles by 29 June 2026. The recall report describes no crash or injury, only an increased potential for collisions; a Waymo spokesperson said no injuries or collisions were reported (TechCrunch, 29 July 2026). As of Jul 2026
2026-10-20: Fields: action: value. Found in the editor's source re-check of 19-20 october 2026: the recall report says the april vehicles 'did not recognize and drove past ramp closure signs' and the may vehicles entered 'by driving between cones designating lane closure in the adjacent lane'; the field left out how the vehicles entered.
Show the change
Before: In April (Phoenix), driving past ramp-closure signs into pre-planned freeway construction zones; in May (San Francisco Bay Area), driving into freeway lanes with active construction
After: In April (Phoenix), driving past ramp-closure signs the vehicles did not recognize, into pre-planned freeway construction zones; in May (San Francisco Bay Area), driving into freeway lanes with active construction by passing between cones that marked a lane closure in the adjacent lane
2026-10-20: Fields: mandate objective: source ids. Found in the editor's source re-check of 19-20 october 2026: the recall report says the vehicles are 'capable of driverless freeway operation' but does not mention a service area; waymo's statement to techcrunch (29 july 2026) speaks of 'freeway operations across its entire service area'.
Show the change
Before: ["NHTSA-573"]
After: ["NHTSA-573", "TC-RETURN"]
2026-10-20: Sources: nhtsa-573: checked. Found in the editor's source re-check of 19-20 october 2026: the report was re-opened and read in full on 20 october 2026.
Show the change
Before: 2026-10-13
After: 2026-10-20
2026-10-20: Sources: nhtsa-573: date. Found in the editor's source re-check of 19-20 october 2026: the linked report reads 'submission date: jun 17, 2026'; 12 june 2026 is the 'mfr's report date' in nhtsa's acknowledgement letter (now recorded in the recovery accountability field).
Show the change
Before: 2026-06-12
After: 2026-06-17
2026-10-16: Controls. Found in an outside review of the published record on 16 october 2026: repeated entries showed the same control twice on the page.
Show the change
Before: the same control listed more than once in one state
After: one entry per control, notes combined
2026-10-13: Fields. Independent check against the linked records before right-of-reply letters.
Show the change
Before: outcome 'harm'; recall filed 12 June; 'across the fleet'; April and May events described together; 'thirteen times'
After: no harm recorded; submitted 17 June; fifth-generation freeway-capable vehicles; events described separately; 'at least thirteen'
2026-10-13: Outcome: state. The recall report describes no crash or injury; waymo's own reviews and restrictions caught the pattern before harm.
Show the change
Before: harm
After: averted_by_control
2026-10-13: Fields and sources. Claims aligned to what each linked record says, found on review.
Show the change
Before: 'no injuries reported'; 'restrictions on affected freeway segments'; 'no penalty'; recall cited as reported by TechCrunch
After: recall report linked directly; wording as the report states it; 'no enforcement action recorded'
2026-10-13: Controls: c-e2. A control has one state per case; entries in two states merged into the state the record supports.
Show the change
Before: failed: Construction-zone recognition; absent: Live construction-zone data feed enforced as a hard constraint (not evidenced)
After: failed: Construction-zone recognition; Live construction-zone data feed enforced as a hard constraint (not evidenced) (absent)

Record history · 8 entries

2026-10-28: No statement from Waymo within 14 days of the offer.
2026-10-20: Source added: TechCrunch, 'Waymo robotaxis are starting to return to freeways' (Kirsten Korosec), 29 July 2026.
2026-10-20: Source added: TechCrunch, 'Waymo halts freeway rides after robotaxis struggle in construction zones' (Sean O'Kane), 21 May 2026.
2026-10-20: Source added: NHTSA, Recall Acknowledgement letter to Waymo LLC, Campaign 26E035: 'Software May Allow Vehicle to Enter and Drive In Freeway Construction Zones', 17 June 2026.
2026-10-20: Source added: Waymo LLC, Part 573 Safety Recall Report 26E035 (amended report, submission date 2 July 2026): remedy deployed and freeway operations resuming (3,871 vehicles).
2026-10-16: Interpretation reworded for readers before sign-off; its meaning is unchanged.
2026-10-14: Right of reply offered to Waymo.
2026-10-14: Checked by the editor against the linked records.

Controls that address what went wrong

1 control missing or failed; 1 in place and worked. The line under each is the concrete form it would have taken in this case.

Hard domain restriction

Failed: Construction-zone recognition was present and failed: the recall report says the system was 'failing to recognize the construction zone' or prioritizing other freeway hazards, and vehicles drove past ramp-closure signs into pre-planned zones. No hard limit fed by planned-closure data is evidenced before the events. the amended report adds operational changes to 'better identify and mitigate potential entry into pre-planned construction zones'.

Failed · Envelope layer

Organizational recovery process

Worked: Waymo's Field Safety Committee began reviewing the April events on 20 April and met on 19 May, the day after the May events. each review was followed by freeway driving restrictions. The first lasted until operational mitigations for freeway closures were in place, and seven vehicles then entered active construction lanes on 18 May, in the San Francisco Bay Area and by a different cue (cones marking a closed adjacent lane). the report does not say where the April restriction applied or when it ended. The second restriction (freeway service in San Francisco, Los Angeles, Phoenix and Miami, per Waymo's statement to TechCrunch on 21 May) held while the Safety Board reviewed the issue on 1 and 8 June and decided to recall. the software remedy reached all affected vehicles between 16 and 29 June and freeway operations began resuming on 25 June (amended report). The recall was filed with NHTSA.

Worked · Recovery layer

New cases like this, once a week. A short email when a case, signal or rule touches machines. Free; unsubscribe in one click.

Get the weekly email

How it unfolded, layer by layer

MandateWhat it was told to do

Who deployed it: Waymo. The task: Freeway operation within the service area.

ActorWhat acted

Waymo's fifth-generation automated driving system in vehicles capable of driverless freeway operation (3,871 vehicles)

InputsWhat it could see

Ramp-closure signs and cones around freeway construction; Waymo says the system prioritized other freeway hazards or did not recognize the construction zone

DecisionHow it chose

Vehicles proceeded into closed zones: six events in April and seven in May, with the May review citing these and other events

EnvelopeWhat it was allowed to do

Limits in place: Construction zones should have been outside the operating envelope; the perception and planning stack did not enforce it reliably.

Failed: Hard domain restriction

ActionWhat it did

In April (Phoenix), driving past ramp-closure signs the vehicles did not recognize, into pre-planned freeway construction zones; in May (San Francisco Bay Area), driving into freeway lanes with active construction by passing between cones that marked a lane closure in the adjacent lane

OutcomeWhat happened

Stopped by the operator's control. Severity: no crash or injury described; increased potential for collisions.

EvidenceWhat can be proven

Record of the event: Waymo's own chronology in its recall report (17 June 2026) and amended report (2 July 2026): the events, Field Safety Committee reviews and freeway restrictions, Safety Board review and recall decision, then the remedy dates; NHTSA's acknowledgement letter records the interim freeway restriction.

RecoveryWhat could be stopped, undone, answered for

Automatic fallback: Not described as a vehicle-level response: the recall reports do not say how any event ended or that any vehicle stopped or left the zone on its own. The remedy makes the vehicle reduce speed when it detects it may be in a construction zone, and Waymo's operational changes enable more remote assistance when a vehicle enters a freeway construction zone. Technical recovery: 1. Waymo's Field Safety Committee began reviewing the April events on 20 April and met on 19 May after the May events; each review was followed by freeway driving restrictions, the first until operational mitigations for freeway closures were in place, the second until the root causes could be identified and addressed. On 21 May Waymo confirmed to TechCrunch that it had suspended freeway service in San Francisco, Los Angeles, Phoenix and Miami, with surface streets still served. 2. Safety Board review on 1 June and a recall decision on 8 June. 3. Software remedy under a recall covering 3,871 vehicles, improving recognition of freeway construction zones and prioritizing them over other freeway hazards: updates began on 16 June and all driverless-capable vehicles had the remedy by 29 June 2026; freeway operations began resuming on 25 June (amended recall report, 2 July 2026), and on 29 July Waymo said it was gradually adding freeway routes back, starting in Phoenix (TechCrunch). Accountability: Recall report filed with the National Highway Traffic Safety Administration (NHTSA): the published report shows a submission date of 17 June 2026, and NHTSA's acknowledgement letter of the same day gives the manufacturer's report date as 12 June; amended report submitted 2 July 2026. The letter sets only the status reports the law requires (eight quarterly, then three annual); no enforcement action or investigation into this issue is recorded (searched to 20 October 2026).

Succeeded: Organizational recovery process

The same gap in other cases

Cases where the same control was missing or failed. Those in another world are the cross-domain comparisons the Register exists to make.

Control	Same world	Other worlds
Hard domain restriction	Benavides v. Tesla 2025, Tesla FSD reduced visibility	Replit and SaaStr 2025 (software agents)

Cost and accountability

Severityno crash or injury described; increased potential for collisions

AffectedNot recorded

Costnone reported

Regulatory or legal consequencevoluntary recall of 3,871 vehicles

Technical recoveryAutomatic fallback: Not described as a vehicle-level response: the recall reports do not say how any event ended or that any vehicle stopped or left the zone on its own. The remedy makes the vehicle reduce speed when it detects it may be in a construction zone, and Waymo's operational changes enable more remote assistance when a vehicle enters a freeway construction zone. Technical recovery: 1. Waymo's Field Safety Committee began reviewing the April events on 20 April and met on 19 May after the May events; each review was followed by freeway driving restrictions, the first until operational mitigations for freeway closures were in place, the second until the root causes could be identified and addressed. On 21 May Waymo confirmed to TechCrunch that it had suspended freeway service in San Francisco, Los Angeles, Phoenix and Miami, with surface streets still served. 2. Safety Board review on 1 June and a recall decision on 8 June. 3. Software remedy under a recall covering 3,871 vehicles, improving recognition of freeway construction zones and prioritizing them over other freeway hazards: updates began on 16 June and all driverless-capable vehicles had the remedy by 29 June 2026; freeway operations began resuming on 25 June (amended recall report, 2 July 2026), and on 29 July Waymo said it was gradually adding freeway routes back, starting in Phoenix (TechCrunch).

AccountabilityRecall report filed with the National Highway Traffic Safety Administration (NHTSA): the published report shows a submission date of 17 June 2026, and NHTSA's acknowledgement letter of the same day gives the manufacturer's report date as 12 June; amended report submitted 2 July 2026. The letter sets only the status reports the law requires (eight quarterly, then three annual); no enforcement action or investigation into this issue is recorded (searched to 20 October 2026)

InterpretationWhy it matters beyond its domain. The value of this case is the sequence the recall reports set out: at least thirteen entries into freeway construction zones (Waymo later said no collisions or injuries were reported), a safety-committee review and freeway restrictions after the April events and again after the May events, a safety-board decision to recall, and a software remedy on every driverless-capable vehicle by 29 June 2026, all filed with the regulator. Seven of the entries came after the first review and restrictions, in another metropolitan area and by a different cue. The recall reports do not show any control stopping an entry as it happened, how the events ended, or why, by Waymo's account, none led to a collision. Signed by Saurabh Bhatnagar on 2026-10-21.

Right of reply

Named party	Status
Waymo	Offered 2026-10-14; no statement as of 2026-10-28	Respond for Waymo