Incident: F-35B Stealth Jet Crash into Mediterranean Sea due to Engine Malfunction

Published Date: 2021-11-18

Postmortem Analysis
Timeline 1. The software failure incident involving an RAF F-35B Lightning crashing into the sea after taking off from HMS Queen Elizabeth occurred on the day the article was published, which was November 18, 2021 [Article 120850].
System 1. F-35B Lightning aircraft [Article 120850] 2. F-35A aircraft [Article 120850] 3. F-35 stealth fighter jet [Article 120850]
Responsible Organization 1. The software failure incident was caused by technical or human error, as indicated by the Ministry of Defence focusing the investigation on technical or human error [120850]. 2. The incident was not attributed to hostile action, according to the Ministry of Defence [120850].
Impacted Organization 1. Royal Air Force (RAF) pilot and aircraft [Article 120850] 2. Ministry of Defence (MoD) [Article 120850]
Software Causes 1. Fractured rotor causing a catastrophic engine fire in a USAF F-35A in Florida in June 2014 [Article 120850]. 2. Fire in the weapons bay of a US Marine Corp F-35B in 2016 [Article 120850]. 3. Fuel tube failure in flight leading to grounding of all operational F-35s in 2018 [Article 120850]. 4. Unresponsive tail glitch causing a F-35 crash on landing in 2020 [Article 120850]. 5. Technical or human error being investigated as potential causes of the recent F-35B crash in the Mediterranean [Article 120850].
Non-software Causes 1. Engine malfunction leading to the crash of the F-35B Lightning into the sea [Article 120850]. 2. Pilot ejection due to the crash and subsequent parachute entanglement with the edge of the aircraft carrier's flight deck [Article 120850]. 3. Mid-air collision with a KC-130J tanker resulting in the F-35 stealth fighter jet falling out of the sky and exploding on the ground [Article 120850]. 4. Fractured rotor causing a catastrophic engine fire in a USAF F-35A in 2014 [Article 120850]. 5. Fire in the weapons bay of a US Marine Corp F-35B in 2016 [Article 120850]. 6. Fuel tube failure leading to the grounding of all operational F-35s in 2018 [Article 120850]. 7. Tail glitch and pilot distraction causing a F-35 crash on landing in 2020 [Article 120850].
Impacts 1. The F-35B Lightning aircraft crashed into the sea due to a suspected engine malfunction, leading to the pilot ejecting and the aircraft sinking to the bottom of the Mediterranean [Article 120850]. 2. The crash triggered a scramble to recover the advanced jet from the sea bed before it could be reached by foreign powers, particularly Russia, to prevent sensitive technology from falling into the wrong hands [Article 120850]. 3. The incident raised fresh questions about the reliability and safety of the F-35B fleet, with concerns about technical or human error being the cause of the crash [Article 120850]. 4. The pilot suffered minor injuries but was safely rescued by a search and rescue helicopter after ejecting from the aircraft [Article 120850]. 5. The recovery operation involved the use of deep water remote-controlled vehicles, inflatable lift bags, and other specialized equipment to locate and lift the sunken F-35B aircraft from the sea bed, which was believed to be more than a mile beneath the surface [Article 120850]. 6. The F-35 program has faced a series of technical issues and operational shortcomings, including software vulnerabilities, cyber-attack risks, operational limitations, and various faults identified during Pentagon tests, raising concerns about the overall effectiveness and reliability of the aircraft [Article 120850].
Preventions 1. Implementing more rigorous testing procedures for the F-35's software system to identify and address vulnerabilities before deployment [120850]. 2. Conducting thorough cybersecurity assessments to ensure the software is protected against potential cyber-attacks [120850]. 3. Addressing operational shortcomings and technical issues identified during testing, such as excessive vibrations in the 25mm cannon and problems with the aircraft's 'virtual reality' helmet [120850]. 4. Ensuring proper maintenance and monitoring of components prone to overheating and premature wear, such as the vertical tails [120850]. 5. Investigating and resolving any flaws in the computer system that could lead to grounding of the aircraft, as seen in the case of the US Marine Corps [120850].
Fixes 1. Conduct a comprehensive investigation into the technical systems and software of the F-35B Lightning to identify any potential faults or vulnerabilities that may have led to the crash [120850]. 2. Implement necessary software upgrades and patches to address any identified issues in the aircraft's software system [120850]. 3. Enhance cybersecurity measures to protect the F-35B's software from potential cyber-attacks and ensure its integrity and functionality [120850]. 4. Conduct thorough testing and validation of the software independently to verify its performance and reliability [120850]. 5. Address any operational shortcomings identified in previous tests, such as excessive vibrations in the 25mm cannon, problems with the aircraft's helmet system, overheating issues, premature wear of components, and vulnerability to fire [120850].
References 1. Retired Rear Admiral Chris Parry [Article 120850] 2. Ministry of Defence [Article 120850]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident having happened again at one_organization: The F-35B Lightning crash into the sea was the first mishap for the RAF's F-35B fleet and for the £3 billion aircraft carrier, HMS Queen Elizabeth, which left the UK seven months ago. This incident raises fresh questions about the F-35B, of which Britain currently has 24 [120850]. (b) The software failure incident having happened again at multiple_organization: The F-35 aircraft has faced multiple incidents in the past, including a catastrophic engine fire in 2014, a mid-flight fire in 2016, a fuel tube failure in 2018, a crash in 2019, and a mid-air collision in 2020. These incidents have occurred with F-35 jets from different organizations such as the USAF, US Marine Corp, and Japanese F-35s [120850].
Phase (Design/Operation) design, operation (a) The article mentions that the F-35 aircraft has been plagued by a catalogue of problems, which have sent costs soaring. There are concerns about shortcomings in the technical systems underpinning the new generation of warplanes that may leave them unable to function properly. The true cost of the British planes delivered is estimated to be over £150 million each to cover 'extras' such as software upgrades and spare parts. Additionally, there are concerns that the plane's software system is vulnerable to cyber-attacks and cannot be tested independently by the UK. These issues point towards potential failures in the design phase of the software system [120850]. (b) The article also highlights operational shortcomings related to the F-35 aircraft. In a mock air battle in 2015, the F-35 was defeated by an older generation F-16, indicating operational challenges. Furthermore, in 2020, Pentagon tests found 276 different faults in the jet's combat system, including issues with the 25mm cannon vibrating excessively, problems with the aircraft's 'virtual reality' helmet, overheating, premature wear of components in the vertical tails, and vulnerability to fire. The US Air Force temporarily grounded dozens of its F-35 stealth fighters due to an oxygen supply issue, and the Marine Corps had to ground its planes after flaws were found in the computer system. These operational issues suggest failures related to the operation phase of the software system [120850].
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the F-35B Lightning crash into the sea after taking off from HMS Queen Elizabeth was likely within the system. The incident raised questions about the F-35B's safety and performance, including concerns about technical systems underpinning the new generation of warplanes, software vulnerabilities to cyber-attacks, and operational shortcomings such as issues with the aircraft's combat system, cannon, virtual reality helmet, overheating, premature wear of components, and vulnerability to fire [120850]. (b) outside_system: The article does not provide specific information indicating that the software failure incident was due to contributing factors originating from outside the system.
Nature (Human/Non-human) human_actions (a) The software failure incident occurring due to non-human actions: The articles do not specifically mention any software failure incident occurring due to non-human actions. (b) The software failure incident occurring due to human actions: The incident involving the F-35B crash in the Mediterranean was attributed to a potential engine malfunction, which is a technical issue likely caused by human actions or errors. The investigation was focusing on technical or human error as potential causes of the crash [Article 120850].
Dimension (Hardware/Software) hardware, software (a) The software failure incident occurring due to hardware: - The incident involving the F-35B Lightning crashing into the sea was speculated to have occurred due to engine malfunction, which is a hardware-related issue [120850]. - The crash of the F-35B was attributed to technical or human error, with the Ministry of Defence stating that no hostile action was involved in the incident [120850]. (b) The software failure incident occurring due to software: - The F-35 aircraft has faced various software-related issues, including vulnerabilities to cyber-attacks, inability to function properly due to shortcomings in technical systems, and concerns about the software system's independence for testing [120850]. - Pentagon tests in 2020 identified 276 different faults in the F-35's combat system, including issues with the 25mm cannon, the aircraft's 'virtual reality' helmet, overheating, premature wear of components, and vulnerability to fire [120850].
Objective (Malicious/Non-malicious) non-malicious The software failure incident related to the F-35B Lightning crash into the sea after taking off from HMS Queen Elizabeth was non-malicious. The incident was attributed to technical or human error, with the Ministry of Defence stating that "no hostile action" was involved in the crash [Article 120850]. The crash was described as likely occurring due to engine malfunction, and the investigation was focusing on technical or human error [Article 120850].
Intent (Poor/Accidental Decisions) unknown The articles do not provide specific information related to a software failure incident caused by poor decisions or accidental decisions.
Capability (Incompetence/Accidental) development_incompetence (a) The software failure incident occurring due to development incompetence: - The F-35B crash into the sea was attributed to a likely engine malfunction, indicating a technical issue possibly related to the development or maintenance of the aircraft [120850]. - The F-35 program has faced a series of problems and faults, including operational shortcomings and vulnerabilities in the software system, raising concerns about the technical systems underpinning the new generation of warplanes [120850]. (b) The software failure incident occurring accidentally: - The incident involving the F-35B crash into the sea was described as an accident, with the Ministry of Defence stating that no hostile action was involved in the crash and the investigation focusing on technical or human error [120850]. - The pilot's ejection from the F-35 jet and subsequent parachute deployment, where he ended up dangling from the edge of the HMS Queen Elizabeth, was described as a series of events resulting from the accident rather than intentional actions [120850].
Duration unknown The articles do not provide specific information about a software failure incident related to the duration of the failure being permanent or temporary. Therefore, the duration of the software failure incident in this case is unknown.
Behaviour crash, other (a) crash: The software failure incident in this case resulted in a crash, where the F-35B Lightning aircraft crashed into the sea soon after taking off from the HMS Queen Elizabeth aircraft carrier [Article 120850]. (b) omission: There is no specific mention of the software failure incident omitting to perform its intended functions at an instance(s) in the provided articles. (c) timing: The software failure incident did not involve the system performing its intended functions too late or too early. (d) value: The software failure incident did not involve the system performing its intended functions incorrectly. (e) byzantine: The software failure incident did not involve the system behaving erroneously with inconsistent responses and interactions. (f) other: The software failure incident in this case involved a catastrophic engine fire caused by a fractured rotor, leading to the crash of the F-35B Lightning aircraft into the sea [Article 120850].

IoT System Layer

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

Other Details

Category Option Rationale
Consequence death, harm (a) death: People lost their lives due to the software failure - In the 1966 Palomares B-52 bomber crash incident, a USAF B-52G bomber carrying four hydrogen bombs crashed into a KC-135 tanker during mid-air over the Mediterranean Sea off the coast of Spain. The KC-135 was destroyed, and all four crew members aboard were killed. Additionally, three of the seven crew members on the B-52G bomber died [Article 120850]. (b) harm: People were physically harmed due to the software failure - In the recent F-35B Lightning crash incident, the RAF pilot was forced to eject from the aircraft, and he suffered minor injuries. The pilot was rescued by a search and rescue helicopter after ejecting from the stricken F-35 jet [Article 120850].
Domain government The failed system in the incident was related to the defense industry, specifically the F-35 stealth fighter jet used by the RAF and US military [Article 120850]. The F-35 is a fifth-generation combat aircraft designed for air-to-surface strikes and electronic warfare, equipped with advanced sensors for operating undetected in enemy airspace. The incident involving the crash of an F-35B Lightning into the Mediterranean Sea highlighted the sensitive technology onboard the aircraft, including top-secret radar and sensors [Article 120850]. The recovery operation for the crashed jet involved the use of deep water remote-controlled vehicles and inflatable lift bags to retrieve the aircraft from the sea bed [Article 120850].

Sources

Back to List