| Recurring |
one_organization, multiple_organization |
(a) The software failure incident related to the Boeing 777X involves an "upcoming major software update with the software load of flight control" and a "software fix for the un-commanded pitch event that occurred on December 8, 2020" [116254]. This indicates that there have been software issues within Boeing itself, specifically with the 737 MAX planes in the past, which had software flaws that caused fatal crashes.
(b) The article mentions that European regulators have stated they will subject the Boeing 777X to extra scrutiny after the fatal crashes of the 737 MAX planes, which were also related to software flaws [116254]. This suggests that similar incidents related to software failures have occurred in multiple organizations within the aviation industry. |
| Phase (Design/Operation) |
design |
(a) The software failure incident related to the development phase of design is evident in the article. The U.S. Federal Aviation Administration (FAA) cited concerns about lack of data, lack of a preliminary safety assessment, and issues with an upcoming major software update with the software load of flight control for the Boeing 777X [116254]. These issues indicate that the failure was due to contributing factors introduced during the design and development phases of the aircraft.
(b) The software failure incident related to the development phase of operation is not explicitly mentioned in the provided article. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the Boeing 777X certification process involves issues that are within the system. The article mentions concerns about an "upcoming major software update with the software load of flight control" and the need for Boeing to implement corrective actions identified by the root cause investigation to prevent similar issues in the future [116254]. These issues indicate that the failure is primarily due to factors originating from within the system itself, such as software updates and control mechanisms. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident related to non-human actions:
The software failure incident related to the Boeing 777X certification process was primarily due to issues with the software, including an "upcoming major software update with the software load of flight control" and a "software fix for the un-commanded pitch event" that occurred on December 8, 2020. The FAA expressed concerns about the delays in software updates and the need for better visibility into the causes of these delays. The agency also emphasized the importance of Boeing implementing a robust process to prevent similar issues in the future and ensure that such failures are not systemic problems [116254].
(b) The software failure incident related to human actions:
The article does not provide specific information about the software failure incident being directly caused by human actions. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident related to hardware:
- The article mentions an "upcoming major software update with the software load of flight control" and a "software fix for the un-commanded pitch event" that occurred on December 8, 2020, indicating a hardware-related issue [116254].
(b) The software failure incident related to software:
- The article highlights concerns about software, mentioning "software load dates are continuously sliding" and the FAA needing better visibility into the causes of delays related to software updates [116254]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The articles do not mention any malicious intent or actions related to the software failure incident. The issues cited by the FAA in the letter to Boeing primarily revolve around concerns regarding lack of data, lack of a preliminary safety assessment, upcoming major software updates, delays in software load dates, and the need for Boeing to implement a robust process to prevent similar issues in the future. These factors point towards non-malicious contributing factors rather than intentional harm to the system [116254]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The articles do not provide specific information about a software failure incident related to poor decisions or accidental decisions. |
| Capability (Incompetence/Accidental) |
development_incompetence, unknown |
(a) The software failure incident related to development incompetence is evident in the case of the Boeing 777X development. The FAA cited concerns about lack of data, lack of a preliminary safety assessment, an upcoming major software update with flight control software load, and continuous sliding software load dates. The agency also mentioned the need for Boeing to implement a robust process to prevent similar issues in the future, indicating a lack of professional competence in the development process [116254].
(b) The software failure incident related to accidental factors is not explicitly mentioned in the provided article. |
| Duration |
unknown |
The articles do not provide information about a specific software failure incident being either permanent or temporary. The focus of the articles is on the certification process and delays related to the Boeing 777X aircraft, including concerns about software updates and safety issues. |
| Behaviour |
other |
(a) crash: The software failure incident mentioned in the articles does not specifically describe a crash where the system loses state and does not perform any of its intended functions.
(b) omission: The articles do not mention a specific instance where the system omitted to perform its intended functions at an instance(s).
(c) timing: The software failure incident does not relate to a timing issue where the system performed its intended functions too late or too early.
(d) value: The articles do not provide information about the software failure incident being related to the system performing its intended functions incorrectly.
(e) byzantine: The software failure incident does not align with a byzantine behavior where the system behaves erroneously with inconsistent responses and interactions.
(f) other: The behavior of the software failure incident is related to issues with software updates, lack of data, lack of a preliminary safety assessment, delays in software load dates, un-commanded pitch events, and the need for Boeing to implement a robust process to prevent similar issues in the future. These factors point to a combination of delays, safety concerns, and the need for corrective actions rather than fitting into the specific categories mentioned above. |