Technology

Waymo Robotaxi Pulled Over and Alerted Police to Riders With a Ghost Gun

Martin HollowayPublished 6d ago3 min readBased on 3 sources
Reading level
Waymo Robotaxi Pulled Over and Alerted Police to Riders With a Ghost Gun
source:waymo.com

Two juveniles were arrested in San Francisco after the Waymo robotaxi they were riding in pulled over and alerted police.

Officers recovered a loaded AR-style ghost gun from the riders. A ghost gun is an untraceable firearm, often assembled from parts without a serial number, and AR-style refers to a rifle design modeled on the AR type. The juveniles were taken to juvenile hall, according to reporting published Sept. 13 The Verge.

Waymo confirmed to the Los Angeles Times that the vehicle involved was one of its vehicles. A company spokesperson said a "violation of our terms of service involving a firearm" was detected, after which the car pulled over and alerted authorities.

The incident follows an earlier contact between Waymo and police in the region. In July, Waymo contacted the San Mateo Police Department regarding two teens drinking alcohol and firing toy guns inside a car, as reported Sept. 12 Los Angeles Times.

Waymo directs law enforcement, first responders, and those reporting a collision to call 1 (877) 503-0840 Waymo. In this case, the alert came from the vehicle operation itself.

The broader context here is where enforcement happens when there is no driver. In a human-driven taxi or rideshare, detection and response depend on driver judgment. The driver sees, decides, stops, and calls. In a driverless system, that chain is split across automated detection by in-car sensors, review by remote staff, and a programmed stop plus a message to police. This incident puts that whole chain in public view. The car becomes both the place of the violation and the reporting party.

Looking at what this means for fleet operators, the questions are narrower than the headlines. How is a firearms violation defined in sensor readings and company procedures. What confidence threshold, or level of certainty, triggers a pull-over. Where does the vehicle stop once it decides to stop. Who receives the alert, with what location and cabin-state data, and under what rules for keeping and sharing that data. None of those details are in the confirmed record here. For technology professionals building or working with autonomous systems, those are the control points that decide whether this kind of stop is reliable, reviewable, and legally sound.

In my view, the juvenile aspect will shape company and regulatory scrutiny more than the autonomy aspect. Unaccompanied minors in robotaxis combine access control, or who can order and board, identity verification, and rules enforcement, in a setting with no onboard authority figure. The July toy-gun report and the September ghost-gun arrest, taken together, point to a problem operators will need to address directly. Worth flagging as a design problem rather than only a policing problem. If driverless networks are to scale as public-facing transport, they need clear policies for young riders, prohibited items, and in-ride violations that hold up without a driver to intervene.

Over the longer term, technology of this kind tends to improve when responsibilities are made explicit. Automated pull-over and direct notification leave less doubt about what happens after detection. That clarity helps riders, police, and operators alike. The task now is to document the logic behind those actions well enough that trust does not rest on a single arrest.