bytevyte
bytevyte
Language
ai-beats

Tesla FSD Radar Document Investigation: NHTSA Demands Internal "Radar Saves Us" File

Tesla FSD radar document investigation

Federal regulators have demanded access to a Tesla internal document titled "Radar Saves Us" as part of a rapidly escalating investigation into Full Self-Driving crashes during low-visibility conditions, a probe that now threatens a recall covering approximately 3.2 million vehicles. The National Highway Traffic Safety Administration's 24-part information request, sent July 2 and signed by Office of Defects Investigation Director Tanya Topka, is the most aggressive move yet in Engineering Analysis EA26002.

What the Document Reveals

NHTSA's demand specifically targets the "Radar Saves Us" document and all related internal communications, supporting materials, and any correspondence associated with it. Tesla had already submitted this document to the agency during the earlier preliminary investigation (PE24031-01), but the regulator is now seeking the full scope of associated records to understand how deeply the analysis ran through the organization.

The title of the file carries heavy implications. An internal Tesla document named "Radar Saves Us" almost certainly contains the company's own engineering analysis showing that radar, or a fusion of radar and vision, catches scenarios that a camera-only approach misses. If that analysis touches the exact failure modes identified in the nine crashes under investigation, it directly undercuts Tesla's decision to remove radar from its vehicles starting in 2021 when it introduced "Tesla Vision."

The document's existence suggests that Tesla's own engineers documented the safety rationale for radar-based sensing even as the company committed to a camera-only architecture. This apparent internal contradiction is the core of NHTSA's interest in the Tesla FSD radar document investigation. The agency is not simply checking whether radar is useful. It is asking whether Tesla knew radar was critical and removed it anyway.

The Shift from Radar to Vision Only

Tesla began phasing out radar hardware from the Model 3 and Model Y in early 2021, replacing it with a camera-only system the company called "Tesla Vision." The company argued that cameras alone could achieve sufficient perception accuracy and that radar introduced noise and complexity. Other automakers took a different path. Most Level 2 and Level 3 systems on the market today use some combination of cameras, radar, and sometimes lidar to provide redundant sensing across different environmental conditions.

The core engineering question in this probe is whether removing radar created a safety gap in conditions where cameras fail. Sun glare, heavy fog, and airborne dust are all scenarios that degrade optical sensors while leaving radar largely unaffected. Radar operates at radio frequencies that penetrate atmospheric scattering, meaning it can detect objects that cameras cannot in those specific failure modes identified in the crash record.

NHTSA is also examining a 2024 software change that reduced the prominence of the "FSD Degraded" alert from a red warning to a yellow indication with no accompanying audible chime. This change could have reduced driver awareness of system limitations precisely when they needed to intervene. If drivers received less noticeable warnings while the system struggled with conditions that radar would have handled, the combination creates a clear safety concern relevant to the Tesla FSD radar document investigation.

The Scale of the Engineering Analysis

Engineering Analysis EA26002 covers approximately 3.2 million Tesla vehicles in the United States that have operated with FSD engaged. The investigation links these vehicles to nine reported crashes in low-visibility conditions: sun glare, fog, and airborne dust. Among those incidents, one resulted in a fatality and another caused an injury.

These numbers are likely to grow. NHTSA stated in its demand that the documented incidents are conditions where the system may have failed to detect and respond appropriately to reduced roadway visibility. The agency is actively collecting additional incident reports from Tesla's own database, which the company is required to maintain under NHTSA's Standing General Order for autonomous vehicle crash reporting.

The engineering analysis phase is the final investigative step before NHTSA decides whether to close the probe or demand a recall. An upgrade from preliminary evaluation to engineering analysis in March signaled that the agency had already found enough evidence of a potential safety defect to warrant deeper scrutiny. The "Radar Saves Us" document request is the next logical step in the Tesla FSD radar document investigation: verifying whether Tesla's internal analysis aligns with or contradicts its public engineering choices.

Parallel Investigations and Growing Pressure

The low-visibility probe is not the only regulatory front Tesla faces. In October 2025, NHTSA opened Preliminary Evaluation PE25012 covering approximately 2.88 million vehicles after documented incidents of FSD running red lights and driving against traffic. That investigation had grown from 58 initial incidents to 80 by December 2025, with 14 crashes and 23 injuries reported. Both investigations now run in parallel, creating compounding regulatory risk for the company's FSD program.

Senators Edward Markey and Richard Blumenthal have also entered the fray. In June 2026, they sent a formal letter to NHTSA demanding an audit of Tesla's self-reported FSD safety data, citing concerns that the company uses a "5-second disengagement window" to reclassify emergency takeover crashes as human-caused. If NHTSA finds that Tesla has been underreporting incidents or misclassifying crash data, the regulatory response could extend beyond the current engineering analyses.

A separate probe into a fatal crash in Katy, Texas, where a Tesla on FSD struck a home at 73 mph and killed a 76-year-old resident, has drawn in both NHTSA and the National Transportation Safety Board. Investigators are pulling the vehicle's event data recorder and onboard logs to determine whether driver-assistance systems were engaged at the time of impact.

Financial Pressure and Compliance Deadlines

The July 2 information demand carries specific penalties for non-compliance. Tesla faces daily fines of $27,874 if it fails to produce the requested materials by the August 12 deadline, with a maximum penalty of $139 million. This structure gives the company limited room to delay or negotiate. Either Tesla provides the "Radar Saves Us" document and all related correspondence by mid-August, or it risks accumulating substantial fines while the investigation continues without its input.

The penalty scale signals that NHTSA is treating the Tesla FSD radar document investigation as a high priority. Daily fines at this level are designed to compel rapid compliance, and the agency has shown increasing willingness to use its enforcement tools against Tesla. In August 2025, NHTSA opened an investigation into whether Tesla had been reporting FSD and Autopilot crashes months after they occurred, violating the Standing General Order requirement to report within one or five days of receiving notice.

Why This Matters

The Tesla FSD radar document investigation is the most direct regulatory threat the company's autonomous driving program has faced. An engineering analysis that culminates in a recall order would affect millions of vehicles already on the road and force Tesla to either retrofit radar hardware or accept restrictions on FSD operation in low-visibility conditions. For decision-makers tracking the autonomous vehicle sector, this case establishes a precedent: regulators are now willing to subpoena internal engineering documents to test whether a company's safety claims match its own technical analysis. The outcome will influence not only Tesla's FSD roadmap but the broader regulatory framework for camera-only autonomous systems across the industry.

Photo by Brecht Corbeel on Unsplash

✔Human Verified


Researched and cross-referenced against primary sources by the Bytevyte editorial team.