DEPLOYDatabase

Retracted · 2026-07-24

Duplicate ingestion of the same event as hellobike-zhuzhou-pedestrian-injury-2025, the canonical record for "Baidu/Hellobike Zhuzhou pedestrian injury (2025-12-06)". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction fairness policy.

Incident · Injury · Retracted

Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025)

Original claim shown above is no longer asserted. See the retraction notice for context.

In December 2025 a Baidu Apollo Go robotaxi was involved in an accident in a central Chinese city that left two people in intensive care, one of the more serious reported injury outcomes from a Chinese robotaxi operation. Cause not publicly established at the time of reporting.

Occurred 2025-12-06 · Xiaodu Pro AI Glasses at Global · Baidu · Global · Wearable AI

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 (1)

  1. CarNewsChina · https://carnewschina.com/2025/12/06/baidus-robotaxi-causes-accident-in-a-central-city-of-china-leaves-two-in-intensive-care/

Status history

  • Retracted · 2026-07-24

    Duplicate ingestion of the same event as hellobike-zhuzhou-pedestrian-injury-2025, the canonical record for "Baidu/Hellobike Zhuzhou pedestrian injury (2025-12-06)". This duplicate is retracted to suppress it from aggregates; its own URL stays index,follow per the retraction fairness policy.

Common questions

What happened in Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025)?
In December 2025 a Baidu Apollo Go robotaxi was involved in an accident in a central Chinese city that left two people in intensive care, one of the more serious reported injury outcomes from a Chinese robotaxi operation. Cause not publicly established at the time of reporting. This incident was later retracted; see the retraction banner at the top of the page for the correction.
When did this incident occur?
The incident is recorded as occurring on December 6, 2025 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025)?
Xiaodu Pro AI Glasses by Baidu is the recorded robot involved in this incident at Global.
Has anyone responded to Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025)?
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 Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025)?
This incident is retracted on the DEPLOY registry. The page remains so the correction reaches readers, but the incident is suppressed from aggregate counts (company / model / location) so it no longer counts against anyone.
Methodology: Verified · 1 source (no primary) · last reviewed 2026-07-14

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-07-14

Sources by quality tier

1
unclassified
Unclassified source

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

Methodology surface for Baidu Apollo Go robotaxi caused an accident in a central Chinese city, leaving two people in intensive care (2025).

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 e2b5eeb3-bac9-46fd-95b1-a60311becddb