FirstAlerts
Plane CrashesVersion 3

Tesla Model Y crash in Batavia, Illinois, under investigation; driver-assist system engaged

A Tesla Model Y collided with two vehicles in Batavia, Illinois, on a date reported as either March 25, 2026, or December 7, 2025; the driver-assist system was engaged, and the crash remains under investigation.

By AI ReporterFirst reported Sep 1, 2026, 10:52 a.m. ETUpdated Sep 9, 2026, 10:23 a.m. ET
A crash involving a Tesla Model Y in , remains under investigation, according to Electrek and Free Republic. The date of the crash is reported as either March 25, 2026, or December 7, 2025, and the time as either approximately or , according to conflicting reports from Electrek and Free Republic. One person was injured, Electrek reported. The Batavia Police Department said the crash "remains under investigation and is currently under review by the Kane County State's Attorney's Office," Electrek reported. A county prosecutor is weighing whether anyone should be charged, Free Republic reported. Tesla verified that its driver-assist system was engaged during the crash, Electrek reported. Tesla's report to NHTSA states the Full Self-Driving system was engaged at the time of the crash. The crash occurred during an unprotected left turn, a maneuver that basic Autopilot cannot perform. Tesla redacted the crash narrative, software version, and road operating area as confidential business information. The cause of the crash has not been determined. The investigation is being conducted by the Batavia Police Department, the Kane County State's Attorney's Office, and the NHTSA.

Was this report accurate and useful?

Reference data

From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.

Terrain elevation
725 ft
Nearest aerodrome
5.2 miles SW of Dupage Airport (KDPA/DPA)

Sources

Revision history

  1. Version 39 Sept 2026, 14:23current

    Updated to reflect conflicting reports on date, time, and location; added attribution for conflicting reports.

  2. Version 24 Sept 2026, 05:36

    Corrected location to Illinois; added detail on FSD engagement and investigation status.

  3. Version 11 Sept 2026, 15:18

    First published.

How we work

This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.

Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.

Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.

None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.