Recurring |
one_organization, multiple_organization |
(a) The software failure incident having happened again at one_organization:
- United Airlines experienced a software failure incident related to the grounding of its Boeing 777-200 planes due to missed inspections of the front edges of the wings and wing slats [132248].
- This incident is not the first time United Airlines faced issues with its aircraft. In February 2021, a United flight to Honolulu suffered engine failure and debris showered over nearby cities, leading to an emergency landing [132248].
(b) The software failure incident having happened again at multiple_organization:
- The article mentions the grounding of United's Boeing 777 planes equipped with Pratt & Whitney engines after an engine failure incident in Denver [132248].
- The article also discusses the grounding of Boeing 737 Max aircraft following two deadly crashes involving Lion Air and Ethiopian Airlines, leading to a $200 million fine for Boeing over misleading safety assurances [132248]. |
Phase (Design/Operation) |
design |
(a) The software failure incident related to the design phase can be seen in the case of United Airlines grounding about 25 of its Boeing 777-200 planes due to the failure to inspect the front edges of the wings, specifically the wing slats. This failure in required inspections during the design phase led to flight cancellations and subsequent issues with the hydraulic system of one of the cleared aircraft [132248].
(b) The software failure incident related to the operation phase occurred when a United Airlines Boeing 777-200ER experienced what is suspected to be a hydraulic pressure pump failure shortly after takeoff from Newark Airport. The crew reported an emergency, and the aircraft had to dump fuel over the ocean to reduce weight before making a safe emergency landing back at Newark Airport. The FAA is investigating the cause of this malfunction, which occurred during the operation of the aircraft [132248]. |
Boundary (Internal/External) |
within_system |
(a) The software failure incident related to the grounding of United Airlines' Boeing 777-200 planes was primarily within the system. The incident was caused by the failure to perform required inspections of the front edges of the wings, specifically the wing slats, which are part of the hydraulic system of the aircraft [132248].
Additionally, the failure to inspect the wing leading-edge panels, which are used during takeoffs and landings, was also an internal system issue [132248].
(b) There is no information in the provided articles indicating that the software failure incident related to the grounding and subsequent issues with United Airlines' Boeing 777-200 planes was due to 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 involving United Airlines' Boeing 777-200 planes was primarily related to the failure to conduct required inspections of the front edges of the wings, specifically the wing slats, which are part of the hydraulic system [132248].
- The incident led to the grounding of 25 of the jets after it was discovered that the inspections of the wing slats, crucial for takeoffs and landings, had been missed [132248].
(b) The software failure incident occurring due to human actions:
- The failure to conduct the required inspections on the wing leading-edge panels of the Boeing 777-200 planes was attributed to human error, as United Airlines had failed to perform these inspections as required by regulations [132248].
- The Federal Aviation Administration (FAA) was reviewing United's inspection plan and the circumstances that led to the missed inspections, indicating a potential human error in the inspection process [132248]. |
Dimension (Hardware/Software) |
hardware |
(a) The software failure incident occurring due to hardware:
- The incident involving United Airlines' Boeing 777-200 aircraft being forced to turn back after taking off from Newark Airport was due to an issue with its hydraulic system, which is a hardware component [132248].
- The Federal Aviation Administration (FAA) mentioned that the United Airlines flight to Honolulu suffered engine failure and showered debris over nearby cities, leading to an emergency landing. This incident was attributed to a hardware failure of the engine [132248].
(b) The software failure incident occurring due to software:
- There is no specific mention of a software failure incident in the provided articles. |
Objective (Malicious/Non-malicious) |
non-malicious |
(a) The software failure incident reported in the articles does not seem to be malicious. The incident involved issues with the hydraulic system of a Boeing 777-200 aircraft operated by United Airlines, leading to an emergency landing after experiencing a suspected hydraulic pressure pump failure on the landing gear [132248].
(b) The software failure incident appears to be non-malicious, as it was related to a technical issue with the hydraulic system of the aircraft, specifically a suspected hydraulic pressure pump failure, which forced the plane to make an emergency landing [132248]. |
Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
(a) The software failure incident related to the grounding of United Airlines' Boeing 777-200 planes was primarily due to poor decisions. United Airlines failed to perform required inspections of the front edges of the wings, specifically the wing slats, which are crucial components of the hydraulic system [132248]. The failure to conduct these inspections led to the grounding of 25 aircraft and subsequent flight cancellations. Additionally, the incident where a 777-200 aircraft had to turn back due to an issue with its hydraulic system was a result of the missed inspections on the wing slats [132248].
(b) The software failure incident can also be attributed to accidental decisions or mistakes. The missed inspections of the wing leading-edge panels on the Boeing 777-200s were not related to engines or recent engine work, indicating a lack of proper oversight or unintentional neglect in conducting the required inspections [132248]. The incident where a United plane was forced to make an emergency landing due to suspected hydraulic pressure pump failure on the landing gear can be considered an accidental decision or mistake, as it was an unforeseen issue that occurred during the flight [132248]. |
Capability (Incompetence/Accidental) |
development_incompetence |
(a) The software failure incident related to development incompetence:
- The incident involving United Airlines grounding 25 of its Boeing 777-200 planes was due to the failure to inspect the front edges of the wings, specifically the wing slats, which are part of the hydraulic system [132248].
- The Federal Aviation Administration (FAA) is investigating the missed inspections and reviewing United's inspection plan to understand the circumstances that led to the oversight [132248].
(b) The software failure incident related to accidental factors:
- The incident where a United Airlines Boeing 777-200ER experienced a suspected hydraulic pressure pump failure after takeoff from Newark Airport, leading to a shower of sparks and debris falling off the plane, was an accidental incident that required an emergency landing [132248].
- The FAA is probing the cause of the malfunction that led to the emergency landing of the United Airlines flight [132248]. |
Duration |
temporary |
The software failure incident related to the United Airlines Boeing 777-200 planes was temporary. The incident involved the grounding of 25 planes due to the failure to perform required inspections of the front edges of the wings, specifically the wing slats [132248]. This failure led to flight cancellations and rebooking of affected passengers. Additionally, a specific incident occurred where a 777-200 aircraft had to turn back shortly after takeoff due to an issue with its hydraulic system, which is connected to the wing slats [132248]. The FAA launched an investigation into the missed inspections and the circumstances surrounding the incident [132248]. The grounding of the planes was temporary as United Airlines stated they had inspected 10 of the planes and were working with the FAA to return the others to service within the next two weeks without causing additional flight cancellations [132248]. |
Behaviour |
crash, omission, timing, other |
(a) crash: The incident involving a United Airlines Boeing 777-200 aircraft that was forced to turn back shortly after takeoff from Newark Airport due to an issue with its hydraulic system can be categorized as a crash. The system lost its state and was unable to perform its intended function of maintaining the aircraft's hydraulic system, leading to the emergency landing [132248].
(b) omission: United Airlines grounded 25 of its Boeing 777-200 planes after realizing that some of the aircraft had not undergone required inspections of the front edges of the wings or the wing slats. This failure to conduct necessary inspections can be classified as an omission where the system omitted to perform its intended function of ensuring safety checks were completed [132248].
(c) timing: The incident where a United Airlines Boeing 777-200ER flight had to make an emergency landing after experiencing a suspected hydraulic pressure pump failure shortly after takeoff from Newark Airport can be related to a timing issue. The system performed its intended functions correctly but at an incorrect time, leading to the emergency landing [132248].
(d) value: There is no specific information in the provided articles that directly relates to a failure due to the system performing its intended functions incorrectly.
(e) byzantine: There is no specific information in the provided articles that directly relates to a failure due to the system behaving erroneously with inconsistent responses and interactions.
(f) other: The incident involving the shower of sparks and debris falling from a United Airlines Boeing 777-200ER shortly after takeoff from Newark Airport, leading to an emergency landing, could be categorized as an "other" behavior. This unexpected event was not explicitly described in the options provided [132248]. |