At about 8:31 on the morning of Saturday 22 August 2026, a Tesla travelling south on Route 55 in Vineland, New Jersey, left the left side of the road near milepost 34.6, crossed the grass median, struck a tree and continued into the northbound lanes, where it hit a Chevrolet SUV head-on. The SUV's driver, 68-year-old Phillip Eastman of Springfield, Pennsylvania, was killed. The Tesla's driver and a passenger in the Chevrolet were taken to hospital with moderate injuries, the New Jersey State Police said. No charges have been filed and the investigation is open.
Local coverage told it as a driver who lost control. Eastman had just been sworn in to the Springfield school board and had coached youth and high-school ice hockey for close to three decades, so his death was widely reported around Philadelphia. None of that reporting mentioned driver assistance.
Tesla's own filing with the US regulator does.
What the filing says
Under the National Highway Traffic Safety Administration's Standing General Order, a manufacturer must report any crash in which a Level 2 driver-assistance system was engaged within 30 seconds of impact and someone died. TeslAnt read the entry in NHTSA's published file.
| Field | What Tesla filed |
|---|---|
| Vehicle | 2021 Model Y |
| Engagement status | Verified Engaged |
| Incident time | 12:29 UTC, about 8:29 local |
| Pre-crash speed | 37 mph (60 km/h) |
| Injury severity | Fatality |
| Roadway | Highway / Freeway |
| How Tesla learned of it | Media |
| Data Tesla holds | Telematics only |
| Narrative, software version, approved operating area | Redacted |
"Verified Engaged" means Tesla confirmed through its own telematics that Autopilot or FSD was active in the window before impact, rather than a driver claiming so afterwards. The report names the New Jersey State Police as the investigating agency and says Tesla learned of the crash from the media, consistent with the police not knowing the system was on.
The matching is Electrek's, from its ongoing investigation pairing redacted federal entries with reported crashes. The record is unredacted on the city, the state, the vehicle, the fatality and the month, and the logged time converts to within two minutes of the police time.
What it does not prove
Three cautions apply. "Engaged within 30 seconds" is the reporting trigger, not proof the software was steering when the car crossed the median; the driver may have been overriding it. Tesla redacted the version field, so there is no telling whether this was basic Autopilot or FSD. And 37 mph is low for a freeway, which suggests a single telematics snapshot from somewhere in the pre-crash window rather than the speed at which the car left the road. Tesla also ticked only telematics, not the event data recorder or video, so there may be less onboard evidence than usual.
Why TeslAnt keeps reading these
This is the seventh such match TeslAnt has written up since late August, after a road departure at 55 mph in Alabama and the cases linked from it, and it follows the month in which Tesla's driver-assist crash reports hit a record. The pattern does not change: a fatal crash is recorded locally as driver error, and the fact that a Level 2 system was on exists only inside a redacted federal spreadsheet.
For European owners the point is the one this series has made before. Nothing in the filing says the system caused the crash. But no European crash statistic captures whether Tesla's driver assistance was engaged either, and as the company brings its renamed supervised system to more EU markets, the reconciliation between what a car's telemetry knows and what a police report records is still being done by journalists, one redacted row at a time.