A Philadelphia woman has been arrested after deliberately blocking an Uber Eats delivery robot on a public pavement, bringing a dispute over automated deliveries, pedestrian rights and freedom of protest into sharper focus.
Carolyn Marvin, a 78-year-old retired University of Pennsylvania professor, was arrested on Wednesday, 14 October 2026, after reportedly refusing repeated police instructions to move. Local broadcasters covered the incident before The Verge reported it on 18 October.
Philadelphia police have confirmed the encounter through statements to local reporters. But the legal questions are less straightforward than the arrest suggests. Pennsylvania permits autonomous delivery robots on pavements while explicitly requiring them to yield to pedestrians. The case raises an important question: how should police and robot operators respond when someone intentionally prevents an otherwise lawful delivery?
What happened during the Philadelphia delivery robot protest?
Police responded to the 1200 block of Filbert Street, near Reading Terminal Market, at approximately 1:16pm on 14 October after a report involving an Uber Eats delivery robot.
According to a police statement reported by PhillyVoice, officers responded to an alleged criminal mischief involving a robot. They instructed Marvin to move out of its path, but she repeatedly refused. Officers arrested her and issued a criminal violation notice for disorderly conduct.
| Detail | Confirmed information |
|---|---|
| Incident date | 14 October 2026 |
| Location | 1200 block of Filbert Street, Philadelphia |
| Person arrested | Carolyn Marvin, 78 |
| Reported offence | Disorderly conduct |
| Delivery platform | Uber Eats |
| Legal outcome | No final court determination established in the reporting reviewed |
Marvin told local reporters that she objects to companies replacing human delivery workers with automated machines. She described standing in front of delivery robots as a deliberate form of public protest and indicated that she intends to challenge the charge.
This was not her first encounter with the technology. Marvin said she had obstructed robots on multiple previous occasions, including an incident in September. She maintains that she tries to avoid obstructing human pedestrians.
Uber declined to comment when PhillyVoice approached it. Public reporting has not established who initially contacted police, whether a remote robot operator intervened, or what recovery procedures were attempted before the arrest.
Pennsylvania gives delivery robots pedestrian status, but humans retain priority
The most consequential detail is how Pennsylvania legally classifies autonomous delivery devices.
Under the state’s personal delivery device framework, qualifying robots are treated as pedestrians rather than conventional motor vehicles. However, that classification comes with an explicit restriction: robots must yield to pedestrians and cyclists in pedestrian areas.
PennDOT’s official personal delivery device guidance requires operators to obtain authorisation before deploying these machines. The state also limits their dimensions, weight and operating speeds.
The legal maximum speed on pedestrian routes is 12mph. That is a regulatory ceiling, not evidence of how quickly the Philadelphia robot was travelling.
PennDOT’s authorised-operator list identifies Avride, working in partnership with Uber Eats, as a Phase 2 operator in Philadelphia, with authorisation dated 23 September 2026.
Phase 2 permits remote supervision rather than requiring a human operator to follow every machine within sight. Crucially, a remote operator must be able to intervene and override the device.
Nothing in those requirements grants a robot unconditional priority over a person standing on a pavement. Similarly, a robot’s obligation to yield does not automatically create a right to obstruct deliveries indefinitely.
Those are separate questions involving the robot’s operating obligations and the legality of an individual’s conduct.
Philadelphia already has powers to restrict dangerous robot routes
Although PennDOT controls authorisation, Philadelphia still has power over deployment locations.
Section 12-3502 of the Philadelphia Code requires authorised operators to notify the city at least 30 days before beginning operations. Operators must provide details of their intended operating areas so officials can assess potential hazards.
The city’s Streets Department can prohibit robots from certain sections of the public right-of-way when it determines their operation poses a hazard, after consulting with the operator.
This is a narrower power than imposing a general ban at will. Pennsylvania’s statewide framework limits independent municipal regulation, but preserves specific local safety restrictions.
Philadelphia City Council has also considered further delivery-service rules. Bill 260526, introduced in May 2026, proposes registration and compliance measures involving delivery workers and autonomous delivery units. Its official legislative record still lists it as in committee, so those proposed measures are not law.
For robot operators, the practical consequence is that statewide approval does not remove the need to assess individual pavements, crossings, construction zones and crowded routes.
Uber’s customer rules do not automatically govern every passer-by
Uber publishes Autonomous Vehicle Global Rider and Eater Guidelines covering customers who use autonomous transport and delivery services.
Those guidelines prohibit interference with vehicle controls and sensors, physically pushing or shaking delivery robots, and forcibly opening their compartments. Uber also reserves the ability to refer appropriate incidents to law enforcement.
An important limitation: these are platform rules governing people who use Uber’s services. A member of the public who has not ordered a delivery is not automatically subject to a customer agreement simply because a robot approaches them.
That does not give bystanders permission to damage property or commit an offence. It means a platform’s contractual rules cannot themselves settle the legality of a protest on a public pavement.
The unresolved operational question is whether the robot stopped safely, attempted to navigate around Marvin, requested remote assistance or remained stationary until police intervened. None of those steps has been publicly established for this specific encounter.
Does blocking a delivery robot amount to disorderly conduct?
Marvin argues that her behaviour is protected by the First Amendment. Police treated her repeated refusal to move as grounds for intervention.
Pennsylvania’s disorderly conduct statute, 18 Pa.C.S. Section 5503, addresses conduct undertaken with the intent to cause public inconvenience, annoyance, or alarm, or that recklessly creates that risk. Its provisions include conduct creating certain hazardous or physically offensive conditions without a legitimate purpose.
The available reporting does not establish which statutory elements authorities intend to rely upon, or how a court would assess Marvin’s protest.
A charge is not a finding of guilt. Nor is the existence of a lawful delivery service, by itself, enough to determine whether someone’s expressive conduct has crossed a legal boundary.
A further distinction concerns obstruction of the pavement itself. Preventing a machine from advancing while leaving space for other pedestrians differs in fact from blocking wheelchair users, people with pushchairs, or the general public.
Those details could matter in any subsequent assessment. No court ruling from this incident has established a general precedent for arrests involving passive obstruction of delivery robots.
Why robot operators need a specific public-obstruction procedure
The arrest exposes an operational risk that obstacle-detection demonstrations rarely address.
A robot can correctly identify a stationary person and stop without solving the delivery problem. If the person remains deliberately in its path, the machine still needs a safe and accountable way to end the encounter.
Operators should distinguish between three types of obstruction:
| Situation | Appropriate operational response |
|---|---|
| Pedestrian temporarily crosses or pauses | Stop or yield, maintain clearance and continue when safe |
| Person deliberately blocks the route without violence | Keep the robot stationary, request remote assistance, assess a safe alternative and record the interruption |
| Robot is damaged, tampered with or creates an immediate safety risk | Enter a safe state, escalate to a human operator and involve emergency services where justified |
These are recommended operational safeguards, not a claim that Avride used this exact procedure.
Useful incident records would include the robot’s location, obstruction duration, route alternatives considered, remote-control events and the reason for any decision to request police assistance. Any retained camera footage would also need appropriate privacy controls and access restrictions.
These decisions have a commercial cost. A delayed robot occupies fleet capacity, may interrupt a paid delivery and can require human supervision or retrieval. Allowing an automated system to sit indefinitely is inefficient, but immediately escalating an otherwise non-violent obstruction to police can create reputational and community-relations costs.
Better planning technology may eventually improve recovery from unexpected obstacles. Our coverage of planning-capable robotics agents explains why predicting alternative actions is an important technical problem. Yet even sophisticated navigation cannot resolve disagreements about who should use public space.
Human interruption and override matter just as much. Similar control principles feature in Microsoft’s proposed Humanist AI code of conduct, although that draft is not a regulatory safety standard for delivery robots.
Earlier incidents reveal a broader public-access problem
The Philadelphia arrest follows other confrontations involving autonomous couriers.
In April, local broadcaster 6abc reported that someone kicked an Uber Eats delivery robot, overturning it near Juniper and Locust Streets. That was a separate incident involving physical interference, not a legal precedent that would determine the outcome of Marvin’s case.
Public discussion around the robots has also raised concerns about machines occupying pavement space while waiting for orders. Repeated complaints focus on whether parked robots leave enough clearance for wheelchair users, pushchairs, and pedestrians navigating around street furniture.
Those accounts do not independently establish accessibility violations, but they show the weakness of assessing these deployments purely through collision statistics.
A robot that never touches a pedestrian can still inconvenience people if it remains stationary in a narrow pedestrian route. Route planning, waiting locations and time spent obstructing usable pavement are therefore meaningful performance measures alongside accident rates.
What happens next?
The immediate question is whether Marvin contests the disorderly conduct charge and whether subsequent proceedings clarify the limits of protest against autonomous delivery devices.
For Uber Eats and Avride, more useful public disclosures would address how they manage prolonged obstructions, when remote operators intervene, how they assess pedestrian access, and what circumstances warrant police involvement.
Pennsylvania already requires authorised operators to maintain liability insurance, with statutory minimum general liability coverage of $100,000 per incident. Operators must also disclose reportable accidents involving injury, death, or property damage within 24 hours. A stationary protest without a qualifying accident does not automatically trigger that accident-reporting requirement.
The broader deployment lesson is straightforward: a delivery robot can be legally authorised, technically capable and fully insured while still encountering situations that its navigation system cannot resolve.
Philadelphia’s next test is whether operators, officials and residents can establish workable procedures that preserve pedestrian access, allow lawful protest and prevent routine delivery interruptions from unnecessarily becoming police incidents.
