A Tesla Clipped a Curb in Redmond. The Suspension Wasn't the Real Damage.
What happened
A bent suspension component and a scraped underbody, that's the entire physical toll from this incident. On August 1, 2017, a Tesla sedan running Autopilot in Redmond, Washington failed to hold its lane and rolled straight over a raised yellow median divider. Read as a repair bill, it barely registers. Read as a test of what the system understood about the road in front of it, it's a failure worth taking seriously.
Lane-keeping systems like Autopilot depend on reading painted lines, curbs, and road edges to figure out where a car belongs. A dividing curb is about as unambiguous a boundary as pavement offers. It's raised, colored, and physically present, the kind of feature a human driver registers without thinking. The car drove over it anyway, which means the perception or control logic misjudged something basic about the lane geometry at that spot, not some rare edge case buried in bad weather or faded markings.
The stakes here aren't about one bent axle. They're about what happens when the same failure mode shows up somewhere less forgiving: a curb at highway speed, a median with oncoming traffic on the other side, a moment when the driver has stopped paying attention because the last fifty miles went fine. Minor incidents like this one are how blind spots in a driving system get discovered, and they only stay minor if someone is watching closely enough to catch the pattern before it repeats somewhere worse.
That's the part missing from the public account of this event. There's no indication of what Autopilot's sensors registered in the moments before the car left its lane, what confidence level the system assigned to its own positioning, or whether the failure was logged and reviewed as anything more than a warranty claim. A vehicle that takes over steering also takes on responsibility for justifying that override after the fact.
Reported impact
- Affected parties
- Not publicly disclosed
- Harm type
- Not publicly disclosed
- Scale
- Not publicly disclosed
- Financial impact
- Not publicly disclosed
- Regulatory action
- Not publicly disclosed
Classification
Relevant governance controls
Governance control mapping is not available for this record.
- No controls mapped
Not publicly disclosed
Control mapping is analytical. It does not state that any control would have prevented the incident.
Sources and evidence
This record was researched and written by the Index. The event is also catalogued in the following database, which is listed for cross-reference.