Search NASA⌕ Search

SEARCH · Search NASA

Results for “Launch Abort System”

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

Design, development, and test of Shuttle/Centaur G-prime cryogenic tankage thermal protection systems

The thermal protection systems (TPS) for the Shuttle/Centaur were designed to provide fail-safe thermal protection during prelaunch, launch ascent, and on-orbit operations as well as during potential abort, where the Shuttle and Centaur would return to earth. The TPS selected used a helium-purged polyimide foam beneath three radiation shields for the liquid-hydrogen (LH2) tank and radiation shields only for the liquid-oxygen (LO2) tank. A double-walled vacuum bulkhead separated the two tanks. The LH2 tank had one 1.9 cm-thick layer of foam on the forward bulkhead and two layers on the larger-area sidewall. Full scale tests of the flight vehicle in a simulated Shuttle cargo bay gave total prelaunch heating rates of 29.5 and 12.9 kW for the LH2 and LO2 tanks, respectively. Calorimeter tests on a representative sample of the LH2 tank sidewall TPS indicated that the measured unit heating one would rapidly decrease from the prelaunch rate of about 300 W/sq m to a desired rate less than 4 W/sq m once on-orbit.

Macneil, Peter N.↗

Space Shuttle Main Engine (SSME) Options for the Future Shuttle

The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.The main engines for the Future Shuttle will focus on improved safety and operability. Performance enhancements may also be required for vehicle safety purposes to achieve more desirable abort scenarios. This paper discusses the potential improvements that will be considered for implementation into the Future Shuttle. Integrated engine and vehicle health management systems will achieve additional system-level reliability improvements over those currently in development. Advanced instrumentation for detecting leaks, analyzing component wear and degradation, and providing sophisticated operational data will be used for reliable engine control and scheduling maintenance operations. A new nozzle and main combustion chamber (MCC) will reduce failure probability by 50% and allow for higher thrust capability without requiring the entire engine to be redesigned. Turbopump improvements may range from minor component improvements to using 3rd-generation pumps built on the advanced concepts demonstrated by the Integrated Powerhead Development (IPD) program and the Space Launch Initiative (SLI) prototype engines.

Jue, Fred↗

STS-51 pad abort. OV103-engine 2033 (ME-2) fuel flowmeter sensor open circuit

The STS-51 initial launch attempt of Discovery (OV-103) was terminated on KSC launch pad 39B on 12 Aug. 1993 at 9:12 AM E.S.T. due to a sensor redundancy failure in the liquid hydrogen system of ME-2 (Engine 2033). The event description and time line are summarized. Propellant loading was initiated on 12 Aug. 1993 at 12:00 AM EST. All space shuttle main engine (SSME) chill parameters and Launch Commit Criteria (LCC) were nominal. At engine start plus 1.34 seconds a Failure Identification (FID) was posted against Engine 2033 for exceeding the 1800 spin intra-channel (A1-A2) Fuel Flowrate sensor channel qualification limit. The engine was shut down at 1.50 seconds followed by Engines 2032 and 2030. All shut down sequences were nominal and the mission was safely aborted. SSME Avionics hardware and software performed nominally during the incident. A review of vehicle data table (VDT) data and controller software logic revealed no failure indications other than the single FID 111-101, Fuel Flowrate Intra-Channel Test Channel A disqualification. Software logic was executed according to requirements and there was no anomalous controller software operation. Immediately following the abort, a Rocketdyne/NASA failure investigation team was assembled. The team successfully isolated the failure cause to an open circuit in a Fuel Flowrate Sensor. This type of failure has occurred eight previous times in ground testing. The sensor had performed acceptably on three previous flights of the engine and SSME flight history shows 684 combined fuel flow rate sensor channel flights without failure. The disqualification of an Engine 2 (SSME No. 2033) Fuel Flowrate sensor channel was a result of an instrumentation failure and not engine performance. All other engine operations were nominal. This disqualification resulted in an engine shutdown and safe sequential shutdown of all three engines prior to ignition of the solid boosters.

Source record↗

Evolution and Impact of Saturn V on Space Launch System from a Guidance, Navigation, and Mission Analysis Perspective

The Saturn V launch vehicle represented a jump in capability for heavy lift launch vehicles, enabling the Lunar Orbit Rendezvous approach to planetary exploration employed by the Apollo program 50 years ago. Following Apollo, and the development of the Space Transportation System, the NASA space exploration program shifted focus from lunar exploration to long-term, sustained, re-usable access to Low Earth Orbit. With the recent focus of NASA on the Artemis program and continued exploration of cislunar space as a precursor to Martian exploration, the shift has swung back to heavy lift capability. To meet this need, NASA has developed the Space Launch System. While the vehicle is a new design, it is heavily influenced by the engineering solutions and approach used on the Saturn V while taking advantage of the state of the art of launch vehicle design. The approach to abort, for example, shares many familiarities with the triggers and concept of operations used on Saturn V. Analysis approaches to dispersed trajectory performance are also very similar, but advances in computing technology have enabled a much more expanded set of inputs that can be modelled and assessed in a rapid manner. Additionally, guided flight algorithms share similar first principles but have expanded to include day of launch wind information. Trajectory optimization has also advanced significantly due to the availability of computing resources, but similar maneuvers and profiles are flown across both vehicles. Also, while the approach of onboard inertial navigation has been maintained between the two programs, the shift from platform to strapdown systems enables reduced complexity in the system design while maintaining required performance. As described, the Space Launch System is the evolution of NASA launch vehicle designs, owing a large heritage to the Saturn vehicle program and incorporating advances in propulsion systems, avionics, computing, and sensor technology over the past 50 years.

Ahmad, Naeem↗

The Evaluation of the Regional Atmospheric Modeling System in the Eastern Range Dispersion Assessment System

The Applied Meteorology Unit (AMU) evaluated the Regional Atmospheric Modeling System (RAMS) contained within the Eastern Range Dispersion Assessment System (ERDAS). ERDAS provides emergency response guidance for Cape Canaveral Air Force Station and Kennedy Space Center operations in the event of an accidental hazardous material release or aborted vehicle launch. The RAMS prognostic data are available to ERDAS for display and are used to initialize the 45th Space Wing/Range Safety dispersion model. Thus, the accuracy of the dispersion predictions is dependent upon the accuracy of RAMS forecasts. The RAMS evaluation consisted of an objective and subjective component for the 1999 and 2000 Florida warm seasons, and the 1999-2000 cool season. In the objective evaluation, the AMU generated model error statistics at surface and upper-level observational sites, compared RAMS errors to a coarser RAMS grid configuration, and benchmarked RAMS against the nationally-used Eta model. In the subjective evaluation, the AMU compared forecast cold fronts, low-level temperature inversions, and precipitation to observations during the 1999-2000 cool season, verified the development of the RAMS forecast east coast sea breeze during both warm seasons, and examined the RAMS daily thunderstorm initiation and precipitation patterns during the 2000 warm season. This report summarizes the objective and subjective verification for all three seasons.

Case, Jonathan↗

Constellation Program Lessons Learned in the Quantification and Use of Aerodynamic Uncertainty

The NASA Constellation Program has worked for the past five years to develop a re- placement for the current Space Transportation System. Of the elements that form the Constellation Program, only two require databases that define aerodynamic environments and their respective uncertainty: the Ares launch vehicles and the Orion crew and launch abort vehicles. Teams were established within the Ares and Orion projects to provide repre- sentative aerodynamic models including both baseline values and quantified uncertainties. A technical team was also formed within the Constellation Program to facilitate integra- tion among the project elements. This paper is a summary of the collective experience of the three teams working with the quantification and use of uncertainty in aerodynamic environments: the Ares and Orion project teams as well as the Constellation integration team. Not all of the lessons learned discussed in this paper could be applied during the course of the program, but they are included in the hope of benefiting future projects.

Walker, Eric L.↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The development of the Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large complex systems engineering challenge being addressed in part by focusing on the specific subsystems handling of off-nominal mission and fault tolerance. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML), the Mission and Fault Management (M&FM) algorithms are crafted and vetted in specialized Integrated Development Teams composed of multiple development disciplines. NASA also has formed an M&FM team for addressing fault management early in the development lifecycle. This team has developed a dedicated Vehicle Management End-to-End Testbed (VMET) that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. The flexibility of VMET enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the algorithms utilizing actual subsystem models. The intent is to validate the algorithms and substantiate them with performance baselines for each of the vehicle subsystems in an independent platform exterior to flight software test processes. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test processes. Risk reduction is addressed by working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and detection and responses that can be tested in VMET and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM. The plan for VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes. This paper is outlined in a systematic fashion analogous to a lifecycle process flow for engineering development of algorithms into software and testing. Section I describes the NASA SLS M&FM context, presenting the current infrastructure, leading principles, methods, and participants. Section II defines the testing philosophy of the M&FM algorithms as related to VMET followed by section III, which presents the modeling methods of the algorithms to be tested and validated in VMET. Its details are then further presented in section IV followed by Section V presenting integration, test status, and state analysis. Finally, section VI addresses the summary and forward directions followed by the appendices presenting relevant information on terminology and documentation.

Trevino, Luis↗

Meteorological Conditions Experienced During the Orion Pad Abort Test

Presentation describes the atmosphere at launch minus one day and a forecast associated for launch. Also presented is the day of launch observations from weather balloons, the 924 MHz wind profiler, and four Surface Automatic Meteorological System (SAMS) from nearby locations. Details will be provided illustrating the terrain and atmosphere interactions that produced strong winds at the launch site and calm winds at the balloon launch facility just 3 miles away.

Teets, Edward H., Jr.↗

Lockheed Martin Response to the OSP Challenge

The Lockheed Martin Orbital Space Plane System provides crew transfer and rescue for the International Space Station more safely and affordably than current human space transportation systems. Through planned upgrades and spiral development, it is also capable of satisfying the Nation's evolving space transportation requirements and enabling the national vision for human space flight. The OSP System, formulated through rigorous requirements definition and decomposition, consists of spacecraft and launch vehicle flight elements, ground processing facilities and existing transportation, launch complex, range, mission control, weather, navigation, communication and tracking infrastructure. The concept of operations, including procurement, mission planning, launch preparation, launch and mission operations and vehicle maintenance, repair and turnaround, is structured to maximize flexibility and mission availability and minimize program life cycle cost. The approach to human rating and crew safety utilizes simplicity, performance margin, redundancy, abort modes and escape modes to mitigate credible hazards that cannot be designed out of the system.

Sullivan, Robert T.↗

Safety and rescue during STS operations

The space shuttle means, provided to the crew, of abort/escape for noncatastrophic mishap scenaries, during Space Transportation Systems (STS) operations, are discussed. From vehicle ingress until launch, the crew can escape the launch pad by use of slidewire baskets. For various emergencies during ascent, the crew can fly an intact abort. Such aborts include return to launch site, transoceanic abort landing, abort once around, and abort to orbit. The crew can fly the orbiter to an emergency airfield, or to an over ocean bailout for more serious ascent or on-orbit emergencies. For failures during landing, the crew can quickly egress the orbiter from the overhead hatch, or by use of an inflatable slide mounted at the side hatch.

Oconnor, Bryan↗

The effects of RCS jet firing on the isolated Orbiter and mated coast phases of the glide return to launch site maneuver at Mach number 6 (IA302B)

An updated Space Shuttle aerodynamic data base was obtained in Tunnel B for two phases of the Glide Return to Launch Site (GRTLS) abort maneuver. One-and-a-quarter percent scale models of the Space Shuttle Orbiter and External Tank were used to measure the effects of various combinations of Reaction Control System (RCS) jet thrusters at Mach number 6. The angle-of-attack range for the isolated orbiter was -10 to 15 deg at sideslip angles from -5 to 10 deg during Phase 1 of testing. The angle-of-attack range for the mated orbiter and external tank was -5 to 15 deg with sideslip angles of -2 to 5 deg during Phase 2. The test was conducted at a unit Reynolds number of 0.75 million per foot.

Garrett, L. V.↗

Evaluation of the Regional Atmospheric Modeling System in the Eastern Range Dispersion Assessment System

The Applied Meteorology Unit is conducting an evaluation of the Regional Atmospheric Modeling System (RAMS) contained within the Eastern Range Dispersion Assessment System (ERDAS). ERDAS provides emergency response guidance for operations at the Cape Canaveral Air Force Station and the Kennedy Space Center in the event of an accidental hazardous material release or aborted vehicle launch. The prognostic data from RAMS is available to ERDAS for display and is used to initialize the 45th Range Safety (45 SW/SE) dispersion model. Thus, the accuracy of the 45 SW/SE dispersion model is dependent upon the accuracy of RAMS forecasts. The RAMS evaluation task consists of an objective and subjective component for the Florida warm and cool seasons of 1999-2000. The objective evaluation includes gridded and point error statistics at surface and upper-level observational sites, a comparison of the model errors to a coarser grid configuration of RAMS, and a benchmark of RAMS against the widely accepted Eta model. The warm-season subjective evaluation involves a verification of the onset and movement of the Florida east coast sea breeze and RAMS forecast precipitation. This interim report provides a summary of the RAMS objective and subjective evaluation for the 1999 Florida warm season only.

Case, Jonathan↗

Design Optimisation and Mass Saving of the Structure of the Orion-MPCV European Service Module

This paper presents an overview of the design optimisation measures that have been proposed and analysed in order to reduce the mass of the structure, including the MMOD (Micro-Meteoroid and Orbital Debris) protection system, of the ESM (European Service Module) for the “Orion” MPCV (Multi-Purpose Crew Vehicle). Under an agreement between NASA and ESA, the NASA Orion MPCV for human space exploration missions will be powered by a European Service Module, based on the design and experience of the ATV (Automated Transfer Vehicle). The development and qualification of the European Service Module is managed and implemented by ESA. The ESM prime contractor and system design responsible is Airbus Defence and Space. Thales Alenia Space Italia is responsible for the design and integration of the ESM Structure and MMOD protection system in addition to the Thermal Control System and the Consumable Storage System. The Orion Multi-Purpose Crew Vehicle is a pressurized, crewed spacecraft that transports up to four crew members from the Earth’s surface to a nearby destination or staging point. Orion then brings the crew members safely back to the Earth’s surface at the end of the mission. Orion provides all services necessary to support the crew members while on-board for short duration missions (up to 21 days) or until they are transferred to another orbiting habitat. The ESM supports the crew module from launch through separation prior to re-entry by providing: in-space propulsion capability for orbital transfer, attitude control, and high altitude ascent aborts; water and oxygen/nitrogen needed for a habitable environment; and electrical power generation. In addition, it maintains the temperature of the vehicle's systems and components and offers space for unpressurized cargo and scientific payloads. The ESM has been designed for the first 2 Lunar orbit missions, EM-1 (Exploration mission 1) is an un-crewed flight planned around mid-2020, and EM-2, the first crewed flight, is planned in 2022. At the time where the first ESM is about to be weighted, the predicted mass lies slightly above the initial requirement. For future builds, mass reduction of the Service Module has been considered necessary. This is being investigated, together with other design improvements, in order to consolidate the ESM design and increase possible future missions beyond the first two Orion MPCV missions. The mass saving study has introduced new optimised structural concepts, optimisation of the MMOD protection shields, and optimised redesign of parts for manufacturing through AM (Additive Manufacturing).

Micro-Meteroids and Orbital Debris Protection Syst↗

A Vehicle Management End-to-End Testing and Analysis Platform for Validation of Mission and Fault Management Algorithms to Reduce Risk for NASA's Space Launch System

The engineering development of the new Space Launch System (SLS) launch vehicle requires cross discipline teams with extensive knowledge of launch vehicle subsystems, information theory, and autonomous algorithms dealing with all operations from pre-launch through on orbit operations. The characteristics of these spacecraft systems must be matched with the autonomous algorithm monitoring and mitigation capabilities for accurate control and response to abnormal conditions throughout all vehicle mission flight phases, including precipitating safing actions and crew aborts. This presents a large and complex system engineering challenge, which is being addressed in part by focusing on the specific subsystems involved in the handling of off-nominal mission and fault tolerance with response management. Using traditional model based system and software engineering design principles from the Unified Modeling Language (UML) and Systems Modeling Language (SysML), the Mission and Fault Management (M&FM) algorithms for the vehicle are crafted and vetted in specialized Integrated Development Teams (IDTs) composed of multiple development disciplines such as Systems Engineering (SE), Flight Software (FSW), Safety and Mission Assurance (S&MA) and the major subsystems and vehicle elements such as Main Propulsion Systems (MPS), boosters, avionics, Guidance, Navigation, and Control (GNC), Thrust Vector Control (TVC), and liquid engines. These model based algorithms and their development lifecycle from inception through Flight Software certification are an important focus of this development effort to further insure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. NASA formed a dedicated M&FM team for addressing fault management early in the development lifecycle for the SLS initiative. As part of the development of the M&FM capabilities, this team has developed a dedicated testbed that integrates specific M&FM algorithms, specialized nominal and off-nominal test cases, and vendor-supplied physics-based launch vehicle subsystem models. Additionally, the team has developed processes for implementing and validating these algorithms for concept validation and risk reduction for the SLS program. The flexibility of the Vehicle Management End-to-end Testbed (VMET) enables thorough testing of the M&FM algorithms by providing configurable suites of both nominal and off-nominal test cases to validate the developed algorithms utilizing actual subsystem models such as MPS. The intent of VMET is to validate the M&FM algorithms and substantiate them with performance baselines for each of the target vehicle subsystems in an independent platform exterior to the flight software development infrastructure and its related testing entities. In any software development process there is inherent risk in the interpretation and implementation of concepts into software through requirements and test cases into flight software compounded with potential human errors throughout the development lifecycle. Risk reduction is addressed by the M&FM analysis group working with other organizations such as S&MA, Structures and Environments, GNC, Orion, the Crew Office, Flight Operations, and Ground Operations by assessing performance of the M&FM algorithms in terms of their ability to reduce Loss of Mission and Loss of Crew probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses that can be tested in VMET to ensure that failures can be detected, and confirm that responses do not create additional risks or cause undesired states through interactive dynamic effects with other algorithms and systems. VMET further contributes to risk reduction by prototyping and exercising the M&FM algorithms early in their implementation and without any inherent hindrances such as meeting FSW processor scheduling constraints due to their target platform - ARINC 653 partitioned OS, resource limitations, and other factors related to integration with other subsystems not directly involved with M&FM such as telemetry packing and processing. The baseline plan for use of VMET encompasses testing the original M&FM algorithms coded in the same C++ language and state machine architectural concepts as that used by Flight Software. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure the effectiveness of M&FM algorithms performance in the FSW development and test processes.

Trevino, Luis↗

Wind Tunnel Investigation of the Supersonic Stage Separation Aerodynamics of a Generic 0.0175-Scale Bimese Two-Stage-to-Orbit Reusable Launch Vehicle Configuration

A wind tunnel investigation was conducted of the supersonic stage separation aerodynamics of a generic two-stage-to-orbit bimese wingbody configuration in the NASA Langley Research Center Unitary Plan Wind Tunnel. Proximity and isolated model testing was conducted at Mach numbers of 2.3, 3.0, and 4.5 and a unit Reynolds number of 2.0 million per foot using 0.0175-scale models of the Langley Glide-Back Booster concept designated as the orbiter and booster in belly-to-belly and back-to-belly configurations. Longitudinal forces and moments were obtained on both models and surface static pressure measurements were obtained on the orbiter model at 328 relative proximity locations and at relative angles of attack of 0 degrees and 5 degrees. The test results supported a larger effort to develop and validate experimental and computational tools applicable to the design and simulation of stage separation and abort procedures for reusable launch vehicles composed of multiple bodies, including winged bodies. An initial proof-of-concept experiment featuring low-cost uninstrumented models was conducted to verify an emerging automated model control system and new support system hardware, and to identify potential model and support system blockage and unsteady aerodynamics/model dynamics prior to committing to higher-fidelity instrumented models. This investigation led to upgrades in the facility stage separation hardware, calibration and testing techniques and capabilities, and data analysis and documentation methodologies that have been extended to the more recent NASA Constellation and Space Launch System crew and cargo launch vehicle programs. A virtual diagnostics interface methodology was used to facilitate the design of the stage separation support hardware, to position the models in the test section, and to define the experimental test space. Advances in the facility automated model positioning system established a foundation for the development of a continuous-sweep data acquisition technique that is responsible for significant productivity improvements to the current NASA Space Launch System test program. The automated model positioning capability was leveraged to conduct a companion statistically-designed stage separation experiment requiring randomization of the relative proximity positions of the orbiter and booster models. The respective zones of influence and interference effects of the orbiter and booster were identified from three-dimensional scatter plots, contour and influence maps, and two-dimensional plotting methods. The highly-nonlinear, shock-dominated aerodynamic characteristics of the orbiter and booster in the Unitary Plan Wind Tunnel exhibited good agreement with independent test data obtained in a NASA Marshall Space Flight Center wind tunnel and with computational fluid dynamics predictions using a compressible, three-dimensional flow solver and an inviscid, unstructured Cartesian method.

Erickson, Gary E.↗

Artemis I Trajectory Design and Optimization

This paper presents the overall trajectory design and optimization process for NASA’s Artemis I mission to send an uncrewed Orion vehicle to a lunar Distant Retrograde Orbit (DRO). The on-orbit trajectory begins at the Space Launch System (SLS) core separation and ends at the Orion service module Earth Entry Interface (EI) point. The details of the trajectory optimization process are presented, including design of nominal and extended mission options, launch windows, and abort options. Novel design techniques are also discussed to account for contingencies, such as using auxiliary thrusters to protect against main engine failure and applying trajectory shaping to mitigate or reduce eclipse durations.

Artemis I↗

Prognostics for Ground Support Systems: Case Study on Pneumatic Valves

Prognostics technologies determine the health (or damage) state of a component or sub-system, and make end of life (EOL) and remaining useful life (RUL) predictions. Such information enables system operators to make informed maintenance decisions and streamline operational and mission-level activities. We develop a model-based prognostics methodology for pneumatic valves used in ground support equipment for cryogenic propellant loading operations. These valves are used to control the flow of propellant, so failures may have a significant impact on launch availability. Therefore, correctly predicting when valves will fail enables timely maintenance that avoids launch delays and aborts. The approach utilizes mathematical models describing the underlying physics of valve degradation, and, employing the particle filtering algorithm for joint state-parameter estimation, determines the health state of the valve and the rate of damage progression, from which EOL and RUL predictions are made. We develop a prototype user interface for valve prognostics, and demonstrate the prognostics approach using historical pneumatic valve data from the Space Shuttle refueling system.

Daigle, Matthew↗

Digital Human Modeling

The development of models to represent human characteristics and behaviors in human factors is broad and general. The term "model" can refer to any metaphor to represent any aspect of the human; it is generally used in research to mean a mathematical tool for the simulation (often in software, which makes the simulation digital) of some aspect of human performance and for the prediction of future outcomes. This section is restricted to the application of human models in physical design, e.g., in human factors engineering. This design effort is typically human interface design, and the digital models used are anthropometric. That is, they are visual models that are the physical shape of humans and that have the capabilities and constraints of humans of a selected population. They are distinct from the avatars used in the entertainment industry (movies, video games, and the like) in precisely that regard: as models, they are created through the application of data on humans, and they are used to predict human response; body stresses workspaces. DHM enable iterative evaluation of a large number of concepts and support rapid analysis, as compared with use of physical mockups. They can be used to evaluate feasibility of escape of a suited astronaut from a damaged vehicle, before launch or after an abort (England, et al., 2012). Throughout most of human spaceflight, little attention has been paid to worksite design for ground workers. As a result of repeated damage to the Space Shuttle which adversely affected flight safety, DHM analyses of ground assembly and maintenance have been developed over the last five years for the design of new flight systems (Stambolian, 2012, Dischinger and Dunn Jackson, 2014). The intent of these analyses is to assure the design supports the work of the ground crew personnel and thereby protect the launch vehicle. They help the analyst address basic human factors engineering questions: can a worker reach the task site from the work platform provided; can she or he see the task site; can she or he control tools, which, if dropped, might damage the system? Figure 7.3.1 provides an example of such analysis for a future NASA launch vehicle. [figure 7.3.1 here] In-space systems for operation by astronauts have long been targets for DHM analysis, given the focus on mission success and concerns for astronaut safety. Figure 7.3.2 illustrates the analysis of the design to support astronaut tasks for an International Space Station glovebox. [Figure 7.3.2 here] Use by

Dischinger, H. Charles, Jr.↗