Physical State Logo
Physical State

Knightscope K5 did not summon police when a bystander pressed its emergency button during a fight

[OTHER]

Oct 4, 2019 · Knightscope · Knightscope K5 · M Resort Spa Casino, Henderson NV

All Incidents

Failure Mode

OTHER

Event Date

Oct 4, 2019

Primary Entity

Knightscope

Robotic Platform

Knightscope K5

Jurisdiction / Location

M Resort Spa Casino, Henderson NV

Audit Standard

Physical State Verified

Incident Abstract & Audit Findings

During a fight in a Huntington Park, California park, a bystander pressed the emergency button on a Knightscope K5 patrol unit ("HP RoboCop") to alert police, but the robot did not summon officers. The police chief later explained the unit routed alerts to Knightscope rather than dispatch, exposing a gap between public expectation and the robot response loop. The case illustrates the load-bearing security-robot claim axis: alert-to-human versus autonomous response.

System & Fleet Architecture

Operating Manufacturer

KnightscopeView Manufacturer

Hardware Platform

Knightscope K5View Spec

Operational Sectors

Physical AI / Robotics

Primary Sources & Evidentiary Filings

  • https://www.nbcnews.com/tech/tech-news/robocop-park-fight-how-expectations-about-robots-are-clashing-reality-n1059671

    https://www.nbcnews.com/tech/tech-news/robocop-park-fight-how-expectations-about-robots-are-clashing-reality-n1059671

  • https://incidentdatabase.ai/cite/77/

    https://incidentdatabase.ai/cite/77/

Related Incidents & Failure Precedents

6 records on file

Incident Context & FAQ

What happened in Knightscope K5 did not summon police when a bystander pressed its emergency button during a fight?

During a fight in a Huntington Park, California park, a bystander pressed the emergency button on a Knightscope K5 patrol unit ("HP RoboCop") to alert police, but the robot did not summon officers. The police chief later explained the unit routed alerts to Knightscope rather than dispatch, exposing a gap between public expectation and the robot response loop. The case illustrates the load-bearing security-robot claim axis: alert-to-human versus autonomous response.

When did this incident occur?

The incident is recorded as occurring on October 4, 2019 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 did not summon police when a bystander pressed its emergency button during a fight?

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 did not summon police when a bystander pressed its emergency button during a fight?

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 did not summon police when a bystander pressed its emergency button during a fight?

This incident is an active record on the DEPLOY registry; no retraction or correction has been issued.