| Recurring |
one_organization |
(a) The software failure incident related to the loss of the Meteor-M satellite due to a programming error is an example of a failure happening again within the same organization, Roscosmos. This incident occurred after a previous technical glitch at the Vostochny spaceport in Russia, where delays and massive costs overruns were experienced during the launch of the first rocket from Vostochny in April last year [66003]. |
| Phase (Design/Operation) |
design |
(a) The software failure incident in Article 66003 was related to the design phase. Russian deputy prime minister Dmitry Rogozin mentioned that the loss of the satellite was due to an embarrassing programming error. The rocket carrying the satellites had been programmed with the wrong coordinates, specifically given bearings for take-off from a different cosmodrome – Baikonur – instead of the correct coordinates for take-off from Vostochny cosmodrome. This error in the design phase of programming the rocket's coordinates led to the failure of the mission [66003]. |
| Boundary (Internal/External) |
within_system |
(a) within_system: The software failure incident in the article was attributed to an embarrassing programming error within the system. Russian deputy prime minister Dmitry Rogozin mentioned that the failure of the satellite launch was caused by human error, specifically a programming mistake where the rocket carrying the satellites was programmed with the wrong coordinates, as if it was taking off from a different cosmodrome [66003]. This indicates that the failure originated from within the system due to an internal programming error. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident in the article was attributed to a programming error that occurred due to non-human actions. Specifically, the failure was caused by the rocket being programmed with the wrong coordinates, leading to the loss of the satellite launched from the Vostochny cosmodrome. This error was not a deliberate human action but rather a mistake in the programming process [66003].
(b) However, the deputy prime minister Dmitry Rogozin mentioned that the failure was caused by human error. He stated that the rocket carrying the satellites had been given the wrong coordinates for take-off, as if it was launching from a different cosmodrome (Baikonur) instead of Vostochny. This indicates that the human action of incorrectly inputting the coordinates contributed to the software failure incident [66003]. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident mentioned in the article is attributed to a programming error, specifically a mistake in the coordinates programmed into the rocket carrying the satellites. This error led to the loss of the satellite launched from the Vostochny cosmodrome in Russia [66003].
(b) The software failure incident is directly linked to a programming error, indicating that the contributing factors that led to the failure originated in the software used to program the rocket. The incorrect coordinates programmed into the rocket's system caused it to behave as if it was taking off from a different cosmodrome, ultimately resulting in the loss of the satellite [66003]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident related to the loss of the Meteor-M satellite was non-malicious. Russian deputy prime minister Dmitry Rogozin attributed the failure to an embarrassing programming error, specifically stating that the rocket carrying the satellites had been programmed with the wrong coordinates due to human error. He mentioned that the rocket was programmed as if it was taking off from a different cosmodrome, Baikonur, instead of Vostochny. This indicates that the failure was not due to malicious intent but rather a mistake in the programming process [66003]. |
| Intent (Poor/Accidental Decisions) |
poor_decisions |
(a) The software failure incident related to the loss of the Russian weather satellite Meteor-M was attributed to an embarrassing programming error. Russian deputy prime minister Dmitry Rogozin mentioned that the failure was caused by human error, specifically a programming mistake where the rocket carrying the satellites was programmed with the wrong coordinates, as if it was taking off from a different cosmodrome (Baikonur) instead of Vostochny cosmodrome. This indicates that the failure was a result of poor decisions made during the programming process [66003]. |
| Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident in the article was attributed to development incompetence. Russian deputy prime minister Dmitry Rogozin mentioned that the loss of the satellite was due to an embarrassing programming error caused by human error. The rocket carrying the satellites had been programmed with the wrong coordinates, as if it was taking off from a different cosmodrome, leading to the failure [66003]. |
| Duration |
temporary |
The software failure incident related to the loss of the Meteor-M satellite due to a programming error was temporary. The incident was attributed to human error in programming the rocket with the wrong coordinates, specifically using the coordinates for take-off from a different cosmodrome (Baikonur) instead of the correct coordinates for Vostochny cosmodrome. This indicates that the failure was due to specific circumstances related to the incorrect programming rather than a permanent issue affecting all circumstances [66003]. |
| Behaviour |
other |
(a) crash: The software failure incident in the article is not described as a crash where the system loses state and does not perform any of its intended functions. The failure was attributed to a programming error that led to the loss of a satellite [66003].
(b) omission: The incident does not indicate that the failure was due to the system omitting to perform its intended functions at an instance(s). Instead, it was caused by a programming error related to incorrect coordinates [66003].
(c) timing: The failure was not related to the system performing its intended functions correctly but too late or too early. It was a result of a programming error in setting the coordinates for the rocket launch [66003].
(d) value: The software failure incident was not due to the system performing its intended functions incorrectly in terms of the value it provided. It was a result of a programming error in setting the launch coordinates [66003].
(e) byzantine: The incident does not suggest that the failure was due to the system behaving erroneously with inconsistent responses and interactions. It was attributed to a programming error in setting the wrong coordinates for the rocket launch [66003].
(f) other: The behavior of the software failure incident in the article can be categorized as a failure caused by a programming error that led to the loss of a satellite. The error involved setting the wrong coordinates for the rocket launch, which resulted in the failure of the mission [66003]. |