Incident · Injury
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.
Occurred 2026-05-11 · Avride delivery robot at Bowling Green, Ohio, USA · Avride · Bowling Green, Ohio, USA · Sidewalk delivery
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
- Markdown mirror: /incidents/injury-2026-05-11-avride.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/incidents/c58c64d4-b354-407f-b9d5-93adc0fae7b2
- Data documentation: /data
- Query this programmatically: Deploy MCP
Sources (2)
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?
When did this incident occur?
What robot was involved in Jersey City cyclist injured when Avride delivery robot drove into bike lane?
Has anyone responded to Jersey City cyclist injured when Avride delivery robot drove into bike lane?
What is the current status of Jersey City cyclist injured when Avride delivery robot drove into bike lane?
Methodology: Verified · 2 sources (no primary) · last reviewed 2026-07-14
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-07-14
Sources by quality tier
- 2
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Jersey City cyclist injured when Avride delivery robot drove into bike lane.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 c58c64d4-b354-407f-b9d5-93adc0fae7b2