The Tesla Model S involved in a fatal crash in Florida a few months ago was speeding prior to the collision, according to a report from the National Transportation Safety Board.
The preliminary report, which references performance data downloaded from the car, says the Model S was traveling at 74 mph right before the impact, above the 65-mph posted speed limit. The NTSB has not yet established a probable cause for the crash.
The report also confirms the Tesla driver was using Autopilot features, including traffic-aware cruise control and Autosteer lane keeping assist. The car also comes equipped with emergency braking to help mitigate front crashes or avoid them all together.
Five members from the NTSB went to the scene of the crash near Williston, Fla., to conduct an investigation. The team used three-dimensional laser scanning technology to gather clues, and the NTSB continues to collect performance data from the vehicle’s electronic systems for more information. The crash still remains under investigation, and the NTSB has not said when it will be complete. However, the agency noted it usually takes 12 months after the release of a preliminary report for a final report to be published, so we could see a final ruling on this matter a year from now.
The Model S accident occurred on May 7 after a tractor-trailer turned left at an intersection with no traffic light in front of the Tesla. In a blog post at the time, Tesla said, “Neither Autopilot nor the driver noticed the white side of the tractor trailer against a brightly lit sky, so the brake was not applied.” The Tesla driver died in the accident.
Tesla has faced considerable backlash directed toward its Autopilot system since the crash. Consumer Reports called on Tesla to scale back some of its Autopilot features, including Autosteer. Tesla has defended Autopilot and said it will continue to educate consumers about the technology.
Source: NTSB
The post Tesla Model S Involved in Fatal Crash Was Speeding, NTSB Says appeared first on Motor Trend.
from Motor Trend http://ift.tt/2a5BfNj
No comments:
Post a Comment