A two-vehicle collision involving a Waymo vehicle in Los Angeles sent two people to the hospital early Sunday, according to local reports. The crash occurred at about 5:45 a.m. near Venice Boulevard and Toberman Street in the Pico-Union area, close to downtown Los Angeles. Several other people were evaluated at the scene, although early reports differed on the exact number and severity of injuries.

The most important fact is also the least dramatic: investigators had not announced a final cause. The Los Angeles Police Department was still examining the sequence of events, and the available public accounts did not establish legal fault. A headline saying a crash “involved” Waymo describes presence, not responsibility.

What Waymo says happened

Waymo told the Los Angeles Times that its vehicle was traveling east on Venice Boulevard at 27 mph. According to the company’s account, a blue sedan traveling an estimated 47 to 50 mph struck a pedestrian outside a crosswalk, swerved into the opposite lane and then hit the Waymo. That description is material, but it remains Waymo’s account unless and until police, video evidence or a formal report independently confirms it.

“The safety of our riders and other road users is our top priority.”

The company said it was coordinating with first responders. Local television footage and initial emergency information showed a serious scene, but early dispatch descriptions can change as responders sort out who was in which vehicle and how injuries occurred. ABC7, NBC Los Angeles, KTLA and the Los Angeles Times reported different hospital totals at various points, another reason to avoid presenting the first number as a settled final count.

Why it matters

Robotaxi incidents draw unusual attention because every collision becomes a test of public trust in automation. That attention is legitimate. Driverless systems operate around people who did not choose the technology, and companies should provide clear timelines, video where legally possible and standardized crash reports. But scrutiny should work in both directions: it should expose system failures without assuming that an autonomous vehicle caused every collision in which it appears.

Waymo opened its Los Angeles service to the public in 2024 and now operates across complex streets shared with pedestrians, cyclists, emergency responders and human-driven vehicles. Its vehicles are designed to stop or pull over when the system determines that is safest, and the company uses simulation and collision-avoidance testing to evaluate rare hazards. None of those programs determines the facts of this particular crash.

The incident also illustrates why raw crash totals are easy to misuse. A reportable event can include a stationary autonomous vehicle being struck by another road user, as well as a collision initiated by the automated system. Injury severity, exposure miles, road type, operating mode and fault all matter. Without those details, a single count can support whatever conclusion a reader already prefers.

The same standard should apply whether the first account appears favorable or unfavorable to Waymo.

What comes next

The useful next documents are the police collision report and, if required, a federal automated-driving crash filing. Video from the Waymo and nearby cameras could clarify speeds, signal phases, pedestrian movement and evasive action. Until then, the responsible conclusion is narrow: a serious Los Angeles collision involved a Waymo vehicle, people were hurt, and the publicly available evidence does not yet justify a final verdict about fault or system performance.

Related EVBASE reading

Tesla Cybercab Moves From Diner Display to Fleet Infrastructure

EVBASE Tesla and Robotaxi news hub

Sources

KTLA—Waymo-involved Los Angeles collision

Los Angeles Times—Pico-Union collision report and Waymo account

NBC Los Angeles—early responder account

Waymo—collision avoidance testing

Waymo—Los Angeles public service launch