Search NASA⌕ Search

SEARCH · Search NASA

Results for “ground delay program”

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.

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

At least 181 records · Page 10

Mission safety evaluation report for STS-39, postflight edition

After a delay of approximately 2 months due to a rollback from the pad to replace the External Tank door lug housing, Space Shuttle Discovery was launched from NASA-Kennedy at 7:33 a.m. Eastern Daylight Time on 28 April 1991. STS-39 was the first unclassified DoD Shuttle mission. On 28 April, countdown proceeded normally through the T-20 minute hold. No significant problems were encountered except for the Operations Sequence-2 recorder starting unexpectedly; it was stopped by an uplink command. Discovery landed on KSC runway 15 at 2:55 p.m. EDT on 6 May 1991. This was the second time in 6 months that the Space Shuttle was diverted to KSC for landing because of high winds at Edwards AFB, Calif. This was also the 7th of 40 Shuttle missions to land at KSC in the history of the Space Shuttle Program. The Main Landing Gear outer right tire shredded 3 of the 16 cords due to either an uneven landing or a maximum force breaking test during rollout. Contributing factors to the tire cord shredding were the development of last minute crosswinds and reluctance of the ground controllers to distract the Shuttle pilots with warnings of the low flight path. As a corrective action, communication procedures will be modified for future flights.

Hardie, Kenneth O.↗

Observing Campaign for Potential Deep Impact Flyby Target 163249 (2002 GT)

The Deep Impact spacecraft is currently on course for a Jan. 4, 2020 flyby of the sub-kilometer near-Earth asteroid 163249 (2002 GT). The re-targeting will be complete with a final small maneuver scheduled for Oct. 4, 2012. 2002 GT, which is also designated as a Potentially Hazardous Asteroid (PHA), has a well-determined orbit and is approx 800 m in diameter (H=18.3). Little more is known about the nature of this object, but in mid-2013 it will pass near the Earth, affording an exceptional opportunity for ground-based characterization. At this apparition 2002 GT will be in range of Arecibo. In addition to Doppler measurements, radar delay observations with precisions of a few microseconds are expected and have a good chance of revealing whether the system is binary or not. The asteroid will be brighter than 16th mag., which will facilitate a host of observations at a variety of wavelengths. Light curve measurements across a wide range of viewing perspectives will reveal the rotation rate and ultimately lead to strong constraints on the shape and pole orientation. Visible and infrared spectra will constrain the mineralogy, taxonomy, albedo and size. Along with the radar observations, optical astrometry will further constrain the orbit, both to facilitate terminal guidance operations and to potentially reveal nongravitational forces acting on the asteroid. Coordinating all of these observations will be a significant task and we encourage interested observers to collaborate in this effort. The 2013 apparition of 2002 GT represents a unique opportunity to characterize a potential flyby target, which will aid interpretation of the high-resolution flyby imagery and aid planning and development of the flyby imaging sequence. The knowledge gained from this flyby will be highly relevant to the human exploration program at NASA, which desires more information on the physical characteristics of sub-kilometer near-Earth asteroids.

Pittichova, Jana↗

NASA Tech Briefs, November 2003

Topics covered include: Computer Program Recognizes Patterns in Time-Series Data; Program for User-Friendly Management of Input and Output Data Sets; Noncoherent Tracking of a Source of a Data-Modulated Signal; Software for Acquiring Image Data for PIV; Detecting Edges in Images by Use of Fuzzy Reasoning; A Timer for Synchronous Digital Systems; Prototype Parts of a Digital Beam-Forming Wide-Band Receiver; High-Voltage Droplet Dispenser; Network Extender for MIL-STD-1553 Bus; MMIC HEMT Power Amplifier for 140 to 170 GHz; Piezoelectric Diffraction-Based Optical Switches; Numerical Modeling of Nanoelectronic Devices; Organizing Diverse, Distributed Project Information; Eigensolver for a Sparse, Large Hermitian Matrix; Modified Polar-Format Software for Processing SAR Data; e-Stars Template Builder; Software for Acoustic Rendering; Functionally Graded Nanophase Beryllium/Carbon Composites; Thin Thermal-Insulation Blankets for Very High Temperatures; Prolonging Microgravity on Parabolic Airplane Flights; Device for Locking a Control Knob; Cable-Dispensing Cart; Foam Sensor Structures Would be Self-Deployable and Survive Hard Landings; Real-Gas Effects on Binary Mixing Layers; Earth-Space Link Attenuation Estimation via Ground Radar Kdp; Wedge Heat-Flux Indicators for Flash Thermography; Measuring Diffusion of Liquids by Common-Path Interferometry; Zero-Shear, Low-Disturbance Optical Delay Line; Whispering-Gallery Mode-Locked Lasers; Spatial Light Modulators as Optical Crossbar Switches; Update on EMD and Hilbert-Spectra Analysis of Time Series; Quad-Tree Visual-Calculus Analysis of Satellite Coverage; Dyakonov-Perel Effect on Spin Dephasing in n-Type GaAs; Update on Area Production in Mixing of Supercritical Fluids; and Quasi-Sun-Pointing of Spacecraft Using Radiation Pressure.

Source record↗

Human Flight to Lunar and Beyond - Re-Learning Operations Paradigms

For the first time since the Apollo era, NASA is planning on sending astronauts on flights beyond LEO. The Human Space Flight (HSF) program started with a successful initial flight in Earth orbit, in December 2014. The program will continue with two Exploration Missions (EM): EM-1 will be unmanned and EM-2, carrying astronauts, will follow. NASA established a multi-center team to address the communications, and related tacking/navigation needs. This paper will focus on the lessons learned by the team designing the architecture and operations for the missions. Many of these Beyond Earth Orbit lessons had to be re-learned, as the HSF program has operated for many years in Earth orbit. Unlike the Apollo missions that were largely tracked by a dedicated ground network, the HSF planned missions will be tracked (at distances beyond GEO) by the DSN, a network that mostly serves robotic missions. There have been surprising challenges to the DSN as unique modern human spaceflight needs stretch the experience base beyond that of tracking robotic missions in deep space. Close interaction between the DSN and the HSF community to understand the unique needs (e.g. 2-way voice) resulted in a Concept of Operations (ConOps) that leverages both the deep space robotic and the Human LEO experiences. Several examples will be used to highlight the unique challenges the team faced in establishing the communications and tracking capabilities for HSF missions beyond Earth Orbit, including: Navigation. At LEO, HSF missions can rely on GPS devices for orbit determination. For Lunar-and-beyond HSF missions, techniques such as precision 2-way and 3-way Doppler and ranging, Delta-Difference-of-range, and eventually possibly on-board navigation will be used. At the same time, HSF presents a challenge to navigators, beyond those presented by robotic missions - navigating a dynamic/"noisy" spacecraft. Impact of latency - the delay associated with Round-Trip-Light-Time (RTLT). Imagine trying to have a 2-way discussion (audio or video) with an astronaut, with a 2-3 sec or more delay inserted (for lunar distances) or 20 minutes delay (for Mars distances). Balanced communications link. For robotic missions, there has been a heavy emphasis on higher downlink data rates, e.g. bringing back science data. Higher uplink data rates were of secondary importance, as uplink was used only to send commands (and occasionally small files) to the spacecraft. The ratio of downlink-to-uplink data rates was often 10:1 or more. For HSF, a continuous forward link is established and rates for uplink and downlink are more similar.

Kenny, Edward (Ted)↗

Reconfigurable Microwave Phase Delay Element for Frequency Reference and Phase-Shifter Applications

A technique was developed to provide a reconfigurable high-precision micro - wave electrical phase delay for resonators and phase shifters. The invention employs multiple branches of transmission lines with open-ended or ground-ended terminations as configurable bits or digits. This technique minimizes the errors due to limited precision of switching devices. In addition, the proposed linear analytical approach significantly produces a much simpler design than that of other prior inventions at the time of this reporting. Microwave components such as filters, phase delay elements, or resonators require a method that can accurately adjust their frequency responses. Most tuning techniques offer very wide frequency tuning range; however, it is often difficult and expensive to tune their response in a very narrow operating frequency, especially when the tuning element reaches its minimum discrete step due to fabrication tolerances. The problem becomes worse as the operating frequency is in mm-wave frequency range (>26 GHz). The electrical tuning sensitivity of a microwave line is dependent on the position of the tuning element with respect to the reference termination. By placing this tuning element away from this reference with the main transmission line connecting the two elements together the sensitivity of the tuning element can change significantly. This concept can be used in the system that requires multiple tuning sensitivities. In this case, multiple tuning branches are superimposed in the main transmission line. The proposed invention allows the transmission-line electrical length to be accurately programmed using switching elements that have limited accuracy. The invention consists of multiple branches of transmission lines connected to discrete switching devices with open-ended terminations. They are used as discrete tuning elements. These elements are connected to the main microwave transmission line and are separated by a well-defined electrical degree spacing. Each branch is programmed to have different electrical degree sensitivity, such as a combination of discrete steps in each branch, which results in a reflective line with a unique effective phase response. To reduce the number of switching devices, it is desirable to program the devices in binary configuration where each branch represents one bit in the base-2 number system. This invention allows the transmission line electrical length to be tuned precisely with customizable sensitivity based on the known sensitivity of the base tuning circuit. The tuning resolution is dependent on the distance among tuning branches.

Hsieh, Wen-Ting↗

The Ceres S'COOL Project: Two Years After First Launch

The idea for the Students' Cloud Observations OnLine (S'COOL) project as an outreach and education element of NASA's Clouds and the Earth's Radiant Energy System (CERES) research program was conceived in late 1996 during a conversation with a middle school science teacher. S'COOL was implemented in a series of increasingly developed test phases during 1997, as the launch of the first CERES instrument approached. Even before launch, the reception of the project in schools far exceeded expectations. After several delays the first instrument, on the Tropical Rainfall Measuring Mission (TRMM) spacecraft, was launched on Thanksgiving Day, 1997. Since the first launch, development and expansion of the project has continued with expectations for launch of Terra carrying two CERES instruments into a polar orbit in mid-1998. That launch is now expected in fall 1999, and will finally provide overflight of all participating schools. In two years, the project has grown from three initial test participants to over 300 schools now participating in 23 countries on five continents. Students from first grade through university level are involved (most participants are ages 10-15). S'COOL is also being used by a few education professors to teach about Internet use in the classroom. The project continues to grow through word of mouth, presentations at teacher workshops, and now increasingly through teachers who find it during web searches. Participants in the S'COOL project are part of the CERES validation team. They provide ground truth measurements at the time the CERES instrument flies over their location, to be compared with the retrieval of cloud properties by remote sensing from CERES. Quantities reported include cloud type, height, fraction and opacity; information on contrails; surface temperature, pressure and relative humidity; and ground cover (snow/ice, wet, dry; leaves on trees or not). in addition, a comment field on the report form serves as a catch-all for all kinds of interesting observations, including similes written by some classes to describe more exactly the clouds they see. Several not totally unexpected complications with the CERES instrument and processing software mean that the CERES team has not yet reached the point of computing the cloud properties, a high level product at the end of the processing stream. However, progress is being made and we anticipate that we will soon be populating the S'COOL database with a large number of satellite retrievals for comparison with the students' observations. Some satellite retrievals from the initial test phases are already available in the database, The CERES instruments are planned to operate at least through 2006, and the S'COOL Project is planned to continue at least that long, providing motivational learning to as many students as possible. This paper reports on the first several years of the S'CCOL project. It further reports on some of the noteworthy observations and comparisons made possible by this project. Schools are often located in interesting places, in terms of the clouds found there and the satellite's ability to observe these clouds. The paper also reports on the learning opportunities delivered by this project, and on new questions about the planet and its climate which arise in the students' minds as a result of their active participation.

Chambers, Lin H.↗

Verification Testing and Veg-05 Tomato Crop Production on the International Space Station

Production of fresh, nutritious, and tasty produce for astronauts during spaceflight may provide health-promoting, bioavailable nutrients and enhance the dietary experience as we move into longer-duration missions. Growing and caring for plants may also reduce the psychological stresses associated with spaceflight and enhance connections to Earth. Requirements to consistently grow a diversity of crops under spaceflight environmental conditions remain poorly defined. The VEG-05 experiment is part of a series of experiments with pick-and-eat salad crops to better define best practices for crop production and handling in space. VEG-05 and predecessor experiments VEG-04A and VEG-04B, use the Veggie vegetable production facilities on the International Space Station to grow salad crops under different spectral compositions. In VEG-04A and B, mizuna mustard was cultivated with two different red: blue light treatments, and in VEG-05 we are cultivating ‘Red Robin’ dwarf cherry tomatoes under the same light spectra. Light can impact the growth habit, yield, nutritional composition, microbial levels, and even flavor attributes within crops, and our team will assess these characteristics for this crop during VEG-05. Prior to launch and installation on ISS in late 2022, both a science verification test (SVT), and an experiment verification test (EVT) were conducted at Kennedy Space Center in ISS Environment Simulator Chambers. Science verification testing, and a previous fertilizer test, grew plants in both plant pillows and PONDS (Passive Orbital Nutrient Delivery System) units and tested two different fertilizer treatments in both sets of hardware, with each test under only one of the light conditions. Because of challenges validating the PONDS hardware on ISS, and with good crop production in plant pillows, the EVT moved forward using only plant pillows with the highest fertilizer composition tested during SVT, and two Veggie units were utilized. One Veggie had light settings consisting of equal levels of red: blue light (150 µmol/m2/s for each color) plus green light (30 µmol/m2/s) while the second Veggie had a 90:10 ratio of red: blue light (270 µmol/m2/s red and 30 µmol/m2/s blue) plus green, so each unit provided 330 µmol/m2/s of photosynthetically active radiation to the tomato crops on average. Our original plan, based on prior ground testing, was to grow the crop for 104 days and harvest at 80, 90 and 104 days after initiation. For SVT, under the equal red: blue light treatment, fruit ripening in plant pillows was delayed and fruit were not ripe by day 80, so actual harvest days were days 90, 97, and 104. For EVT we saw fruit ripening earlier, especially in the high red treatment, and so we harvested at days 83, 90, and 99 days after initiation. In SVT we had mostly daily watering, and this led to excess water in plant pillows, which leaked out. This excess water also caused fungus to grow on one leaf and a couple of plant stems. To reduce this excess moisture, we throttled back the watering for EVT, and used the root mat reservoir more frequently. This led to watering only every other day, reducing crew time needed for plant care, however, two wilting events occurred during this EVT, at days 51 and 75. Plants recovered from these wilting events, but these events may have influenced the rate of fruit ripening and flower formation. Regardless, more than 10 fruit were produced from each plant on average, with the high red treatment producing slightly heavier fruit. Microbial testing from fruit during SVT indicated that fruit were safe for consumption with microbial levels below detection limits. VEG-05 flight and ground operations are expected to run between December 2022 and March 2023. This research was co-funded by the Human Research Program and Space Biology (MTL#1075) in the ILSRA 2015 NRA call.

Gioia D. Massa↗

Kennedy Space Center (KSC) Pad B Catenary Capability Analysis and Technical Exchange Meeting (TEM) Support

The existing lightning protection system at Pad 39B for the Space Shuttle is an outgrowth of a system that was put in place for the Apollo Program. Dr. Frank Fisher of Lightning Technologies was a key participant in the design and implementation of that system. He conveyed to the NESC team that the catenary wire provision was put in place quickly (as assurance against possible vehicle damage causing critical launch delays) rather than being implemented as a comprehensive system designed to provide a high degree of guaranteed protection. Also, the technology of lightning protection has evolved over time with considerable work being conducted by groups such as the electric utilities companies, aircraft manufacturers, universities, and others. Several accepted present-day methods for analysis of lightning protection were used by Drs. Medelius and Mata to study the expected lightning environment for the Pad 39B facility and to analyze the degree of protection against direct lightning attachment to the Space Shuttle. The specific physical configuration directly affects the vulnerability, so cases that were considered included the RSS next to and rolled back from the Space Shuttle, and the GOx Vent Arm both extended and withdrawn from the ET. Elements of the lightning protection system at Pad 39B are shown in Figure 6.0-1 and consist of an 80 foot insulating mast on top of the Fixed Support Structure (FSS), a catenary wire system that runs from the mast in a North/South direction to grounds 1000 feet away on each side of the mast, the RSS which can either be next to or away from the Space Shuttle, and a GOx vent that can either be extended or retracted from the top of the ET.

Wilson, Timmy R.↗

A Vision of the Future Air Traffic Control System

The air transportation system is on the verge of gridlock, with delays and cancelled flights this summer reaching all time highs. As demand for air transportation continues to increase, the capacity needed to accommodate the growth in traffic is falling farther and farther behind. Moreover, it has become increasingly apparent that the present system cannot be scaled up to provide the capacity increases needed to meet demand over the next 25 years. NASA, working with the Federal Aviation Administration and industry, is pursuing a major research program to develop air traffic management technologies that have the ultimate goal of doubling capacity while increasing safety and efficiency. This seminar will describe how the current system operates, what its limitations are and why a revolutionary "shift in paradigm" is needed to overcome fundamental limitations in capacity and safety. For the near term, NASA has developed a portfolio of software tools for air traffic controllers, called the Center-TRACON Automation System (CTAS), that provides modest gains in capacity and efficiency while staying within the current paradigm. The outline of a concept for the long term, with a deployment date of 2015 at the earliest, has recently been formulated and presented by NASA to a select group of industry and government stakeholders. Automated decision making software, combined with an Internet in the sky that enables sharing of information and distributes control between the cockpit and the ground, is key to this concept. However, its most revolutionary feature is a fundamental change in the roles and responsibilities assigned to air traffic controllers.

Erzberger, Heinz↗

Exploration Medical Capability Clinical Decision Support System Concept of Operations

The Clinical Decision Support (CDS) project supports the Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP). Specifically, the CDS project addresses the ExMC gap, Medical-701: Enhance medical capabilities within an exploration medical system. For long-duration, deep space missions, computational and data resources will play an important role in maintaining crew health, wellness and performance where the crew will need to be more self-reliant as we enter a new era in space exploration to return to the moon and explore Mars. These ambitious goals will require significant change in in-flight medical care due to constraints on mass, volume, power, crew time, skills reduction over time and medical evacuation capabilities. These constraints make it absolutely necessary to develop transformative solutions using new technologies. Unlike the current paradigm for crew health in low-Earth orbit missions that rely on constant communication with Mission Control, the deep space missions will experience communication delays and possibly, no communications for finite periods of time. Hence, crew health management will benefit from analytics’ capabilities to augment decision support. A comprehensive, multi-functional on-board clinical decision support system (CDSS) will help crews assess and diagnose conditions, decide appropriate responses, and guide the provision of tailored and evidence-based treatments, while reflecting contextual factors and constraints. The context may include present and historical data, viable diagnostic equipment, available supplies and medications, and vehicle and environmental health. Communication time with ground-based personnel is delayed or non-existent during significant portions of the mission so the crew will need to autonomously respond to health, performance and medical situations, particularly those that are unplanned. The CDSS must also provide additional capabilities as complex as training for an emergency situation while augmenting non-expert practitioner skillsets if the Crew Medical Officer (CMO) is incapacitated, and as routine as facilitating delayed communication with flight surgeons on the ground. The CDSS must connect complex issues involving health, wellness, task performance and environmental domains. Furthermore, CDSS functionality will focus on semi-autonomous and autonomous decision-making by the crew that is necessary to address challenges in executing a self-contained medical system that enables health care without assistance from ground clinical experts. The document, ExMC CDSS Architecture Recommendation, (HRP- 48032) establishes a description of the envisioned CDSS architecture. The analytics, descriptive or advanced, contained in a CDSS will interface with the integrated crew health and performance architecture that provides the appropriate data sets. The aim of the CDS project is to develop requirements for a CDSS through a series of test-bed prototype developments and demonstrations.

HRP↗

Teams in Space: Knowledge Gained, but More to Explore

NASA’s Human Research Program oversees the Team Risk (i.e., Risk of Performance and Behavioral Health Decrements due to Inadequate Cooperation, Coordination, Communication and Psychosocial Adaptation within a Team). Research in this area informs all aspects of an astronaut’s career, from hiring to training to mission support, and works to address new challenges related to lunar and Mars missions. NASA’s astronaut selection process creates an astronaut corps of highly qualified, team-oriented individuals, which allows mission planners much flexibility in composing small crews for specific missions. These crews are further developed and supported through extensive training, including team skills training, and countermeasures available to the crew throughout the mission. However, in the high consequence environment of long-duration missions, team composition is complex and is not a one-time concern to be addressed pre-mission. Team factors such as team cohesion, dyadic relationships, and shared team cognition are likely to change dynamically in response to each interaction and event experienced by the individuals and the team as a whole. Thus, monitoring and optimizing team composition at a more micro level (e.g., per task) is one way to support team functioning and performance. Spaceflight teams research also includes the multi-team system of Mission Control and coordination between space-to-ground, adding another avenue in which risk might be introduced, particularly under exploration missions that experience significant communication delays. Spaceflight teams research has recently experienced a concentrated flurry of analog research over the past decade, shedding light on the many unique challenges and potential solutions to mitigate the team risk in long-duration exploration missions. However, questions still remain about how to, for example, create unobtrusive operational measures and how to advance interdisciplinary teams research and countermeasure development. We present an overview of the challenges facing teams in space, our current knowledge, and the next steps for research and spaceflight operations.

Lauren Blackwell Landon↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Gateway Autonomy for Enabling Deep Space Exploration

The Gateway spacecraft is an important stepping-stone to exploration of the solar system, integrating commercial and international partners into a tightly coupled system, enabling cislunar activities, and implementing key technologies for missions to Mars. Autonomy is a capability area necessary to handle long communication outages where intervention from Earth is impossible, to prepare to operate with long communication delays that will be common in interplanetary travel, and to make spaceflight more affordable and accessible by reducing sustaining operations costs. The Gateway Concept of Operations states that one of Gateway’s goals is to “focus on infrastructure and systems that will allow autonomous operations aboard the Gateway with robotics, automated systems, advanced communications, and distributed computing.” Gateway’s Vehicle Systems Manager (VSM) and associated Autonomous Spacecraft Management Architecture (ASMA) are key products towards delivering autonomous capability. The primary functions of the control architecture are Mission Management and Timeline Execution, Resource Management, Fault Management, and Vehicle Control and Operation (VCO). In each of these areas, there is an initial level of capability to be delivered at launch, with plans to continue development and grow to greater capability. The initial deployment of VSM will focus on maintaining vehicle safety by focusing on full fault management capabilities and deploying only enough resource and timeline planning functionality to support that. The final deployment of VSM will add significant planning and control optimization functionality to support nominal operations for up to 21 days without ground support, even accommodating fault and failure conditions. While the VSM is the vehicle-level representation of autonomous reasoning, distributed automation is essential to provide the right scope and abstraction of information to process. Module and system support of automation and simplicity of interfaces are two important design paradigms that Gateway is focusing on to garner a systems approach to autonomy. Distribution of reasoning can increase complexity, so Gateway is also taking a strict hierarchical approach to information flow and decision making. VSM is not the only capability necessary to achieve an autonomous spacecraft. Robotics support for maintenance of the spacecraft will be essential to provide continued vehicle functionality even when crew is not present. Technical and programmatic challenges exist when implementing autonomous robotics operations. These challenges include sufficient network flexibility to support data transfer to the rest of the vehicle to coordinate module-to-module robotic walk-offs and finding the proper interfaces to allow sufficient dexterity. Communication system upgrades planned for Gateway include Delay Tolerant Networking to best utilize the complex network of relays that will be part of mature cislunar operations. Distributed computing and management will provide failure tolerance, robustness, and growth of capabilities while still allowing significant reuse of heritage software on heritage systems as well as reuse of common applications across a spacecraft to minimize new development, but this requires adherence to key standards and interfaces. The Gateway program has demonstrated significant progress towards these capabilities and has identified challenges other spacecraft developers should be aware of from the start.

Molly Anderson↗

Space station evolution: Planning for the future

The need for permanently manned presence in space has been recognized by the United States and its international partners for many years. The development of this capability was delayed due to the concurrent recognition that reusable earth-to-orbit transportation was also needed and should be developed first. While the decision to go ahead with a permanently manned Space Station was on hold, requirements for the use of the Station were accumulating as ground-based research and the data from unmanned spacecraft sparked the imagination of both scientists and entrepreneurs. Thus, by the time of the Space Station implementation decision in the early 1980's, a variety of disciplines, with a variety of requirements, needed to be accommodated on one Space Station. Additional future requirements could be forecast for advanced missions that were still in the early planning stages. The logical response was the development of a multi-purpose Space Station with the ability to evolve on-orbit to new capabilities as required by user needs and national or international decisions, i.e., to build an evolutionary Space Station. Planning for evolution is conducted in parallel with the design and development of the baseline Space Station. Evolution planning is a strategic management process to facilitate change and protect future decisions. The objective is not to forecast the future, but to understand the future options and the implications of these on today's decisions. The major actions required now are: (1) the incorporation of evolution provisions (hooks and scars) in the baseline Space Station; and (2) the initiation of an evolution advanced development program.

Diaz, Alphonso V.↗

Localization of Ad-Hoc Lunar Constellations in Communication Failure Modes for Distributed Spacecraft Autonomy

As Lunar missions increase in complexity, inspired by NASA’s Artemis Program, they will require reliable and sufficient Position, Navigation, and Timing (PNT) capability to support the upcoming Lunar users. The navigation service should also be compatible with the smaller platforms, like CubeSats, being sent by the public and private sectors. A non-dedicated, ad-hoc Lunar navigation constellation can provide PNT services on-demand using the non-dedicated swarm assets. Swarm members cooperatively and autonomously localize themselves with minimal interaction from Earth, freeing up valuable bandwidth and ground segment resources. The autonomous localization of Lunar constellations utilizes neighbor two-way intersatellite link (ISL) measurements in a distributed extended Kalman filter (DEKF) system to minimize operating costs. Because the decentralized Lunar PNT system relies on relay communication amongst the agents, network failures or loss of assets among ad-hoc Lunar constellations may impact localization performance. This study presents an evaluation of localization performance under increasing levels of network degradation. A simulation of an ad-hoc Lunar PNT swarm is augmented to include system faults and the impacts of intermittent and permanent failures on localization performance are evaluated. We investigate three potential causes of network degradation: single spacecraft loss, multiple spacecraft loss, and antenna failure. The numerical assessments from the simulation show that the LPNT system under study, based on an autonomous decentralized concept of operation, is highly robust and resilient to communication failures. Minor faults, such as single spacecraft loss, solar interference, technical malfunctions, message delays, and antenna outages, have minimal impact on state estimation, with only a 4.47% and 3.75% degradation in median position error for assets and a representative ground user, respectively, compared to an ideal communication scenario. However, major faults, such as hardware failures or meteor strikes leading to the loss of multiple spacecrafts, are more concerning. The permanent loss of three spacecraft results in a more severe performance degradation, with median position error increasing by 23.3% for assets and 11.7% for a representative ground user, despite the Lunar PNT system remaining functional.

Yeji Kim↗

Crew Medical Training to Progressively Enable EIMO

Background. Onboard medical capabilities have greatly expanded over the history of the US space program. Newly identified space-related medical conditions, technological advances, and longer mission durations have led to an increasing need for on-demand medical expertise. Lengthy communications delays, lack of resupply and evacuation opportunities on exploration-class missions place an ever-increasing burden on the crew to provide medical care. Having adequate knowledge, skills, and abilities (KSA) available is an essential component of successful Earth Independent Medical Operations (EIMO). Without appropriate crew training and KSA, cutting-edge medical equipment has little value. Presumably, the crew will include a qualified physician; however, if the physician is incapacitated, a non-physician crew medical officer (CMO) will be needed. While more crew time is needed for medical training, there will be concomitant increases in preflight training demands for vehicle system management, operations, science, and contingencies. In truly independent operations, onboard resources such as just-in-time training, mixed reality, decision support tools, and AI-enabled chatbot “consultants” will be needed to augment KSA. Overview. Because of crew time constraints, topical priorities must be determined for preflight training. Curricula should be developed that emphasize management of conditions with relatively high incidence and morbidity/mortality. Defining the required KSA levels to treat each condition is essential, but all crewmembers should have basic lifesaving skills. Procedural and diagnostic training on live patients and simulators should be prioritized over classroom lectures. Crews must be trained with onboard equipment, resources, mixed reality, and AI-based decision support tools. Mission simulations should include medical problems with/without ground support and with appropriate communication delays. Certification guidelines for each level of KSA must be established. Skills rapidly decay for non-physician CMO’s; both pre-flight and in-flight refresher training will be needed. During spaceflight just-in-time training, simulations, and onboard CME with crew physician can help retain skills. Discussion. Medical technology, simulation design, mixed reality, and AI are advancing at a dizzying rate. Recognizing the severe constraints on crew time, it is critical that astronaut training is highly efficient and adapted to keep pace with new innovations both pre-flight and during exploration missions. These challenges will be discussed during this panel session.

Jay Lemery↗

Clinical Decision Support Project

As NASA plans for exploration missions into deep space, significant challenges are realized due to the distance from Earth. Beside the effects of microgravity and radiation exposure, the astronauts face the additional constraints of isolation, lack of resupply, increasingly difficult evacuation, and delayed and disrupted communication with ground-based medical care providers. These constraints require a paradigm shift from current medical care where crews rely on the real-time communications with ground-based medical care providers toward Earth-independent medical operations for astronaut medical care. Medical expertise and decision-making are ground-based for current International Space Station and planned Lunar missions. However, a deep space exploration crew will need to autonomously perform the detection, diagnosis, treatment, and prevention of medical conditions. One approach to provide Earth-independent medical operations is to augment the requisite knowledge, skills, and abilities (KSAs) of a time-constrained crew—operating under stressful conditions, combatting fatigue, and facing a potential medical crisis—with a robust clinical decision support system (CDSS). The CDSS is envisioned as an integrated, software-based tool deployed on a laptop computer or handheld device. The CDSS will assist the crew and ground support when interacting with knowledge/data bases (e.g. records, pharmacy, schedule), instrumentation (e.g. imaging, physiological monitoring devices), and habitat (e.g. wellness system, task performance system) and vehicle systems (e.g. environmental system, communication system). In addition, the human interface will employ a context-based approach that accounts for the crew’s situation. Thus, extraneous and clinically/operationally non-relevant information are reduced to avoid an increase in cognitive load. The framework of an ideal spaceflight CDSS is to include core and advanced analytical features that maintain a flexible platform for integrating new technology in the future. The Exploration Medical Capability (ExMC) Element of the Human Research Program (HRP) is expanding the boundaries of space medical systems to advance the care of astronauts on future exploration missions beyond low Earth orbit by actively identifying and testing next-generation medical care and crew health maintenance technologies. The Clinical Decision Support (CDS) project addressed ap Medical-701 within the Inflight Medical Conditions risk: “We need to increase inflight medical capabilities and identify new capabilities that (a) maximize benefit and/or (b) reduce “costs” on human system/mission/vehicle resources.” Though mass, volume, and power will face increasing constraints, the projected computational capabilities of spacecraft systems will increase exponentially as information technology advances in this decade and beyond. Hence, data, software, and computational resources will play an essential and synergistic role in maintaining crew health, wellness, and performance in deep space missions. The focus of the CDS project was to develop recommended requirements for an in-vehicle CDSS that acts as a ‘virtual assistant’ for delivering optimal health, performance, and medical care during exploration missions. In fiscal year 2022 (FY22), the CDS project was chartered to baseline and/or revise all CDS project related documentation and update the CDS project model to include the revised CDSS Concept of Operations, revised systems-based modeling language (SysML) activity diagrams, and baseline requirements. The focus of this presentation will be an overview of the CDS products and CDS model content.

Decision Support↗

The X-43A Flight Research Program: Lessons Learned on the Road to Mach 10

During an aerospace engineer's undergraduate studies, he or she will attend classes in aerodynamics, thermodynamics, structures, stability and control, dynamics, design, propulsion, and computer science, along with the related courses in mathematics, physics, statistics, and chemistry required to understand the material. Upon graduation, the new engineer will have acquired a basic knowledge of how to build an aerospace vehicle. What only comes through experience, however, is the understanding of the inevitable imperfect process through which an aerospace vehicle is built. This is the adventure of turning a basic concept into functional hardware. Engineers working on a project must often deal with ambiguous situations. They are routinely asked by management to provide risk assessments of a project, yet even after careful analysis uncertainties remain. The project must be accomplished within finite limits of time and money. The question an engineer answers is whether the solution to potential problem is worth the cost and schedule delay, or if the solution might actually be worse than the problem it is meant to solve. Review protocols are established to ensure that an unknown has not been overlooked. But these cannot protect against an unknown unknown. Examples of these situations can be found in the history of the X-43A Hyper-X (Hypersonic Experiment) program. In this NASA project, a supersonic combustion ramjet (scramjet) engine was flight tested on a subscale vehicle. The X-43A Hyper-X Research Vehicle (HXRV) was launched from a B-52B mothership, then boosted to the test speed by a modified Pegasus rocket first stage, called the Hyper-X Launch Vehicle (HXLV). Once at the proper speed and altitude, the X-43A separated from the booster, stabilized itself, and then the engine test began. Although wind-tunnel scramjet engine tests had begun in the late 1950s, before the Hyper-X program there had never been an actual in-flight test of such an engine integrated with an appropriate airframe. Thus, while the scramjet had successfully operated in the artificial airflow of wind tunnels, the concept had yet to be proven in real air. These conditions meant changes in density and temperature, as well as changes in angle of attack and sideslip of a free-flying vehicle. A wind tunnel is limited in its ability to simulate these subtle factures, which have a major impact on almost any vehicle, but especially that of a scramjet's performance. The Hyper-X project was to provide a real-world benchmark of the ground test data. The full scale X-43A engine would be operated in the wind tunnel, and then flown, and the data from its operation would then be compared with projections. If these matched, the wind tunnel data would be considered a reliable design tool for future scramjet. If there were significant differences, the reasons for these would have to be identified. Until such information was available, scramjets would lack the technological maturity to be considered for future space launch or high-speed atmospheric flight vehicles.

Peebles, Curtis↗