Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Transportation Software Apple Hardware

Apple Records First-Ever Accident In Self-Driving Car Program (appleinsider.com) 74

Apple's self-driving car program has reported its first-ever accident, according to a filing to the state's DMV. No injuries were reported. AppleInsider reports: A test car was rear-ended by a Nissan Leaf while merging onto an expressway, Bloomberg's Mark Gurman said on Twitter. The Apple vehicle suffered "moderate" damage. Details are still forthcoming, so it's unclear if the fault was with the Nissan driver, Apple's hardware and software, or some combination of the two. In an update, AppleInsider provided the following information: "The Apple vehicle, a Lexus SUV, was merging onto the Lawrence Expressway in California's Bay Area on Aug. 24, Gurman later wrote, citing a filing by Apple's Steve Kenner with the Department of Motor Vehicles. The Leaf was moving at just 15 miles per hour, but was also damaged."
This discussion has been archived. No new comments can be posted.

Apple Records First-Ever Accident In Self-Driving Car Program

Comments Filter:
  • by Anonymous Coward on Friday August 31, 2018 @07:23PM (#57234566)

    If you rear end someone it means you were following too closely and could not manage your speed appropriately.

    • by SeaFox ( 739806 )

      The Leaf was only driving 15 mph. Sounds like the driver was looking somewhere besides what was right right in front of him (like maybe over his shoulder at oncoming traffic from up the way) and didn't notice the Apple vehicle had slowed down/stopped while waiting for an opening to merge.

    • Apple’s car was traveling at less than 1 mile per hour, while the car that rear-ended it, a Nissan Leaf, was moving at about 15 miles per hour

      Merging on Lawrence Expy at 1 mph ??? Either it was congested and the other car driver was distracted, or the Apple car was doing something really dangerous ... the other car braked and ended up crashing at 15 mph (down from ?).

      • by dgatwood ( 11270 )

        I'm guessing it was one of those awful Sunnyvale intersections like Kifer eastbound or Central/Enochs eastbound, where you're lucky to be moving 1 MPH during certain times of day. :-)

    • Re: (Score:3, Informative)

      by Anonymous Coward

      That is correct -- at least in general.

      However it seems likely that we will see more accidents where a self driving car is rear ended by a non-self driving car (after factoring out the increased number of non-self driving cars that have some form of collision avoidance built into them). Self driving cars are just going to behave differently than human piloted ones - esp. with respect to detecting a hazard that actually doesn't exist and braking unexpectedly. This, in fact, is apparently somewhat why the Ube

    • by Anonymous Coward

      In *most*, not all, circumstances. A situation in which the lead car does not indicate that it is slowing/stopping (failed brake lights + no hand signal, for example) can be an issue in which the following car would not necessarily be wholly at fault.

      Of course, there's also the trivial case of cutting someone off and slamming on the brakes, a not-uncommon form of insurance fraud in some locales.

    • Yeah, not always. In the UK there is a big problem with "crash for cash" which tries to capitalise on that the Amy of thinking, where fraudsters will overtake you, pull back in much too close and then slam their brakes on immediately, giving you no chance to avoid them. The fraudsters will then claim for all sorts of medical, psychological and other compensations from you.

      The rise of dash cams is slowly bringing them under control.

      Similarly here - we need to full details before we can be sure who is to bl

      • iOS autocorrect strikes again - I have no idea what's Amy's way of thinking is, but I do know the fraudsters are trying to capitalise on that *way* of thinking...

      • Yeah, not always. In the UK there is a big problem with "crash for cash" which tries to capitalise on that the Amy of thinking, where fraudsters will overtake you, pull back in much too close and then slam their brakes on immediately,

        They have that everywhere. The poorer the citizenry, the more there is, but it's a problem every place. If you don't have a dash cam (as you say later) then you're screwed. It's hard to prove that someone did that stuff on purpose otherwise.

        giving you no chance to avoid them.

        Unless they have a vehicle with a shorter stopping distance than you do, you had a chance to avoid them — start braking as soon as they come over. Which is what you do if you're driving defensively, to maintain a safe distance.

        Still, having a camera is a great idea

      • One website had a few videos. First one of a woman jumping from behind a tree onto the street, right in front of a car, but estimating the jump wrong and getting badly hurt. One was a car overtaking a truck, braking hard but not managing to cause a crash, going on the fast line and falling back, overtaking again and repeating the manouvre. With everything caught on the truck's dash cam.
    • by Duds ( 100634 )

      That is not universally true by any means.

      Most notably a case a friend of mine had when they were slowing down for a queue and someone changed lanes and immediately stood on the brakes.

      In the pre-dash cam era the case took 18 months to win but he won it.

    • If you rear end someone it means you were following too closely and could not manage your speed appropriately.

      You're making a lot of assumptions. Sometimes you're just a completely distracted and useless git.

      I got rear ended at a bridge opening once. I was at a red light. Car was standing behind me. I saw the bridge opening, the instructions are clear: turn your motor off, you're going to be there for 20min.

      So I took my foot off the break, and put on the handbreak and switched my car off and got rear-ended.

      The guy behind me tapping away on his phone just saw the red lights on my car turn off and assumed the traffic

  • It was probably updating when the crash occurred.
  • The thought of a Leaf damaging anything, at any speed (much less 15 MPH), kind of makes me laugh.

    They must quantify "moderate" damage by cost, it was probably over $10 to re-paint the bumper on the Apple Lexus SUV.

    That said even though rear-endings are normally the fault of the follower, I have to wonder if the Apple self driving car did not do something super un-expected...

  • by fluffernutter ( 1411889 ) on Friday August 31, 2018 @08:14PM (#57234788)
    Sometimes human drivers are just responsible.
    • by Kjella ( 173770 )

      Sometimes human drivers are just responsible.

      Well you'd think so, considering they're driving. I suppose there can be a few mechanical faults where they're not, but otherwise duuuuh.

      • No that's not true. If the robot car was doing something that a human never would have, I blame the robot car; because technology companies should be striving to make them act human so that other humans don't get confused. But unless the robot car was doing something unusual in this case, it is truly the human's fault.
        • No that's not true. If the robot car was doing something that a human never would have, I blame the robot car; because technology companies should be striving to make them act human so that other humans don't get confused.

          Name something that a robot car might do in traffic that a human would never do.

    • Sometimes human drivers are just responsible.

      That's rarely the case. I tend to find human drivers mostly irresponsible.

  • Nothing says merging onto the expressway like "going 15 mph"

    • It's worse than that. The Apple car was probably merging at 1mph while the guy behind sped up to 15mph to fill a gap in the next lane over, but mistimed it. That part of Lawrence Expressway is like a huge parking lot during 'peak hour(s)' which lasts for a good half of the day, morning and evening.

  • How is the Apple car supposed to protect from being rear-ended?

    It's always the person in back's fault in a rear end collision. ALWAYS. Even if the front driver is being a dick. It sucks, but that's how the law works: Did the car stop suddenly? Then you were following too closely. The the lead car hit another car an stop short, making you hit them? Then you were following too closely. Did the axle fall off the lead car and then you hit it? Then you were following too closely.

    At best, Apple could onl

    • by mlyle ( 148697 )

      > It's always the person in back's fault in a rear end collision. ALWAYS.

      Not necessarily in a merge. I agree it's probably the human driver's fault, but if you dive in front of someone it is not necessarily physically possible for them to stop.

Work is the crab grass in the lawn of life. -- Schulz

Working...