Tesla data confirms Autopilot/FSD was engaged in fatal New Jersey crash that killed 68-year-old

A Tesla crossed the grass median of Route 55 in New Jersey, hit a tree, slid into oncoming traffic, and struck an SUV head-on. The SUV’s driver, 68-year-old Phillip Eastman, was killed.

Police reported it as a driver who lost control. What they didn’t say, and likely didn’t know, is that Tesla’s own report to federal regulators says the car’s driver-assist system was engaged. This is part of an ongoing Electrek investigation matching reported crashes to Tesla’s redacted NHTSA data.

What happened on Route 55

Around 8:31 a.m. on Saturday, August 22, 2026, a Tesla was heading south on Route 55 in Vineland, in Cumberland County, near milepost 34.6. The driver lost control, ran off the left side of the road, crossed the grass median, struck a tree, and continued into the northbound lanes, where the car hit a northbound Chevrolet SUV, according to the New Jersey State Police.

The SUV’s driver, Phillip “Phil” Eastman, 68, of Springfield, Pennsylvania, was killed. The Tesla’s driver and a passenger in the Chevrolet were hurt and taken to a hospital with moderate injuries.

Eastman had just been sworn in as a Springfield School District board member, and he spent nearly three decades coaching youth and high school ice hockey, including 17 years as the varsity head coach at Springfield High. His death was widely covered in the Philadelphia area.

And in all of it, no report mentioned Autopilot, “Full Self-Driving,” or any driver-assist system. The crash was told as a driver who lost control of his car.

What Tesla told the federal government

Under a NHTSA Standing General Order, automakers must report crashes where a Level 2 driver-assist system was engaged within 30 seconds of impact and someone is killed. Tesla filed a report on this crash.

In it, Tesla identifies the car as a 2021 Model Y and marks the automation “Engagement Status” as “Verified Engaged” — meaning Tesla confirmed through its own telematics that Autopilot or “Full Self-Driving” was active. It lists the New Jersey State Police as the investigating agency, and says it learned of the crash from the media.

Then it redacts the fields that would explain what the car did: the crash narrative, the software version, and whether the road was within the system’s approved operating area. All blacked out as “confidential business information,” the same redactions Tesla applies to 99.9% of its reports.

What the data doesn’t settle

We want to be precise about what this does and doesn’t prove. “Engaged within 30 seconds of impact” is the reporting trigger, not proof the system was steering when the car crossed the median. The driver may have been overriding it. And Tesla redacted the software version, so there’s no telling whether this was basic Autopilot or FSD.

Two more gaps are worth flagging. Tesla logs a pre-crash speed of just 37 mph, low for a freeway, which is more likely a single telematics snapshot from the pre-crash window than the speed at which the car left the road. And on this report Tesla checks only that it holds the car’s telematics, not the event-data recorder or video, so there may be less onboard evidence here than in other cases.

What is not in doubt is the one fact the public never got: a driver-assist system was on in a car that crossed a highway median and killed a man. Everything that would explain how is sealed.

Why we keep doing this

This is the pattern the investigation keeps surfacing, and it’s why the redaction matters. Tesla is, more than ever, pushing owners to treat a Level 2 driver-assistance system as if it drives itself. It sells the software as “Full Self-Driving,” Elon Musk keeps promising unsupervised autonomy is close, and the branding invites drivers to trust the car.

But it is still Level 2. The human is driving and responsible at all times, and Tesla’s own actions confirm it: consumer FSD still requires supervision, and its robotaxi service is a small, closely watched fleet. At the moment Tesla is telling owners to trust the car, it hides the records that would show how the system behaves when things go wrong, and a man coaching kids’ hockey one season is a name in a sealed federal file the next.

How we matched it, and why it’s notable: Electrek flagged this crash weeks ago, from the news, as a fatal Tesla wreck that had no corresponding entry in the federal data, and no public mention of driver-assist. The latest NHTSA release added it, flagged as a fatality with the system verified engaged. The record is unredacted on location (Vineland), state, vehicle (2021 Model Y), the fatality, and the month, and the incident time Tesla logged, 12:29 UTC, converts to about 8:29 a.m. local, within two minutes of the 8:31 a.m. police reported. It’s the same crash. Electrek has reached out to the New Jersey State Police for the crash report and the vehicle data, and asked whether investigators received Tesla’s raw telemetry or only Tesla’s own interpretation of it.

Electrek’s Take

Strip the redaction away and this is a Tesla, running its driver-assist software, that crossed a median and killed a school board member in the oncoming lane. Leave it in place, as Tesla did, and it’s a driver who “lost control.” Those are very different stories, and the public got the one that leaves Tesla out of it.

We’re careful here. The system being on doesn’t prove it caused the crash, the driver may have been overriding it, and we don’t even know if it was Autopilot or FSD. That is exactly the problem. Tesla knows all of it. It has the telematics, it filed the report confirming the system was engaged, and it decided that what its car did in a fatal crash is a trade secret, down to which software was running. Phillip Eastman’s family, and the troopers still investigating, deserve the full account, not a redacted one.

Tesla is already under NHTSA investigation over how it reports these crashes. We’ll keep matching them, one by one, until the record is whole.

If you’re driving a Tesla, powering it with home solar is one of the cheapest ways to cut your fuel costs to almost nothing. With electricity rates up almost 10% last year and expected to keep climbing, going solar is one of the best ways to protect yourself against rising costs. And with lease and PPA options, you can do it with zero upfront cost and start saving immediately. If you want to find the best deal, check out EnergySage. It’s a free service with hundreds of pre-vetted installers competing for your business, so you save 20 to 30% compared to going it alone. No sales calls until you pick an installer. Get your free quotes here.