Tesla’s latest crash reports to federal regulators add two more “Robotaxi” crashes where a remote operator, not the car’s autonomous system, was driving when it hit something.

That brings it to five in the data now. And every remote takeover that has shown up in a Tesla crash report has ended in a collision.

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.

A new defect petition accuses Tesla’s Robotaxis of speeding through active school zones, and NHTSA has opened a file to decide whether to investigate. The agency puts the affected fleet at about 1,000 vehicles, Model Y and Cybercab.

It’s the third federal action aimed at Tesla’s driverless fleet in about five weeks, after an audit query and a Special Order over how the Cybercab was certified.

A Tesla Cybercab was involved in a crash in Philadelphia this week, and it came out of it missing the entire outer panel of its driver-side door.

We don’t know who was at fault or whether Tesla’s software was driving. But Tesla has no permit to run automated vehicles in Pennsylvania, and that narrows down what this car was doing on Broad Street.

NHTSA has opened a formal investigation into comma.ai’s aftermarket driver assistance devices after five crashes where cars running openpilot plowed into stopped or slow-moving vehicles in their own lane. Two of those crashes killed three people.

The probe covers an estimated 30,000 comma three, comma 3X, and comma four devices. It’s the biggest regulatory problem for George Hotz’s startup since NHTSA pushed it to cancel its first product back in 2016.