DEPLOYDatabase

Incident · Other

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.

Occurred 2019-10-04 · 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.
Track Knightscope K5 did not summon police when a bystander pressed its emergency button during a fight

Machine-readable surfaces

Sources (2)

  1. NBC News · https://www.nbcnews.com/tech/tech-news/robocop-park-fight-how-expectations-about-robots-are-clashing-reality-n1059671 · 2019-10-11
  2. AI Incident Database (Incident 77) · https://incidentdatabase.ai/cite/77/

Common questions

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.
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-08-21

Verification posture

Verified

Low confidence

Review state

Stable

Last reviewed 2026-08-21

Sources by quality tier

2
unclassified
Unclassified source

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

Methodology surface for Knightscope K5 did not summon police when a bystander pressed its emergency button during a fight.

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 ce4757c7-3395-402f-8561-9f1d7d4c8314