A Tesla driver crashed into a residential swimming pool and home on June 22, 2026, reigniting a familiar debate: what information should Tesla disclose when its Full Self-Driving system is involved in an accident?

Public reporting has not confirmed the crash's specifics—whether FSD (Supervised) was actively engaged at impact, the driver's condition, or even the exact location. But the incident exposes a structural tension in how Tesla collects and shares vehicle data, one that matters for regulators, insurers, and anyone trying to assess whether self-driving cars are ready for residential streets.

Two Data Systems, Two Different Purposes

Tesla operates two separate telemetry systems that often get confused in post-crash reporting. The first is the Full Self-Driving (Supervised) Vehicle Safety Report, published quarterly with aggregate, anonymized data: miles driven per quarter, road classifications (highway, city, residential), and whether FSD or a human held active control. Think of it as a fleet-wide report card. It answers big-picture questions—is FSD safer overall?—but cannot reconstruct what happened in any single crash.

The second is the Event Data Recorder (EDR), a forensic layer built into Tesla vehicles that captures pre- and post-impact data in crash or near-crash situations: airbag deployment, obstacle detection events, vehicle dynamics, and crucially, whether FSD was engaged in the seconds before impact. EDRs are what investigators use to understand individual events.

The distinction matters. The FSD Safety Report cannot tell you whether FSD was active on the street where this crash occurred. The EDR can.

What Regulators Can Access

Under federal EDR regulations (49 CFR Part 563), law enforcement, the vehicle owner, and anyone with a court order can request standardized data from most passenger vehicles. Tesla's EDR records more sensor data than federal law requires, which can include FSD engagement status. That granularity has been crucial in past National Highway Traffic Safety Administration (NHTSA) investigations into Tesla's driver-assistance systems.

If FSD (Supervised)—which Tesla classifies as a Level 2 system—was active at any point in the sequence leading to this crash, Tesla faces a mandatory reporting obligation to NHTSA. That requirement exists independent of any civil or criminal case. The catch is timing and access: the most detailed data lives inside Tesla's proprietary systems and reaches regulators and outside investigators only through formal legal channels or the vehicle owner's consent. That constraint can slow NHTSA preliminary investigations.

Why the Public Safety Report Has Limits

Tesla's published methodology compares its FSD miles-per-crash rates against national averages from NHTSA's Fatality Analysis Reporting System. The comparison offers useful directional information, but it carries a known bias: FSD miles skew toward favorable driving conditions—experienced users, well-mapped highways, good weather—while national crash averages include all contexts. A controlled, apples-to-apples comparison between FSD safety and human driving has not yet been published by Tesla or its critics.

More fundamentally, aggregate safety data cannot explain specific crashes. A vehicle might log zero FSD-active miles in the moments before impact if the driver or the system itself disengaged before the final collision sequence. Whether that happened here is the question EDR telemetry would answer, not fleet-level aggregates.

For policymakers and the public debate about self-driving cars, this creates an asymmetry. Regulators and insurers rely on event-level data to investigate individual crashes and assign liability. But the only transparent, regularly published data available to the public is fleet-level aggregate reporting. Tesla has committed to no independent disclosure of crash-specific telemetry in real time.

The gap between these two information tiers—what investigators can access and what the public can see—is where the unresolved policy work on autonomous vehicle accountability still sits. Each incident tends to sharpen legislative focus on the question, but historically, concrete disclosure requirements have been slow to materialize.