Connect with us

News

Fatal 2021 Tesla crash tied to excessive speed, not Autopilot: NTSB

Credit: Reuters/Twitter

Published

on

The National Transportation Safety Board (NTSB) confirmed on Wednesday that its investigation into an April 2021 fatal crash involving a Tesla Model S found no indications that the vehicle was operating on Autopilot at the time of the incident. Instead, the probable cause of the crash was determined to be the driver’s excessive speed, alcohol impairment, and inability to maintain control of the vehicle.

Two men were fatally injured in the accident, which resulted in the ill-fated Tesla Model S bursting into flame. The men were determined to be 69-year-old engineer Everett Talbot and 59-year-old Dr. William Varner. One man was found in the front passenger seat while the other was found in the back seat. 

Following the crash, Harris County Pct. 4 Constable Mark Herman told reporters that investigators were “100% certain” that there was no one in the fill-fated Model S’ driver’s seat when it crashed. This prompted widespread coverage from numerous media outlets, with several immediately declaring the fatal incident as a “driverless” crash. 

“They are 100% certain that no one was in the driver seat driving that vehicle at the time of impact. They are positive… Several of our folks are reconstructionists, but they feel very confident just with the positioning of the bodies after the impact that there was no one driving that vehicle,” Herman told journalists. He later noted that a search warrant had been executed on Tesla to secure data about the tragic incident.

But while the idea of a fatal Tesla Autopilot crash may be compelling, there were immediately some issues with the idea. For one, the absence of lane markings in the area’s streets meant that Autopilot could not have been engaged. Traffic-Aware Cruise Control could only go up to 30 mph in the area as well. For context, the incident involved the Model S accelerating to 67 mph before it crashed.

Other details, such as the allegation that firefighters had to call Tesla for help due to the Model S’ supposed uncontrollable fire, were debunked by the fire chief for The Woodlands Township Fire Department a few days after the incident made international news. 

Needless to say, the findings of the NTSB have revealed that the fatal accident did not involve Autopilot at all. The agency noted that a review of the data from the crash showed “no use of the Autopilot system at any time during this ownership period of the vehicle, including the time frame up to the last transmitted timestamp on April 17, 2021.” 

Advertisement
-

The agency also noted that the probable cause of the crash was the “driver’s excessive speed and failure to control his car, due to impairment from alcohol intoxication in combination with the effects of two sedating antihistamines, resulting in a roadway departure, tree impact, and post-crash fire.”

The NTSB further noted that “the available evidence suggests that the driver was seated in the driver’s seat at the time of the crash and moved into the rear seat” and that “it was not possible to determine whether the doors were manually operational following the power loss.” These conclusions are in line with footage retrieved from the owner’s home, which showed the driver entering the ill-fated Model S’ front seat before driving away. 

Tesla has not issued a comment about the matter as of writing. Teslarati also conducted a deep dive into the matter in 2021. A link to that report, which includes pertinent background about the incident, can be viewed below.

Don’t hesitate to contact us with news tips. Just send a message to simon@teslarati.com to give us a heads up.

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

Elon Musk

Tesla Cybercabs narrowly miss deadly Amazon cargo plane crash

An Amazon cargo plane crash near Miami’s airport stopped feet from dozens of Tesla Cybercabs.

Published

on

By

Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab
Photorealistic depiction of the Amazon Prime plane crash in Miami on Sep 3, 2026 near a fleet of Tesla Cybercab

An Amazon Prime Air Boeing 767 cargo jet overran the runway at Miami International Airport on Sunday afternoon, killing five people and injuring five more. The jet, operated by North Carolina based carrier 21 Air as Flight 7598, touched down around 2 p.m. after arriving from San Juan, Puerto Rico, then crossed the airport perimeter, plowed across NW 67th Avenue and struck multiple vehicles before catching fire, according to the Associated Press.

Photos and video from the scene show the aircraft’s nose stopped within meters of a fenced staging lot holding dozens of gold painted Tesla Cybercabs, the steering wheel free robotaxi Tesla began putting on public roads in Austin last week. Miami-Dade Fire Rescue has confirmed the plane struck “multiple vehicles” but has not said whether any Cybercabs were among them, and neither Tesla nor airport officials have addressed the fleet directly.

The Cybercabs had not yet entered commercial service in Miami. Tesla’s existing Robotaxi operation there runs on modified Model Y vehicles and has been unsupervised since Ashok Elluswamy confirmed the detail on X in July.


Elon Musk offered the briefest of reactions. Replying to a Zero Hedge post about the Cybercabs sitting so close to the wreckage, he wrote a single word: “Weird.” He has not commented further, and Tesla has not issued a statement.

The timing puts Tesla’s newest vehicle near an unrelated but highly visible tragedy just days after its Austin debut, a launch that had already drawn scrutiny from federal regulators. The National Highway Traffic Safety Administration opened an audit how Tesla certified the Cybercab as compliant with federal vehicle safety standards, a process Teslarati covered after the vehicle’s September 3 launch event. That inquiry concerns the car’s lack of a steering wheel and pedals, not the Miami crash.

Investigators from the FAA and NTSB are focused on the plane, not the parking lot beside it. Flight data reviewed by outlets including Simple Flying show the 767 touched down around 170 knots, well above the 135 to 140 knot range typical for the aircraft, though investigators have not determined a cause. Amazon said it is working with authorities and that its priority is the safety of everyone affected.

Whether any Cybercabs were damaged, and what Tesla plans for the fleet parked near one of the country’s busiest airports, remain open questions.

Continue Reading

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.

Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.

The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.

In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla

Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.

The company has not released a city-by-city breakdown of the one million unsupervised miles.

The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.

Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.

The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla

Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.

The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.

The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.

That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.

Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.

Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.

By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.

Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.

Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.

If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.

That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.

Continue Reading