deniz.in

Markets

Weather

Loading weather

· via Hacker News – Front Page (hnrss.org)

Tesla data confirms driver-assist system was active in fatal New Jersey stop-sign crash

Electrek matched a fatal July 2025 New Jersey crash to a Tesla report to NHTSA confirming a driver-assist system was engaged, while Tesla redacted the details that would explain what happened.

Tesla data confirms driver-assist system was active in fatal New Jersey stop-sign crash

A fatal intersection in New Jersey

On the evening of July 6, 2025, New Jersey State Police responded to a crash at the junction of County Route 671 and Chestnut Avenue in Buena Vista Township, Atlantic County. According to Electrek, a Tesla Model 3 failed to stop at a stop sign and struck a Honda Civic that was making a left turn. The Civic's driver, 82-year-old Stephen Field, suffered fatal injuries. The Tesla's driver and three passengers were taken to a hospital with moderate injuries, state police spokesman Jeffrey Lebron told the outlet.

Local coverage treated the incident as an ordinary failure-to-stop collision, with no mention of Autopilot or "Full Self-Driving." The driver-assist connection surfaced only later, through an ongoing Electrek investigation that cross-references publicly reported crashes with data Tesla must submit to the US traffic safety regulator.

What Tesla reported to NHTSA

Under NHTSA's Standing General Order, automakers must report crashes in which a Level 2 driver-assistance system was engaged within 30 seconds of impact. Tesla filed such a report for this incident. According to Electrek, the report identifies the vehicle as a 2019 Model 3, records a fatality, and marks the automation status as "Verified Engaged" — Tesla's own telematics confirmed the system was active. The company also states that it holds the car's event-data recorder and telematics.

The report, however, blacks out the three fields that would explain what happened: the crash narrative, the software version, and whether the road was inside the system's approved operating area. Tesla filed the redactions as "confidential business information," a practice Electrek says applies to 99.9% of the company's reports.

Electrek matched the federal record to the local crash using location, state, vehicle model, the fatality and the month, plus a timestamp within three minutes of the time state police gave.

Autopilot or FSD

With the software version redacted, nobody outside Tesla can confirm which system was running. Electrek argues the stop sign itself points to FSD: reading and responding to stop signs is a City Streets capability that belongs to FSD, whereas basic Autopilot is a highway lane-keeping system that does not react to stop signs at all.

The inference is not airtight. Electrek has previously documented cases where drivers engaged basic Autopilot on roads it was never meant for, and the vehicle sailed straight through intersections. Either outcome cuts against Tesla, the outlet notes: one system isn't designed to handle stop signs, and the other is the one Tesla sells as self-driving.

One figure complicates the picture. Tesla logged the car's pre-crash speed at 4 mph — near-stationary, which fits a rolling stop far better than a car barreling through a junction. Electrek also notes the number doesn't square cleanly with a fatal impact and deployed airbags, so it was probably a snapshot from the pre-crash data rather than the speed at collision. Rolling stops are familiar territory for the software: NHTSA pushed Tesla to recall roughly 54,000 vehicles in 2022 after FSD rolled through stop signs instead of halting.

Electrek also raises, explicitly as speculation, the possibility of pedal misapplication — drivers resting a foot over the accelerator while FSD crawls through stop-sign-heavy neighborhoods. In the earlier fatal Katy, Texas crash, Tesla said the driver overrode the system by pressing the accelerator. The sealed narrative and the event-data recorder would settle the question here, the outlet argues.

Why it matters

Two facts are now confirmed, and they are narrow but serious: a man died in this crash, and Tesla's own data shows a driver-assist system was engaged. Everything that would explain how — the narrative, the software version, the telemetry — sits with Tesla, sealed as a trade secret.

The context sharpens the concern. Tesla markets the software as "Full Self-Driving" and Elon Musk keeps promising unsupervised autonomy, yet the system remains Level 2: the human behind the wheel is driving and responsible at all times. Electrek argues that the gap between the branding and the actual capability breeds complacency, and that redacting the records while urging owners to trust the car makes the problem worse. NHTSA is already investigating how Tesla reports these crashes. Until the redactions lift, the victim's family, the troopers still investigating, and the public are left reading between blacked-out lines.

  • #tesla
  • #autonomous-driving
  • #nhtsa
  • #driver-assist
  • #crash-safety

Related posts