_Incident · Injury_

# Jersey City cyclist injured when Avride delivery robot drove into bike lane

Canonical ID: `c58c64d4-b354-407f-b9d5-93adc0fae7b2`

- **Occurred:** 2026-05-11
- **Kind:** `injury`
- **Status (derived):** active
- **Company:** [Avride](/companies/avride.md) (id: `4143e494-260e-49c8-8d04-3e85d9c7218a`)

A cyclist in Jersey City was injured when a delivery robot drove into a bike lane causing a collision. The incident was described as a robot hit-and-run. This occurred during the Grubhub Avride delivery pilot in Jersey City.

## Sources (1)

1. https://www.instagram.com/reel/DYM9-_mE8QT/

## Status history

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

## Common questions

### What happened in Jersey City cyclist injured when Avride delivery robot drove into bike lane?

A cyclist in Jersey City was injured when a delivery robot drove into a bike lane causing a collision. The incident was described as a robot hit-and-run. This occurred during the Grubhub Avride delivery pilot in Jersey City.

### 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 Jersey City cyclist injured when Avride delivery robot drove into bike lane?

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

### Has anyone responded to Jersey City cyclist injured when Avride delivery robot drove into bike lane?

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 Jersey City cyclist injured when Avride delivery robot drove into bike lane?

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


_API: GET /v1/incidents/c58c64d4-b354-407f-b9d5-93adc0fae7b2 · sources: /v1/incidents/c58c64d4-b354-407f-b9d5-93adc0fae7b2/sources · responses: /v1/incidents/c58c64d4-b354-407f-b9d5-93adc0fae7b2/responses · status: /v1/incidents/c58c64d4-b354-407f-b9d5-93adc0fae7b2/status · canonical URL: /incidents/injury-2026-05-11-avride_