What you need to know
- Two of Apple's self-driving cars have been in minor accidents in August.
- Both accidents were not the fault of Apple's cars.
- It is the first time in two years that one of the cars was involved in an accident.
Apple's self-driving car fleet has experienced two accidents within a week of each other.
As reported by MacRumors, two of Apple's self-driving cars have been in minor accidents this month. The California DMV posted reports of each accident this week showing that, in both cases, someone rear-ended Apple's cars while they were idle in traffic.
Thankfully each accident was minor and in neither case was it the fault of Apple's self-driving cars. This is great news as, if it went the other way, it would be quite worrisome for anyone who is interested in eventually purchasing the company's rumored electric Apple Car.
Apple has been recently adding to its self-driving fleet. A report from the beginning of August noted that the company has expanded the number of drivers for its fleet by 20 percent:
Rumors continue to swirl around Apple releasing its own electric car. The latest projections show the company releasing Apple Car as early as 2025, but most expect a release closer to 2030.
Get the best of iMore in in your inbox, every day!
Joe Wituschek is a Contributor at iMore. With over ten years in the technology industry, one of them being at Apple, Joe now covers the company for the website. In addition to covering breaking news, Joe also writes editorials and reviews for a range of products. He fell in love with Apple products when he got an iPod nano for Christmas almost twenty years ago. Despite being considered a "heavy" user, he has always preferred the consumer-focused products like the MacBook Air, iPad mini, and iPhone 13 mini. He will fight to the death to keep a mini iPhone in the lineup. In his free time, Joe enjoys video games, movies, photography, running, and basically everything outdoors.
Thank you for signing up to iMore. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.