Public Safety at Risk: Robot Crashes Continue

A delivery robot navigating a sidewalk in an urban area

Two “autonomous” delivery robots shattered Chicago bus-shelter glass in back-to-back crashes—raising a basic question taxpayers keep asking: who’s accountable when tech fails in public spaces?

Quick Take

Two different delivery robots—Serve Robotics and Coco Robotics—crashed into Chicago bus shelters within about 48 hours, breaking glass in West Town (March 23) and Old Town (March 24).
No injuries were reported in the coverage, but both incidents left dangerous debris on busy sidewalks near CTA stops.
The companies said they handled cleanup and repairs while launching reviews, as public pushback grows against Chicago’s sidewalk-delivery robot pilot.
Chicago’s pilot program runs through May 2027, and residents have organized a petition—reported at 3,700+ signatures—calling for the program to end over safety and accessibility concerns.

Back-to-back crashes put “pilot programs” under a harsher spotlight

Chicago saw two strikingly similar incidents in late March: a Serve Robotics delivery robot hit a CTA bus shelter in West Town on March 23, then a Coco Robotics robot struck another shelter in Old Town around 4 p.m. on March 24. Videos circulated online showing the machines pushing through glass panels, then continuing on. Reports said no one was hurt, but shattered glass scattered across sidewalks near transit stops.

Serve Robotics said it dispatched a human crew to clean up the West Town site and that it was reviewing what happened and contacting relevant stakeholders. In Old Town, witnesses described hearing the crash and seeing broken glass left near the shelter. Coverage also noted a second robot in the area with a red flag, though reports did not clearly explain its purpose. In both incidents, the emphasis quickly shifted from “viral footage” to public safety.

Company statements stress rarity, but the public measures risk differently

Coco Robotics, through a company executive involved in government relations, described the Old Town collision as not representative of normal operations and said it was the first time the company’s robot had collided with a structure after more than one million miles traveled. Coco said safety is a priority, it would take full responsibility for repairs, and it launched an internal investigation. Serve similarly characterized its crash as extremely rare.

Those assurances may be technically meaningful to investors and city staff, but everyday residents tend to judge risk by outcomes, not mileage statistics. Sidewalks are shared space: parents with strollers, seniors, commuters, and the disabled don’t get to “opt out” of a machine’s mistake at a bus stop. Even when nobody is injured, broken shelter glass and debris create immediate hazards—exactly the kind of problem local government exists to prevent, not normalize.

Chicago’s pilot program faces a familiar credibility problem: enforcement after the fact

Chicago’s delivery-robot program is set to run through May 2027, and the city has even created a 311 complaint category for robot-related issues—an indicator that problems are frequent enough to require a dedicated reporting lane. The reporting also pointed to ongoing community opposition, including a petition effort led by Josh Robertson that had gathered more than 3,700 signatures seeking to end the program over safety and accessibility concerns.

That pattern—roll out first, patch later—hits a nerve for voters who’ve watched government grow more confident in experimenting with daily life while staying vague about accountability. In a country where local leaders insist they can regulate everything from home heating choices to school speech policies, the public has reason to demand clear rules here too: who pays, who’s liable, what’s the enforcement mechanism, and what is the threshold for pausing a program when failures stack up?

What’s known, what isn’t, and what to watch next

As of late March coverage, both sites were cleaned and the companies said they would cover repairs; Serve’s repairs were reported as completed, while Coco said it was investigating. No additional crashes were reported in the provided sources after those two days, and there were no confirmed injuries tied to the incidents. What remains unclear is what the investigations will conclude and whether the city will tighten restrictions, impose new technical requirements, or reconsider the pilot.

For conservatives frustrated by waste and government overreach, the practical question isn’t whether delivery robots are “cool” or “the future.” It’s whether public officials are protecting the basics—safe sidewalks, transparent rules, and real accountability—before letting private companies turn dense neighborhoods into a living lab. Until Chicago publishes clearer standards and consequences, the public will keep treating these crashes as a warning, not an isolated glitch.