Tesla filed 236 driver-assistance crash reports with the US National Highway Traffic Safety Administration for July 2026. That is the most the company has ever submitted for a single month, and it beats a record that was only a month old.
Four of those crashes killed someone. In all four, Tesla's own submission records the automation as engaged. In none of them did the public learn that from the police report, the local news, or Tesla.
The monthly trend
Under NHTSA's Standing General Order, carmakers must report crashes in which an advanced driver-assistance system was active within roughly 30 seconds of impact and the crash crossed a severity threshold — an airbag firing, a tow-away, an injury, a death, or a struck pedestrian or cyclist. Tesla's monthly totals have climbed all year:
| Month (2026) | Reports filed |
|---|---|
| March | 135 |
| May | 207 |
| June | 209 |
| July | 236 |
May's 207 was reported at the time as a record. June passed it. July passed June.
A rising count is not by itself a rising crash rate — more cars running FSD for more miles will generate more reports. What the filings do not let you do is check that, because the fields that would tell you how the system was being used are the fields Tesla removes.
The four fatal crashes
| Date | Place | What the filing records |
|---|---|---|
| 12 July | Upper Marlboro, Maryland | A Model 3 turning left failed to yield to a Harley-Davidson. Three died: the motorcyclist Matthew Vowell, 48, his passenger Krystal Vowell, 47, and Tesla passenger Adriana Maxwell, 22. Engaged at 20 mph. |
| 15 July | San Mateo, California | A 2016 Model S left the road, hit a light pole and caught fire, killing the driver. Engaged at 52 mph. |
| 20 July | Ashby, Minnesota | On Interstate 94 a westbound Ford and an eastbound Tesla collided; a third vehicle then struck them. Tesla driver Harold Ennulat, 73, and the 24-year-old Ford driver died. Engaged at 50 mph. |
| 22 July | Ione, California | A 2026 Model Y crossed into the southbound lane, sideswiped a Honda and hit a Cadillac head-on. Driver Shelby Waldie, 25, died; a two-year-old was hospitalised. Engaged at 54 mph. |
Add those up and seven people are dead. Tesla's filings record four fatalities, because the count follows the reporting vehicle rather than the crash.
What Tesla removes, and what others do not
Tesla redacts three fields in each report: the crash narrative, the software version, and whether the road was inside the system's approved operating area. It does this on 100% of its filings. General Motors, which files the same way for Super Cruise, redacts none of its narratives.
Without the version field there is no way to tell whether a crash involved Autopilot, an old FSD build, or the current one. Without the operating-area field there is no way to tell whether the car was somewhere the system was designed to work. Tesla is already under NHTSA investigation over how it reports.
TeslAnt has matched several of these redacted entries to named crashes before, including a 4 mph stop-sign collision in New Jersey and a 104 mph crash in Clute, Texas.
Why this lands in Europe now
This is US data about US roads, and it arrives in the month Europe decides what to do with the same software. FSD (Supervised) is recognised in six member states, Tesla is shipping FSD 14.2.2.6 to European cars, and bloc-wide recognition goes to a vote in the Technical Committee on Motor Vehicles on 6 October — the vote that sits behind everything Tesla has said about bringing more autonomy to Europe.
The July file is the largest single-month body of evidence that exists about how this software behaves in the wild. It is also, by Tesla's own redactions, the least readable.