| Recurring |
one_organization, multiple_organization |
(a) The software failure incident having happened again at one_organization:
The article [55973] reports that Ryanair raged at the Air Traffic Service after a computer glitch that delayed 1,300 flights. This incident occurred at the National Air Traffic Service (NATS) headquarters in Swanwick, Hampshire, which is the same organization that experienced a previous software issue as mentioned in article [20547].
(b) The software failure incident having happened again at multiple_organization:
The article [55973] mentions that a 'complex' technical glitch affected 1,300 flights across Britain and Ireland. This incident indicates that similar software failure incidents have occurred at multiple organizations, not just at NATS. |
| Phase (Design/Operation) |
design, operation |
(a) The software failure incident related to the design phase can be seen in Article 20547, where a computer glitch at the air traffic control center in Swanwick, Hampshire, caused delays for thousands of airline passengers. The article mentions that the disruption was caused by a software issue that had been rectified. This indicates that the failure was due to contributing factors introduced during the system development or updates [20547].
(b) The software failure incident related to the operation phase is evident in Article 55973, where a technical glitch at the National Air Traffic Service's headquarters in Swanwick, Hampshire, led to delays for over 1,300 flights. The issue occurred during a shift change when the night-time operating system did not properly switch over to the daytime system, causing a communication problem with the internal telephones. This highlights a failure due to contributing factors introduced by the operation or misuse of the system [55973]. |
| Boundary (Internal/External) |
within_system |
(a) The software failure incident reported in the articles was primarily within the system. In Article 20547, the incident was attributed to a computer glitch at the air traffic control center, which was a software issue that had been rectified [20547]. Similarly, in Article 55973, the technical glitch that caused delays in over 1,300 flights was related to a temporary problem with the telephone computer system at the National Air Traffic Service's headquarters in Swanwick, Hampshire [55973]. These incidents point to internal system issues leading to the software failures. |
| Nature (Human/Non-human) |
non-human_actions |
(a) The software failure incident occurring due to non-human actions:
- Article 20547 reports a software issue at the air traffic control center in Swanwick, Hampshire, which was caused by a computer glitch. NATS mentioned that it was 'a software issue that has now been rectified' [20547].
- Article 55973 describes a technical glitch at the National Air Traffic Service's headquarters in Swanwick, Hampshire, which caused chaos at airports across the country. The issue was related to the telephone computer system not properly switching over from the night-time operating system to the daytime system, causing a communication problem with internal telephones [55973].
(b) The software failure incident occurring due to human actions:
- There is no specific mention in the articles about the software failure incidents being caused by human actions. |
| Dimension (Hardware/Software) |
software |
(a) The software failure incident occurring due to hardware:
- There is no specific mention in the articles about the software failure incident being caused by hardware issues [20547, 55973].
(b) The software failure incident occurring due to software:
- The software failure incidents in both articles were attributed to software issues. In Article 20547, the disruption at the air traffic control centre was caused by a computer glitch, described as 'a software issue that has now been rectified.' Similarly, in Article 55973, a 'temporary problem with the telephone computer system' at the National Air Traffic Service's headquarters caused delays for over 1,300 flights. The statement from Nats in Article 55973 also emphasized that the problem was related to a complex software system with more than a million lines of software [20547, 55973]. |
| Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident reported in Article 20547 was non-malicious. The incident was attributed to a computer glitch at the air traffic control center, which was described as a 'software issue that has now been rectified' by NATS [20547].
(b) In contrast, the software failure incident reported in Article 55973 was also non-malicious. The technical glitch that caused delays to 1,300 flights was due to a temporary problem with the telephone computer system at the National Air Traffic Service's headquarters in Swanwick, Hampshire. The issue was described as a 'complex' technical glitch that affected the communication system with internal telephones at the center [55973]. |
| Intent (Poor/Accidental Decisions) |
unknown |
(a) The software failure incident reported in Article 55973 was related to poor_decisions. The article mentions that a temporary problem with the telephone computer system at the National Air Traffic Service's headquarters in Swanwick, Hampshire caused mayhem at airports across the country, leading to delays in over 1,300 flights. The issue occurred when the night-time operating system did not properly switch over to the daytime system, causing a communication problem with the internal telephones [55973].
(b) The software failure incident reported in Article 20547 was related to accidental_decisions. The article mentions that a computer glitch was to blame for the disruption at the air traffic control center, and it was described as 'a software issue that has now been rectified.' The incident led to delays for thousands of airline passengers, but safety was maintained as the airspace was not closed [20547]. |
| Capability (Incompetence/Accidental) |
accidental |
(a) The software failure incidents reported in the articles seem to be more related to accidental factors rather than development incompetence. In the incident reported in Article 20547, a computer glitch was to blame for the disruption at the air traffic control center, which was described as a 'software issue that has now been rectified' [20547]. Similarly, in Article 55973, a 'complex' technical glitch at the National Air Traffic Service's headquarters in Swanwick, Hampshire caused mayhem at airports across the country, leading to delays in over 1,300 flights [55973]. These incidents point more towards accidental technical glitches rather than failures due to development incompetence. |
| Duration |
temporary |
(a) The software failure incident reported in Article 55973 was temporary. It caused mayhem at airports across the UK, with more than 1,300 flights delayed due to a temporary problem with the telephone computer system at the National Air Traffic Service's headquarters in Swanwick, Hampshire. The issue began early on Saturday morning and was finally fixed after 14 hours [55973].
(b) The software failure incident reported in Article 20547 was also temporary. It was caused by a computer glitch at the hi-tech air traffic control center at Swanwick, near Southampton, in Hampshire. The problem led to restrictions on the number of aircraft flying across the south of England and those taking off from airports. NATS mentioned that the software issue had been rectified, and most delays were no more than 20 minutes [20547]. |
| Behaviour |
crash, omission, other |
(a) crash:
- Article 20547 reports a software issue at the air traffic control center that led to delays in flights. The article mentions a computer glitch as the cause of the disruption, which can be indicative of a crash where the system loses state and fails to perform its intended functions [20547].
(b) omission:
- Article 55973 describes a technical glitch at the National Air Traffic Service's headquarters in Swanwick, Hampshire, which caused delays in over 1,300 flights. The issue occurred during a shift change when the night-time operating system did not properly switch over to the daytime system, leading to a communication problem with internal telephones. This omission to switch systems caused delays in flights [55973].
(c) timing:
- The articles do not specifically mention a timing-related failure where the system performs its intended functions but at the wrong time.
(d) value:
- The articles do not mention a value-related failure where the system performs its intended functions incorrectly.
(e) byzantine:
- The articles do not mention a byzantine-related failure where the system behaves erroneously with inconsistent responses and interactions.
(f) other:
- The behavior of the software failure incidents reported in the articles can be categorized as a combination of crash and omission. The system crashed due to a computer glitch at the air traffic control center, leading to delays in flights. Additionally, the omission of properly switching systems during a shift change also contributed to the disruption in air traffic control operations [20547, 55973]. |