Software in military aviation and drone mishaps: Analysis and recommendations for the investigation process

Abstract

Software plays a central role in military systems. It is also an important factor in many recent incidents and accidents. A safety gap is growing between our software-intensive technological capabilities and our understanding of the ways they can fail or lead to accidents. Traditional forms of accident investigation are poorly equipped to trace the sources of software failure, for instance software does not age in the same way that hardware components fail over time. As such, it can be hard to trace the causes of software failure or mechanisms by which it contributed to accidents back into the development and procurement chain to address the deeper, systemic causes of potential accidents. To identify some of these failure mechanisms, we examined the database of the Air Force Accident Investigation Board (AIB) and analyzed mishaps in which software was involved. Although we have chosen to focus on military aviation, many of the insights also apply to civil aviation. Our analysis led to several results and recommendations. Some were specific and related for example to specific shortcomings in the testing and validation of particular avionic subsystems. Others were broader in scope: for instance, we challenged both the investigation process (aspects of) and the findings in several cases, and we provided recommendations, technical and organizational, for improvements. We also identified important safety blind spots in the investigations with respect to software, whose contribution to the escalation of the adverse events was often neglected in the accident reports. These blind spots, we argued, constitute an important missed learning opportunity for improving accident prevention, and it is especially unfortunate at a time when Remotely Piloted Air Systems (RPAS) are being integrated into the National Airspace. Our findings support the growing recognition that the traditional notion of software failure as non-compliance with requirements is too limited to capture the diversity of roles that software plays in military and civil aviation accidents. The identification of several specific mechanisms by which software contributes to accidents can help populate a library of patterns and triggers of software contributions to adverse events, a library which in turn can be used to help guide better software development, better coding, and better testing to avoid or eliminate these particular patterns and triggers. Finally, we strongly argue for the examination of software's causal role in accident investigations, the inclusion of a section on the subject in the accident reports, and the participation of software experts in accident investigations.

A Review for Software Supportability Assessment of Military Equipment

“…2) Evaluation based on Fuzzy Theory A method of uncertain interval attribute evaluation based on fuzzy entropy is studied in literature [18][19][20][21]. This method mainly improves the rationality of the weight distribution, which affects the accuracy of impact assessment ranking.…”

Joint Common Architecture Demonstration (JCA Demo) Final Report

“…Challenges with software have led to significant cost increases, schedule delays, fielded capabilities shortfalls, and catastrophic loss of life and property [13].…”

Research on the Establishment of Evaluation Index System for Military Software Suppliers

“…In recent years, with the continuous progress of national defense and military modernization, military informatization construction has been improved (Foreman, Favaró, Saleh, & Johnson, 2015). The number of development projects for military software has increased (Cho, Hwang, Shin, Kim, & In, 2021), and an increasing number of software vendors have participated in the development and maintenance of military software systems (Merola, 2006).…”