Recurring |
one_organization, multiple_organization |
(a) The software failure incident having happened again at one_organization:
- The F-35 fighter jet, manufactured by Lockheed Martin, has been involved in multiple incidents, including crashes and malfunctions [122907].
- The incident in South Korea, where a pilot had to make an emergency 'belly landing' due to landing gear failure, is not the first for the F-35. Previous incidents include a British F-35 toppling into the sea during a failed takeoff and a US pilot ejecting after a crash on landing in Florida [122907].
(b) The software failure incident having happened again at multiple_organization:
- The F-35 fighter jet, developed by Lockheed Martin, has faced issues in different countries, such as the UK, the US, and Japan, with incidents ranging from crashes to malfunctions [122907].
- The South Korean incident is part of a series of incidents involving the F-35, indicating that similar software failure incidents have occurred with this aircraft model across different organizations and countries [122907]. |
Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase is evident in the case of the F-35 fighter jet incidents. The article mentions that the South Korean F-35A fighter jet had to make an emergency 'belly landing' due to a malfunction in the air, specifically with the landing gear failing to extend. This failure was attributed to electronic issues, indicating a design flaw or fault introduced during the system development or updates [122907].
(b) The software failure incident related to the operation phase is highlighted by the various incidents involving F-35 fighter jets crashing or experiencing malfunctions during operation. For example, a US pilot was forced to eject midair after an F-35 jet crashed in South Carolina in 2018, with the US Air Force attributing the crash to pilot and plane systems faults. Additionally, a Japanese F-35 crashed into the Pacific Ocean near Japan in 2019, with officials blaming the crash on spatial disorientation, which could be considered an operational issue [122907]. |
Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident related to the F-35 fighter jet in South Korea was primarily within the system. The incident was caused by electronic issues within the jet's equipment, leading to the failure of the landing gear to extend properly, forcing the pilot to make an emergency 'belly landing' [122907].
(b) outside_system: There is no specific mention in the articles of contributing factors originating from outside the system that led to the software failure incident. |
Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident occurring due to non-human actions:
- The article reports that the South Korean F-35A fighter jet made an emergency 'belly landing' due to a malfunction in the air, specifically mentioning that the landing gear failed to extend, leading to the pilot deciding to land the jet on its belly [Article 122907].
- The incident was attributed to electronic issues causing the equipment failure, as stated by a South Korean Air Force spokesman [Article 122907].
(b) The software failure incident occurring due to human actions:
- The US Air Force attributed a previous crash of an F-35 to the pilot and plane systems being at fault [Article 122907].
- The article mentions a British F-35B crashing into the Mediterranean during takeoff, with a possible contributing factor being a red plastic rain cover accidentally left on and sucked into an engine, indicating a potential human error [Article 122907]. |
Dimension (Hardware/Software) |
hardware |
(a) The software failure incident occurring due to hardware:
- The incident involving the South Korean F-35A fighter jet making an emergency 'belly landing' was attributed to equipment failure due to electronic issues, which is a hardware-related problem [122907].
(b) The software failure incident occurring due to software:
- The article does not mention any specific software-related contributing factors that led to the incident. Therefore, it is unknown if the failure originated in the software. |
Objective (Malicious/Non-malicious) |
non-malicious |
(a) The articles do not mention any indication of a malicious software failure incident.
(b) The software failure incident related to the emergency 'belly landing' of the South Korean F-35A fighter jet was non-malicious. The incident was attributed to equipment failure due to electronic issues, forcing the pilot to make the unprecedented decision to perform a belly landing [122907]. |
Intent (Poor/Accidental Decisions) |
unknown |
The articles do not provide information about a software failure incident related to poor_decisions or accidental_decisions. |
Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident related to development incompetence is not explicitly mentioned in the provided article [122907].
(b) The software failure incident related to an accidental factor is mentioned in the article. The incident involving the South Korean F-35A fighter jet making an emergency 'belly landing' was due to equipment failure caused by electronic issues, forcing the pilot to take unprecedented action [122907]. |
Duration |
unknown |
The articles do not mention any specific software failure incident related to the F-35 fighter jet incidents reported. Therefore, the duration of the software failure incident, whether permanent or temporary, cannot be determined from the provided articles [122907]. |
Behaviour |
crash, other |
(a) crash: The incident involving the South Korean F-35A fighter jet making an emergency 'belly landing' was due to a malfunction in the air, specifically the landing gear failing to extend. This led to the pilot deciding to land the aircraft on its belly, indicating a crash scenario [122907].
(b) omission: There is no specific mention of a software failure incident related to omission in the provided article.
(c) timing: There is no specific mention of a software failure incident related to timing in the provided article.
(d) value: There is no specific mention of a software failure incident related to value in the provided article.
(e) byzantine: There is no specific mention of a software failure incident related to Byzantine behavior in the provided article.
(f) other: The incident involving the South Korean F-35A fighter jet making an emergency 'belly landing' due to a malfunction in the air, specifically the landing gear failing to extend, could also be categorized as an 'other' behavior as it involves a unique scenario of the system losing its intended functionality [122907]. |