| Recurring |
unknown |
(a) The software failure incident having happened again at one_organization:
The article does not mention any specific details about a previous software failure incident within Blue Origin or with its products and services. Therefore, it is unknown if a similar incident has happened before within the same organization [132402].
(b) The software failure incident having happened again at multiple_organization:
The article mentions that Virgin Galactic also aims to fly paying customers to the edge of space, and SpaceX has flown a series of NASA astronaut crews to the International Space Station. This indicates that multiple organizations are involved in similar spaceflight activities, but there is no specific mention of a software failure incident happening again at other organizations or with their products and services [132402]. |
| Phase (Design/Operation) |
operation |
(a) The article does not provide specific information about a software failure incident related to the design phase of the system development process. Therefore, it is unknown if the incident was caused by contributing factors introduced during system development, system updates, or procedures to operate or maintain the system.
(b) The article mentions that the New Shepard rocket experienced a serious problem about a minute after launch, leading to the emergency abort system kicking in and jettisoning the capsule away from the booster. Blue Origin stated on Twitter that there was a booster "failure," but did not provide additional details on what went wrong [132402]. This indicates that the failure was related to the operation phase, possibly due to factors introduced during the operation of the system. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the Blue Origin New Shepard rocket can be categorized as within_system. The article mentions that during the flight, at about 1 minute and 5 seconds into the flight, bright flames burst from the booster, and the capsule's emergency abort system kicked in, shooting it away from the rocket [132402]. This indicates that the failure was within the system itself, likely related to the rocket's software or control systems. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident in the Blue Origin New Shepard rocket incident appears to be related to a non-human action. The article mentions that the emergency abort system of the unmanned capsule kicked in after a serious problem occurred about a minute after the launch, leading to the successful jettisoning of the capsule away from the booster [132402]. This indicates that the failure was triggered by factors within the system itself rather than being directly caused by human actions. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident related to hardware:
- The article does not specifically mention any hardware-related issues contributing to the software failure incident reported in the news article [132402].
(b) The software failure incident related to software:
- The article mentions that during the flight of the Blue Origin's New Shepard rocket, at about 1 minute and 5 seconds into flight, bright flames burst from the booster, and the capsule's emergency abort system kicked in, shooting it away from the rocket [132402].
- Blue Origin stated on Twitter that there was a booster "failure," but did not provide additional details on what went wrong [132402].
- The article highlights that before flying any people, Blue Origin rigorously tested the capsule's emergency escape system on the ground and twice during flight, emphasizing safety as the highest value at Blue Origin [132402].
- The mishap with the New Shepard rocket led to the need for an investigation by the Federal Aviation Administration to determine if any system, process, or procedure related to the mishap affected public safety before the vehicle can return to flight [132402]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The articles do not mention any indication of a malicious software failure incident related to the Blue Origin's New Shepard rocket incident. It appears that the failure was not due to contributing factors introduced by humans with the intent to harm the system [132402].
(b) The software failure incident related to the Blue Origin's New Shepard rocket was described as an anomaly during the flight, with the capsule's emergency abort system kicking in to ensure the safety of the mission. Blue Origin mentioned responding to an issue at their launch site and later referred to a booster "failure," without providing additional details on what went wrong. The incident was characterized as unplanned, and the company emphasized its commitment to safety and redundancy in the system design [132402]. |
| Intent (Poor/Accidental Decisions) |
accidental_decisions |
(a) The articles do not provide information about the software failure incident being related to poor decisions.
(b) The software failure incident related to the Blue Origin's New Shepard rocket was not attributed to poor decisions but rather to an unexpected anomaly during the flight, leading to the emergency abort system kicking in to ensure the safety of the mission [132402]. |
| Capability (Incompetence/Accidental) |
unknown |
(a) The articles do not mention any software failure incident occurring due to development incompetence [132402].
(b) The software failure incident related to the Blue Origin's New Shepard rocket was not attributed to accidental factors but rather to a booster failure, which triggered the emergency abort system [132402]. |
| Duration |
temporary |
(a) The software failure incident in the Blue Origin New Shepard rocket incident appears to be temporary. The article mentions that there was a booster "failure" during the flight, but it did not provide specific details on what exactly went wrong with the software or the contributing factors that led to the failure [132402]. The emergency abort system kicked in, indicating that the system was able to respond to the anomaly and successfully jettison the capsule away from the booster. Blue Origin stated that the capsule escape system functioned as designed, suggesting that the software failure was not permanent but rather a temporary issue that occurred during the flight. |
| Behaviour |
crash, other |
(a) crash: The software failure incident in the Blue Origin's New Shepard rocket resulted in a crash as the emergency abort system kicked in about a minute after launch, leading to the capsule being jettisoned away from the booster [132402].
(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 article.
(c) timing: The timing of the software failure incident was crucial as it occurred about 1 minute and 5 seconds into the flight, just after the vehicle entered "Max Q" or the moment of greatest aerodynamic pressure [132402].
(d) value: The software failure incident did not involve the system performing its intended functions incorrectly; rather, it led to the emergency abort system kicking in to ensure the safety of the mission [132402].
(e) byzantine: The software failure incident did not exhibit characteristics of a byzantine failure where the system behaves erroneously with inconsistent responses and interactions; instead, the emergency abort system functioned as designed in response to the anomaly [132402].
(f) other: The behavior of the software failure incident can be categorized as an emergency response triggered by an anomaly during flight, leading to the successful jettisoning of the capsule away from the booster to ensure a safe landing [132402]. |