Tesla crashes into parked fire truck, Autopilot being blamed once again

I’m actually glad to see these types of serious but non fatal crashes. Even if it is the driver’s fault, Tesla will learn something from it and possibly make all Tesla’s more safe.

@simonalvarez0987 , had you seen the Washington Post article about the reported DUI? See my post #10 above.

What the hell are people doing in their car? You would see a fire truck hundreds of meters in advance, autopilot doesn’t disable your brakes and steering wheel.

Unanswered questions w/r this article: was this an AP-1 or AP-2 vehicle? Was AP even active at the time? Which rev of s’ware was installed? Until these and many others have answers, this is just another sensationalized article about something that occurs thousands of times a week in cars built by every manufacturer on the planet. Yes, indeed…what in hell are people doing in their car??!

I hope the driver got a ticket. You are responsible for driving the car.

Please tell me someone checked to see if there was an Orange in the car. For those that don’t understand that – good.
If he did hack autopilot then he is an idiot. I use AP2 everyday on the busy Rt2 into Boston and it is fine with the stop and go traffic and the idiots who cut in when there isn’t a space.

Periodically tugging the steering wheel is not an indication that one is paying attention to the road ahead. Conversely not tugging on it is not an indication that they are not paying attention or don’t have their hand on the steering wheel. This was a failure to regulate the speed of the vehicle or slow down to a stop, not a failure to steer. Based on the photo in that section there wasn’t anywhere for him to steer, but to only stop. Perhaps he could have changed lanes earlier to avoid the emergency vehicles.

Looking at the long shadows the sun was low and may have blinded the camera, so it was up to the radar to detect the still obstacle. Given that at highway speed there seems little chance that the car would stop by itself.

Looks like Tesla will eventually have to make their crash avoidance system active at all times unless deliberately turned off by the driver *(note that it should not turn off when the brake pedal it touched, this should require accessing a sub-menu on the computer so it cannot be disabled easily)..

When the accident happened would have been some time prior to the video we see above. I doubt «blindness» of sensors had anything to do with this.

The accident happened at approx. 8:30am, sunrise at Culver City was at 6:56am. We cannot exclude the possibility, we know it can and has been a factor.

What the hell are people doing in their car? You would see a fire truck hundreds of meters in advance, autopilot doesn’t disable your brakes and steering wheel.[/QUOTE][QUOTE=»Ric, post: 12078, member: 756″]Unanswered questions w/r this article: was this an AP-1 or AP-2 vehicle? Was AP even active at the time? Which rev of s’ware was installed? Until these and many others have answers, this is just another sensationalized article about something that occurs thousands of times a week in cars built by every manufacturer on the planet. Yes, indeed…what in hell are people doing in their car??!

Here’s the answer… D.U.I. :rolleyes:
https://www.washingtonpost.com/news/innovations/wp/2018/01/23/a-tesla-owners-excuse-for-his-dui-crash-the-car-was-driving/
Autopilot is NOT FSD and does not relieve the driver to pay attention at all times!
Happy to set the record straight.

Interesting.. that doesn’t seem like a crash with 65 mph, but i also don’t see skid marks on the road in the picture… If the car was moving at 65 mph before the crash, something must have slowed it down to at least under 35 mph. for the damage to make sense.

All eyes are on Tesla once more, after a Model S traveling at highway speeds crashed into a parked fire truck in Culver City, California earlier this week. The collision, which allegedly happened while the car was on Autopilot, has incited renewed debates, criticisms, and an upcoming government probe on Tesla and its evolving driving-assist software.

As more details about the accident emerge, here is a brief discussion on the latest and most pertinent information relating to the recent Model S collision.

[SIZE=6]The accident[/SIZE]

As we stated in a previous report, the Tesla Model S was traveling at 65 mph on Interstate 405 on Monday morning when it crashed into a stationary fire truck. The emergency vehicle was parked on the road after being deployed to a separate accident in the area.

The driver of the electric car was able to walk away unharmed from the accident. Upon being questioned by the authorities, the Model S driver stated that the vehicle was on Autopilot when it collided with the parked fire truck. Tesla released a brief statement on Monday, stating that Autopilot is intended only to be used by an attentive driver.

[SIZE=6]More details emerge[/SIZE]

As the online forum community continued to debate about the benefits and risks of Tesla’s Autopilot software, a member of the r/TeslaMotors subreddit who claimed to know the driver of the crashed Model S spoke up and provided some details about the accident. According to the Redditor, the Model S was traveling behind a pickup truck with Autopilot engaged. Due to the truck’s size, the Tesla’s driver was unable to see beyond the vehicle in front.

“The driver of the Tesla is my dad’s friend. He said that he was behind a pickup truck with AP engaged. The pickup truck suddenly swerved into the right lane because of the firetruck parked ahead. Because the pickup truck was too high to see over, he didn’t have enough time to react.” notes mikhpat.

Tesla Model S crashes into a stationary firetruck [Credit: Culver City Fire Department via Twitter]

Tesla’s Autopilot system allegedly did not have enough time to react while driving at 65 mph. The driver stated that the Model S’ emergency braking system might have activated moments before the car hit the emergency vehicle, but he could not be certain, according to mikhpat‘s statement.

“As for the 65mph detail, the braking system could’ve intervened before the collision, but there’s no way he could tell.”

The impact was strong enough to push the steering wheel two feet into the cabin, however. The Model S driver had some minor cuts and bruises from the accident but was otherwise unharmed. According to the Redditor, the driver admits that he was at fault for not paying close attention to the road. The Model S owner also refused to blame Tesla for the accident.

While it’s still unconfirmed if Tesla’s Autopilot suite, including Traffic-Aware Cruise Control and Autosteer, was activated at the time of the accident, Tesla’s Model S Owner’s Manual warns of a similar scenario that would not be detected by the driving-assist system.

According to the About Drive Assistance section of the owner’s manual:

[QUOTE]“Traffic-Aware Cruise Control cannot detect all objects and may not brake/decelerate for stationary vehicles, especially in situations when you are driving over 50 mph (80 km/h) and a vehicle you are following moves out of your driving path and a stationary vehicle or object is in front of you instead.”

[/QUOTE]

The warning appears to mimic the exact situation being described by Redditor mikhpat.

[SIZE=6]The investigations begin[/SIZE]

As the online forum community exploded amidst heated debates on who is to blame for the recent Model S collision, the US National Transportation Safety Board announced that it is sending two of its investigators to California to study the crash. According to the NTSB, the investigators will be examining both “driver and vehicle” factors in Monday’s accident.

By Tuesday, the National Highway Traffic Safety Administration announced that it is also sending a team of investigators to California to evaluate the recent accident, as well as to assess any “lessons learned” from the crash, as noted in a Bloomberg report. The NHTSA did not specify which team of investigators it was sending to California, but expectations are high that the regulating body would be deploying its Special Crash Investigations unit.

Article: Tesla Model S firetruck crash in California: What we know so far

@simonalvarez0987 , had you seen the Washington Post article about the reported DUI? See my post #10 above.

Ah, this is quite interesting, actually. It turns out the DUI mentioned in the WaPo article was referring to the Model S incident on Bay Bridge earlier during the weekend, so we’re not entirely sure if the driver of the Model S that crashed into the firetruck was also a bit, erhm, distracted. 😀

Ah, this is quite interesting, actually. It turns out the DUI mentioned in the WaPo article was referring to the Model S incident on Bay Bridge earlier during the weekend, so we’re not entirely sure if the driver of the Model S that crashed into the firetruck was also a bit, erhm, distracted. 😀

Oh, my bad, I missed that these were two separate incidents. Hence my ‘informative’ rating… 😉
I was hesitating with ‘funny’ ‘cause if your closing statement! 😀
As to cause, the investigation should speak to it. Facts Matter!

Here’s the answer… D.U.I. :rolleyes:
https://www.washingtonpost.com/news/innovations/wp/2018/01/23/a-tesla-owners-excuse-for-his-dui-crash-the-car-was-driving/
Autopilot is NOT FSD and does not relieve the driver to pay attention at all times!
Happy to set the record straight.

Of course…goes without saying. Interestingly, a reminder from the owner’s manual has been highlighted by several folks, emphasizing the fact that, especially under the circumstance of following a moving vehicle that suddenly moves to another lane and reveals a stationery object, the AP software interprets the object as something to ignore. According to subsequent reports attributed to the owner, that is exactly the (very rare) circumstance he experienced, and he takes responsibility.