The MachineRecord
RegistryTMR-0009

An Uber Eats delivery robot became stuck on railroad tracks in Miami and was struck and destroyed by an oncoming train on January 15, 2026, with no injuries reported.

Property damagecollisiondeliveryUber Eats
Date of incident
2026-01-15
Location
Miami, Florida, USA
Sources
6
EscalationFollow-up

Established by press reporting. No regulator or court document is linked to this case yet.

Timeline

How the event developed

  1. 2026-01-16Report

    An Uber Eats delivery robot became stuck on railroad tracks in Miami and was struck and destroyed by an oncoming train on January 15, 2026, with no injuries reported.

    nbcnews.com
  2. 2026-01-16Report

    An Uber Eats delivery robot became stuck on railroad tracks in Miami and was struck and destroyed by an oncoming train on January 15, 2026, with no injuries reported.

    people.com
  3. 2026-01-16Report

    A Coco food delivery robot was destroyed after becoming stuck on railroad tracks and being struck by a Brightline train in Fort Lauderdale, Florida.

    local10.com
  4. 2026-01-17Follow-up

    A Coco Robotics delivery robot became stuck on a railroad track in Miami and was destroyed after a Brightline commuter train struck it; no humans were injured.

    nypost.com
  5. 2026-01-17Follow-up

    A delivery robot became stuck on train tracks in Miami and was destroyed by an oncoming train on Thursday night; no people were injured.

    thedailybeast.com
  6. 2026-01-18Report

    A commuter train demolished an autonomous food delivery robot that had become stuck on the tracks in South Florida.

    abcnews.com
Sources

Every claim above traces to one of these

Links are never hidden behind a paywall of ours. Where a copy of the page exists it is linked beside the source with the date it was taken, because news links rot and a dead link next to a saved copy is still evidence. Some copies predate this register: they were made by the Internet Archive before we existed, and the date shown is the date of that copy, not of our visit.

Right of reply

Named in this case?

Any company named here can submit a response. We publish it in the case unedited, and a request makes the pipeline re-check the case against its own sources within a day. Target turnaround for our reply is five working days.