Federal Regulators Examine Tesla Crash After Driver Says He Slept With FSD Engaged

Federal safety regulators are gathering information about a California crash in which a Tesla tore through a closed section of Interstate 80 and hit an occupied Highway Patrol car.

The driver told investigators he had been asleep and that Tesla’s Full Self-Driving system was operating.

That claim is now part of an active investigation. It is not yet a technical finding that FSD was engaged at impact or that the software caused the crash.

What is already confirmed is bad enough: two officers were seriously injured while sitting inside a patrol car at a crash scene marked by flares, cones and flashing emergency lights.

CHP released several angles of the impact and delivered the warning in plain language:

The collision happened late Tuesday on eastbound I-80 west of Air Base Parkway in Fairfield, roughly 50 miles northeast of San Francisco.

Officers had closed four lanes while they handled an earlier fatal crash. Traffic was being moved into the slow lane.

The Tesla instead entered the closed lanes at freeway speed and struck a Dodge Charger patrol car with two officers inside, according to CHP.

CBS Sacramento reports that the closure was protected by flares and cones, with multiple emergency vehicles displaying flashing lights. The driver was identified only as a 22-year-old man from Sacramento, and investigators said he claimed both that he had been asleep and that the Tesla was operating in Full Self-Driving mode.

Both officers were taken to a hospital with serious injuries and have since been released. The Tesla driver suffered minor injuries.

The impact was captured by dashcams in the struck patrol car and another vehicle at the scene. CBS reports that both the fatal crash and the later Tesla collision remain under investigation.

CHP stressed that driver-assistance technology does not relieve the person behind the wheel of the responsibility to operate the vehicle safely.

The officers were working an especially grim scene. About an hour earlier, a 19-year-old San Pablo man had lost control of a Honda Civic and was hit by a Chevrolet Tahoe.

He later died.

That context makes the second crash more than another argument about what an assisted-driving feature can or cannot do. People were already dealing with a death on the highway, and two officers were nearly added to it.

Now the federal government wants the vehicle data and the rest of the evidence.

NBC News reports that the National Highway Traffic Safety Administration said it was aware of the crash and had contacted both Tesla and CHP for additional information. CHP said its own investigation remained active, while the Solano County district attorney had not yet received a report on the case.

Tesla did not immediately respond to the outlet’s request for comment. No public charging decision has been announced, and CHP has not released the driver’s name.

NBC also placed the crash inside a larger driver-monitoring problem. Tesla vehicles use an in-cabin camera to watch eye and head movement, and the system is supposed to warn drivers when it detects inattention.

The open question is what the car recorded before impact—and whether the driver’s account survives comparison with those logs.

That evidence matters because the driver’s statement alone cannot establish what the software was doing. Tesla can determine whether FSD was engaged, whether it issued attention warnings, whether the driver touched a pedal or steering control, and whether the feature disengaged before the collision.

There are two separate accountability questions here.

The first is brutally simple: a driver cannot go to sleep behind the wheel of a supervised system. If investigators confirm that admission, no product name erases the driver’s responsibility.

The second question is technical and just as important. If FSD remained engaged, why did the vehicle reportedly continue through a flare-and-cone pattern toward an occupied car surrounded by emergency lights?

Tesla describes Full Self-Driving as a supervised driver-assistance feature that can handle steering, acceleration, braking and route decisions under a human driver’s supervision. The company says the person behind the wheel must remain attentive and be ready to take control.

Tesla’s own description is explicit that the feature does not make the vehicle autonomous. That distinction matters here because the driver’s reported decision to sleep would violate the basic operating condition of the product, even before investigators determine how the software responded to the closed lanes, cones, flares and emergency lights.

That warning is clear. It also does not end the inquiry into how a safety system performed during a predictable highway hazard.

NHTSA was already examining other FSD crashes before the Fairfield collision.

An official NHTSA investigation document identifies four reported crashes in reduced-visibility conditions with FSD engaged, including one in which a pedestrian was killed and another involving an injury. That inquiry covers how the system detects and responds to conditions such as glare, fog and airborne dust.

The Fairfield scene is different. The public record describes a nighttime highway closure filled with deliberate warning devices, not fog or dust, and NHTSA has not publicly added this crash to that existing case.

Still, the underlying question is familiar: whether the system and its driver-monitoring controls keep a human meaningfully engaged when software is doing most of the driving.

That question cannot be answered from a viral clip, a driver’s excuse or a reflexive defense of Tesla.

It will be answered by the car’s logs, the patrol-car video, the crash reconstruction and the communications now moving among NHTSA, Tesla and CHP.

Until those records are available, the responsible conclusion is narrow.

Two officers were hurt, and a driver says he was asleep. A Tesla hit a clearly marked emergency scene.

Federal regulators have started asking why.

 

Join the conversation!

Please share your thoughts about this article below. We value your opinions, and would love to see you add to the discussion!

We Talk Tesla