Search NASA⌕ Search

SEARCH · Search NASA

Results for “Space Flight Architecture”

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 235 records · Page 13

Launch site integration for mixed fleet operations

Launch site impacts and integration planning issues are presented to support launch operations for a mixed vehicle fleet (manned and cargo). Proposed ground systems and launch site configurations are described. Prelaunch processing scenarios and schedules are developed for candidate launch vehicles. Earth-to-orbit (ETO) vehicle architectures are presented to meet future launch requirements, including the Space Exploration Initiative (SEI). Flight vehicle design recommendations to enhance launch processing are discussed. The significance of operational designs for future launch vehicles is shown to be a critical factor in planning for mixed fleet launch site operations.

Scott, L. P.↗

Applications of intelligent computer-aided training

Intelligent computer-aided training (ICAT) systems simulate the behavior of an experienced instructor observing a trainee, responding to help requests, diagnosing and remedying trainee errors, and proposing challenging new training scenarios. This paper presents a generic ICAT architecture that supports the efficient development of ICAT systems for varied tasks. In addition, details of ICAT projects, built with this architecture, that deliver specific training for Space Shuttle crew members, ground support personnel, and flight controllers are presented. Concurrently with the creation of specific ICAT applications, a general-purpose software development environment for ICAT systems is being built. The widespread use of such systems for both ground-based and on-orbit training will serve to preserve task and training expertise, support the training of large numbers of personnel in a distributed manner, and ensure the uniformity and verifiability of training experiences.

Loftin, R. B.↗

Autonomic Computing for Spacecraft Ground Systems

Autonomic computing for spacecraft ground systems increases the system reliability and reduces the cost of spacecraft operations and software maintenance. In this paper, we present an autonomic computing solution for spacecraft ground systems at NASA Goddard Space Flight Center (GSFC), which consists of an open standard for a message oriented architecture referred to as the GMSEC architecture (Goddard Mission Services Evolution Center), and an autonomic computing tool, the Criteria Action Table (CAT). This solution has been used in many upgraded ground systems for NASA 's missions, and provides a framework for developing solutions with higher autonomic maturity.

Li, Zhenping↗

Embedded Thermal Control for Spacecraft Subsystems Miniaturization

Optimization of spacecraft size, weight and power (SWaP) resources is an explicit technical priority at Goddard Space Flight Center. Embedded Thermal Control Subsystems are a promising technology with many cross cutting NSAA, DoD and commercial applications: 1.) CubeSatSmallSat spacecraft architecture, 2.) high performance computing, 3.) On-board spacecraft electronics, 4.) Power electronics and RF arrays. The Embedded Thermal Control Subsystem technology development efforts focus on component, board and enclosure level devices that will ultimately include intelligent capabilities. The presentation will discuss electric, capillary and hybrid based hardware research and development efforts at Goddard Space Flight Center. The Embedded Thermal Control Subsystem development program consists of interrelated sub-initiatives, e.g., chip component level thermal control devices, self-sensing thermal management, advanced manufactured structures. This presentation includes technical status and progress on each of these investigations. Future sub-initiatives, technical milestones and program goals will be presented.

Thermal Control↗

Deep Space Test Bed

The DSTB Facility provides a new capability for the National Aeronautics and Space Administration s (NASA s) Space Radiation Shielding Project (SRSP). The objective of the DSTB is to provide a platform to conduct radiation shielding investigations in an environment more similar to deep space than most Low Earth orbits or is achievable at a particle accelerator. The DSTB provides a means to experimentally test radiation shielding effectiveness of various materials and to test the accuracy of radiation transport code predictions in the deep space cosmic ray environment more frequently and at a lower cost compared to space flight missions. New spectrometers, dosimeters and other techniques may be exercised and verified using the DSTB before space flight. The DSTB will be implemented through NASA s National Scientific Balloon Facility (NSBF) which provides polar balloon flights that lift science payloads to high altitude (120,000 A. (36.58km)) to escape much of the shielding effects of the Earth s atmosphere and magnetosphere. Polar flights are conducted through NSBF in coordination with the United States Polar Program. The DSTB will be launched on a Long Duration Balloon (LDB) from McMurdo, Antarctica (77.86 degrees south latitude) for circumpolar flights, nominally 20 days, traveling to the west and typically bounded between 73 to 82 degrees south latitude. Float altitudes for these balloons with payload are 115,000 to 130,000 feet (35.05 to 39.62km). The DSTB will be able to accommodate up to 20 investigations per flight. Annual flight opportunities are planned starting in December 2005. Balloon campaigns in Antarctica occur in December and January during the Austral summer. Since a key goal of the DSTB facility is to efficiently serve the varied needs of the radiation shielding community; it must be designed with a flexible architecture. By implementing the DSTB facility with NASA s balloon program, which operates under reduced formalities compared to space flight, the DSTB facility can adjust for different investigation priorities on successive flights. This flexibility in the DSTB will be applied at several levels; in the distribution of the shared resources for each flight; addressing the payload configuration on a system level for each flight; and utilizing a selection process for investigations that considers yearly flight opportunities as well as the possibility for repeated flights. This approach for operating the DSTB facility will allow it to handle a wide range of investigations.

Milton, Martha E.↗

Architecture Study on Telemetry Coverage for Immediate Post-Separation Phase

This paper presents the preliminary results of an architecture study that provides continuous telemetry coverage for NASA missions for immediate post-separation phase. This study is a collaboration effort between Jet Propulsion Laboratory (JPL), Goddard Space Flight Center (GSFC), and Applied Physics Laboratory (APL). After launch when the spacecraft separated from the upper stage, the spacecraft typically executes a number of mission-critical operations prior to the deployment of solar panels and the activation of the primary communication subsystem. JPL, GSFC, and APL have similar design principle statements that require continuous coverage of mission-critical telemetry during the immediate post-separation phase. To conform to these design principles, an architecture that consists of a separate spacecraft transmitter and a robust communication network capable of tracking the spacecraft signals is needed.This paper presents the preliminary results of an architecture study that provides continuous telemetry coverage for NASA missions for immediate post-separation phase. This study is a collaboration effort between Jet Propulsion Laboratory (JPL), Goddard Space Flight Center (GSFC), and Applied Physics Laboratory (APL). After launch when the spacecraft separated from the upper stage, the spacecraft typically executes a number of mission-critical operations prior to the deployment of solar panels and the activation of the primary communication subsystem. JPL, GSFC, and APL have similar design principle statements that require continuous coverage of mission-critical telemetry during the immediate post-separation phase. To conform to these design principles, an architecture that consists of a separate spacecraft transmitter and a robust communication network capable of tracking the spacecraft signals is needed. The main results of this study are as follows: 1) At low altitude (< 10000 km) when most post-separation critical operations are executed, Earth-based network (e.g. Deep Space Network (DSN)) can only provide limited coverage, whereas space-based network (e.g. Space Network (SN)) can provide continuous coverage. 2) Commercial-off-the-shelf SN compatible transmitters are available for small satellite applications. In this paper we present the detailed coverage analysis of Earth-based and Space-based networks. We identify the key functional and performance requirements of the architecture, and describe the proposed selection criteria of the spacecraft transmitter. We conclude the paper with a proposed forward plan.

architecture↗

The importance of the space station as an element of the total Space System architecture

The paper describes the role of the Space Station in the ensemble of the space-based infrastructure necessary for achieving permanent manned presence in space. The major elements of the architecture are identified, functionally interrelated and discussed in terms of their evolutionary development as an extension of current STS capabilities. It is shown that they require a logical succession of flight R&D experiments and demonstrations using the Space Shuttle and the Space Station as test beds. The paper describes the interrelationships between the Space Station and the various major infrastructure elements and shows that the latter are indispensable for full operational utilization of the former. Only the total ensemble of the architecture provide all the necessary prerequisites for permanent manned presence in space.

Bekey, I.↗

Orion Launch Abort System Performance on Exploration Flight Test 1

This paper will present an overview of the flight test objectives and performance of the Orion Launch Abort System during Exploration Flight Test-1. Exploration Flight Test-1, the first flight test of the Orion spacecraft, was managed and led by the Orion prime contractor, Lockheed Martin, and launched atop a United Launch Alliance Delta IV Heavy rocket. This flight test was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety. This test included the first flight test of the Launch Abort System preforming Orion nominal flight mission critical objectives. NASA is currently designing and testing the Orion Multi-Purpose Crew Vehicle (MPCV). Orion will serve as NASA's new exploration vehicle to carry astronauts to deep space destinations and safely return them to earth. The Orion spacecraft is composed of four main elements: the Launch Abort System, the Crew Module, the Service Module, and the Spacecraft Adapter (Fig. 1). The Launch Abort System (LAS) provides two functions; during nominal launches, the LAS provides protection for the Crew Module from atmospheric loads and heating during first stage flight and during emergencies provides a reliable abort capability for aborts that occur within the atmosphere. The Orion Launch Abort System (LAS) consists of an Abort Motor to provide the abort separation from the Launch Vehicle, an Attitude Control Motor to provide attitude and rate control, and a Jettison Motor for crew module to LAS separation (Fig. 2). The jettison motor is used during a nominal launch to separate the LAS from the Launch Vehicle (LV) early in the flight of the second stage when it is no longer needed for aborts and at the end of an LAS abort sequence to enable deployment of the crew module's Landing Recovery System. The LAS also provides a Boost Protective Cover fairing that shields the crew module from debris and the aero-thermal environment during ascent. Although the Orion Program has tested a number of the critical systems of the Orion spacecraft on the ground, the launch environment cannot be replicated completely on Earth. A number of flight tests have been conducted and are planned to demonstrate the performance and enable certification of the Orion Spacecraft. Exploration Flight Test 1, the first flight test of the Orion spacecraft, was successfully flown on December 5, 2014 from Cape Canaveral Air Force Station's Space Launch Complex 37. Orion's first flight was a two-orbit, high-apogee, high-energy entry, low-inclination test mission used to validate and test systems critical to crew safety, such as heat shield performance, separation events, avionics and software performance, attitude control and guidance, parachute deployment and recovery operations. One of the key separation events tested during this flight was the nominal jettison of the LAS. Data from this flight will be used to verify the function of the jettison motor to separate the Launch Abort System from the crew module so it can continue on with the mission. The LAS nominal jettison event on Exploration Flight Test 1 occurred at six minutes and twenty seconds after liftoff (See Fig. 3). The abort motor and attitude control motors were inert for Exploration Flight Test 1, since the mission did not require abort capabilities. A suite of developmental flight instrumentation was included on the flight test to provide data on spacecraft subsystems and separation events. This paper will focus on the flight test objectives and performance of the LAS during ascent and nominal jettison. Selected LAS subsystem flight test data will be presented and discussed in the paper. Exploration Flight Test -1 will provide critical data that will enable engineering to improve Orion's design and reduce risk for the astronauts it will protect as NASA continues to move forward on its human journey to Mars. The lessons learned from Exploration Flight Test 1 and the other Flight Test Vehicles will certainly contribute to the vehicle architecture of a human-rated space launch vehicle.

McCauley, R.↗

Cell-wall architecture and lignin composition of wheat developed in a microgravity environment

The microgravity environment encountered during space-flight has long been considered to affect plant growth and developmental processes, including cell wall biopolymer composition and content. As a prelude to studying how microgravity is perceived - and acted upon - by plants, it was first instructive to investigate what gross effects on plant growth and development occurred in microgravity. Thus, wheat seedlings were exposed to microgravity on board the space shuttle Discovery (STS-51) for a 10 day duration, and these specimens were compared with their counterparts grown on Earth under the same conditions (e.g. controls). First, the primary roots of the wheat that developed under both microgravity and 1 g on Earth were examined to assess the role of gravity on cellulose microfibril (CMF) organization and secondary wall thickening patterns. Using a quick freeze/deep etch technique, this revealed that the cell wall CMFs of the space-grown wheat maintained the same organization as their 1 g-grown counterparts. That is, in all instances, CMFs were randomly interwoven with each other in the outermost layers (farthest removed from the plasma membrane), and parallel to each other within the individual strata immediately adjacent to the plasma membranes. The CMF angle in the innermost stratum relative to the immediately adjacent stratum was ca 80 degrees in both the space and Earth-grown plants. Second, all plants grown in microgravity had roots that grew downwards into the agar; they did not display "wandering" and upward growth as previously reported by others. Third, the space-grown wheat also developed normal protoxylem and metaxylem vessel elements with secondary thickening patterns ranging from spiral to regular pit to reticulate thickenings. Fourthly, both the space- and Earth-grown plants were essentially of the same size and height, and their lignin analyses revealed no substantial differences in their amounts and composition regardless of the gravitational field experienced, i.e. for the purposes of this study, all plants were essentially identical. These results suggest that the microgravity environment itself at best only slightly affected either cell wall biopolymer synthesis or the deposition of CMFs, in contrast to previous assertions.

manned↗

MUSTANG: A Workhorse for NASA Spaceflight Avionics

The Modular Unified Space Technology Avionics for Next Generation (MUSTANG) is a small integrated Avionics system including Command and Data Handling (C&DH), Power System Electronics (PSE), Attitude Control System Interfaces (ACS), and Propulsion Electronics. The MUSTANG Avionics Architecture is built upon many years of knowledge capture and lessons learned at the Goddard Space Flight Center. With a motivation towards modularity and keeping board redesign costs to a minimum, MUSTANG offers flexibility in features with a backplane-less design and allows the user to choose the options (cards) needed for their system. It incorporates a distributed power system that provides secondary power to all its subcomponents reducing the number of primary services needed for an Avionics. MUSTANG can be integrated into one system or divided into several smaller components. MUSTANG supports redundancy and cross-strap ability for a more robust and reliable Avionics system. A variation of MUSTANG exists for Instrument Electronics called iMUSTANG and allows the user to select functionality applicable to the instrument electronics. MUSTANG is not meant to replace Avionics for all spacecraft. There are limitations due to its relatively compact size, but the MUSTANG design has proven broadly applicable on many spacecraft and instrument bus avionics architectures.

MUSTANG↗

Dynamic Routing for Delay-Tolerant Networking in Space Flight Operations

Contact Graph Routing (CGR) is a dynamic routing system that computes routes through a time-varying topology composed of scheduled, bounded communication contacts in a network built on the Delay-Tolerant Networking (DTN) architecture. It is designed to support operations in a space network based on DTN, but it also could be used in terrestrial applications where operation according to a predefined schedule is preferable to opportunistic communication, as in a low-power sensor network. This paper will describe the operation of the CGR system and explain how it can enable data delivery over scheduled transmission opportunities, fully utilizing the available transmission capacity, without knowing the current state of any bundle protocol node (other than the local node itself) and without exhausting processing resources at any bundle router.

CGR↗

Executive Summary of Propulsion on the Orion Abort Flight-Test Vehicles

The National Aeronautics and Space Administration Orion Flight Test Office was tasked with conducting a series of flight tests in several launch abort scenarios to certify that the Orion Launch Abort System is capable of delivering astronauts aboard the Orion Crew Module to a safe environment, away from a failed booster. The first of this series was the Orion Pad Abort 1 Flight-Test Vehicle, which was successfully flown on May 6, 2010 at the White Sands Missile Range in New Mexico. This report provides a brief overview of the three propulsive subsystems used on the Pad Abort 1 Flight-Test Vehicle. An overview of the propulsive systems originally planned for future flight-test vehicles is also provided, which also includes the cold gas Reaction Control System within the Crew Module, and the Peacekeeper first stage rocket motor encased within the Abort Test Booster aeroshell. Although the Constellation program has been cancelled and the operational role of the Orion spacecraft has significantly evolved, lessons learned from Pad Abort 1 and the other flight-test vehicles could certainly contribute to the vehicle architecture of many future human-rated space launch vehicles

Jones, Daniel S.↗

Designing for Annual Spacelift Performance

This paper presents a methodology for approaching space launch system design from a total architectural point of view. This different approach to conceptual design is contrasted with traditional approaches that focus on a single set of metrics for flight system performance, i.e., payload lift per flight, vehicle mass, specific impulse, etc. The approach presented works with a larger set of metrics, including annual system lift, or "spacelift" performance. Spacelift performance is more inclusive of the flight production capability of the total architecture, i.e., the flight and ground systems working together as a whole to produce flights on a repeated basis. In the proposed methodology, spacelift performance becomes an important design-for-support parameter for flight system concepts and truly advanced spaceport architectures of the future. The paper covers examples of existing system spacelift performance as benchmarks, points out specific attributes of space transportation systems that must be greatly improved over these existing designs, and outlines current activity in this area.

spaceports↗

The Orion Pad Abort 1 (PA-1) Flight Test: A Propulsion Success

This poster provides a concise overview of the highly successful Orion Pad Abort 1 (PA-1) flight test, and the three rocket motors that contributed to this success. The primary purpose of the Orion PA-1 flight was to help certify the Orion Launch Abort System (LAS), which can be utilized in the unlikely event of an emergency on the launchpad or during mission vehicle ascent. The PA-1 test was the first fully integrated flight test of the Orion LAS, one of the primary systems within the Orion Multi-Purpose Crew Vehicle (MPCV). The Orion MPCV is part of the architecture within the Space Launch System (SLS), which is being designed to transport astronauts beyond low-Earth orbit for future exploration missions. Had the Orion PA-1 flight abort occurred during launch preparations for a real human spaceflight mission, the PA-1 LAS would have saved the lives of the crew. The PA-1 flight test was largely successful due to the three solid rocket motors of the LAS: the Attitude Control Motor (ACM); the Jettison Motor (JM); and the Abort Motor (AM). All three rocket motors successfully performed their required functions during the Orion PA-1 flight test, flown on May 6, 2010 at the White Sands Missile Range in New Mexico, culminating in a successful demonstration of an abort capability from the launchpad.

JM↗

Orion Launch Abort System (LAS) Propulsion on Pad Abort 1 (PA-1)

This presentation provides a concise overview of the highly successful Orion Pad Abort 1 (PA-1) flight test, and the three rocket motors that contributed to this success. The primary purpose of the Orion PA-1 flight was to help certify the Orion Launch Abort System (LAS), which can be utilized in the unlikely event of an emergency on the launchpad or during mission vehicle ascent. The PA-1 test was the first fully integrated flight test of the Orion LAS, one of the primary systems within the Orion Multi-Purpose Crew Vehicle (MPCV). The Orion MPCV is part of the architecture within the Space Launch System (SLS), which is being designed to transport astronauts beyond low-Earth orbit for future exploration missions. Had the Orion PA-1 flight abort occurred during launch preparations for a real human spaceflight mission, the PA-1 LAS would have saved the lives of the crew. The PA-1 flight test was largely successful due to the three solid rocket motors of the LAS: the Attitude Control Motor (ACM); the Jettison Motor (JM); and the Abort Motor (AM). All three rocket motors successfully performed their required functions during the Orion PA-1 flight test, flown on May 6, 2010 at the White Sands Missile Range in New Mexico, culminating in a successful demonstration of an abort capability from the launchpad.

SLS↗

Architecting Systems for Human Space Flight

Human-system interactions have been largely overlooked in the traditional systems engineering process. Awareness of human factors (HF) has increased in the past few years, but the involvement of HF specialists is still often too little and too late. In systems involving long-duration human space flight, it is essential that the human component be properly considered in the initial architectural definition phase, as well as throughout the system design process. HF analysis must include not only the strengths and limitations of humans in general, but the variability between individuals and within an individual over time, and the dynamics of group interactions.

Wocken, Gerald↗

Transformational Spaceport and Range Concept of Operations: A Vision to Transform Ground and Launch Operations

The Transformational Concept of Operations (CONOPS) provides a long-term, sustainable vision for future U.S. space transportation infrastructure and operations. This vision presents an interagency concept, developed cooperatively by the Department of Defense (DoD), the Federal Aviation Administration (FAA), and the National Aeronautics and Space Administration (NASA) for the upgrade, integration, and improved operation of major infrastructure elements of the nation s space access systems. The interagency vision described in the Transformational CONOPS would transform today s space launch infrastructure into a shared system that supports worldwide operations for a variety of users. The system concept is sufficiently flexible and adaptable to support new types of missions for exploration, commercial enterprise, and national security, as well as to endure further into the future when space transportation technology may be sufficiently advanced to enable routine public space travel as part of the global transportation system. The vision for future space transportation operations is based on a system-of-systems architecture that integrates the major elements of the future space transportation system - transportation nodes (spaceports), flight vehicles and payloads, tracking and communications assets, and flight traffic coordination centers - into a transportation network that concurrently accommodates multiple types of mission operators, payloads, and vehicle fleets. This system concept also establishes a common framework for defining a detailed CONOPS for the major elements of the future space transportation system. The resulting set of four CONOPS (see Figure 1 below) describes the common vision for a shared future space transportation system (FSTS) infrastructure from a variety of perspectives.

Source record↗

Future Standardization of Space Telecommunications Radio System with Core Flight System

NASA Glenn Research Center (GRC) is integrating the NASA Space Telecommunications Radio System (STRS) Standard with the Core Flight System (cFS), an avionics software operating environment. The STRS standard provides a common, consistent framework to develop, qualify, operate and maintain complex, reconfigurable and reprogrammable radio systems. The cFS is a flexible, open architecture that features a plugand- play software executive called the Core Flight Executive (cFE), a reusable library of software components for flight and space missions and an integrated tool suite. Together, STRS and cFS create a development environment that allows for STRS compliant applications to reference the STRS application programmer interfaces (APIs) that use the cFS infrastructure. These APIs are used to standardize the communication protocols on NASAs space SDRs. The cFS-STRS Operating Environment (OE) is a portable cFS library, which adds the ability to run STRS applications on existing cFS platforms. The purpose of this paper is to discuss the cFS-STRS OE prototype, preliminary experimental results performed using the Advanced Space Radio Platform (ASRP), the GRC S‑ band Ground Station and the SCaN (Space Communication and Navigation) Testbed currently flying onboard the International Space Station (ISS). Additionally, this paper presents a demonstration of the Consultative Committee for Space Data Systems (CCSDS) Spacecraft Onboard Interface Services (SOIS) using electronic data sheets (EDS) inside cFE. This configuration allows for the data sheets to specify binary formats for data exchange between STRS applications. The integration of STRS with cFS leverages mission-proven platform functions and mitigates barriers to integration with future missions. This reduces flight software development time and the costs of software-defined radio (SDR) platforms. Furthermore, the combined benefits of STRS standardization with the flexibility of cFS provide an effective, reliable and modular framework to minimize software development efforts for spaceflight missions.

space communications↗