Search NASA⌕ Search

SEARCH · Search NASA

Results for “launch vehicle systems performance”

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 163 records · Page 9

The First Development of Human Factors Engineering Requirements for Application to Ground Task Design for a NASA Flight Program

The National Aeronautics and Space Administration has long applied standards-derived human engineering requirements to the development of hardware and software for use by astronauts while in flight. The most important source of these requirements has been NASA-STD-3000. While there have been several ground systems human engineering requirements documents, none has been applicable to the flight system as handled at NASA's launch facility at Kennedy Space Center. At the time of the development of previous human launch systems, there were other considerations that were deemed more important than developing worksites for ground crews; e.g., hardware development schedule and vehicle performance. However, experience with these systems has shown that failure to design for ground tasks has resulted in launch schedule delays, ground operations that are more costly than they might be, and threats to flight safety. As the Agency begins the development of new systems to return humans to the moon, the new Constellation Program is addressing this issue with a new set of human engineering requirements. Among these requirements is a subset that will apply to the design of the flight components and that is intended to assure ground crew success in vehicle assembly and maintenance tasks. These requirements address worksite design for usability and for ground crew safety.

Dischinger, H. Charles, Jr.↗

Java-based Graphical User Interface for MAVERIC-II

A computer program entitled "Marshall Aerospace Vehicle Representation in C II, (MAVERIC-II)" is a vehicle flight simulation program written primarily in the C programming language. It is written by James W. McCarter at NASA/Marshall Space Flight Center. The goal of the MAVERIC-II development effort is to provide a simulation tool that facilitates the rapid development of high-fidelity flight simulations for launch, orbital, and reentry vehicles of any user-defined configuration for all phases of flight. MAVERIC-II has been found invaluable in performing flight simulations for various Space Transportation Systems. The flexibility provided by MAVERIC-II has allowed several different launch vehicles, including the Saturn V, a Space Launch Initiative Two-Stage-to-Orbit concept and a Shuttle-derived launch vehicle, to be simulated during ascent and portions of on-orbit flight in an extremely efficient manner. It was found that MAVERIC-II provided the high fidelity vehicle and flight environment models as well as the program modularity to allow efficient integration, modification and testing of advanced guidance and control algorithms. In addition to serving as an analysis tool for techno logy development, many researchers have found MAVERIC-II to be an efficient, powerful analysis tool that evaluates guidance, navigation, and control designs, vehicle robustness, and requirements. MAVERIC-II is currently designed to execute in a UNIX environment. The input to the program is composed of three segments: 1) the vehicle models such as propulsion, aerodynamics, and guidance, navigation, and control 2) the environment models such as atmosphere and gravity, and 3) a simulation framework which is responsible for executing the vehicle and environment models and propagating the vehicle s states forward in time and handling user input/output. MAVERIC users prepare data files for the above models and run the simulation program. They can see the output on screen and/or store in files and examine the output data later. Users can also view the output stored in output files by calling a plotting program such as gnuplot. A typical scenario of the use of MAVERIC consists of three-steps; editing existing input data files, running MAVERIC, and plotting output results.

Seo, Suk Jai↗

Advanced Compatibility Characterization Of AF-M315E With Spacecraft Propulsion System Materials Project

All spacecraft require propulsion systems for thrust and maneuvering. Propulsion systems can be chemical, nuclear, electrical, cold gas or combinations thereof. Chemical propulsion has proven to be the most reliable technology since the deployment of launch vehicles. Performance, storability, and handling are three important aspects of liquid chemical propulsion. Bipropellant systems require a fuel and an oxidizer for propulsion, but monopropellants only require a fuel and a catalyst for propulsion and are therefore simpler and lighter. Hydrazine is the state of the art propellant for monopropellant systems, but has drawbacks because it is highly hazardous to human health, which requires extensive care in handling, complex ground ops due to safety and environmental considerations, and lengthy turnaround times for reusable spacecraft. All users of hydrazine monopropellant must contend with these issues and their associated costs. The development of a new monopropellant, intended to replace hydrazine, has been in progress for years. This project will apply advanced techniques to characterize the engineering properties of materials used in AF-M315E propulsion systems after propellant exposure. AF-M315E monopropellant has been selected HQ's Green Propellant Infusion Mission (GPIM) to replace toxic hydrazine for improved performance and reduce safety and health issues that will shorten reusable spacecraft turn-around time. In addition, this project will fundamentally strengthen JSC's core competency to evaluate, use and infuse liquid propellant systems.

McClure, Mark B.↗

Space Launch System Launch Windows and Day of Launch Processes

Lunar missions benefit from varying the launch azimuth as a function of launch time to allow longer launch windows with minimum performance impacts. This variable azimuth approach allows the vehicle to track the Moon’s apparent motion due to Earth’s rotation. The Space Launch System (SLS) Block 1 vehicle design requires the mission to launch into an elliptical parking orbit to provide sufficient energy to insert Orion into a Trans-Lunar Injection (TLI) orbit. The primary benefit of varying the launch azimuth, and as a result the achieved orbit inclination, allows the SLS Interim Cryogenic Propulsion Stage (ICPS) to perform its TLI burn closer to perigee and take advantage of performing a burn in a location where the burn will optimally raise apogee.

launch window↗

Mission Capabilities of Ion Engines. Phase II

Payloads and mission times were calculated for space vehicles propelled by ion rockets using nuclear power supplies having specific weights from 10 t o 50 lb/kw. Included in the study were five missions: low-altitude lunar satellite, low-altitude Venus satellite, solar probe, Saturn probe, and a Jupiter satellite with a circular orbit at the altitude of Jupiter's fourth moon. The variation of payload with the ration of power supply weight to gross weight was studied and the optimum power levels thereby determined. The ion rocket payload capabilities were compared with those of high-thrust vehicles using hydrogen-oxygen rockets and tungsten-core nuclear rockets; in addition the performance of high- and low-thrust systems staged in combination has been investigated. Launch vehicles considered in this study were the Atlas-Centaur, the Saturn C-1, and the Saturn C-5.

IONIC PROPULSION↗

Skylab consolidated instrumentation plan for SL-1/SL-2

The consolidated instrumentation plan is presented for employing optical and electronic data acquisition systems to monitor the performance and trajectory of Skylab 1 and Skylab 2 vehicles during the launch phase. Telemetry, optical, and electronic tracking equipment on board the vehicles, and data acquisition systems monitoring the flights are discussed. Flight safety instrumentation, vehicle data transmission systems, and instrumentation geography are also described.

Clark, D. E.↗

Preliminary Sizing of Vertical Take-off Rocket-based Combined-cycle Powered Launch Vehicles

The task of single-stage-to-orbit has been an elusive goal due to propulsion performance, materials limitations, and complex system integration. Glenn Research Center has begun to assemble a suite of relationships that tie Rocket-Based Combined-Cycle (RBCC) performance and advanced material data into a database for the purpose of preliminary sizing of RBCC-powered launch vehicles. To accomplish this, a near optimum aerodynamic and structural shape was established as a baseline. The program synthesizes a vehicle to meet the mission requirements, tabulates the results, and plots the derived shape. A discussion of the program architecture and an example application is discussed herein.

Roche, Joseph M.↗

Accomplishments of the Advanced Reusable Technologies (ART) RBCC Project at NASA/Marshall Space Flight Center

The focus of the NASA / Marshall Space Flight Center (MSFC) Advanced Reusable Technologies (ART) project is to advance and develop Rocket-Based Combined-Cycle (RBCC) technologies. The ART project began in 1996 as part of the Advanced Space Transportation Program (ASTP). The project is composed of several activities including RBCC engine ground testing, tool development, vehicle / mission studies, and component testing / development. The major contractors involved in the ART project are Aerojet and Rocketdyne. A large database of RBCC ground test data was generated for the air-augmented rocket (AAR), ramjet, scramjet, and ascent rocket modes of operation for both the Aerojet and Rocketdyne concepts. Transition between consecutive modes was also demonstrated as well as trajectory simulation. The Rocketdyne freejet tests were conducted at GASL in the Flight Acceleration Simulation Test (FAST) facility. During a single test, the FAST facility is capable of simulating both the enthalpy and aerodynamic conditions over a range of Mach numbers in a flight trajectory. Aerojet performed freejet testing in the Pebble Bed facility at GASL as well as direct-connect testing at GASL. Aerojet also performed sea-level static (SLS) testing at the Aerojet A-Zone facility in Sacramento, CA. Several flight-type flowpath components were developed under the ART project. Aerojet designed and fabricated ceramic scramjet injectors. The structural design of the injectors will be tested in a simulated scramjet environment where thermal effects and performance will be assessed. Rocketdyne will be replacing the cooled combustor in the A5 rig with a flight-weight combustor that is near completion. Aerojet's formed duct panel is currently being fabricated and will be tested in the SLS rig in Aerojet's A-Zone facility. Aerojet has already successfully tested a cooled cowl panel in the same facility. In addition to MSFC, other NASA centers have contributed to the ART project as well. Inlet testing and parametrics were performed at NASA / Glenn Research Center (GRC) and NASA / Langley Research Center (LaRC) for both the Aerojet and Rocketdyne concepts. LaRC conducted an Air-Breathing Launch Vehicle (ABLV) study for several vehicle concepts with RBCC propulsion systems. LaRC is also performing a CFD analysis of the ramjet mode for both flowpaths based on GASL test conditions. A study was performed in 1999 to investigate the feasibility of performing an RBCC flight test on the NASA / Dryden Flight Research Center (DFRC) SR-71 aircraft. Academia involvement in the ART project includes parametric RBCC flowpath testing by Pennsylvania State University (PSU). In addition to thrust and wall static pressure measurements, PSU is also using laser diagnostics to analyze the flowfield in the test rig. MSFC is performing CFD analysis of the PSU rig at select test conditions for model baseline and validation. Also, Georgia Institute of Technology (GT) conducted a vision vehicle study using the Aerojet RBCC concept. Overall, the ART project has been very successful in advancing RBCC technology. Along the way, several major milestones were achieved and "firsts" accomplished. For example, under the ART project, the first dynamic trajectory simulation testing was performed and the Rocketdyne engine A5 logged over one hour of accumulated test time. The next logical step is to develop and demonstrate a flight-weight RBCC engine system.

Nelson, Karl W.↗

Space Launch System Mission Flexibility Assessment

The Space Launch System (SLS) is envisioned as a heavy lift vehicle that will provide the foundation for future beyond low Earth orbit (LEO) missions. While multiple assessments have been performed to determine the optimal configuration for the SLS, this effort was undertaken to evaluate the flexibility of various concepts for the range of missions that may be required of this system. These mission scenarios include single launch crew and/or cargo delivery to LEO, single launch cargo delivery missions to LEO in support of multi-launch mission campaigns, and single launch beyond LEO missions. Specifically, we assessed options for the single launch beyond LEO mission scenario using a variety of in-space stages and vehicle staging criteria. This was performed to determine the most flexible (and perhaps optimal) method of designing this particular type of mission. A specific mission opportunity to the Jovian system was further assessed to determine potential solutions that may meet currently envisioned mission objectives. This application sought to significantly reduce mission cost by allowing for a direct, faster transfer from Earth to Jupiter and to determine the order-of-magnitude mass margin that would be made available from utilization of the SLS. In general, smaller, existing stages provided comparable performance to larger, new stage developments when the mission scenario allowed for optimal LEO dropoff orbits (e.g. highly elliptical staging orbits). Initial results using this method with early SLS configurations and existing Upper Stages showed the potential of capturing Lunar flyby missions as well as providing significant mass delivery to a Jupiter transfer orbit.

Monk, Timothy↗

Space Shuttle Ascent Flight Design Process: Evolution and Lessons Learned

The Space Shuttle Ascent Flight Design team is responsible for defining a launch to orbit trajectory profile that satisfies all programmatic mission objectives and defines the ground and onboard reconfiguration requirements for this high-speed and demanding flight phase. This design, verification and reconfiguration process ensures that all applicable mission scenarios are enveloped within integrated vehicle and spacecraft certification constraints and criteria, and includes the design of the nominal ascent profile and trajectory profiles for both uphill and ground-to-ground aborts. The team also develops a wide array of associated training, avionics flight software verification, onboard crew and operations facility products. These key ground and onboard products provide the ultimate users and operators the necessary insight and situational awareness for trajectory dynamics, performance and event sequences, abort mode boundaries and moding, flight performance and impact predictions for launch vehicle stages for use in range safety, and flight software performance. These products also provide the necessary insight to or reconfiguration of communications and tracking systems, launch collision avoidance requirements, and day of launch crew targeting and onboard guidance, navigation and flight control updates that incorporate the final vehicle configuration and environment conditions for the mission. Over the course of the Space Shuttle Program, ascent trajectory design and mission planning has evolved in order to improve program flexibility and reduce cost, while maintaining outstanding data quality. Along the way, the team has implemented innovative solutions and technologies in order to overcome significant challenges. A number of these solutions may have applicability to future human spaceflight programs.

Picka, Bret A.↗

In-Space Chemical Propulsion Systems Roadmap

In-space propulsion begins where the launch vehicle upper stage leaves off, performing the functions of primary propulsion, reaction control, station keeping, precision pointing, and orbital maneuvering. The main engines used in space provide the primary propulsive force for orbit transfer, planetary trajectories and extra planetary landing and ascent. The reaction control and orbital maneuvering systems provide the propulsive force for orbit maintenance, position control, station keeping, and spacecraft attitude control. Advanced in-space propulsion technologies will enable much more effective exploration of our Solar System and will permit mission designers to plan missions to "fly anytime, anywhere, and complete a host of science objectives at the destinations" with greater reliability and safety. With wide range of possible missions and candidate propulsion technologies, the question of which technologies are "best" for future missions is a difficult one. A portfolio of propulsion technologies should be developed to provide optimum solutions for a diverse set of missions and destinations. A large fraction of the rocket engines in use today are chemical rockets; that is, they obtain the energy needed to generate thrust by chemical reactions to create a hot gas that is expanded to produce thrust. A significant limitation of chemical propulsion is that it has a relatively low specific impulse (Is, or thrust per mass flow rate of propellant). A significant improvement (>30%) in Is can be obtained by using cryogenic propellants, such as liquid oxygen and liquid hydrogen, for example. Historically, these propellants have not been applied beyond upper stages.

Oxidizers↗

Studies of an extensively axisymmetric rocket based combined cycle (RBCC) engine powered single-stage-to-orbit (SSTO) vehicle

The present comparative performance study has established that rocket-based combined cycle (RBCC) propulsion systems, when incorporated by essentially axisymmetric SSTO launch vehicle configurations whose conical forebody maximizes both capture-area ratio and total capture area, are capable of furnishing payload-delivery capabilities superior to those of most multistage, all-rocket launchers. Airbreathing thrust augmentation in the rocket-ejector mode of an RBCC powerplant is noted to make a major contribution to final payload capability, by comparison to nonair-augmented rocket engine propulsion systems.

Foster, Richard W.↗

Absolute stability analysis of attitude control systems for large boosters.

A method for performing absolute stability analyses of attitude control systems for large launch vehicles is presented. Absolute stability of these systems is shown in a finite region of the state space. The regions are computed by using the Lur'e-Postnikov Liapunov function. This function is chosen to provide additional information about the exponential property of absolute stability. Significant advantages of the method proposed in this paper are: it is independent of the order of the system; algebraic operations involved in the computations are relatively simple and convenient for machine implementation; and the obtained results are valid not only for a particular nonlinearity but also for an entire class of nonlinear characteristics that satisfy certain general conditions. A system model representing the Saturn V launch vehicle is used to illustrate the method.

Seltzer, S. M.↗

Knowledge base rule partitioning design for CLIPS

This describes a knowledge base (KB) partitioning approach to solve the problem of real-time performance using the CLIPS AI shell when containing large numbers of rules and facts. This work is funded under the joint USAF/NASA Advanced Launch System (ALS) Program as applied research in expert systems to perform vehicle checkout for real-time controller and diagnostic monitoring tasks. The Expert System advanced development project (ADP-2302) main objective is to provide robust systems responding to new data frames of 0.1 to 1.0 second intervals. The intelligent system control must be performed within the specified real-time window, in order to meet the demands of the given application. Partitioning the KB reduces the complexity of the inferencing Rete net at any given time. This reduced complexity improves performance but without undo impacts during load and unload cycles. The second objective is to produce highly reliable intelligent systems. This requires simple and automated approaches to the KB verification & validation task. Partitioning the KB reduces rule interaction complexity overall. Reduced interaction simplifies the V&V testing necessary by focusing attention only on individual areas of interest. Many systems require a robustness that involves a large number of rules, most of which are mutually exclusive under different phases or conditions. The ideal solution is to control the knowledge base by loading rules that directly apply for that condition, while stripping out all rules and facts that are not used during that cycle. The practical approach is to cluster rules and facts into associated 'blocks'. A simple approach has been designed to control the addition and deletion of 'blocks' of rules and facts, while allowing real-time operations to run freely. Timing tests for real-time performance for specific machines under R/T operating systems have not been completed but are planned as part of the analysis process to validate the design.

Mainardi, Joseph D.↗

Waterhammer Testing and Modeling of the Ares I Upper Stage Reaction Control System

NASA's Ares I rocket is the agency's first step in completing the goals of the Constellation Program, which plans to deliver a new generation of space explorers into low earth orbit for future missions to the International Space Station, the moon, and other destinations within the solar system. Ares I is a two-stage rocket topped by the Orion crew capsule and its service module. The launch vehicle's First Stage is a single, five-segment reusable solid rocket booster (RSRB), derived from the Space Shuttle Program's four segment RSRB. The vehicle's Upper Stage, being designed at Marshall Space Flight Center (MSFC), is propelled by a single J-2X Main Engine fueled with liquid oxygen and liquid hydrogen. During active Upper Stage flight of the Ares I launch vehicle, the Upper Stage Reaction Control System (US ReCS) will perform attitude control operations for the vehicle. The US ReCS will provide three-axis attitude control capability (roll, pitch, and yaw) for the Upper Stage while the J-2X is not firing and roll control capability while the engine is firing. Because of the requirements imposed upon the system, the design must accommodate rapid pulsing of multiple thrusters simultaneously to maintain attitude control. In support of these design activities and in preparation for Critical Design Review, analytical models of the US ReCS propellant feed system have been developed using the Thermal Hydraulic Library of MSC.EASY5 v.2008, herein referred to as EASY5. EASY5 is a commercially available fluid system modeling package with significant history of modeling space propulsion systems. In Fall 2009, a series of development tests were conducted at MSFC on a cold-flow test article for the US ReCS, herein referred to as System Development Test Article (SDTA). A subset of those tests performed were aimed at examining the effects of waterhammer on a flight-representative system and to ensure that those effects could be quantified with analytical models and incorporated into the design of the flight system. This paper presents an overview of the test article and the test approach, along with a discussion of the analytical modeling methodology. In addition, the results of that subset of development tests, along with analytical model pre-test predictions and post-test model correlations, will also be discussed in detail.

Williams, J. Hunter↗

Design Considerations for a Launch Vehicle Development Flight Instrumentation System

When embarking into the design of a new launch vehicle, engineering models of expected vehicle performance are always generated. While many models are well established and understood, some models contain design features that are only marginally known. Unfortunately, these analytical models produce uncertainties in design margins. The best way to answer these analytical issues is with vehicle level testing. The National Aeronautics and Space Administration respond to these uncertainties by using a vehicle level system called the Development Flight Instrumentation, or DFI. This DFI system can be simple to implement, with only a few measurements, or it may be a sophisticated system with hundreds of measurement and video, without a recording capability. From experience with DFI systems, DFI never goes away. The system is renamed and allowed to continue, in most cases. Proper system design can aid the transition to future data requirements. This paper will discuss design features that need to be considered when developing a DFI system for a launch vehicle. It will briefly review the data acquisition units, sensors, multiplexers and recorders, telemetry components and harnessing. It will present a reasonable set of requirements which should be implemented in the beginning of the program in order to start the design. It will discuss a simplistic DFI architecture that could be the basis for the next NASA launch vehicle. This will be followed by a discussion of the "experiences gained" from a past DFI system implementation, such as the very successful Ares I-X test flight. Application of these design considerations may not work for every situation, but they may direct a path toward success or at least make one pause and ask the right questions.

Johnson, Martin L.↗

Max Launch Abort System (MLAS) Pad Abort Test Vehicle (PATV) II Attitude Control System (ACS) Integration and Pressurization Subsystem Dynamic Random Vibration Analysis

In order to mitigate catastrophic failures on future generation space vehicles, engineers at the National Aeronautics and Space Administration have begun to integrate a novel crew abort systems that could pull a crew module away in case of an emergency at the launch pad or during ascent. The Max Launch Abort System (MLAS) is a recent test vehicle that was designed as an alternative to the baseline Orion Launch Abort System (LAS) to demonstrate the performance of a "tower-less" LAS configuration under abort conditions. The MLAS II test vehicle will execute a propulsive coast stabilization maneuver during abort to control the vehicles trajectory and thrust. To accomplish this, the spacecraft will integrate an Attitude Control System (ACS) with eight hypergolic monomethyl hydrazine liquid propulsion engines that are capable of operating in a quick pulsing mode. Two main elements of the ACS include a propellant distribution subsystem and a pressurization subsystem to regulate the flow of pressurized gas to the propellant tanks and the engines. The CAD assembly of the Attitude Control System (ACS) was configured and integrated into the Launch Abort Vehicle (LAV) design. A dynamic random vibration analysis was conducted on the Main Propulsion System (MPS) helium pressurization panels to assess the response of the panel and its components under increased gravitational acceleration loads during flight. The results indicated that the panels fundamental and natural frequencies were farther from the maximum Acceleration Spectral Density (ASD) vibrations which were in the range of 150-300 Hz. These values will direct how the components will be packaged in the vehicle to reduce the effects high gravitational loads.

Ekrami, Yasamin↗