USA 24

Tesla Autopilot crash kills 87-year-old driver in pond

Tesla Autopilot – An 87-year-old man driving a Tesla Model Y in Autopilot mode died after the vehicle veered off a Florida roadway, struck an electrical box, and submerged in a pond on May 26 in Tampa, as investigators with the Florida Highway Patrol said they are still determi

The moment the Tesla lurched forward, there was no warning—at least none that emergency responders could later point to. On May 26, around 8:10 p.m. in Tampa. a Tesla Model Y equipped with Autopilot left the roadway. struck an electrical box. and continued into a pond where the vehicle became submerged.

The driver, an 87-year-old man, was taken to a hospital, where he later died. A 75-year-old woman passenger was also transported, and she survived with non-life-threatening injuries, according to investigators with the Florida Highway Patrol. The crash happened in an area with a 30 mph speed limit.

Highway Patrol investigators said the Tesla was operating in Autopilot mode when it approached the train tracks. But officials have not explained how they made that determination. nor what may have caused the vehicle to veer off the road. The investigation remains ongoing, and authorities have not released the identities of those involved.

The patrol also has not said whether speed, medical conditions, or system behavior may have contributed to the crash. Even the timeline of the rescue remains uncertain: authorities have not indicated how long the vehicle was submerged before crews arrived.

That unanswered sequence—Autopilot engagement, a sudden lurch, a plunge into the water—lands as Tesla faces heightened scrutiny over its driver-assistance technology.

In a separate case, a federal judge recently upheld a $243 million jury verdict tied to a 2019 crash in Florida involving an Autopilot-equipped Tesla Model S. The crash in Key Largo killed a 22-year-old woman and seriously injured her boyfriend after a vehicle ran through an intersection.

U.S. District Judge Beth Bloom ruled the evidence “more than supports” the jury’s findings. The jury assigned partial responsibility to Tesla after George McGee drove his 2019 Model S through an intersection and crashed into an SUV parked on the shoulder. Jurors awarded $200 million in punitive damages to two people. including Naibel Benavides Leon. who was killed in the crash. and Dillon Angulo. The jury determined that the Autopilot system played a role alongside driver behavior.

During the trial, Tesla argued the driver should bear sole responsibility. The company said it plans to appeal and has maintained that its vehicles are not designed to make drivers complacent. adding that Autopilot requires supervision. More broadly, Tesla has faced multiple lawsuits involving its driver-assistance systems, with many settled or dismissed before trial.

The company’s broader pitch for autonomy has continued under CEO Elon Musk. who has promoted Tesla’s autonomous driving ambitions as central to its future. Speaking during a video appearance at the Samson International Smart Mobility Summit in Tel Aviv on May 18. Musk said: “Ten years from now. probably 90% of all distance driven will be driven by the AI in a self-driving car. It will be quite a niche thing in 10 years to actually be driving your own car.”.

image

While the Florida crash investigation moves forward without answers that families and drivers can quickly understand. regulators are also weighing how Tesla’s systems perform under real-world conditions. The National Highway Traffic Safety Administration initially announced a probe into Tesla’s Full Self-Driving software in October 2024 and expanded it on March 19.

The expanded probe covered roughly 3.2 million cars and six more possibly related accidents that the initial 2024 investigation did not. The agency’s initial probe covered 2.4 million Tesla vehicles and referenced seven potentially related crashes.

In describing why it broadened the inquiry, the NHTSA said the expanded probe would help regulators gather more information about Tesla’s updated visibility degradation detection system—a safety feature designed to monitor environmental conditions.

The agency said the available incident data raise concerns that Tesla’s degradation detection system. both as originally deployed and later updated. fails to detect and/or warn the driver appropriately under degraded visibility conditions such as glare and airborne obscurants. The NHTSA also said that in accidents its Office of Defects Investigation reviewed. Tesla’s FSD system “did not detect common roadway conditions that impaired camera visibility and/or provide alerts when camera performance had deteriorated until immediately before the crash occurred.”.

Last April, the NHTSA ended the probe after finding it was linked to only two low-speed accidents, Reuters reported. The agency concluded the feature was primarily linked to low-speed incidents resulting in minor property damage. and it had reports of roughly 100 crashes with no injuries or fatalities. Based on those findings, the agency said the low frequency and severity of the incidents did not warrant further action.

For now. the Florida crash remains the kind of case where every detail matters—how Autopilot was determined to be active. how the vehicle moved from the roadway to the pond. and what might have contributed to the moment the car “lurch[ed] forward with no warning.” As investigators continue their work. the same question sits at the center of both legal disputes and regulatory scrutiny: when driver-assistance systems are engaged. how reliably do they account for what drivers cannot immediately see—or control?.

Tesla Autopilot Full Self-Driving NHTSA Florida Highway Patrol Tampa crash Model Y pond crash Elon Musk Key Largo Autopilot case Beth Bloom George McGee

Leave a Reply

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha


Secret Link

Warning: foreach() argument must be of type array|object, null given in /home/misryoum/public_html/wp-content/plugins/wp-defender/src/component/class-network-cron-manager.php on line 216