Still, even if it was caused by lack of supervision while the car was operating in Summon mode, that still does not answer the question as to why there was that lack of supervision: because Overton claims he never asked the car to be in Summon mode.

Advertisement

The story Overton and the employee he spoke with does not make sense if Tesla is to be believed. According to them, Overton set the car into Summon mode; in Tesla’s letter, the Summon mode was activated three seconds after Overton got out of the car and closed the door.

If they were there both talking around the car for 30 second to a minute, surely they would have noticed the car starting and ramming its head into the trailer. Perhaps Overton essentially butt-dialed the Summon feature from his phone’s Tesla app; even then, the problem is with Tesla, not the owner, as it’s the responsibility of the company to both make the process of summoning as accident-proof as possible, and if the car is going to drive unmanned, it’s their responsibility to give it the means not to run itself into anything or anyone.

Advertisement

Tesla does claim the system is in Beta, and only to be used on private property. That still doesn’t really get them off the hook. Beta software exists so developers can test and learn and improve. So, here’s a nice big test, and in this case, the car failed.

That’s not a reason to blame the owner; that’s a set of data Tesla can use to improve their product.

Advertisement

That, or call it Autonomous A-Pillar Creasing System and knock off early.