SEARCH · Engineering Papers

Results for “Flight safety”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 685 records · Page 38

All sources NASA NTRS DOE OSTI

NASA NTRS2010

Ares I-X Range Safety Simulation Verification and Analysis IV and V

NASA s ARES I-X vehicle launched on a suborbital test flight from the Eastern Range in Florida on October 28, 2009. NASA generated a Range Safety (RS) flight data package to meet the RS trajectory data requirements defined in the Air Force Space Command Manual 91-710. Some products included in the flight data package were a nominal ascent trajectory, ascent flight envelope trajectories, and malfunction turn trajectories. These data are used by the Air Force s 45th Space Wing (45SW) to ensure Eastern Range public safety and to make flight termination decisions on launch day. Due to the criticality of the RS data in regards to public safety and mission success, an independent validation and verification (IV&V) effort was undertaken to accompany the data generation analyses to ensure utmost data quality and correct adherence to requirements. Multiple NASA centers and contractor organizations were assigned specific products to IV&V. The data generation and IV&V work was coordinated through the Launch Constellation Range Safety Panel s Trajectory Working Group, which included members from the prime and IV&V organizations as well as the 45SW. As a result of the IV&V efforts, the RS product package was delivered with confidence that two independent organizations using separate simulation software generated data to meet the range requirements and yielded similar results. This document captures ARES I-X RS product IV&V analysis, including the methodology used to verify inputs, simulation, and output data for an RS product. Additionally a discussion of lessons learned is presented to capture advantages and disadvantages to the IV&V processes used.

Tarpley, Ashley↗

NASA NTRS2001

Calcium Kinetics During Long-Duration Space Flight

Bone loss represents one of the most significant effects of space flight on the human body. Understanding the mechanisms underlying this loss is critical for maintaining crew health and safety during and after flight. This investigation documents the changes in bone metabolism and calcium kinetics during and after space flight. We previously reported calcium studies on three subjects during and after a 115-d stay on the Russian space station Mir. We report here data on an additional three subjects, whose stays on Mir were approximately 4 (n=l) and 6 (n=2) mos. Previously published data are included for comparison.

Smith, Scott M.↗

NASA NTRS2014

Preliminary Assessment of Optimal Longitudinal-Mode Control for Drag Reduction through Distributed Aeroelastic Shaping

The emergence of advanced lightweight materials is resulting in a new generation of lighter, flexible, more-efficient airframes that are enabling concepts for active aeroelastic wing-shape control to achieve greater flight efficiency and increased safety margins. These elastically shaped aircraft concepts require non-traditional methods for large-scale multi-objective flight control that simultaneously seek to gain aerodynamic efficiency in terms of drag reduction while performing traditional command-tracking tasks as part of a complete guidance and navigation solution. This paper presents results from a preliminary study of a notional multi-objective control law for an aeroelastic flexible-wing aircraft controlled through distributed continuous leading and trailing edge control surface actuators. This preliminary study develops and analyzes a multi-objective control law derived from optimal linear quadratic methods on a longitudinal vehicle dynamics model with coupled aeroelastic dynamics. The controller tracks commanded attack-angle while minimizing drag and controlling wing twist and bend. This paper presents an overview of the elastic aircraft concept, outlines the coupled vehicle model, presents the preliminary control law formulation and implementation, presents results from simulation, provides analysis, and concludes by identifying possible future areas for research

aeroelastic↗

NASA NTRS1998

A Worst-Case Approach for On-Line Flutter Prediction

Worst-case flutter margins may be computed for a linear model with respect to a set of uncertainty operators using the structured singular value. This paper considers an on-line implementation to compute these robust margins in a flight test program. Uncertainty descriptions are updated at test points to account for unmodeled time-varying dynamics of the airplane by ensuring the robust model is not invalidated by measured flight data. Robust margins computed with respect to this uncertainty remain conservative to the changing dynamics throughout the flight. A simulation clearly demonstrates this method can improve the efficiency of flight testing by accurately predicting the flutter margin to improve safety while reducing the necessary flight time.

Lind, Rick C.↗

NASA NTRS2012

Spinoff 2011

Topics include: Bioreactors Drive Advances in Tissue Engineering; Tooling Techniques Enhance Medical Imaging; Ventilator Technologies Sustain Critically Injured Patients; Protein Innovations Advance Drug Treatments, Skin Care; Mass Analyzers Facilitate Research on Addiction; Frameworks Coordinate Scientific Data Management; Cameras Improve Navigation for Pilots, Drivers; Integrated Design Tools Reduce Risk, Cost; Advisory Systems Save Time, Fuel for Airlines; Modeling Programs Increase Aircraft Design Safety; Fly-by-Wire Systems Enable Safer, More Efficient Flight; Modified Fittings Enhance Industrial Safety; Simulation Tools Model Icing for Aircraft Design; Information Systems Coordinate Emergency Management; Imaging Systems Provide Maps for U.S. Soldiers; High-Pressure Systems Suppress Fires in Seconds; Alloy-Enhanced Fans Maintain Fresh Air in Tunnels; Control Algorithms Charge Batteries Faster; Software Programs Derive Measurements from Photographs; Retrofits Convert Gas Vehicles into Hybrids; NASA Missions Inspire Online Video Games; Monitors Track Vital Signs for Fitness and Safety; Thermal Components Boost Performance of HVAC Systems; World Wind Tools Reveal Environmental Change; Analyzers Measure Greenhouse Gasses, Airborne Pollutants; Remediation Technologies Eliminate Contaminants; Receivers Gather Data for Climate, Weather Prediction; Coating Processes Boost Performance of Solar Cells; Analyzers Provide Water Security in Space and on Earth; Catalyst Substrates Remove Contaminants, Produce Fuel; Rocket Engine Innovations Advance Clean Energy; Technologies Render Views of Earth for Virtual Navigation; Content Platforms Meet Data Storage, Retrieval Needs; Tools Ensure Reliability of Critical Software; Electronic Handbooks Simplify Process Management; Software Innovations Speed Scientific Computing; Controller Chips Preserve Microprocessor Function; Nanotube Production Devices Expand Research Capabilities; Custom Machines Advance Composite Manufacturing; Polyimide Foams Offer Superior Insulation; Beam Steering Devices Reduce Payload Weight; Models Support Energy-Saving Microwave Technologies; Materials Advance Chemical Propulsion Technology; and High-Temperature Coatings Offer Energy Savings.

Source record↗

NASA NTRSDate not supplied

Current Status and Future Plans for Electric Motors and Drives at NASA

Current Status and Future Plans for Electric Motors and Drives at NASA: Our work advances propulsion for aircraft while reducing energy consumption, noise, emissions and the cost of air travel. We are committed to investigating the use of alternative energy sources and improving the safety and expediency of flight. Electrified Aircraft Propulsion (EAP) is the use of propulsors (propellers or fans) driven by electric motors to propel aircraft ranging from air taxis to subsonic transports. NASA is developing technology, aircraft concepts, test aircraft, and ground test facilities to turn this idea from science fiction to reality. Specifically, motors and/or generators (Electric machines) are needed on all electrified aircraft. And NASA is sponsoring or performing work to achieve power densities 2-3 times the state of the art for machines in the MW or larger class. Three major machine types are being developed: permanent magnet, induction, and wound field. Power converters are also an essential component in most EAP aircraft concepts, as they are used to convert from ac to dc power, or vice versa. Silicon carbide and gallium nitride convertors are being developed with conventional cooling as well as a cryogenically cooled converter. Future plans include demonstrating integrated flight-ready systems in both ground and flight tests; collaborating with and leveraging ARPA-E EAP programs; and supporting FAA standards development for market acceptance and safety.

Powertrain↗

NASA NTRSDate not supplied

Current Status and Future Plans for Electric Motors and Drives at NASA

Our work advances propulsion for aircraft while reducing energy consumption, noise, emissions and the cost of air travel. We are committed to investigating the use of alternative energy sources and improving the safety and expediency of flight. Electrified Aircraft Propulsion (EAP) is the use of propulsors (propellers or fans) driven by electric motors to propel aircraft ranging from air taxis to subsonic transports. NASA is developing technology, aircraft concepts, test aircraft, and ground test facilities to turn this idea from science fiction to- reality. Specifically, motors and/or generators (Electric machines) are needed on all electrified aircraft. And NASA is sponsoring or performing work to achieve power densities 2-3 times the state of the art for machines in the MW or larger class. Three major machine types are being developed: permanent magnet, induction, and wound field. Power converters are also an essential component in most EAP aircraft concepts, as they are used to convert from ac to dc power, or vice versa. Silicon carbide and gallium nitride convertors are being developed with conventional cooling as well as a cryogenically cooled converter. Future plans include demonstrating integrated flight-ready systems in both ground and flight tests; collaborating with and leveraging ARPA-E EAP programs; and supporting FAA standards development for market acceptance and safety.

Aircraft↗

NASA NTRS2000

NASA Space Technology Can Improve Soldier Health, Performance and Safety

One of the primary goals of NASA Life Sciences research is '... to enable a permanent human presence in space.' To meet this goal, NASA is creating alternative protocols designed to evaluate and test countermeasures that will account for and correct the environmental effects of space flight on crewmembers health, safety, and operational performance. NASA investigators have previously evaluated the effects of long-duration space flight on physiology and performance of cosmonauts aboard the MIR space station. They also initiated tests of a countermeasure, Autogenic-Feedback Training Exercise (AFTE) designed to prevent and/or correct adverse effects, i.e., facilitate adaptation to space and re-adaptation to Earth. AFTE is a six-hour physiological training program that has proven to be a highly efficient and effective method for enabling people to monitor and voluntarily control a range of their own physiological responses, thereby minimizing adverse reactions to environmental stress. However, because of limited opportunities to test this technology with space flight crews, it is essential to find operational or 'real world' environments in which to validate the efficacy of this approach.

Cowings, Patricia S.↗

NASA NTRSDate not supplied

Recommendations For Developing Space Suit Integrated Food Systems and Delivering Nutrition Before, During, and After Lunar Eva

INTRODUCTION Artemis missions will include a higher tempo and frequency of extravehicular activities (EVAs) than any previous space program. Because of the physical demands expected from the crew, future space suit designs are required to incorporate nutritional support to the astronauts during lunar surface EVAs lasting longer than 4 hours. The purpose of this project was to provide recommendations to aid the development of an in-suit system that can adequately, safely, and acceptably deliver nutrition to a crewmember while confined to a space suit during EVA. METHODS Physiological, logistical, and engineering aspects of potential in-suit nutrition approaches were assessed through literature reviews, assessments of commercial off the shelf (COTS) foods, suit volumetric modeling, and feedback from subject matter experts and crewmembers. Key driving factors in the development of in-suit nutrition requirements included how much and what type of nutrition should be included, what food formulations are appropriate and safe, what are inherent limitations of space suits, what are the potential risks to the crewmember in the suit, and what practices and preferences from astronauts should be considered. Design references were conceptualized and assessed for strengths and limitations as potential in-suit nutrition systems for surface EVA. RESULTS Acute exogenous energy demands vary greatly depending on activity intensity and duration, and partial energy replenishment (i.e., 60–80 kcal∙hr-1 of EVA, or 460–680 kcal for EVAs lasting up to 8 hours) during activities could improve performance, safety, and recovery. COTS foods capable of providing these energy requirements exist; however, no COTS foods have been identified that pass NASA flight standards for microbiological safety and stability. In-suit nutrition delivery design references that were considered included in-suit concepts for a prefilled drink bag, a hydratable drink bag, and a solid food stick. In addition, a helmet feed port concept was considered for use with drink bags external to the suit. Volumetric models of the in-suit drink bag concepts, based on xEMU dimensions, indicate challenges of fitting formulations > 200 ml (equating to approximately 200 kcal). Astronaut feedback on the four concepts indicated that despite some individual preferences for inclusion of solid foods and helmet port designs, the prefilled drink bag concept was the most preferred. A prefilled drink bag can only be used if food safety and stability can be ensured, possibly requiring advancements in food delivery hardware. CONCLUSION The ability to meet the increased need for nutrition during surface EVAs through provision of nutrients in the suited configuration would benefit overall crew health, performance, and morale, and thus increase the likelihood of mission success. It is recommended that in-suit nutrition capabilities provide at least 400–600 kcal within the suit during EVAs lasting > 4 hours and that suit designs include a dedicated volume for food grade nutrition systems. The developed food system should either allow for 1) installation of prefilled (sealed sterile) liquid nutrition in the suit and provide a mechanism to break the seal at the time that consumption is desired or 2) demonstrate that the unsealed food product shelf life allows for safe consumption after at least 12 hours of EVA.

E L Dillon↗

NASA NTRSDate not supplied

Recommendations for Developing Space Suit Integrated Food Systems and Delivering Nutrition Before, During, and After Lunar EVA

space suit↗

NASA NTRS2016

Station Program Note Pull Automation

Upon commencement of my internship, I was in charge of maintaining the CoFR (Certificate of Flight Readiness) Tool. The tool acquires data from existing Excel workbooks on NASA's and Boeing's databases to create a new spreadsheet listing out all the potential safety concerns for upcoming flights and software transitions. Since the application was written in Visual Basic, I had to learn a new programming language and prepare to handle any malfunctions within the program. Shortly afterwards, I was given the assignment to automate the Station Program Note (SPN) Pull process. I developed an application, in Python, that generated a GUI (Graphical User Interface) that will be used by the International Space Station Safety & Mission Assurance team here at Johnson Space Center. The application will allow its users to download online files with the click of a button, import SPN's based on three different pulls, instantly manipulate and filter spreadsheets, and compare the three sources to determine which active SPN's (Station Program Notes) must be reviewed for any upcoming flights, missions, and/or software transitions. Initially, to perform the NASA SPN pull (one of three), I had created the program to allow the user to login to a secure webpage that stores data, input specific parameters, and retrieve the desired SPN's based on their inputs. However, to avoid any conflicts with sustainment, I altered it so that the user may login and download the NASA file independently. After the user has downloaded the file with the click of a button, I defined the program to check for any outdated or pre-existing files, for successful downloads, to acquire the spreadsheet, convert it from a text file to a comma separated file and finally into an Excel spreadsheet to be filtered and later scrutinized for specific SPN numbers. Once this file has been automatically manipulated to provide only the SPN numbers that are desired, they are stored in a global variable, shown on the GUI, and transferred over to a new Excel worksheet for comparison. I managed to get my application to acquire the CSWG (Computer Safety Working Group) and the SPNWG (Space Station Working Group) SPN's with just two mouse clicks for each pull, as opposed to several from the original process. When all three pulls are performed, an Excel sheet containing all three different results will be generated for the user to compare and determine which SPN's will be presented or reviewed the following month. The experience from this internship has been spectacular. As a high school senior who will begin attending college in the fall, this internship has been both educationally and occupationally beneficial. The internship has allowed me the opportunities to learn new programming languages, effectively network with NASA personnel from a variety of departments at JSC, and allowed me to learn new professional skills and etiquette. My internship at NASA's Johnson Space Center has further motivated me to pursue a Master's degree in Software Engineering and strive for a prosperous career with NASA as a civil servant.

Delgado, Ivan↗

NASA NTRS2008

Ares-I-X Vehicle Preliminary Range Safety Malfunction Turn Analysis

Ares-I-X is the designation given to the flight test version of the Ares-I rocket (also known as the Crew Launch Vehicle - CLV) being developed by NASA. As part of the preliminary flight plan approval process for the test vehicle, a range safety malfunction turn analysis was performed to support the launch area risk assessment and vehicle destruct criteria development processes. Several vehicle failure scenarios were identified which could cause the vehicle trajectory to deviate from its normal flight path, and the effects of these failures were evaluated with an Ares-I-X 6 degrees-of-freedom (6-DOF) digital simulation, using the Program to Optimize Simulated Trajectories Version 2 (POST2) simulation framework. The Ares-I-X simulation analysis provides output files containing vehicle state information, which are used by other risk assessment and vehicle debris trajectory simulation tools to determine the risk to personnel and facilities in the vicinity of the launch area at Kennedy Space Center (KSC), and to develop the vehicle destruct criteria used by the flight test range safety officer. The simulation analysis approach used for this study is described, including descriptions of the failure modes which were considered and the underlying assumptions and ground rules of the study, and preliminary results are presented, determined by analysis of the trajectory deviation of the failure cases, compared with the expected vehicle trajectory.

Beaty, James R.↗

NASA NTRS1996

Integration of Multiple Non-Normal Checklist Procedures into a Single Checklist Procedure for Transport Aircraft: A Preliminary Investigation

Checklists are used by the flight crew to properly configure an aircraft for safe flight and to ensure a high level of safety throughout the duration of the flight. In addition, the checklist provides a sequential framework to meet cockpit operational requirements, and it fosters cross-checking of the flight deck configuration among crew members. This study examined the feasibility of integrating multiple checklists for non-normal procedures into a single procedure for a typical transport aircraft. For the purposes of this report, a typical transport aircraft is one that represents a midpoint between early generation aircraft (B-727/737-200 and DC-10) and modern glass cockpit aircraft (B747-400/777 and MD-11). In this report, potential conflicts among non-normal checklist items during multiple failure situations for a transport aircraft are identified and analyzed. The non-normal checklist procedure that would take precedence for each of the identified multiple failure flight conditions is also identified. The rationale behind this research is that potential conflicts among checklist items might exist when integrating multiple checklists for non-normal procedures into a single checklist. As a rule, multiple failures occurring in today's highly automated and redundant system transport aircraft are extremely improbable. In addition, as shown in this analysis, conflicts among checklist items in a multiple failure flight condition are exceedingly unlikely. The possibility of a multiple failure flight condition occurring with a conflict among checklist items is so remote that integration of the non-normal checklists into a single checklist appears to be a plausible option.

Foernsler, Lynda J.↗

NASA NTRS2016

Construction of Supersonic Flight Dynamics Test (SFDT-2) Vehicle Monte Carlo Splashdown Footprints for Use in Range Safety and Recovery Planning

Overview of Low Density Supersonic Decelerator (LDSD) SFDT-2 ( Supersonic Flight Dynamics Test-2) flight profile; Description of Monte Carlo flight dynamics simulations performed; Modeling and uncertainties; Results with statistical prediction of test vehicle splashdown location; Use of Monte Carlo results for range safety and recovery planning.

Strauss, Bill↗

NASA NTRS1988

STS-26 Preflight Press Briefing: 5 Man Crew

This NASA KSC video release presents part of a press conference held prior to Discovery flight STS-26, the first shuttle mission flown following the 51-L Challenger accident. The video opens with a statement from Commander Frederick H. Hauck, and the introductions of crew members, Richard O. Covey, Pilot, and mission specialists, John M. Lounge, George D. Nelson, and David C. Hilmers. Some of the questions posed by scientific journalists addressed the following subjects: launch preparation in the month prior to flight, astronaut family anxieties in light of the Challenger accident, extent of safety measures made prior to flight, flight readiness firing, the crew escape system, civilians in space, conservative mission design, astronaut selection, mission turnaround and launch rate, and the ability to maintain a high level of scrutiny regarding safety on future missions.

Source record↗

NASA NTRS2005

Formal Safety Certification of Aerospace Software

In principle, formal methods offer many advantages for aerospace software development: they can help to achieve ultra-high reliability, and they can be used to provide evidence of the reliability claims which can then be subjected to external scrutiny. However, despite years of research and many advances in the underlying formalisms of specification, semantics, and logic, formal methods are not much used in practice. In our opinion this is related to three major shortcomings. First, the application of formal methods is still expensive because they are labor- and knowledge-intensive. Second, they are difficult to scale up to complex systems because they are based on deep mathematical insights about the behavior of the systems (t.e., they rely on the "heroic proof"). Third, the proofs can be difficult to interpret, and typically stand in isolation from the original code. In this paper, we describe a tool for formally demonstrating safety-relevant aspects of aerospace software, which largely circumvents these problems. We focus on safely properties because it has been observed that safety violations such as out-of-bounds memory accesses or use of uninitialized variables constitute the majority of the errors found in the aerospace domain. In our approach, safety means that the program will not violate a set of rules that can range for the simple memory access rules to high-level flight rules. These different safety properties are formalized as different safety policies in Hoare logic, which are then used by a verification condition generator along with the code and logical annotations in order to derive formal safety conditions; these are then proven using an automated theorem prover. Our certification system is currently integrated into a model-based code generation toolset that generates the annotations together with the code. However, this automated formal certification technology is not exclusively constrained to our code generator and could, in principle, also be integrated with other code generators such as RealTime Workshop or even applied to legacy code. Our approach circumvents the historical problems with formal methods by increasing the degree of automation on all levels. The restriction to safety policies (as opposed to arbitrary functional behavior) results in simpler proof problems that can generally be solved by fully automatic theorem proves. An automated linking mechanism between the safety conditions and the code provides some of the traceability mandated by process standards such as DO-178B. An automated explanation mechanism uses semantic markup added by the verification condition generator to produce natural-language explanations of the safety conditions and thus supports their interpretation in relation to the code. It shows an automatically generated certification browser that lets users inspect the (generated) code along with the safety conditions (including textual explanations), and uses hyperlinks to automate tracing between the two levels. Here, the explanations reflect the logical structure of the safety obligation but the mechanism can in principle be customized using different sets of domain concepts. The interface also provides some limited control over the certification process itself. Our long-term goal is a seamless integration of certification, code generation, and manual coding that results in a "certified pipeline" in which specifications are automatically transformed into executable code, together with the supporting artifacts necessary for achieving and demonstrating the high level of assurance needed in the aerospace domain.

Denney, Ewen↗

NASA NTRS1971

Shuttle operations, maintenance, and safety.

Review of a systematic search for practical solutions in the areas of space shuttle cryogenics, flight operations, ground operations, and safety. The insulation of the main-propulsion hydrogen tanks for both booster and orbiter to prevent water condensation is considered, as well as the insulation of the orbiter's orbital cryogen tanks for ground storage. Two approaches to the feeding of cryogens are outlined - namely, an approach depending on a periodic axial force to settle propellants and refill the basket, and a method of continuous feed through a capillary network adjacent to the walls throughout the tank, the latter method being independent of vehicle thrust. The development of reliable cryogen components is discussed, and the results of studies of launch-abort problems, shuttle approach and landing techniques, and the tolerance of ?deconditioned' crew and passengers to shuttle reentry g-loads are cited.

Beddingfield, S. T.↗

NASA NTRS2019

Supporting Crew Autonomy in Deep Space Exploration: Preliminary Onboard Capability Requirements and Proposed Research Questions. Technical Report of the Autonomous Crew Operations Technical Interchange Meeting

Communication delays are a critical challenge posed by long duration deep space exploration. Space missions historically have relied on an ever-present Mission Control Center (MCC) to direct operations in near real-time. As unanticipated anomalies that defeat fault detection and resolution systems do arise, the lack of real-time communication will significantly weaken what the MCC support represents: a reliable safety net for the flight crew through its deep and diverse areas of expertise and investigative resources. As a consequence, future space vehicles and habitats need to be equipped with capabilities to support the flight crew to operate with little or no ground support. Considerations must be given to vehicle and mission designs that will fortify the traditionally ground-centered safety net and forge new support systems, when communication delays exist. In August 2018, NASA’s Human Research Program, through its Human Factors and Behavioral Performance Element, convened a Technical Interchange Meeting (TIM) on Autonomous Crew Operations at NASA Ames Research Center. The goal of the meeting was to gather input from NASA centers, industry, academia, and branches of the Department of Defense (DoD) to address how intelligent technologies can be applied to augment onboard capabilities to support crew anomaly response. The TIM featured 24 presentations by 29 speakers and hosted a total of 59 attendees, including 43 from 5 NASA centers (Ames, Johnson, Langley, Marshall, and Jet Propulsion Lab) and 4 from the DoD (3 from Army Research Lab and 1 from Naval Postgraduate School), with remaining attendees from academia (e.g., UC Davis, CMU) and industry (e.g., IBM, Siemens). Discussions were centered around three themes: standards and guidelines, lessons learned in analog environments, and technologies. To help provide a framework for discussion, a concept matrix describing anomaly response processes was created prior to the TIM (Figure 1, page 6). The matrix captures the steps involved (monitoring and detection, diagnosis, solution development and evaluation, solution implementation and verification, resolution documentation) as well as the resources and capabilities required to support these steps (data, knowledge, analysis, synthesis, resource management). A wallpaper size printout of the matrix was utilized at the TIM to solicit attendee inputs along the three themes; the activity garnered 108 submissions of ideas. Overall, what emerged from TIM discussions was a picture of mismatch between crew anomaly response needs and support that can be provided by existing intelligent technologies. The needs are broad, spanning multiple steps and processes/resources, with many of which lacking support from existing technologies, such as knowledge management throughout the steps of problem solving (especially in resolution documentation) and manpower management. The solutions provided by existing intelligent technologies are specific to the steps/processes that they are designed to support and constrained to solving only problems similar to those that have occurred before. What is lacking from technologies is typically made up by humans, specifically their complex critical thinking, creative problem solving, and domain expertise. In the end, the TIM highlighted the pressing need to support responses to onboard anomalies during autonomous crew operations, particularly those that have eluded the system tests, inspection, and other assurance processes. Such anomalies can potentially threaten crew and vehicle safety, as well as significantly impact overall operations with additional workload. These fairly rare events are difficult to anticipate and prepare for, given the state-of-the-art in intelligent technologies. This is true even for anomalies that stem from “unknown knowns”—cases in which there is sufficient external information to characterize the problem but the overall pattern fails to be recognized by the problem solver, or in which the internal knowledge needed to solve a problem is held tacitly and potentially accessible by the problem solver but not articulated. It follows that the ability to tackle anomalies lies not only with the availability of relevant information and knowledge but also their accessibility in times of need. To that end, we propose research questions along the following three broad themes: • How intelligent technologies can help make relevant knowledge and information available? • How intelligent technologies can help make relevant knowledge and information accessible? • How intelligent technologies can help support the crew operating as a team in anomaly response processes?

autonomous crew operations↗