Incident: Electric Scooter Battery Fire Recall by Lime in US Cities

Published Date: 2018-10-30

Postmortem Analysis
Timeline 1. The software failure incident involving Lime's electric scooters happened in late August 2018 as mentioned in Article 76501. 2. Lime learned about the issue with the batteries in its scooters in August 2018 as reported in Article 76464. 3. Lime recalled about 2,000 scooters due to the battery issue in August 2018 according to Article 76598.
System 1. Batteries in Lime's Ninebot model scooters [Article 76598, Article 76464, Article 76501] 2. Batteries made by Ninebot, the parent company of Segway [Article 76464, Article 76501]
Responsible Organization 1. Lime - Lime, the company that operates the electric scooters, was responsible for the software failure incident as they discovered the potential issue with the batteries in their scooters and initiated the recall process [76598, 76464, 76501]. 2. Ninebot - The batteries in Lime's scooters were manufactured by Ninebot, the parent company of Segway, and the defect in the batteries led to the potential risk of catching fire or smoldering, contributing to the software failure incident [76464, 76501].
Impacted Organization 1. Lime - The software failure incident impacted Lime as they had to recall some of their electric scooters due to potential battery issues [76598, 76464, 76501].
Software Causes 1. The software program created by Lime to identify potentially affected batteries and deactivate scooters with a red code to prevent public use [Article 76464]. 2. Lime also developed another software program to detect all scooters that might have defective batteries and bring them back to local headquarters [Article 76501].
Non-software Causes 1. Manufacturing defect in the batteries of Lime's Ninebot model scooters [76598, 76464, 76501] 2. Issues with the batteries made by Ninebot, the parent company of Segway [76464, 76501] 3. Baseboards on the Okai scooters cracking or breaking when subjected to repeated abuse [76464]
Impacts 1. Lime recalled some of its electric scooters after discovering potential battery issues that could lead to fires, impacting about 0.01% of its fleet [76598, 76464, 76501]. 2. The software failure incident led to the removal of thousands of Lime scooters from the streets of Los Angeles, San Diego, and Lake Tahoe [76464]. 3. Lime faced concerns over the safety of riders and "juicers" who charge the scooters overnight due to potential defects in the scooters [76501]. 4. The incident raised questions about the adequacy of Lime's response to safety issues raised by employees and the need for better addressing potential defects in the scooters [76501].
Preventions 1. Implementing thorough quality control measures during the manufacturing process to detect and prevent defects in the batteries [76598, 76464, 76501]. 2. Conducting regular and rigorous testing of the scooters' batteries to identify any potential issues before they lead to failures [76598, 76464, 76501]. 3. Enhancing communication channels within the company to ensure that safety concerns raised by employees are promptly addressed and resolved to prevent incidents [76464, 76501]. 4. Collaborating closely with battery suppliers, such as Ninebot, to continuously monitor and improve the quality of the batteries used in the scooters [76464, 76501]. 5. Implementing software solutions that can proactively identify and deactivate scooters with potentially faulty batteries to prevent any risks to riders and the public [76464, 76501].
Fixes 1. Implement rigorous quality control measures during the manufacturing process to detect and prevent battery defects [76598, 76464, 76501]. 2. Develop and deploy software programs to identify potentially faulty batteries and scooters in real-time to prevent incidents [76464, 76501]. 3. Conduct thorough investigations and testing on all scooter models to identify any vulnerabilities to battery failure and address them promptly [76464]. 4. Enhance communication and collaboration between employees, management, and safety teams to ensure that safety concerns are addressed promptly and effectively [76464, 76501]. 5. Consider reevaluating partnerships with battery and scooter manufacturers to ensure the highest quality standards are met [76464, 76501].
References 1. Lime company statement [Article 76598, Article 76464, Article 76501] 2. Washington Post [Article 76598, Article 76464, Article 76501]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident having happened again at one_organization: - Lime, the company behind the electric scooters, faced a software failure incident related to batteries potentially catching fire in some of its scooters [76598, 76464, 76501]. - Lime mentioned that they are investigating a report that another scooter model they use may also be vulnerable to battery failure, indicating a recurring issue within their own products [76598]. - Lime also mentioned facing issues with its scooter manufacturer, Okai, where baseboards on the Okai scooters have been found to crack or break under certain conditions, showing a pattern of issues with their suppliers [76464]. (b) The software failure incident having happened again at multiple_organization: - The incident involved batteries made by Ninebot, the parent company of Segway, indicating a potential issue with batteries across different scooter brands [76464]. - Lime mentioned receiving an unconfirmed report that another Segway Ninebot scooter model may also be vulnerable to battery failure, suggesting a broader issue with this type of scooter [76464]. - The article highlighted that scooter companies in general have faced safety issues as they rapidly expand in cities worldwide, indicating a common challenge across multiple organizations in the scooter-sharing industry [76501].
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase: - Lime recalled some of its scooters after discovering a potential issue with batteries in its Ninebot model scooters, where a manufacturing defect could result in the battery smoldering or catching fire [76598]. - Lime stated that the issue with the batteries in its scooters originated from the batteries made by Ninebot, the parent company of Segway [76464]. - Lime created software programs to identify potentially affected batteries and to ensure no potentially faulty scooters were in operation, indicating a design flaw in the battery system [76464]. - Lime mentioned that it received an unconfirmed report that another Segway Ninebot scooter model may also be vulnerable to battery failure, suggesting a design issue with the scooter models [76464]. - Lime faced issues with its scooter manufacturer, Okai, where baseboards on the Okai scooter were found to crack or break when subjected to repeated abuse, indicating a design flaw in the scooter's construction [76464]. (b) The software failure incident related to the operation phase: - Lime deactivated scooters promptly when affected batteries were identified to prevent any members of the public from riding or charging them, indicating operational measures taken to address the issue [76464]. - Lime mentioned that it will have employees familiar with the battery issue on hand 24 hours a day at facilities where the Segway Ninebot scooters are held and will run daily diagnostics on all scooters, regardless of where they were made, suggesting operational changes to enhance safety measures [76501]. - Lime mechanics expressed concerns over the safety of "juicers" who may have unknowingly charged scooters with potentially dangerous defects, indicating operational risks associated with charging the scooters [76501]. - Lime emphasized that safety is of utmost importance and stated that they will continue to hold their equipment manufacturers and themselves to the highest possible standard, highlighting the operational aspect of ensuring safety in their operations [76501].
Boundary (Internal/External) within_system, outside_system (a) within_system: - Lime discovered a potential issue with some of the batteries in its Ninebot model scooters, where a manufacturing defect could result in the battery smoldering or catching fire [76598]. - Lime stated that the issue with the batteries in its scooters originated from the batteries made by Ninebot, the parent company of Segway [76464]. - Lime created a software program to identify potentially affected batteries and another software to ensure no potentially faulty scooters were in operation [76464]. - Lime deactivated scooters promptly when affected batteries were identified using a software program [76501]. (b) outside_system: - Lime faced issues with its scooter manufacturer, Okai, where baseboards on the Okai scooters were found to crack or break when subjected to repeated abuse, such as riding off a curb at high speed [76464]. - Lime emphasized that the safety of its riders, Juicers, and community is its highest priority and will continue to hold its equipment manufacturers to the highest possible standard [76464]. - Lime took extra precautions to ensure the safety of anyone who uses or charges its scooters, indicating a focus on external safety factors [76501].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident occurring due to non-human actions: - Lime recalled some of its scooters after discovering a potential issue with batteries that could catch fire due to a manufacturing defect in the batteries [76598]. - Lime identified a manufacturing defect in the batteries of its Ninebot model scooters, which could result in the battery smoldering or catching fire [76464]. - Lime stated that the defect impacted less than 0.01 percent of its scooter fleet and created software programs to identify potentially affected batteries and ensure no faulty scooters were in operation [76464]. - Lime deactivated scooters with affected batteries promptly when identified to prevent any risk to riders or the public [76501]. (b) The software failure incident occurring due to human actions: - Lime employees had alerted the company about safety issues related to the scooters, indicating potential human actions contributing to the failure incident [76464]. - Concerns were raised by Lime mechanics about the safety of "juicers" who charge the scooters overnight, suggesting potential human actions that could have unknowingly contributed to the safety risks [76501]. - Lime mechanics expressed frustrations over the dismissal of their concerns by senior staff regarding the safety of juicers and the need for better addressing the issues, indicating potential human actions affecting the incident [76501].
Dimension (Hardware/Software) hardware, software (a) The software failure incident occurring due to hardware: - Lime recalled some of its electric scooters after discovering that they could contain batteries with the potential to catch fire. The issue was traced back to a potential problem with the batteries in its Ninebot model scooters, where a manufacturing defect could result in the battery smoldering or catching fire [Article 76598]. - Lime identified that the issue with the batteries in its scooters originated from the batteries made by Ninebot, the parent company of Segway. The defect impacted less than 0.01 percent of Lime's scooter fleet, leading to the recall of about 2,000 scooters primarily in Los Angeles, San Diego, and Lake Tahoe areas [Article 76464]. - A Lime scooter caught fire in Lake Tahoe due to a manufacturing defect in the battery, prompting Lime to take extra precautions to ensure the safety of its riders and chargers. The batteries were manufactured by Segway Ninebot, and Lime created software programs to detect and deactivate scooters with potentially defective batteries [Article 76501]. (b) The software failure incident occurring due to software: - Lime created software programs to identify potentially affected batteries and to ensure that no potentially faulty scooters were in operation. When an affected battery was identified, Lime promptly deactivated the scooter to prevent any members of the public from riding or charging it [Article 76464]. - Lime emphasized that it had taken extra precautions to ensure the safety of anyone who uses or charges its scooters by creating software to detect defective batteries and deactivating scooters with identified issues. The company also mentioned running daily diagnostics on all scooters, regardless of their origin, to address any potential software-related failures [Article 76501].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to Lime's electric scooters catching fire was non-malicious. The incident was attributed to a manufacturing defect in the batteries of the scooters, specifically in the Ninebot model scooters. Lime stated that the defect could result in the battery smoldering or catching fire, and it affected less than 0.01% of its scooter fleet [76598, 76464, 76501]. However, there were concerns raised about how Lime addressed the safety issues related to the scooters. Employees reportedly alerted the company to potential issues with the scooters, but they felt that their concerns were not adequately addressed, potentially putting riders and "juicers" (people paid to charge the scooters) at risk [76464, 76501]. This indicates a non-malicious failure due to contributing factors introduced without intent to harm the system.
Intent (Poor/Accidental Decisions) accidental_decisions (a) The articles do not provide specific information indicating that the software failure incident was due to poor decisions. Lime took actions such as recalling scooters, creating software programs to identify potentially affected batteries, and implementing safety measures to address the issue. There is no mention of poor decisions contributing to the software failure incident [76598, 76464, 76501]. (b) The software failure incident involving Lime's electric scooters catching fire was attributed to a manufacturing defect in the batteries, specifically in the Ninebot model scooters. Lime stated that the issue arose from a manufacturing defect that could result in the battery smoldering or catching fire. This indicates that the failure was due to accidental decisions or mistakes in the manufacturing process rather than poor decisions [76598, 76464, 76501].
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to development incompetence is evident in the articles. Lime's scooters were recalled due to a potential issue with some of the batteries in its Ninebot model scooters. The issue arose from a manufacturing defect that could result in the battery smoldering or catching fire [76598]. Lime employees had alerted the company about safety issues, indicating that potential issues were not adequately addressed, which could be attributed to development incompetence [76464]. Lime also faced issues with its scooter manufacturer, Okai, where baseboards on the Okai scooter were found to crack or break when subjected to repeated abuse, suggesting a design flaw or incompetence in the manufacturing process [76464]. (b) The software failure incident related to accidental factors is also present in the articles. Lime stated that the defect in the batteries impacted less than 0.01% of its scooter fleet, indicating that the issue was not intentional but rather accidental [76464]. The incident where a Lime scooter burst into flames in Tahoe was attributed to bad batteries, with Lime acknowledging that a manufacturing defect could result in the battery smoldering or catching fire, suggesting an accidental flaw in the battery manufacturing process [76501]. Lime emphasized that it has taken extra precautions to ensure the safety of anyone who uses or charges its scooters, indicating a reactive response to an accidental issue [76501].
Duration temporary (a) The software failure incident in the articles appears to be temporary. Lime discovered a potential issue with some of the batteries in its Ninebot model scooters, which could result in the battery smoldering or catching fire. Lime took immediate action by recalling about 0.01 percent of its fleet of scooters primarily in Los Angeles, San Diego, and Lake Tahoe areas out of caution. Lime also created software programs to identify potentially affected batteries and ensure that no potentially faulty scooters were in operation. The company promptly deactivated scooters with affected batteries to prevent any risk to riders or the public [Article 76598, Article 76464, Article 76501]. (b) The software failure incident was temporary as Lime took proactive measures to address the issue and ensure the safety of its riders and the public. Lime identified the manufacturing defect in the batteries, recalled the affected scooters, and implemented software programs to detect and deactivate potentially faulty scooters. The company also stated that it would have employees familiar with the issue available 24 hours a day at facilities where the scooters are held and run daily diagnostics on all scooters to prevent any further incidents. Lime emphasized that safety is its highest priority and that it takes full responsibility for its scooters [Article 76598, Article 76464, Article 76501].
Behaviour other (a) crash: The articles do not mention any instances of the Lime scooters crashing due to the software failure incident. The primary issue highlighted in the articles is related to potential battery fires in the scooters, leading to a recall of some models [76598, 76464, 76501]. (b) omission: There is no indication in the articles that the software failure incident led to the Lime scooters omitting to perform their intended functions at any instance [76598, 76464, 76501]. (c) timing: The software failure incident did not involve the Lime scooters performing their intended functions too late or too early. The focus of the incident was on potential battery defects that could lead to fires [76598, 76464, 76501]. (d) value: The software failure incident did not involve the Lime scooters performing their intended functions incorrectly. The issue primarily revolved around the safety concern related to potential battery fires [76598, 76464, 76501]. (e) byzantine: The articles do not mention the Lime scooters behaving erroneously with inconsistent responses and interactions, which would align with a byzantine failure scenario [76598, 76464, 76501]. (f) other: The behavior of the software failure incident in this case is related to potential battery defects in the Lime scooters that could lead to smoldering or catching fire. The incident prompted Lime to recall some scooters and take safety precautions to address the issue [76598, 76464, 76501].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence harm, property, non-human, theoretical_consequence (a) death: People lost their lives due to the software failure - No information about any deaths resulting from the software failure incident was mentioned in the articles [76598, 76464, 76501]. (b) harm: People were physically harmed due to the software failure - The articles mentioned that there were concerns about the safety of riders and "juicers" (people paid to charge the scooters overnight) due to potential defects in the scooters [76464, 76501]. (c) basic: People's access to food or shelter was impacted because of the software failure - No information about people's access to food or shelter being impacted due to the software failure incident was provided in the articles [76598, 76464, 76501]. (d) property: People's material goods, money, or data was impacted due to the software failure - The software failure incident led to the recall of about 2,000 scooters by Lime, impacting the company's property and potentially causing financial losses [76598, 76464]. (e) delay: People had to postpone an activity due to the software failure - There was no mention of people having to postpone activities due to the software failure incident in the articles [76598, 76464, 76501]. (f) non-human: Non-human entities were impacted due to the software failure - The software failure incident affected Lime's electric scooters, specifically related to potential battery issues that could lead to fires or malfunctions [76598, 76464, 76501]. (g) no_consequence: There were no real observed consequences of the software failure - The software failure incident did have consequences, such as the recall of scooters and concerns about safety, as detailed in the articles [76598, 76464, 76501]. (h) theoretical_consequence: There were potential consequences discussed of the software failure that did not occur - Lime mentioned investigating reports of potential vulnerabilities in another scooter model, indicating a theoretical consequence that could potentially lead to further issues if confirmed [76598, 76464]. (i) other: Was there consequence(s) of the software failure not described in the (a to h) options? What is the other consequence(s)? - No other specific consequences of the software failure incident were mentioned in the articles [76598, 76464, 76501].
Domain transportation (a) The failed system in the articles is related to the transportation industry. Lime, a company that operates electric scooters for shared mobility services, experienced a software failure incident with its scooters due to potential battery issues [Article 76598, Article 76464, Article 76501]. The scooters were recalled and taken off the streets in cities like Los Angeles, San Diego, and Lake Tahoe after reports of batteries catching fire or smoldering [Article 76598, Article 76464]. Lime mentioned that the defect impacted less than 0.01% of its scooter fleet and took measures to identify and deactivate potentially affected scooters using software programs [Article 76464]. The safety concerns related to the scooters and their batteries highlight the transportation industry aspect of this software failure incident.

Sources

Back to List