| Recurring |
one_organization |
(a) The software failure incident having happened again at one_organization:
The software failure incident involving an electrical fire in a control panel on a Boeing 787 Dreamliner test aircraft occurred in November, leading to a halt in the test flight program [3570]. This incident was not the first setback for Boeing's Dreamliner program, as the article mentions a series of delays and challenges that have plagued the project, including issues with production, supply chain problems, and assembly difficulties [4056].
(b) The software failure incident having happened again at multiple_organization:
There is no specific mention in the provided articles about similar software failure incidents occurring at other organizations or with their products and services. |
| Phase (Design/Operation) |
design |
(a) The software failure incident related to the design phase can be inferred from the articles. The incident on the Boeing 787 Dreamliner test aircraft was caused by a failure in the P100 panel in the electronics bay, which ignited a nearby insulation blanket [3570]. This failure was attributed to the design of the power panel and its interaction with the systems on the aircraft. The article mentions that the P100 panel receives power from the left engine and distributes it to various systems, and in the event of a failure, backup power sources are designed to engage automatically to ensure safe operation [3570].
(b) The software failure incident related to the operation phase is not explicitly mentioned in the articles provided. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident reported in the articles is primarily within the system. The incident involved a power panel failure in the electronics bay of a Boeing 787 Dreamliner test aircraft, which led to an electrical fire igniting a nearby insulation blanket [3570]. Boeing mentioned that the P100 panel, responsible for distributing power from the left engine to various systems, failed during the flight, causing the insulation blanket to catch fire. The backup power sources were designed to engage automatically in case of such a failure to ensure the safe operation of the airplane [3570].
(b) outside_system: There is no information in the articles to suggest that the software failure incident was caused by contributing factors originating from outside the system. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident occurring due to non-human actions:
- The software failure incident on the Boeing 787 Dreamliner test aircraft was caused by a power panel failure in the electronics bay, which ignited a nearby insulation blanket. This failure was a non-human action as it was due to a technical issue with the P100 panel receiving power from the left engine, leading to the fire [3570].
- The incident led to an emergency landing in Laredo, Texas, and the suspension of the test program. The backup power sources were designed to automatically engage in case of a failure to ensure the safe operation of the airplane [3570].
- The insulation blanket self-extinguished once the fault in the P100 panel cleared, indicating that the failure was due to technical issues rather than human actions [3570].
(b) The software failure incident occurring due to human actions:
- The delays and setbacks in the Dreamliner program, including the software and hardware changes, replacement of electrical power panels, and final software changes, were attributed to human actions and decisions made during the development and testing phases of the aircraft [4056].
- Boeing faced challenges with out-of-sequence production work, parts shortages, software and systems integration activities, supply chain problems, and slow completion of work from suppliers, all of which were influenced by human actions and decisions within the company [4056].
- The delays in the Dreamliner program, including the machinists strike, supply shortages, assembly problems, and the need for reinforcement in certain areas of the aircraft, were all consequences of human actions and decisions that impacted the development and delivery schedule of the aircraft [4056]. |
| Dimension (Hardware/Software) |
hardware, software |
(a) The software failure incident occurring due to hardware:
- The incident reported in Article 3570 was related to a fire aboard a Boeing 787 Dreamliner test aircraft, which started when an electronics bay power panel failed, igniting a nearby insulation blanket. This failure was attributed to the P100 panel in the aft electronics bay failing during the flight, causing the insulation blanket to catch fire [3570].
(b) The software failure incident occurring due to software:
- The software failure incident reported in Article 4056 was related to an on-board electrical fire in a control panel of the Dreamliner test flight program. This incident led to the halt of the test flight program and required the installation of replacement electrical power panels and final software changes over the next several months [4056]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the Boeing 787 Dreamliner test aircraft was non-malicious. The incident was caused by a power panel failure in the electronics bay, which ignited a nearby insulation blanket, leading to a fire onboard the aircraft. Boeing stated that the P100 panel, which failed during the flight, caused the insulation blanket to catch fire. The incident resulted in an emergency landing and the suspension of the test program, impacting the delivery schedule of the Dreamliner [3570].
(b) The software failure incident was not malicious but rather a result of technical issues within the aircraft's systems. The failure of the power panel in the electronics bay was not intentional but rather a technical malfunction that led to the fire onboard the 787 Dreamliner test aircraft. Boeing mentioned that backup power sources were designed to automatically engage in case of such failures to ensure the safe operation of the airplane [3570]. |
| Intent (Poor/Accidental Decisions) |
unknown |
The software failure incident related to the Boeing 787 Dreamliner test aircraft was not directly caused by poor or accidental decisions related to software. The incident was specifically attributed to a power panel failure in the electronics bay, which ignited an insulation blanket nearby, leading to a fire [3570]. The failure was described as a technical issue rather than a result of poor or accidental decisions related to software development or implementation. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incident in the Boeing 787 Dreamliner incident was not directly attributed to development incompetence. The incident was specifically related to a power panel failure in the electronics bay, which caused an insulation blanket to catch fire [3570].
(b) The software failure incident in the Boeing 787 Dreamliner incident was accidental in nature. The fire that occurred on the test aircraft was a result of a power panel failure, which ignited a nearby insulation blanket. This incident was not intentional but rather an unintended consequence of the power panel failure [3570]. |
| Duration |
temporary |
The software failure incident related to the Boeing 787 Dreamliner test aircraft was temporary. The incident occurred when an electronics bay power panel (P100 panel) failed during the flight, causing a nearby insulation blanket to catch fire. Backup power sources were designed to automatically engage in case of such a failure to ensure the safe operation of the airplane [3570]. Following the incident, Boeing took actions to replace the failed panel and implement software and hardware changes gradually over the next few weeks to clear the way for function and reliability testing [4056]. |
| Behaviour |
other |
(a) crash: The incident involving the Boeing 787 Dreamliner test aircraft was not a crash but a fire incident caused by a power panel failure, leading to an emergency landing in Laredo, Texas [3570].
(b) omission: There is no specific mention of the software failure incident being related to the system omitting to perform its intended functions at an instance(s) in the articles.
(c) timing: The software failure incident did not involve the system performing its intended functions too late or too early [3570, 4056].
(d) value: The software failure incident did not involve the system performing its intended functions incorrectly [3570, 4056].
(e) byzantine: The software failure incident did not involve the system behaving erroneously with inconsistent responses and interactions [3570, 4056].
(f) other: The behavior of the software failure incident was related to a power panel failure igniting a nearby insulation blanket, leading to a fire on the aircraft, which is not specifically categorized under the options provided [3570]. |