| Recurring |
one_organization, multiple_organization |
(a) The software failure incident related to the F-35B Joint Strike Fighters in Arizona due to flaws in the Autonomic Logistics Information System (ALIS) has happened again within the same organization. The article mentions that the Marine Fighter Attack Squadron 211 in Yuma had to ground its F-35s due to anomalies with the latest ALIS 2.0.2 software upgrade [60467].
(b) The software failure incident related to the F-35s experiencing hypoxia issues and being grounded has also happened at another organization. The 56th Fighter Wing of Luke Air Force Base in Arizona grounded its F-35s due to pilots experiencing symptoms of hypoxia, and investigators were unable to identify a root cause of the issue [60467]. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in the article where flaws were found in the Autonomic Logistics Information System (ALIS) that transmits details about a jet's mechanical condition to the ground-based computer system. The issues were specifically related to the ALIS 2.0.2 software upgrade, which led to anomalies and necessitated the grounding of the F-35B Joint Strike Fighters in Arizona [60467].
(b) The software failure incident related to the operation phase is evident in the article where pilots experienced symptoms of hypoxia, or lack of oxygen, during flights of the F-35 planes. This operational issue prompted the grounding of the planes, and investigations were conducted to identify the root cause, including maintenance and aircrew flight equipment procedures [60467]. |
| Boundary (Internal/External) |
within_system, outside_system |
(a) The software failure incident related to the F-35B Joint Strike Fighters in Arizona was primarily within the system. The article mentions that the grounding of the F-35s was due to flaws found in the Autonomic Logistics Information System (ALIS), which is an internal computer system transmitting details about the jet's mechanical condition [60467]. The issues with the ALIS software, specifically the latest ALIS 2.0.2 software upgrade, led to anomalies and the need to ensure the ground-based ALIS system was working properly before operations could continue [60467].
(b) Additionally, the incident involved external factors contributing to the failure. For example, the grounding of the F-35s was also related to an oxygen-supply problem aboard the warplanes, which was an external factor affecting the aircraft's operation [60467]. The article mentions that investigators were unable to identify a root cause of the oxygen-supply issue, which prompted the grounding of the planes [60467]. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident in the F-35B Joint Strike Fighters was primarily due to non-human actions. The incident was related to flaws found in the Autonomic Logistics Information System (ALIS) that transmits details about the jet's mechanical condition to the ground-based computer system. This system allows for automatic scheduling of maintenance for the aircraft [60467].
(b) Human actions also played a role in the software failure incident. Major Gen. Mark Wise, commander of the 3rd Marine Aircraft Wing, made the decision to suspend flights for Squadron 211 due to anomalies with the latest ALIS 2.0.2 software upgrade. Additionally, experts are continuing to probe the issue of pilots experiencing symptoms of hypoxia, and precautionary steps are being taken, such as increasing the minimum levels for backup oxygen systems for each flight [60467]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident related to hardware can be seen in the article where the F-35 stealth fighters were grounded due to an oxygen-supply problem aboard the expensive warplanes [60467]. This issue led to pilots experiencing symptoms of hypoxia, or lack of oxygen, which was a hardware-related problem with the aircraft's oxygen supply system.
(b) The software failure incident related to software can be observed in the same article where flaws were found in the Autonomic Logistics Information System (ALIS) of the F-35 jets, which transmits details about a jet's mechanical condition to the ground-based computer system [60467]. The grounding of the F-35s was due to anomalies with the latest ALIS 2.0.2 software upgrade, highlighting a software-related issue affecting the aircraft's maintenance scheduling system. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the F-35B Joint Strike Fighters in Arizona was non-malicious. The incident was caused by flaws in the Autonomic Logistics Information System (ALIS) that transmits details about a jet's mechanical condition to the ground-based computer system. The issues with the ALIS system led to the grounding of the F-35s for maintenance and safety checks, but there was no indication of any malicious intent behind the software failure incident [60467]. |
| Intent (Poor/Accidental Decisions) |
unknown |
(a) The software failure incident related to the grounding of F-35B Joint Strike Fighters in Arizona was not due to poor decisions but rather due to anomalies with the latest ALIS 2.0.2 software upgrade. Maj. Gen. Mark Wise mentioned that there was nothing wrong with the performance or safety of the aircraft itself, but it was imperative to ensure the ground-based ALIS system was working properly before operations continued [60467]. This indicates that the failure was not due to poor decisions but rather a need to ensure the software system was functioning correctly. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
(a) The software failure incident related to development incompetence is evident in the article. The grounding of the F-35B Joint Strike Fighters in Arizona was due to flaws found in the Autonomic Logistics Information System (ALIS) computer system. The article mentions that the grounding was a result of anomalies with the latest ALIS 2.0.2 software upgrade, indicating issues with the software development process [60467].
(b) The software failure incident related to accidental factors is also highlighted in the article. The grounding of the F-35s was prompted by incidents where pilots experienced symptoms of hypoxia, or lack of oxygen, due to an oxygen-supply problem. Investigators were unable to identify a root cause of the issue, and specific concerns were eliminated as possible causes, indicating an accidental nature of the problem [60467]. |
| Duration |
temporary |
The software failure incident related to the F-35B Joint Strike Fighters in Arizona was temporary. The incident led to the grounding of the F-35 stealth fighters for 11 days due to anomalies with the ALIS 2.0.2 software upgrade [60467]. The grounding was necessary to ensure the ground-based ALIS system was working properly before operations could continue. Additionally, the article mentions that the software issue prompted the 56th Fighter Wing of Luke Air Force Base to ground its F-35s, but specific concerns were eliminated as possible causes, indicating a temporary nature of the failure [60467]. |
| Behaviour |
other |
(a) crash: The software failure incident in the F-35B Joint Strike Fighters was not a crash where the system lost state and did not perform any of its intended functions. The issue was related to anomalies with the ALIS software upgrade, which led to the grounding of the aircraft for maintenance checks [60467].
(b) omission: The software failure incident was not due to the system omitting to perform its intended functions at an instance(s). The ALIS system was transmitting details about the jet's mechanical condition to the ground-based computer system, but the anomalies in the software required maintenance checks to ensure proper functioning [60467].
(c) timing: The software failure incident was not due to the system performing its intended functions correctly but too late or too early. The issue with the ALIS software upgrade did not involve timing issues but rather anomalies that required grounding the aircraft for maintenance checks [60467].
(d) value: The software failure incident was not due to the system performing its intended functions incorrectly. The issue with the ALIS software was related to anomalies that needed to be addressed to ensure the proper functioning of the ground-based computer system [60467].
(e) byzantine: The software failure incident was not due to the system behaving erroneously with inconsistent responses and interactions. The ALIS system was identified as the source of the problem, and steps were taken to investigate and address the anomalies in the software upgrade to resume operations safely [60467].
(f) other: The software failure incident in the F-35B Joint Strike Fighters was primarily related to anomalies in the ALIS software upgrade, which necessitated grounding the aircraft for maintenance checks. The incident did not involve a crash, omission, timing issue, value error, or byzantine behavior [60467]. |