John Roach, Esq. | October 24, 2026 | California Law \ Car Accidents
Tesla’s “Full Self-Driving” Killed a Pedestrian on I-80 in Vallejo — Who’s Liable?
Early Thursday morning, a Tesla running on “Full Self-Driving” struck and killed a 71-year-old man crossing I-80 in Vallejo. The driver wasn’t drunk. He wasn’t texting. He wasn’t speeding beyond the limit. By every traditional measure, he did nothing most of us would call reckless — he was simply in the car while a computer did the driving.
That’s exactly why this crash matters. A pedestrian struck on a freeway at 2:30 in the morning used to have a fairly simple legal answer: either the driver saw him in time, or didn’t, and liability followed from there. Now there’s a third party in the car that nobody fully understands yet — and the law, and the engineering, are still catching up to what should happen when it doesn’t react fast enough.
The Crash, By the Numbers
- When: About 2:35 a.m. Thursday, October 22, 2026.
- Where: Westbound I-80 at the I-780 interchange in Vallejo — one of the busier freeway junctions in the North Bay, even at that hour.
- The pedestrian: A 71-year-old Vallejo man, since identified by the Solano County Coroner’s Office. He entered the freeway from the right shoulder, moving toward the center divide. Investigators haven’t said why he was on foot on the freeway — there’s no mention of a disabled car, an emergency, or any other explanation.
- The driver: A 26-year-old San Francisco man, who stayed at the scene and told CHP that “Full Self-Driving” was engaged. He has not been cited.
- The car: CHP reviewed the Tesla’s own dashcam footage. It shows the car traveling about 70 mph in the #2 lane — a middle lane, not the shoulder lane — then braking and steering left in the moments before impact. The right front corner of the car still struck the man.
- Aftermath: At least one more vehicle struck him after the Tesla did. Only the Tesla’s driver remained at the scene.
- Where it stands legally: No charges have been filed. CHP says Solano County’s DA could still charge the driver if the investigation finds he was responsible in some way.
When the Law Expects a Pedestrian on a Freeway
California law doesn’t pretend freeways are open to foot traffic. Vehicle Code section 21960 lets Caltrans and local agencies bar pedestrians from freeways by posting signs, and it carves out one exception no sign can override: the driver or passengers of a disabled vehicle may walk to the nearest exit. The law recognizes exactly one routine scenario where a pedestrian is expected on a freeway, and it isn’t a shortcut or a late-night walk — it’s a disabled car.
That scenario has teeth on the driver’s side too. As of January 1, 2026, Vehicle Code section 21809 requires a driver approaching any stationary vehicle displaying hazard lights or another warning device — cones, flares — to move out of the adjacent lane if it’s safe to do so, and to slow to a safe speed if it isn’t. The statute is written with breakdowns in mind; it doesn’t speak to a lone pedestrian with no stopped car, which is what investigators describe here.
None of that means a pedestrian who’s on a freeway unlawfully has no legal protection, or that a driver’s duty disappears the moment someone is somewhere they “shouldn’t” be. The California Supreme Court’s 2011 decision in Cabral v. Ralphs Grocery Co. is instructive, even though it isn’t a pedestrian case. A Ralphs truck driver stopped on the dirt shoulder of I-10, in an area marked for emergency parking only, to have a snack. A pickup driver drifted off the freeway, hit the parked truck, and was killed. The jury put 90% of the fault on the pickup driver and 10% on Ralphs. The Court of Appeal threw out the verdict, holding Ralphs owed no duty. The Supreme Court reversed: the ordinary duty of care applied, and a court can’t erase it just because the circumstances were unusual. Whether the truck driver acted reasonably in those circumstances was a question for the jury.
The takeaway translates directly to a case like this one: a pedestrian’s unlawful presence on a freeway doesn’t automatically close the door on liability for the driver who hits them. It becomes a comparative-negligence factor — a jury can, and often does, assign some percentage of fault to a pedestrian who was somewhere they legally shouldn’t have been — but California law has never treated that presence alone as a complete bar to recovery once a driver had some real opportunity to see and react to the hazard ahead. The reasonableness of both parties’ conduct, not just who had the legal right to be there, is what a jury ultimately weighs.
That’s the framework this case will likely be measured against as more facts become public: not simply whether he was allowed to be there, but what either side could reasonably have done once the danger became apparent.
Why “React Faster” Isn’t the Whole Answer
A sober, attentive human driver still needs roughly 1.5 seconds just to notice a hazard and begin reacting to it — before the car even starts slowing down. At 70 mph, a car covers about 100 feet per second, so that perception-reaction lag alone eats up more than 150 feet before the brakes are touched at all. Add the distance it then takes to actually stop, and a human driver’s full stopping distance at that speed commonly runs 300–400 feet.
An automated system is supposed to erase most of that first number. There’s no eye-to-brain-to-foot chain — a sensor detects something, software decides what to do, and the car acts, in a fraction of a second. On paper, that should hand Tesla’s system a real head start over any human driver, measured in both time and distance.
But that advantage only matters if two things both held true here, and neither is confirmed yet: that the car’s cameras actually picked up the pedestrian while he was still on the shoulder, rather than only once he’d stepped into the lane; and that the maneuver the system chose was capable of clearing him given the road, the speed, and the traffic around it. CHP’s account — braking and steering left, but still catching him with the right front corner — is consistent with a system that reacted, just not early or completely enough. Tesla’s own logs (speed, steering input, braking input, and sensor-detection timestamps, all time-stamped to fractions of a second) are what will actually answer that, not anyone’s guess after the fact.
It’s also worth taking seriously why the car didn’t just slam on the brakes. The Tesla was in the #2 lane — a middle lane — at 70 mph, at night, almost certainly with other vehicles nearby. A sudden, full emergency stop in a middle freeway lane at highway speed is its own hazard: a trailing or adjacent car with less following distance, or less reaction time of its own, can turn one crash into a multi-vehicle pileup. Braking while steering left — rather than stopping dead — may reflect exactly that tradeoff: trying to avoid the pedestrian without creating a worse crash for everyone else on the freeway at 2:35 in the morning. If so, this isn’t a case of the system failing to brake hard enough; it’s a case of there being no clean, risk-free option once he was in the roadway, which is a very different legal question.
That’s exactly the kind of judgment call accident-reconstruction and human-factors experts get hired to evaluate: given the real distance, speed, and surrounding traffic the instant the pedestrian became visible, was there any available maneuver that avoided him without a meaningfully worse outcome for others? And separately — did the car see him soon enough in the first place? Tesla’s “Full Self-Driving” relies mainly on cameras rather than lidar, the laser-ranging sensors some competitors use for more reliable depth-sensing at night. If a camera-based system has a shorter real-world detection range for a person near a dark freeway’s edge, that’s a design question distinct from reaction speed — the car may have responded appropriately to what it saw, and still not have seen him soon enough to matter.
This Isn’t an Isolated Incident
The Vallejo crash lands in the middle of a live national fight over how much to trust Tesla’s “Full Self-Driving.” The National Highway Traffic Safety Administration has an open investigation covering 58 separate FSD-related incident reports, including cars running red lights and veering into oncoming traffic. Two U.S. senators have publicly criticized NHTSA, arguing the agency has gone too easy on Tesla. And earlier this year, Tesla settled a wrongful-death lawsuit over a 2023 FSD-related pedestrian crash in Arizona.
California law is also unambiguous on one point: a human driver must stay attentive and ready to take control the entire time FSD is active. That’s why CHP’s initial scrutiny falls on the driver, not Tesla — legally, he was still “driving.” But that requirement cuts both ways in a civil case. If a driver can be held to the standard of staying alert and ready to intervene at all times, a manufacturer marketing a system as “Full Self-Driving” can reasonably be held to the standard of the system actually performing as advertised when a human doesn’t intervene in time.
What This Means If You’re Hurt by a Self-Driving Car
- “The car was driving itself” is not a dead end. It usually means there are two potential paths to compensation instead of one: driver negligence, and a product-liability claim against the manufacturer for how the automated system performed. Both can be pursued at the same time.
- The data disappears if nobody asks for it. Modern vehicles log speed, braking, steering input, and sensor activity down to the second. That data can be overwritten or become harder to obtain the longer a case sits. An attorney’s first move in a case like this is almost always a preservation letter demanding the manufacturer and the driver’s insurer hold onto it.
- Expect two insurers to point at each other. The driver’s auto insurer may argue the system should have handled it; the manufacturer may argue the driver was supposed to be in control. That standoff is exactly why these cases benefit from someone who can build both theories in parallel, rather than waiting to see which side blinks first.
- An expert, not a guess, decides what was “avoidable.” Whether a crash like this could have been prevented isn’t a question for a comment-section debate — it takes an accident reconstructionist working from the vehicle’s actual data to say what the car could see, when, and what options it realistically had.
The Bottom Line
The technology is new. The legal questions underneath it aren’t. Who had control, who should have reacted, and who pays when something goes wrong are questions personal injury lawyers have worked through for decades — autonomous and driver-assist features just add new parties and new data to the analysis. As more cars on Bay Area freeways drive themselves, at least part of the time, cases like this one are only going to become more common.
If you or someone you love has been hurt in a crash involving a Tesla or another vehicle using driver-assist or self-driving features, contact the Law Office of John J. Roach for a free consultation. I know how to pursue both the driver and the manufacturer, and how to make sure the data that actually proves what happened doesn’t disappear before anyone asks for it.
Sources: SFist, ABC7 News, CBS News Bay Area, Washington Times