Incident: RAF Top Guns Left Flying Blind Due to Helmet Glitches

Published Date: 2013-11-02

Postmortem Analysis
Timeline 1. The software failure incident with the RAF top guns' helmets occurred in 2013 (November) based on the article published on 2013-11-02 [23215].
System 1. Helmet Mounted Display Systems (HMDS) [23215]
Responsible Organization 1. The software failure incident was caused by technical glitches in the revolutionary helmet used by RAF top guns, leading to disorientation and blurring effect for the pilots [23215].
Impacted Organization 1. RAF pilots were impacted by the software failure incident as they were left flying blind at speeds of 1,000mph due to technical glitches with the helmet-mounted display system [23215].
Software Causes 1. The software cause of the failure incident was a technical fault in the Helmet Mounted Display Systems (HMDS) that led to a blurring effect known as green glow, disorientating the pilots and hindering their vision [23215].
Non-software Causes 1. Technical fault in the revolutionary helmet design led to disorientation and blurring effect for RAF pilots, causing them to fly blind at high speeds [23215]. 2. Excessive information displayed by the Helmet Mounted Display System (HMDS) overwhelmed pilots, leading to confusion and disorientation [23215]. 3. BAE Systems' alternative helmet design was removed from the programme as a cost-cutting measure, with the US opting for a different helmet design (G2) [23215].
Impacts 1. Pilots were left disorientated and unable to see where they were flying at speeds exceeding 1,000 miles per hour due to a series of technical glitches on the revolutionary helmet [23215]. 2. The technical fault caused a blurring effect known as green glow, which could have had fatal consequences [23215]. 3. The Helmet Mounted Display System (HMDS) produced too much information, leading to pilots becoming confused and disorientated by multiple images and information appearing just inches from their eyes, essentially blinding the pilots [23215].
Preventions 1. Thorough testing and validation of the Helmet Mounted Display Systems (HMDS) before deployment could have potentially prevented the software failure incident [23215]. 2. Implementing a more gradual introduction of information and data to the pilots through the HMDS to prevent overwhelming them with too much information at once [23215]. 3. Ensuring proper coordination and communication between the different parties involved in the development and testing of the helmet system, such as BAE Systems and the US Defence Department, to address any potential issues proactively [23215].
Fixes 1. Conduct thorough testing to identify and address issues with the Helmet Mounted Display Systems (HMDS) to ensure they work effectively [23215]. 2. Develop solutions to reduce the amount of information displayed on the HMDS to prevent pilots from becoming confused and disorientated by multiple images and data [23215]. 3. Collaborate with experts in software design and human factors to optimize the HMDS technology for better usability and effectiveness [23215].
References 1. Angus Robertson MP, the Scottish National Party’s defence spokesman [23215] 2. Defence Minister Philip Dunne MP [23215] 3. BAE Systems spokesperson [23215]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization, multiple_organization (a) The software failure incident related to the faulty Helmet Mounted Display Systems (HMDS) occurred within the same organization, specifically with the RAF pilots using the Joint Strike Fighter aircraft. The incident involved technical glitches in the helmet causing disorientation and blurring of images for the pilots, leading to them flying blind at high speeds [23215]. (b) The software failure incident involving the faulty HMDS also had implications beyond the RAF and the Joint Strike Fighter program. BAE Systems, a key manufacturer involved in producing an alternative helmet design, was removed from the program by the US Defence Department as a cost-cutting measure. This decision was made in favor of a US helmet design called the G2 (Generation 2) [23215].
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase is evident in the article. The article mentions that BAE Systems, which was involved in producing an alternative helmet to the faulty one, was removed from the helmet design program as a cost-cutting measure. This decision was made by the US Defence Department in favor of a US helmet called the G2. BAE Systems had produced demonstration helmets based on their design for the JSF, but these were never used on training or test flights. This indicates a failure in the design phase of the software system [23215]. (b) The software failure incident related to the operation phase is also highlighted in the article. It is mentioned that the Helmet Mounted Display System (HMDS) produced too much information, leading to pilots becoming confused and disorientated by multiple images and information appearing just inches from their eyes. This caused the pilots to be blinded and unable to effectively operate the system during flights. This points to a failure in the operation phase of the software system [23215].
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the RAF pilots being left flying blind at speeds of 1,000mph was primarily within the system. The technical glitches and faults were related to the Helmet Mounted Display Systems (HMDS) used by the pilots. The article mentions that the HMDS produced too much information, leading to pilots becoming confused and disorientated by multiple images and information appearing just inches from their eyes. This internal issue with the HMDS technology caused the pilots to be blinded and unable to see where they were flying [23215].
Nature (Human/Non-human) non-human_actions, human_actions (a) The software failure incident in this case was primarily due to non-human actions, specifically technical faults in the revolutionary helmet's Helmet Mounted Display Systems (HMDS). The glitches in the HMDS caused disorientation and a blurring effect for RAF pilots, leading to them flying blind at speeds exceeding 1,000 miles per hour. The excessive information displayed by the HMDS, not directly caused by human actions, overwhelmed the pilots and hindered their ability to see clearly [23215]. (b) Human actions were also involved in responding to the software failure incident. The Defence Minister Philip Dunne MP mentioned that testing was intended to reveal issues so that solutions could be developed, indicating a human response to the technical faults in the helmet's display systems. Additionally, BAE Systems, a key player in the development of the faulty helmet, was removed from the helmet design program by the US Defence Department, apparently as a cost-cutting measure. This decision was made by human actors in response to the software failure incident [23215].
Dimension (Hardware/Software) hardware (a) The software failure incident in the reported article seems to be related to hardware issues rather than software. The technical glitches and faults mentioned in the article primarily stem from the helmet hardware, specifically the Helmet Mounted Display Systems (HMDS). The article highlights how the HMDS produced too much information, leading to pilots becoming confused and disorientated by multiple images and information appearing before their eyes [23215]. (b) There is no specific mention of the software being the primary contributing factor to the failure incident in the article. The focus is more on the technical faults and glitches in the hardware components, particularly the helmet-mounted display system, causing disorientation and blurring for the pilots, rather than software-related issues [23215].
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident described in the article is non-malicious. The failure was due to technical glitches in the revolutionary helmet's Helmet Mounted Display System (HMDS), which led to disorientation and confusion among RAF pilots. The issue was related to the HMDS producing too much information, causing pilots to become overwhelmed by multiple images and data flashing before their eyes, ultimately leaving them flying blind at high speeds [23215].
Intent (Poor/Accidental Decisions) unknown The articles do not provide specific information about the intent behind the software failure incident related to the helmet-mounted display system on the Joint Strike Fighter aircraft. Therefore, it is unknown whether the failure was due 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 article as there were technical glitches in the revolutionary helmet designed for RAF top guns. The article mentions that the Helmet Mounted Display Systems (HMDS) produced too much information, leading to pilots becoming confused and disorientated by multiple images and information appearing just inches from their eyes. This overload of information caused the pilots to be blinded and unable to effectively operate the aircraft [23215]. (b) The software failure incident related to accidental factors is not explicitly mentioned in the provided article.
Duration temporary The software failure incident described in the article was temporary. The article mentions technical glitches and faults in the revolutionary helmet worn by RAF pilots, causing disorientation and blurring of images, leading to pilots being unable to see where they were flying at speeds exceeding 1,000 miles per hour. The issues with the Helmet Mounted Display Systems (HMDS) produced too much information, confusing and disorientating the pilots. The Defence Minister mentioned that testing was intended to reveal issues so that solutions could be developed, indicating that the incident was not permanent but rather due to specific circumstances related to the helmet's design and functionality [23215].
Behaviour crash, omission, other (a) crash: The software failure incident described in the articles can be categorized as a crash. The technical glitches in the revolutionary helmet caused the RAF top guns to be left flying blind at speeds exceeding 1,000 miles per hour, leading to a situation where the system lost its state and did not perform its intended function of providing pilots with all-around vision and awareness [23215]. (b) omission: The software failure incident can also be linked to omission. Due to a technical fault in the Helmet Mounted Display Systems (HMDS), the pilots were unable to see where they were flying, indicating an omission in the system's performance of providing crucial visual information to the pilots [23215]. (c) timing: There is no specific indication in the articles that the software failure incident was related to timing issues. (d) value: The software failure incident does not align with a failure due to the system performing its intended functions incorrectly. (e) byzantine: The software failure incident does not exhibit characteristics of a byzantine failure where the system behaves erroneously with inconsistent responses and interactions. (f) other: The software failure incident can be categorized as a failure due to information overload. The Helmet Mounted Display Systems (HMDS) produced too much information, leading to pilots becoming confused and disorientated by multiple images and data appearing before their eyes, ultimately blinding the pilots [23215].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence theoretical_consequence (a) death: People lost their lives due to the software failure The article does not mention any direct consequences of death resulting from the software failure incident. The focus is more on the potential dangers and risks posed by the technical glitches in the helmet-mounted display system for RAF pilots, emphasizing the disorientation and potential hazards faced by the pilots due to the software issues [23215].
Domain government (a) The failed system was intended to support the defense industry, specifically the Royal Air Force (RAF) pilots flying the Joint Strike Fighter aircraft [23215]. (l) The system failure incident was related to the defense industry, as the RAF pilots were experiencing technical glitches with their helmet-mounted display systems while flying the £100 million Joint Strike Fighter aircraft [23215].

Sources

Back to List