Skip to main content

Morning Overview

Tesla’s Cybercab has already crashed 8 times, and the worst one came at highway speed

Tesla’s purpose-built robotaxi has been giving public rides in Austin for barely two months, and federal crash files already list it eight times. Most of the incidents are parking-lot scrapes at walking pace, but one stands apart: a Cybercab with a test driver aboard hit a car at 53 mph on a highway in Philadelphia.

Read next on Morning Overview: The Justice Department asked courts to undo approvals for three offshore wind farms, one already making power

The split between those two kinds of crashes says a lot about where Tesla’s self-driving program stands. The driverless service looks clean partly because it is kept slow, and the one Cybercab crash recorded at real road speed happened outside that protected zone.

Eight Cybercab reports in two federal datasets

Tesla files crashes under the National Highway Traffic Safety Administration’s Standing General Order, which requires companies to report crashes involving automated systems. As Electrek’s Fred Lambert tallied from the latest releases, the Cybercab now appears eight times across two separate files. Four crashes sit in the Automated Driving System file, which covers Tesla’s driverless Robotaxi service, and none of those topped 5 mph.

Those four were all in Austin. In August, a Cybercab drove into a water-filled pothole in a parking lot at 5 mph with a safety monitor aboard. In September, one was hit on its right side by a car backing out of a parking space, another was rear-ended by a pickup while stopped in traffic, and a fourth rolled over a raised concrete edge, across a sidewalk and down a curb at up to 3 mph with a rider inside. Two were not Tesla’s fault, and none involved an injury.

The other four come from the Level 2 driver-assist file, where crashes land when a human is behind the wheel and Tesla’s software is engaged. Tesla has been testing Cybercabs fitted with steering wheels, often in places where it has no Robotaxi permit. All four happened in September 2026: the 53 mph highway crash in Philadelphia, a 5 mph highway crash in Austin that sent someone to the hospital with minor injuries, an 11 mph intersection crash in Lehi, Utah, with a minor injury, and a property-damage incident in Tampa while the Cybercab was stopped.

A 53 mph crash in a state with no Tesla permit

Tesla redacted the narrative of all four Level 2 reports as confidential business information, so the public data does not show who was at fault or what the system was doing. Pennsylvania State Police are listed as the investigating agency for the Philadelphia crash, which happened on a highway at around 10 p.m. local time.

It is a different incident from the one Philadelphians saw in October, when a gold Cybercab was photographed on South Broad Street missing the entire outer panel of its driver-side door. That vehicle appeared to have been in a low-speed collision. In both cases, Tesla had no permit to operate automated vehicles in Pennsylvania, which suggests the cars were part of a supervised test fleet rather than a commercial service.

The injuries in the Cybercab record all sit on the supervised side. Two of the eight crashes involved injuries, and both are in the Level 2 file.

A driverless service kept slow, off highways and inside small zones

Across all 43 Tesla Robotaxi reports in the driverless file, the highest pre-crash speed is 29 mph, and the median is 1 mph. Not one happened on a highway: Tesla coded 21 on streets, 15 in parking lots and 7 at intersections. Even inside that low-speed envelope, the reports have turned up awkward patterns. In October, Electrek counted five Robotaxi crashes in which a remote operator, not the autonomous system, was driving when the car hit something, including a Dallas Model Y that touched a parked SUV at about 0.40 mph.

Tesla’s own safety report, published October 21, says no one was injured by Robotaxi across 3,112,541 driverless miles between January 22 and October 18. That figure excludes the Cybercab test fleet and every mile driven with a safety monitor aboard. Lambert’s reading of the combined data is pointed: “What the data shows is that Tesla has a speed problem.”

The Level 2 records show what happens when the same software family runs at highway speed. Electrek’s dataset of Tesla driver-assist reports includes a Model Y that left a parkway in El Dorado Hills, California, at 74 mph, hit a tree and burned in September, killing three of the four people inside, and an Autopilot or FSD crash into an overturned truck on Interstate 75 near Naples, Florida, at 71 mph. Engagement within 30 seconds of a crash is what triggers a report, so a filing does not prove the software caused the collision.

Private buyers arrive before the highway question is settled

The crash data lands as Tesla opens the Cybercab to private owners. Motor1 reported that invited buyers can now order the two-seater for $29,990 before taxes, with a $1,000 non-refundable deposit and a mandatory Autonomy Subscription of $299 a month. Tesla’s email to buyers says the car is “Only available in supported service areas,” which for now means parts of Texas and Florida, and deliveries are set to start in Austin in December 2026.

Those service areas are the same small, low-speed zones the crash data describes. Whether the Cybercab can move beyond them depends on the speeds where Tesla’s record is weakest, and the one highway-speed Cybercab crash on file has no public narrative explaining what went wrong.

This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.


More from Morning Overview

Morning Overview is reader-supported. Some links in our articles are affiliate links, and we may earn a commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. Full disclosure.