Missing the road for the trees
This updated Tesla safety report extends the legacy paper into a cinematic investigation built from cached NHTSA warehouse data. The focus is narrower and more concrete: where complaint narratives, recalls, investigations, and outside crash reporting converge on roadway departures, tree impacts, pole strikes, fire, and restraint-system concerns. Alshival.Ai's research suggests that Tesla's Full Self-Driving technology can sometimes lock onto fixed objects like trees and poles and drive straight toward them. This is the kind of situation lidar sensors are meant to mediate, which is why other manufacturers have included them in their autonomous stacks.
External media evidence and narrative overlap #
These are relevant news articles about crashes covered by this investigation.
Complaint text remains allegation data, while the cited articles are external context. The point of combining them is repeated pattern visibility, not treating publisher coverage as proof of root cause.
Testimony
Crash footage
Crash footage 2
Extended opening crash footage
Longer uploaded footage placed below the opening videos for a larger in-report preview without expanding to full-page width.
The rollout curve and why October 2021 still matters #
This section tracks how Tesla complaint patterns shifted across key FSD rollout and regulatory milestones.
The earliest FSD Beta release was still small, but it marks the beginning of the public narrative shift around Tesla's driver-assist ambitions. Complaint acceleration stays comparatively muted at this stage.
Tesla expanded FSD Beta to roughly 1,000 Safety Score drivers in early October 2021. This is the date that matters for the complaint-velocity frame, because the chart begins to show sharper month-to-month movement after the rollout broadens.
Forward-collision, braking, and speed-control language clusters hard in this window. The complaint peak in February 2022 remains the signal that motivated the original paper and still sits at the center of this update.
By late 2022, the user base was much larger. That makes pure volume harder to interpret in isolation, which is why this report adds tree-impact case files, recall timelines, and investigation overlays rather than relying on a single chart.
ODI's reduced-visibility probe and later traffic-safety behavior probe matter because they suggest a regulator response timeline that extends well beyond the initial release window. That broader regulatory arc is visible in the sections that follow.
Use this state to remove the timeline truncation and inspect the entire cached monthly series up to the latest data currently available.
Trees: persistent impact patterns in the warehouse #
The warehouse shows a multi-year tree-impact pattern: a 2022 crest, a 2025 resurgence, heavy Model 3 concentration, and repeated overlap with forward-collision, speed-control, steering, airbag, and fire language.
These are raw complaint counts, not fleet-normalized exposure rates. The comparison is most useful as an EV-peer framing device, not as a cross-industry market-share proxy.
Poles: a smaller pattern with notable assist overlap #
Pole and post strikes are lower-volume than the tree cases, but the warehouse still shows a meaningful adjacent pattern. Model Y appears disproportionately represented, and the 2025 increase matters because it arrives after the first rollout-era complaint surge. Alshival.Ai's research thesis is that some of these runs read like object-fixation failures, where the system may become confused by a pole and drive toward it rather than away from it.
Pole, post, curb, and fixed-object narratives overlap in plain-language complaints. This section keeps the category narrower than the tree section, but it still reflects user-submitted allegation text rather than a regulator finding.
Cybertruck overpass barrier crash
Fox Business reported on March 16, 2026 that dashcam footage showed a Cybertruck continue toward a Houston overpass barrier before impact, in a lawsuit tied to an August 2025 crash.
"Something terrifying happened, without warning, the vehicle attempted to drive straight off an overpass."
Justine Saint Amour, driver of the Tesla Cybertruck in the video
McAllen utility-pole crash
Fox Rio Grande Valley reported on January 28, 2026 that a blue Tesla crashed into a utility pole near the 3600 block of Auburn Avenue in McAllen, drawing local concern and a police investigation into what led to the impact.
Pole-impact crash footage 3
Additional YouTube footage included here for review alongside the other pole-impact examples in this section.
Buildings: wall and structure impacts in complaint narratives #
The warehouse also contains building- and wall-impact complaints, including parking-garage walls, restaurant walls, barrier walls, and other structure-strike narratives. This section tracks how often those complaints overlap with driver-assist, injury, airbag, and fire language.
These counts focus on complaints that describe impacts with walls or building-like structures. They remain raw complaint counts, not fleet-normalized crash rates or adjudicated findings.
Building-impact crash footage
Uploaded building-impact footage included here for direct review alongside the wall and structure complaint patterns summarized in this section.
Building-impact crash footage 2
Embedded YouTube footage included here for side-by-side review within the Buildings section.
Building-impact crash footage 3
Additional YouTube Shorts footage included here for direct review in the Buildings section.
Building-impact crash footage 4
Additional YouTube footage included here for review alongside the other building and wall impact examples.
Building-impact crash footage 5
Additional YouTube footage included here for review alongside the other building and wall impact examples.
Context: complaint composition, recalls, and investigations #
Tree cases are only one slice of the story. The surrounding context still matters: which complaint components dominated in Q1 2022, how recall activity moved, and whether investigation openings tracked the same periods.
-
-
-
-
Methodology, limits, and source notes #
The strongest reading of this report is not that every crash narrative proves an FSD defect. It is that the combined complaint, recall, investigation, and media record is strong enough to justify more detailed case review than Tesla's own summary statistics permit on their own. Throughout this report, Alshival.Ai stresses one recurring hypothesis rather than a final adjudicated finding: in some tree and pole cases, the vehicles appear to lock onto fixed objects and drive straight into them.
60 Minutes Australia report
Supplemental 60 Minutes Australia footage placed immediately before the Appendix for direct review alongside the report's methods and source notes.
Hazard case explorer #
This table expands beyond the curated case files above. It includes every Tesla complaint in the current cache tagged for trees, poles, buildings, or combinations of those hazards, with filterable date ranges, detected fatal or injury signals, and linked monthly trends.
Fatal and injury columns are text-detection signals from complaint narratives, not confirmed case counts.
The explorer reuses the same modal as the curated case sections above, so every row can open a detailed complaint view.
The chart shows tree, pole, and building filings against total Tesla complaints. In All Complaints mode, the table widens to the full Tesla ODI complaint set.
| Incident date | ODI | Hazard | Model | Components | Fatal | Injury | Assist | Summary |
|---|
