Issaquah police say a Tesla operating with Full Self-Driving (Supervised) engaged abruptly crossed into opposing traffic on Newport Way NW on Wednesday, striking a Cadillac Escalade hard enough to shear off roughly the rear third of the Tesla. Despite the dramatic damage, police reported no injuries.
KOMO News first reported the crash, which occurred in the 500 block of Newport Way NW. Officers arriving at the scene found the Tesla separated near its rear section; investigators later learned the driver had FSD engaged when the vehicle swerved into the oncoming lane, according to the department.
Police used the familiar “Full Self-Driving Mode” wording, but Tesla’s current product name is Full Self-Driving (Supervised). Tesla explicitly says the system is not autonomous and requires the driver to continuously monitor the road and take control when necessary. Federal safety guidance makes the same point: consumer driver-assistance systems do not transfer legal driving responsibility from the person behind the wheel.
That distinction matters after any crash involving automation. A vehicle being engaged in FSD at the time of impact establishes neither that the software caused the collision nor that a driver intervention did or did not occur in the seconds before it. The Issaquah report, as described by KOMO, identifies the reported lane departure but does not provide the vehicle’s software version, telemetry, speed, braking data, or whether the driver attempted to override the system.
For Tesla owners, the immediate takeaway is not to treat an engaged blue route line or “Self-Driving” indicator as permission to disengage from driving. Keep hands ready, watch for unexpected lane choices or steering inputs, and intervene early rather than waiting for the system to correct itself.
Issaquah police reiterated that responsibility following the crash. The next question is whether the agency’s investigation produces vehicle data that clarifies why the Tesla crossed the centerline—and whether that information is made public.
The important distinction is “Supervised”
Police used the familiar “Full Self-Driving Mode” wording, but Tesla’s current product name is Full Self-Driving (Supervised). Tesla explicitly says the system is not autonomous and requires the driver to continuously monitor the road and take control when necessary. Federal safety guidance makes the same point: consumer driver-assistance systems do not transfer legal driving responsibility from the person behind the wheel.That distinction matters after any crash involving automation. A vehicle being engaged in FSD at the time of impact establishes neither that the software caused the collision nor that a driver intervention did or did not occur in the seconds before it. The Issaquah report, as described by KOMO, identifies the reported lane departure but does not provide the vehicle’s software version, telemetry, speed, braking data, or whether the driver attempted to override the system.
A serious reminder for assisted-driving users
The severity of the vehicle damage makes the absence of reported injuries fortunate. It also illustrates the practical limit of branding that can sound more capable than the system’s legal and operational status: FSD (Supervised) can steer, accelerate, brake, make turns and change lanes, but the driver remains the responsible operator.For Tesla owners, the immediate takeaway is not to treat an engaged blue route line or “Self-Driving” indicator as permission to disengage from driving. Keep hands ready, watch for unexpected lane choices or steering inputs, and intervene early rather than waiting for the system to correct itself.
Issaquah police reiterated that responsibility following the crash. The next question is whether the agency’s investigation produces vehicle data that clarifies why the Tesla crossed the centerline—and whether that information is made public.
References
- Primary source: KOMO
Published: 2026-07-31T19:15:42+00:00
Loading…
komonews.com - Related coverage: arstechnica.com
Loading…
arstechnica.com - Related coverage: kiro7.com
Loading…
www.kiro7.com - Related coverage: mynorthwest.com
Loading…
mynorthwest.com - Related coverage: washingtonpost.com
Loading…
www.washingtonpost.com - Related coverage: techcrunch.com
Loading…
techcrunch.com