DEPLOYDatabase

Retracted · 2026-07-12

Duplicate of knightscope-k5-stanford-shopping-center-2016, the canonical record (linked to the knightscope-k5 model, primary-sourced, reviewed). This orphan (unlinked, unreviewed) is retracted to suppress it from aggregates; its own URL remains index,follow per the retraction policy.

Incident · Injury · Retracted

Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)

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

In July 2016 a Knightscope K5 autonomous security robot patrolling Stanford Shopping Center in Palo Alto, California struck a 16-month-old toddler, knocking him down, bruising his leg, and running over one foot. Knightscope called it a 'freakish accident.' An early, widely cited public-space security-robot injury.

Occurred 2016-07-07 · Knightscope K5 at M Resort Spa Casino, Henderson NV · Knightscope · M Resort Spa Casino, Henderson NV · Security robots

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. Palo Alto Online · https://www.paloaltoonline.com/news/2016/07/13/parents-upset-after-stanford-shopping-center-security-robot-knocks-down-child/

Status history

  • Retracted · 2026-07-12

    Duplicate of knightscope-k5-stanford-shopping-center-2016, the canonical record (linked to the knightscope-k5 model, primary-sourced, reviewed). This orphan (unlinked, unreviewed) is retracted to suppress it from aggregates; its own URL remains index,follow per the retraction policy.

Common questions

What happened in Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)?
In July 2016 a Knightscope K5 autonomous security robot patrolling Stanford Shopping Center in Palo Alto, California struck a 16-month-old toddler, knocking him down, bruising his leg, and running over one foot. Knightscope called it a 'freakish accident.' An early, widely cited public-space security-robot injury. 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 July 7, 2016 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.
What robot was involved in Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)?
Knightscope K5 by Knightscope is the recorded robot involved in this incident at M Resort Spa Casino, Henderson NV.
Has anyone responded to Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)?
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 Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016)?
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 Knightscope K5 security robot knocked down and ran over a toddler at Stanford Shopping Center (2016).

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 f2318495-c885-4e2b-9e12-319f3502621f