Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Failing Safely”

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 199 records · Page 11

Shuttle avionics system

The avionics system of the Space Shuttle is designed in a fail operational/fail safe architecture. The guidance, navigation and control system is implemented, through the onboard Orbiter digital computers. Guidance, navigation and control sensors are triplex, while the flight control effectors are mechanized either in load sharing or quad structure. Two sets of basic flight instruments and controls are provided along with electronic interfaces to allow for multiple selection of input destination and display source selection. Communications, tracking and instrumentation subsystems are mechanized as a dual hardware design for key operational elements. The data processing system allows for quad, triplex, dual or single computer operation. The power distribution subsystem provides a triple bus system with appropriate tie elements. A functional description is given of the computer system, the data bus, the mass memory unit, the multiplexer/demultiplexer and the CRT display system.

Gardiner, R. A.↗

Evolution of shuttle avionics redundancy management/fault tolerance

The challenge of providing redundancy management (RM) and fault tolerance to meet the Shuttle Program requirements of fail operational/fail safe for the avionics systems was complicated by the critical program constraints of weight, cost, and schedule. The basic and sometimes false effectivity of less than pure RM designs is addressed. Evolution of the multiple input selection filter (the heart of the RM function) is discussed with emphasis on the subtle interactions of the flight control system that were found to be potentially catastrophic. Several other general RM development problems are discussed, with particular emphasis on the inertial measurement unit RM, indicative of the complexity of managing that three string system and its critical interfaces with the guidance and control systems.

Boykin, J. C.↗

Man-machine interface and control of the shuttle digital flight system

The space shuttle main engine (SSME) presented new requirements in the design of controls for large pump fed liquid rocket engine systems. These requirements were the need for built in full mission support capability, and complexity and flexibility of function not previously needed in this type of application. An engine mounted programmable digital control system was developed to meet these requirements. The engine system and controller and their function are described. Design challenges encountered during the course of development included accommodation for a very severe engine environment, the implementation of redundancy and redundancy management to provide fail operational/fail safe capability, removal of heat from the package, and significant constraints on computer memory size and processing time. The flexibility offered by programmable control reshaped the approach to engine design and development and set the pattern for future controls development in these types of applications.

Burghduff, R. D.↗

Main propulsion system design recommendations for an advanced Orbit Transfer Vehicle

Various main propulsion system configurations of an advanced OTV are evaluated with respect to the probability of nonindependent failures, i.e., engine failures that disable the entire main propulsion system. Analysis of the life-cycle cost (LCC) indicates that LCC is sensitive to the main propulsion system reliability, vehicle dry weight, and propellant cost; it is relatively insensitive to the number of missions/overhaul, failures per mission, and EVA and IVA cost. In conclusion, two or three engines are recommended in view of their highest reliability, minimum life-cycle cost, and fail operational/fail safe capability.

Redd, L.↗

Design optimization for a space based, reusable orbit transfer vehicle

Future NASA and DOD missions will benefit from high performance, reusable orbit transfer vehicles. With the advent of a space station, advanced engine technology, and various new vehicle concepts, reusable orbit transfer vehicles that provide significant economic benefits and mission capability improvements will be realized. Engine and vehicle design criteria previously have lacked definition with regard to issues such as space basing and servicing, man-rating and reliability, performance, mission flexibility, and life cycle cost for a reusable vehicle. The design study described here has resulted in the definition of a reusable orbit transfer vehicle concept and subsequent recommendations for the design criteria of an advanced LO2/LH2 engine. These design criteria include number of engines per vehicle, nozzle design, etc. The major characteristics of the vehicle preliminary design include low lift to drag aerocapture capability, a main propulsion system failure criteria of fail operational/fail safe, and either two main engines with a high performance attitude control system for back-up or three main engines with which to meet this failure criteria. In addition, a maintenance approach has been established for the advanced vehicle concept.

Redd, L.↗

Advanced orbit transfer vehicle propulsion system study

A reuseable orbit transfer vehicle concept was defined and subsequent recommendations for the design criteria of an advanced LO2/LH2 engine were presented. The major characteristics of the vehicle preliminary design include a low lift to drag aerocapture capability, main propulsion system failure criteria of fail operational/fail safe, and either two main engines with an attitude control system for backup or three main engines to meet the failure criteria. A maintenance and servicing approach was also established for the advanced vehicle and engine concepts. Design tradeoff study conclusions were based on the consideration of reliability, performance, life cycle costs, and mission flexibility.

Cathcart, J. A.↗

The Legacy of Space Shuttle Flight Software

The initial goals of the Space Shuttle Program required that the avionics and software systems blaze new trails in advancing avionics system technology. Many of the requirements placed on avionics and software were accomplished for the first time on this program. Examples include comprehensive digital fly-by-wire technology, use of a digital databus for flight critical functions, fail operational/fail safe requirements, complex automated redundancy management, and the use of a high-order software language for flight software development. In order to meet the operational and safety goals of the program, the Space Shuttle software had to be extremely high quality, reliable, robust, reconfigurable and maintainable. To achieve this, the software development team evolved a software process focused on continuous process improvement and defect elimination that consistently produced highly predictable and top quality results, providing software managers the confidence needed to sign each Certificate of Flight Readiness (COFR). This process, which has been appraised at Capability Maturity Model (CMM)/Capability Maturity Model Integration (CMMI) Level 5, has resulted in one of the lowest software defect rates in the industry. This paper will present an overview of the evolution of the Primary Avionics Software System (PASS) project and processes over thirty years, an argument for strong statistical control of software processes with examples, an overview of the success story for identifying and driving out errors before flight, a case study of the few significant software issues and how they were either identified before flight or slipped through the process onto a flight vehicle, and identification of the valuable lessons learned over the life of the project.

Hickey, Christopher J.↗

Advanced flight control system study

A fly by wire flight control system architecture designed for high reliability includes spare sensor and computer elements to permit safe dispatch with failed elements, thereby reducing unscheduled maintenance. A methodology capable of demonstrating that the architecture does achieve the predicted performance characteristics consists of a hierarchy of activities ranging from analytical calculations of system reliability and formal methods of software verification to iron bird testing followed by flight evaluation. Interfacing this architecture to the Lockheed S-3A aircraft for flight test is discussed. This testbed vehicle can be expanded to support flight experiments in advanced aerodynamics, electromechanical actuators, secondary power systems, flight management, new displays, and air traffic control concepts.

Hartmann, G. L.↗

Roller Bearings Survive Loss Of Oil Supply

Bearing developed to enable high-speed machinery such as helicopter transmissions to continue to operate safely when oil pump fails. Bearing cup includes porous rib ring containing residual oil supply to lubricate rollers when external oil supply lost. Made by sintering powdered metal, pores of which hold emergency oil.

Kreider, G. E.↗

Design of Launch Abort System Thrust Profile and Concept of Operations

This paper describes how the Abort Motor thrust profile has been tailored and how optimizing the Concept of Operations on the Launch Abort System (LAS) of the Orion Crew Exploration Vehicle (CEV) aides in getting the crew safely away from a failed Crew Launch Vehicle (CLV). Unlike the passive nature of the Apollo system, the Orion Launch Abort Vehicle will be actively controlled, giving the program a more robust abort system with a higher probability of crew survival for an abort at all points throughout the CLV trajectory. By optimizing the concept of operations and thrust profile the Orion program will be able to take full advantage of the active Orion LAS. Discussion will involve an overview of the development of the abort motor thrust profile and the current abort concept of operations as well as their effects on the performance of LAS aborts. Pad Abort (for performance) and Maximum Drag (for separation from the Launch Vehicle) are the two points that dictate the required thrust and shape of the thrust profile. The results in this paper show that 95% success of all performance requirements is not currently met for Pad Abort. Future improvements to the current parachute sequence and other potential changes will mitigate the current problems, and meet abort performance requirements.

Litton, Daniel↗

The US space station and its electric power system

The United States has embarked on a major development program to have a space station operating in low earth orbit by the mid-1990s. This endeavor draws on the talents of NASA and most of the aerospace firms in the U.S. Plans are being pursued to include the participation of Canada, Japan, and the European Space Agency in the space station. From the start of the program these was a focus on the utilization of the space station for science, technology, and commercial endeavors. These requirements were utilized in the design of the station and manifest themselves in: pressurized volume; crew time; power availability and level of power; external payload accommodations; microgravity levels; servicing facilities; and the ability to grow and evolve the space station to meet future needs. President Reagan directed NASA to develop a permanently manned space station in his 1984 State of the Union message. Since then the definition phase was completed and the development phase initiated. A major subsystem of the space station is its 75 kW electric power system. The electric power system has characteristics similar to those of terrestrial power systems. Routine maintenance and replacement of failed equipment must be accomplished safely and easily and in a minimum time while providing reliable power to users. Because of the very high value placed on crew time it is essential that the power system operate in an autonomous mode to minimize crew time required. The power system design must also easily accommodate growth as the power demands by users are expected to grow. An overview of the U.S. space station is provided with special emphasis on its electrical power system.

Thomas, Ronald L.↗

Use of Drying Technologies for Resource Recovery from Solid Wastes and Brines

Long term storage of unprocessed biological wastes and human wastes can present major health issues and a loss of potential resources. Space vehicles and planetary habitats are typically resource-scarce or resource-limited environments for long-term human habitation. To-date, most of the resources will need to be supplied from Earth, but this may not be possible for long duration human exploration. Based on present knowledge, there is only very limited in-situ resources on planetary habitats. Hence, the opportunity to "live off the land" in a planetary habitat is limited. However, if we assume that wastes generated by human explorers are viewed as resources, there is great potential to utilize and recycle them, thereby reducing the requirements for supply Earth and enabling the "live off the land" exploration scenario. Technologies used for the recovery of resources from wastes should be reliable, safe, easy to operate, fail-proof, modular, automated and preferably multifunctional in being capable of handling mixed solid and liquid wastes. For a lunar habitat, energy does not appear to be the major driving factor amongst the technologies studied. Instead, reliability appears to be more important[1] . This paper reports studies to date on drying technologies to remove water from solid wastes and brines. Experimental performance data obtained for recovery water from wastes and brine are presented. Simplicity of operation of hardware and energy efficiency are discussed. Some improvements and modifications to hardware were performed. Hopefully, this information will assist in future efforts in the "downselection" of technologies for recovery of water and resources from solid wastes and brines.

Wignarajah, Kanapathipillai↗

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

The NASA 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 paper 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.↗

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

The NASA 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 paper 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.↗

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.↗

Modeling in the State Flow Environment to Support Launch Vehicle Verification Testing for Mission and Fault Management Algorithms in the NASA Space Launch System

Analysis methods and testing processes are essential activities in the engineering development and verification of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS). Central to mission success is reliable verification of the Mission and Fault Management (M&FM) algorithms for the SLS launch vehicle (LV) flight software. This is particularly difficult because M&FM algorithms integrate and operate LV subsystems, which consist of diverse forms of hardware and software themselves, with equally diverse integration from the engineering disciplines of LV subsystems. M&FM operation of SLS requires a changing mix of LV automation. During pre-launch the LV is primarily operated by the Kennedy Space Center (KSC) Ground Systems Development and Operations (GSDO) organization with some LV automation of time-critical functions, and much more autonomous LV operations during ascent that have crucial interactions with the Orion crew capsule, its astronauts, and with mission controllers at the Johnson Space Center. M&FM algorithms must perform all nominal mission commanding via the flight computer to control LV states from pre-launch through disposal and also address failure conditions by initiating autonomous or commanded aborts (crew capsule escape from the failing LV), redundancy management of failing subsystems and components, and safing actions to reduce or prevent threats to ground systems and crew. To address the criticality of the verification testing of these algorithms, the NASA M&FM team has utilized the State Flow environment6 (SFE) with its existing Vehicle Management End-to-End Testbed (VMET) platform which also hosts vendor-supplied physics-based LV subsystem models. The human-derived M&FM algorithms are designed and vetted in Integrated Development Teams composed of design and development disciplines such as Systems Engineering, Flight Software (FSW), Safety and Mission Assurance (S&MA) and major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GN&C), Thrust Vector Control (TVC), liquid engines, and the astronaut crew office. Since the algorithms are realized using model-based engineering (MBE) methods from a hybrid of the Unified Modeling Language (UML) and Systems Modeling Language (SysML), SFE methods are a natural fit to provide an in depth analysis of the interactive behavior of these algorithms with the SLS LV subsystem models. For this, the M&FM algorithms and the SLS LV subsystem models are modeled using constructs provided by Matlab which also enables modeling of the accompanying interfaces providing greater flexibility for integrated testing and analysis, which helps forecast expected behavior in forward VMET integrated testing activities. In VMET, the M&FM algorithms are prototyped and implemented using the same C++ programming language and similar state machine architectural concepts used by the FSW group. Due to the interactive complexity of the algorithms, VMET testing thus far has verified all the individual M&FM subsystem algorithms with select subsystem vendor models but is steadily progressing to assessing the interactive behavior of these algorithms with LV subsystems, as represented by subsystem models. The novel SFE applications has proven to be useful for quick look analysis into early integrated system behavior and assessment of the M&FM algorithms with the modeled LV subsystems. This early MBE analysis generates vital insight into the integrated system behaviors, algorithm sensitivities, design issues, and has aided in the debugging of the M&FM algorithms well before full testing can begin in more expensive, higher fidelity but more arduous environments such as VMET, FSW testing, and the Systems Integration Lab7 (SIL). SFE has exhibited both expected and unexpected behaviors in nominal and off nominal test cases prior to full VMET testing. In many findings, these behavioral characteristics were used to correct the M&FM algorithms, enable better test coverage, and develop more effective test cases for each of the LV subsystems. This has improved the fidelity of testing and planning for the next generation of M&FM algorithms as the SLS program evolves from non-crewed to crewed flight, impacting subsystem configurations and the M&FM algorithms that control them. SFE analysis has improved robustness and reliability of the M&FM algorithms by revealing implementation errors and documentation inconsistencies. It is also improving planning efficiency for future VMET testing of the M&FM algorithms hosted in the LV flight computers, further reducing risk for the SLS launch infrastructure, the SLS LV, and most importantly the crew.

Trevino, Luis↗

Propulsion Overview of the Orion Pad Abort 1 (PA-1) Flight-Test Vehicle

The NASA 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 presentation provides a concise overview of the three propulsive subsystems used on the Pad Abort 1 Flight-Test Vehicle. Although the Constellation program has been cancelled and the operational role of the Orion spacecraft has significantly evolved, lessons learned from Pad Abort 1 could certainly contribute to the vehicle architecture of many future human-rated space launch vehicles

Jones, Daniel S.↗