_Incident · Injury_

# New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury

Canonical ID: `e7008981-34c9-4678-8bc0-02008b0a8bfd`

- **Occurred:** 2026-05-11
- **Kind:** `injury`
- **Status (derived):** active
- **Company:** [Serve Robotics](/companies/serve-robotics.md) (id: `fe7b5d4c-4e52-4f57-8593-b8289761539b`)

A New Jersey cyclist is suing after a delivery robot 'hit-and-run' left him with a broken shoulder and head injury. Robot failed to stop after collision.

## Sources (1)

1. https://news12.com/new-jersey-cyclist-sues-delivery-robot-hit-and-run/

## Status history

- **active** · 2026-07-03 · agent:depth

## Common questions

### What happened in New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury?

A New Jersey cyclist is suing after a delivery robot 'hit-and-run' left him with a broken shoulder and head injury. Robot failed to stop after collision.

### When did this incident occur?

The incident is recorded as occurring on May 11, 2026 on the DEPLOY registry. The date reflects the underlying real-world event, not the registry record's creation date.

### Who was involved in New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury?

The incident is recorded as involving Serve Robotics on the DEPLOY registry. No specific robot model is linked to this incident in the registry.

### Has anyone responded to New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury?

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 New Jersey cyclist sues after delivery robot hit-and-run leaves him with broken shoulder and head injury?

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


_API: GET /v1/incidents/e7008981-34c9-4678-8bc0-02008b0a8bfd · sources: /v1/incidents/e7008981-34c9-4678-8bc0-02008b0a8bfd/sources · responses: /v1/incidents/e7008981-34c9-4678-8bc0-02008b0a8bfd/responses · status: /v1/incidents/e7008981-34c9-4678-8bc0-02008b0a8bfd/status · canonical URL: /incidents/injury-2026-05-11-serve-robotics_