Space Launch System Flight Readiness Analysis Cycle Approach
Space Launch System Flight Readiness Analysis Cycle Approach
SEARCH · Engineering Papers
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.
Space Launch System Flight Readiness Analysis Cycle Approach
The integration process of the MAST flight system is surveyed. Insight is given into the planned orbital experiment process. The data flow necessary to support the flight operation is outlined.
Papers concerning flight testing and simulation programs for evaluating manned aerospace systems
The development and verification of the Backup Flight System software (BFS) is discussed. The approach taken for the BFS was to develop a very simple and straightforward software program and then test it in every conceivable manner. The result was a program that contained approximately 12,000 full words including ground checkout and the built in test program for the computer. To perform verification, a series of tests was defined using the actual flight type hardware and simulated flight conditions. Then simulated flights were flown and detailed performance analysis was conducted. The intent of most BFS tests was to demonstrate that a stable flightpath could be obtained after engagement from an anomalous initial condition. The extention of the BFS to meet the requirements of the orbital flight test phase is also described.
The present technology used to monitor systems in flight tests is not advanced enough for the modern avionics in high performance aircraft. Research is being conducted at NASA's Dryden Flight Research Facility to design an expert system to monitor test flights. The expert system is to automatically detect any problems in the flight control system (FCS), interpret the problem from the information contained in its knowledge base, inform the systems engineer, and recommend solutions. The data is to be downlinked from the aircraft to the control room. The expert system will lessen the responsibilities of the engineers by providing them with fast, expert advice. Time is the most critical factor in flight testing and the expert system will be able to quickly recognize discrepancies and provide corrections. A demonstration of the expert system, not operating in real time, has already been tested.
In this presentation, we will demonstrate an example Core Flight System (cFS) application written in C++, compatible with the Draco releases of the Core Flight Executive (cFE) and NASA Operating System Abstraction Layer (OSAL). The application boilerplate, supporting library, and associated generation script were recently developed and licensed under the permissive Apache License 2.0 with the goal of easing the cFS app development with C++. The design and features of this application will be presented, including a higher-level interface for interactions with the cFE software bus pipes, tables, and event services. Data structures are provided for centralized telecommand and telemetry parsing which isolates bookkeeping of message components from the calling code in an application's core logic. Specific advantages of writing a cFS application in C++ will be shown, including easier avoidance of symbol collisions via namespaces, expanded compile-time checks via constant expressions, default initialization for data structures, null safety via references, improved syntax for operating on multi-dimensional arrays, and reliable serialization of enumerations via enumeration classes. Special considerations needed for integrating a C++ application will be identified, including function linkage, exceptions, and stack unwinding. Evidence for the usefulness of this template will be discussed in the context of development of a flight software application used for interfacing with a solid-state data recorder.
Simulation & analysis of shock & vibration environments of space flight systems
A scintillation counter time of flight system, incorporated into the Goddard 50 cm by 50 cm spark chamber gamma ray telescope is described. The system, which utilizes constant fractions timing and particle position compensation and digitizes up to 10 ns time differences to six bit accuracy in less than 500 ns is analyzed. The performance of this system during balloon flight is discussed.
Within a few years, JPL will be challenged by the most active mission set in history. Concurrently, flight systems are increasingly more complex. Presently, the knowledge to conduct integration and test of spacecraft and large instruments is held by a few key people, each with many years of experience. JPL is in danger of losing a significant amount of this critical expertise, through retirement, during a period when demand for this expertise is rapidly increasing. The most critical issue at hand is to collect and retain this expertise and develop tools that would ensure the ability to successfully perform the integration and test of future spacecraft and large instruments. The proposed solution was to capture and codity a subset of existing knowledge, and to utilize this captured expertise in knowledge-based systems. First year results and activities planned for the second year of this on-going effort are described. Topics discussed include lessons learned in knowledge acquisition and elicitation techniques, life-cycle paradigms, and rapid prototyping of a knowledge-based advisor (Spacecraft Test Assistant) and a hypermedia browser (Test Engineering Browser). The prototype Spacecraft Test Assistant supports a subset of integration and test activities for flight systems. Browser is a hypermedia tool that allows users easy perusal of spacecraft test topics. A knowledge acquisition tool called ConceptFinder which was developed to search through large volumes of data for related concepts is also described and is modified to semi-automate the process of creating hypertext links.
A thermal protection system (TPS) flight repair kit required for use on a flight of the Space Transportation System is defined. A means of making TPS repairs in orbit by the crew via extravehicular activity is discussed. A cure in place ablator, a precured ablator (large area application), and packaging design (containers for mixing and dispensing) for the TPS are investigated.
Human rated space vehicles have historically employed a Backup Flight System (BFS) for the main purpose of mitigating the loss of the primary avionics control system. Throughout these projects, however, the underlying philosophy and technical implementation vary greatly. This paper attempts to coalesce each of the past space vehicle program's BFS design and implementation methodologies with the accompanying underlining philosophical arguments that drove each program to such decisions. The focus will be aimed at Mercury, Gemini, Apollo, and Space Shuttle However, the ideologies and implementation of several commercial and military aircraft are incorporated as well to complete the full breadth view of BFS development across the varying industries. In particular to the non-space based vehicles is the notion of deciding not to utilize a BFS. A diverse analysis of BFS to primary system benefits in terms of reliability against all aspects of project development are reviewed and traded. The risk of engaging the BFS during critical stages of flight (e.g. ascent and entry), the level of capability of the BFS (subset capability of main system vs. equivalent system), and the notion of dissimilar hardware and software design are all discussed. Finally, considerations for employing a BFS on future human-rated space missions are reviewed in light of modern avionics architectures and mission scenarios implicit in exploration beyond low Earth orbit.
Materials illustrating presentations on the development of electric flight systems for the all-electric aircraft and for spacecraft are presented.
High temperature liquid metal instrumentation for SNAP-10A flight system and mercury vapor quality
This paper offers a comprehensive view of flight system integration and test (I&T) lessons learned related to mishaps and close calls, focusing on what can be done to improve the I&T process to avoid recurrence. Specific areas within the realm of I&T that are covered in this paper include: I&T team communication and training; design of flight and ground systems for I&T; planning and scheduling; configuration management and process documentation; ground support equipment and tools; cleanrooms and contamination; mechanical integration, handling, and deployments; electrical integration and electrostatic discharge; functional testing and troubleshooting; environmental testing and facilities; and launch site operations. To illustrate "real-world" lessons learned for I&T, examples from throughout the history of the U.S. space program are presented. Also presented are some best practices for I&T that can help mitigate mishaps and close calls on the ground or during flight.
The Near Earth Asteroid Scout flight mission is set to launch on the maiden voyage of the Space Launch System as a secondary payload. The spacecraft will be jettisoned in cis-lunar space and embark on an ambitious 2.5 year mission to image an asteroid. The spacecraft is uniquely equipped with an 85m2 solar sail as the main propulsion system. The monolithic sail system is designed to package within a 6U volume for launch and then deploy during flight. The NEA Scout team has presented in the past to the International Symposium on Solar Sailing topics related to the engineering development unit and design efforts to achieve flight hardware build. This paper will focus on the lessons learned from building and testing the NEA Scout flight system. Focus will be on the mechanical, software, and electrical interfaces as well as preparation for subsystem environmental tests, including thermal vacuum. Due to the unique design of the spacecraft, the solar sail subsystem was required to be located in the center of the spacecraft. This requirement lead to design challenges such as designing and accommodating critical cable harnesses to run through the center of the sail subsystem, packaging and deployment design of the sail subsystem, and integrated testing efforts through an avionics test bed to verify and validate a complete system architecture.
A scintillation counter time-of-flight system has been incorporated into the Goddard 50 cm by 50 cm spark chamber gamma-ray telescope. This system, utilizing constant fraction timing and particle position compensation, digitizes up to 10 ns time differences to six bit accuracy in less than 500 ns. Event selection decisions, discriminating against upward-moving particles, are made prior to spark chamber triggering. The performance of this system during a November 1978 balloon flight is discussed.
Provides an overview of the X-48B prototype system flight test including vehicle characteristics and configuration. There are two X-48B Vehicles: the first, Vehicle 1, is the wind tunnel and flight test model. The second, Vehicle 2, provides the primary flight test. In mid-May 2006 the research team successfully completed 250 hours of wind tunnel tests on the X-48B Vehicle 1 at NASA's Langley Air Force Base. The prototype was then shipped to NASA's Dryden Flight Research Center at Edwards Air Force Base to serve as a backup to Vehicle 2, which is used for planned remotely piloted flight tests at Dryden.
An investigation of feel system and flight control system dynamics on lateral flying qualities was conducted using the variable stability USAF NT-33 aircraft. Experimental variations in feel system natural frequency, force-deflection gradient, control system command architecture type, flight control system filter frequency, and control system delay were made. The experiment data include pilot ratings using the Cooper-Harper (1969) rating scale, pilot comments, and tracking performance statistic. Three test pilots served as evaluators. The data indicate that as the feel system natural frequency is reduced lateral flying qualities degrade. At the slowest feel system frequency, the closed-loop response becomes nonlinear with a 'bobweight' effect apparent in the feel system. Feel system influences were essentially independent of the control system architecture. The flying qualities influence due to the feel system was different than when the identical dynamic systenm was used as a flight control system element.