Search NASA⌕ Search

SEARCH · Search NASA

Results for “vehicles”

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 181 records · Page 10
All sourcesNASA NTRSDOE OSTI
NASA NTRSDate not supplied

Development of Urban Air Mobility (UAM) Vehicles for Ease of Operation

To date the air transportation system has been developed with the in-cremental introduction of new technology and with highly experienced air transport pilots and air traffic controllers overseeing flight operations. Thus, we currently have one of the safest commercial aviation systems in the world. General Aviation (GA) in the United States, however, has not always followed the same cautious and monitored approach to implementation; consequently, the GA safety record does not meet the high standards of commercial aviation. Recently, a new system known as Urban Air Mobility (UAM), is attracting considerable interest and investment from industry and government agencies. UAM refers to a system of passenger and small-cargo air transportation vehicles within an urban area with the goal of reducing the number of times we need to use our cars, thus improving urban traffic by moving people and cargo from crowded single pas-senger vehicles on our roads to personal and on-demand air vehicles. These UAM vehicles will be small and based on electric, Vertical-Take-Off-and-Landing (eV-TOL) systems. A significant component of UAM is offloading of flight-man-agement responsibilities from human pilots to newly-developed autonomy. Cur-rently, over 100 UAM vehicles are either in development or production. Most, if not all, have a goal of fully autonomous vehicle operations, but fully autonomous flying vehicles are not expected in the near future. Therefore, we are de-veloping concepts for UAM vehicles that will be easy to fly and/or manage by operators with minimal pilot training. In this paper we will discuss our human-automation teaming approach to develop an easy-to-operate VTOL aircraft, and some of the fly-by-wire technology needed to stabilize the vehicle so that a sim-ple ecological mental model of the flying task can be implemented. We will discuss the requirements for a stability augmentation system that must be developed to support our simple pilot input model, and also present design guidelines and requirements based on a pilot input and management model. Finally, our ap-proach to vehicle development will involve considerable operator testing and evaluation: improving pilot model, inceptors, displays and also work on a plan for how a UAM vehicle can be integrated with terminal area air traffic control airspace with minimal impact on controller workload.

UAM↗
NASA NTRSDate not supplied

A HIRF-Map Certification Approach for UAM, AAM, and UAS Vehicles

Advanced Air Mobility (AAM), Urban Air Mobility (UAM), and Unmanned Aerial Systems (UAS) vehicles will fly in airspace similar to Transport Category Rotorcraft, requiring them to meet stringent requirements for High-Intensity Radiated Fields (HIRF) certification. The environment is notably severe, particularly compared to fixed-wing aircraft, due to operations at lower altitudes. This potentially exposes the vehicles to high-power transmitters on the ground, leading to significant challenges. High-level HIRF exposure can result in avionic system upsets, interference, and undesirable effects. Shielding and circuit protection against HIRF pose significant barriers concerning size, weight, and cost, especially for emerging electric vertical take-off and landing (eVTOL) and electric short take-off and landing (eSTOL) vehicles. This paper proposes a novel HIRF protection approach, aiming to reduce costs by certifying vehicles to a "vehicle tolerance level" lower than that required for Transport Category Rotorcraft. The remaining protection is achieved by maintaining a safe distance from known HIRF sources. This distance is calculated based on the vehicle's tolerance level and transmitter characteristics, such as transmit power, antenna beamwidth, and direction. Tailored flight maps are developed to identify transmitters and avoidance zones within an operating area or along a flight path, enabling restricted vehicle operations. Vehicles with higher tolerance levels could have smaller HIRF avoidance zones, allowing them to operate closer to transmitters. Transmitter data are sourced from government databases, such as those of the Federal Communications Commission (FCC) and the National Oceanic and Atmospheric Administration (NOAA). A map tool is developed using Matlab to calculate and visualize HIRF avoidance zones based on available databases. The tool determines stand-off distances based on input vehicle tolerance levels, displaying results on various base maps depicting HIRF-restricted areas. Illustrations cover various FCC transmitters, including AM/FM/TV transmitters, satellite earth stations, and NOAA weather radars. The HIRF zones of smaller transmitters, such as land-mobile radios, pagers, microwave links, and cellular towers, are also illustrated. An example of flight planning around transmitters is provided. For now, airports and government-owned lands are excluded due to limited access to sensitive transmitter data. Despite this approach, a minimum HIRF tolerance level for vehicles may still be necessary to cover mobile devices, cellular base stations, transmitters on other AAM vehicles, and other small power devices not included in the FCC databases. The paper discusses findings and areas for improving existing databases and suggests an approach for better access to sanitized data in more restricted government databases. This method significantly deviates from the standard approach and introduces slightly higher flight-planning complexity. However, the potential cost savings are considerable. Future AAM/UAM/UAS aeronautical charts could potentially incorporate these new HIRF avoidance zones. Keywords—HIRF; Map; AAM; UAM; UAS; Advanced Air Mobility; Urban Air Mobility; Unmanned Aerial Systems; Certification.

HIRF↗
NASA NTRSDate not supplied

Novel Tilting Ducted-Fan Aerial Vehicle Configurations

There has been recent renewed interested in ducted-fan, powered-lift vertical takeoff and landing aircraft vehicles for uninhabited aerial vehicle and urban aerial mobility aerial applications. Early work was conducted in the 1950’s to the late 1980’s into ducted-fan vehicles, especially at the time for military missions. The focus of ducted-fan research began to shift to UAV’s and personal air transportation in the 2000’s. Work in the early 2000’s fostered interest into ducted-fan aerial vehicles for vertical lift planetary aerial vehicle missions, especially for missions to Titan, a moon of Saturn. For example, early work at NASA Ames conducted the first known investigation into oval ducts (with internal tandem fans) to be used for these aerial vehicles. The use of twin oval ducts (with internal tandem fans) allowed the use of quadrotor-style rotor rpm control for vehicle trim (in hover, for transition to high-speed forward flight the addition of a tilt-actuator to pitch the twin oval ducts forward to be aligned with the freestream needed to be added to the control approach. This current study explores open-rotor, single isolated ducted-fan, and full vehicle configuration aerodynamic performance for hover, transition, and cruise regimes for novel tilting ducted-fan aerial vehicle configurations. The objective of this study is to better understand the design aerodynamics trade space for noncircular tilting ducted-fans. The primary analysis tool used in this paper is the mid-fidelity computational fluid dynamics RotCFD tool. Several interesting and largely unexplored rotor-on-rotor (or fan-on-fan), duct-on-rotor, rotor- on-duct, and duct-on-airframe are examined in this paper. Many of these aerodynamic interactions are the key to overall aerial vehicle performance. Limited parametric sweeps of rotor-to-rotor spacing (and, therefore, sizing and shape of the enveloping ducts) for the various duct configurations will also be performed. The trade-offs between duct thrust augmentation in hover versus improved transition controllability versus improved cruise L/D will be discussed for various novel duct configurations. These ducted-fan configurations include oval ducts, ‘figure-eight’ ducts, and ‘B-shaped’ ducts, among others.

Ducted-Fan↗
NASA NTRS1991

Space transfer vehicle concepts and requirements study. Volume 1: Executive summary

A description of the study in terms of background, objectives, and issues is provided. NASA is currently studying new initiatives of space exploration involving both piloted and unpiloted missions to destinations throughout the solar system. Many of these missions require substantial improvements in launch vehicle and upper stage capabilities. This study provides a focused examination of the Space Transfer Vehicles (STV) required to perform these missions using the emerging national launch vehicle definition, the Space Station Freedom (SSF) definition, and the latest mission scenario requirements. The study objectives are to define preferred STV concepts capable of accommodating future exploration missions in a cost-effective manner, determine the technology development (if any) required to perform these missions, and develop a decision database of various programmatic approaches for the development of the STV family of vehicles. Special emphasis was given to examining space basing (stationing reusable vehicles at a space station), examining the piloted lunar mission as a primary design mission, and restricting trade studies to the high-performance, near-term cryogenics (LO2/LH2) as vehicle propellant. The study progressed through three distinct 6-month phases. The first phase concentrated on supporting a NASA 3 month definition of exploration requirements (the '90-day study') and during this phase developed and optimized the space-based point-of-departure (POD) 2.5-stage lunar vehicle. The second phase developed a broad decision database of 95 different vehicle options and transportation architectures. The final phase chose the three most cost-effective architectures and developed point designs to carry to the end of the study. These reference vehicle designs are mutually exclusive and correspond to different national choices about launch vehicles and in-space reusability. There is, however, potential for evolution between concepts.

Weber, Gary A.↗
NASA NTRS1995

A Simple Space Station Rescue Vehicle

Early in the development of the Space Station it was determined that there is a need to have a vehicle which could be used in the event that the Space Station crew need to quickly depart and return to Earth when the Space Shuttle is not available. Unplanned return missions might occur because of a medical emergency, a major Space Station failure, or if there is a long-term interruption in the delivery of logistics to the Station. The rescue vehicle ms envisioned as a simple capsule-type spacecraft which would be maintained in a dormant state at the Station for several years and be quickly activated by the crew when needed. During the assembly phase for the International Space Station, unplanned return missions will be performed by the Russian Soyuz vehicle, which can return up to three people. When the Station assembly is complete there will be a need for rescue capability for up to six people. This need might be met by an additional Soyuz vehicle or by a new vehicle which might come from a variety of sources. This paper describes one candidate concept for a Space Station rescue vehicle. The proposed rescue vehicle design has the blunt-cone shape of the Apollo command module but with a larger diameter. The rescue vehicle would be delivered to the Station in the payload bay of the Space Shuttle. The spacecraft design can accommodate six to eight people for a one-day return mission. All of the systems for the mission including deorbit propulsion are contained within the conical spacecraft and so there is no separate service module. The use of the proven Apollo re-entry shape would greatly reduce the time and cost for development and testing. Other aspects of the design are also intended to minimize development cost and simplify operations. This paper will summarize the evolution of rescue vehicle concepts, the functional requirements for a rescue vehicle, and describe the proposed design.

Petro, Andrew↗
NASA NTRS2007

The Ares I-1 Flight Test--Paving the Road for the Ares I Crew Launch Vehicle

In accordance with the U.S. Vision for Space Exploration and the nation's desire to again send humans to explore beyond Earth orbit, NASA has been tasked to send human beings to the moon, Mars, and beyond. It has been 30 years since the United States last designed and built a human-rated launch vehicle. NASA is now building the Ares I crew launch vehicle, which will loft the Orion crew exploration vehicle into orbit, and the Ares V cargo launch vehicle, which will launch the Lunar Surface Access Module and Earth departure stage to rendezvous Orion for missions to the moon. NASA has marshaled unique resources from the government and private sectors to perform the technically and programmatically complex work of delivering astronauts to orbit early next decade, followed by heavy cargo late next decade. Our experiences with Saturn and the Shuttle have taught us the value of adhering to sound systems engineering, such as the "test as you fly" principle, while applying aerospace best practices and lessons learned. If we are to fly humans safely aboard a launch vehicle, we must employ a variety of methodologies to reduce the technical, schedule, and cost risks inherent in the complex business of space transportation. During the Saturn development effort, NASA conducted multiple demonstration and verification flight tests to prove technology in its operating environment before relying upon it for human spaceflight. Less testing on the integrated Shuttle system did not reduce cost or schedule. NASA plans a progressive series of demonstration (ascent), verification (orbital), and mission flight tests to supplement ground research and high-altitude subsystem testing with real-world data, factoring the results of each test into the next one. In this way, sophisticated analytical models and tools, many of which were not available during Saturn and Shuttle, will be calibrated and we will gain confidence in their predictions, as we gain hands-on experience in operating the first of two new launch vehicle systems. The Ares I-1 flight test vehicle (FTV) will incorporate a mix of flight and mockup hardware, reflecting a configuration similar in mass, weight, and shape (outer mold line or OML) to the operational vehicle. It will be powered by a four-segment reusable solid rocket booster (RSRB), which is currently in Shuttle inventory, and will be modified to include a fifth, inert segment that makes it approximately the same size and weight as the five segment RSRB, which will be available for the second flight test in 2012. The Ares I-1 vehicle configuration is shown. Each test flight has specific objectives appropriate to the design analysis cycle in progress. The Ares I-1 demonstration test, slated for April 2009, gives NASA its first opportunity to gather critical data about the flight dynamics of the integrated launch vehicle stack, understand how to control its roll during flight, and other characterize the severe stage separation environment that the upper stage will experience during future operational flights. NASA also will begin the process of modifying the launch infrastructure and fine-tuning ground and mission operational scenarios, as NASA transitions from the Shuttle to the Ares/Orion system.

Davis, Stephan R.↗
NASA NTRS2008

Effect of Orion Post-Touchdown Parachute Release Time on Vehicle Rollover

The effects that the Orion parachutes have on the vehicle response once the vehicle lands on the ground are examined in this report. A concern with the Orion landing is that structural accelerations will cause vehicle and/or crew injuries or that the vehicle may roll over. The parachute effects are thought to have the potential of pulling the vehicle over during conditions such as higher winds or in some cases stabilizing the vehicle by preventing its motions after touchdown. A collection of representative landing conditions is used to assess the post-touchdown parachute release effect, and it was determined that, in general, there is no significant advantage or disadvantage to releasing the parachutes past the time when the vehicle touches ground. For landing conditions when there is a high horizontal wind, retaining the parachutes has a detrimental effect on vehicle rollover because the drag force on the parachutes pulls the vehicle over. Under this condition, some form of automated parachute release should be a requirement given that an attached parachute may cause the vehicle to roll over. An automated system would ensure that the release occur within 0.50 sec of touchdown (time when parachute regains tension), which is not enough time for a crew-operated manual release.

Lawrence, Charles↗
NASA NTRS2008

Attitude and Translation Control of a Solar Sail Vehicle

A report discusses the ability to control the attitude and translation degrees-of-freedom of a solar sail vehicle by changing its center of gravity. A movement of the spacecraft s center of mass causes solar-pressure force to apply a torque to the vehicle. At the compact core of the solar-sail vehicle lies the spacecraft bus which is a large fraction of the total vehicle mass. In this concept, the bus is attached to the spacecraft by two single degree-of-freedom linear tracks. This allows relative movement of the bus in the sail plane. At the null position, the resulting solar pressure applies no torque to the vehicle. But any deviation of the bus from the null creates an offset between the spacecraft center of mass and center of solar radiation pressure, resulting in a solar-pressure torque on the vehicle which changes the vehicle attitude. Two of the three vehicle degrees of freedom can be actively controlled in this manner. The third, the roll about the sunline, requires a low-authority vane/propulsive subsystem. Translation control of the vehicle is achieved by directing the solar-pressure-induced force in the proper inertial direction. This requires attitude control. Attitude and translation degrees-of-freedom are therefore coupled. A guidance law is proposed, which allows the vehicle to stationkeep at an appropriate point on the inertially-rotating Sun-Earth line. Power requirements for moving the bus are minimal. Extensive software simulations have been performed to demonstrate the feasibility of this concept.

Singh, Gurkirpal↗
NASA NTRS2009

ATK Launch Vehicle (ALV-X1) Liftoff Acoustic Environments: Prediction vs. Measurement

The ATK Launch Vehicle (ALV-X1) provided an opportunity to measure liftoff acoustic noise data. NASA Marshall Space Flight Center (MSFC) engineers were interested in the ALV-X1 launch because the First Stage motor and launch pad conditions, including a relativity short deflector ducting, provide a potential analogue to future Ares I launches. This paper presents the measured liftoff acoustics on the vehicle and tower. Those measured results are compared to predictions based upon the method described in NASA SP-8072 "Acoustic Loads Generated by the Propulsion System" and the Vehicle Acoustic Environment Prediction Program (VAEPP) which was developed by MSFC acoustics engineers. One-third octave band sound pressure levels will be presented. This data is useful for the ALV-X1 in validating the pre-launch environments and loads predictions. Additionally, the ALV-X1 liftoff data can be scaled to define liftoff environments for the NASA Constellation program Ares vehicles. Vehicle liftoff noise is caused by the supersonic jet flow interaction with surrounding atmosphere or more simply, jet noise. As the vehicle's First Stage motor is ignited, an acoustic noise field is generated by the exhaust. This noise field persists due to the supersonic jet noise and reflections from the launch pad and tower, then changes as the vehicle begins to liftoff from the launch pad. Depending on launch pad and adjacent tower configurations, the liftoff noise is generally very high near the nozzle exit and decreases rapidly away from the nozzle. The liftoff acoustic time range of interest is typically 0 to 20 seconds after ignition. The exhaust plume thermo-fluid mechanics generates sound at approx.10 Hz to 20 kHz. Liftoff acoustic noise is usually the most severe dynamic environment for a launch vehicle or payload in the mid to high frequency range (approx.50 to 2000 Hz). This noise environment can induce high-level vibrations along the external surfaces of the vehicle and surrounding launch facility structures. The acoustic pressure fluctuations will induce severe vibrations in relatively large lightweight structures. Consequently, there is the potential for failure of the structure or attached electrical components. Due to these potential failures, the liftoff acoustic noise is one of the noise source inputs used to determine the vibro-acoustic qualification environment for a launch vehicle and its components.

Houston, Janice↗
NASA NTRS2011

Launch Vehicle Demonstrator Using Shuttle Assets

The Marshall Space Flight Center Advanced Concepts Office (ACO) has the leading role for NASA s preliminary conceptual launch vehicle design and performance analysis. Over the past several years the ACO Earth-to-Orbit Team has evaluated thousands of launch vehicle concept variations for a multitude of studies including agency-wide efforts such as the Exploration Systems Architecture Study (ESAS), Constellation, Heavy Lift Launch Vehicle (HLLV), Heavy Lift Propulsion Technology (HLPT), Human Exploration Framework Team (HEFT), and Space Launch System (SLS). NASA plans to continue human space exploration and space station utilization. Launch vehicles used for heavy lift cargo and crew will be needed. One of the current leading concepts for future heavy lift capability is an inline one and a half stage concept using solid rocket boosters (SRB) and based on current Shuttle technology and elements. Potentially, the quickest and most cost-effective path towards an operational vehicle of this configuration is to make use of a demonstrator vehicle fabricated from existing shuttle assets and relying upon the existing STS launch infrastructure. Such a demonstrator would yield valuable proof-of-concept data and would provide a working test platform allowing for validated systems integration. Using shuttle hardware such as existing RS-25D engines and partial MPS, propellant tanks derived from the External Tank (ET) design and tooling, and four-segment SRB s could reduce the associated upfront development costs and schedule when compared to a concept that would rely on new propulsion technology and engine designs. There are potentially several other additional benefits to this demonstrator concept. Since a concept of this type would be based on man-rated flight proven hardware components, this demonstrator has the potential to evolve into the first iteration of heavy lift crew or cargo and serve as a baseline for block upgrades. This vehicle could also serve as a demonstration and test platform for the Orion Program. Critical spacecraft systems, re-entry and recovery systems, and launch abort systems of Orion could also be demonstrated in early test flights of the launch vehicle demo. Furthermore, an early demonstrator of this type would provide a stop-gap for retaining critical human capital and infrastructure while affording the current emerging generation of young engineers opportunity to work with and capture lessons learned from existing STS program offices and personnel, who were integral in the design and development of the Space Shuttle before these resources are no longer available. The objective of this study is to define candidate launch vehicle demonstration concepts that are based on Space Shuttle assets and determine their performance capabilities and how these demonstration vehicles could evolve to a heavy lift capability to low earth orbit.

Threet, Grady E., Jr.↗
NASA NTRS2011

Launch Vehicle Demonstrator Using Shuttle Assets

The Advanced Concepts Office at NASA's George C. Marshall Space Flight Center undertook a study to define candidate early heavy lift demonstration launch vehicle concepts derived from existing space shuttle assets. The objective was to determine the performance capabilities of these vehicles and characterize potential early demonstration test flights. Given the anticipated budgetary constraints that may affect America's civil space program, and a lapse in U.S. heavy launch capability with the retirement of the space shuttle, an early heavy lift launch vehicle demonstration flight would not only demonstrate capabilities that could be utilized for future space exploration missions, but also serve as a building block for the development of our nation s next heavy lift launch system. An early heavy lift demonstration could be utilized as a test platform, demonstrating capabilities of future space exploration systems such as the Multi Purpose Crew Vehicle. By using existing shuttle assets, including the RS-25D engine inventory, the shuttle equipment manufacturing and tooling base, and the segmented solid rocket booster industry, a demonstrator concept could expedite the design-to-flight schedule while retaining critical human skills and capital. In this study two types of vehicle designs are examined. The first utilizes a high margin/safety factor battleship structural design in order to minimize development time as well as monetary investment. Structural design optimization is performed on the second, as if an operational vehicle. Results indicate low earth orbit payload capability is more than sufficient to support various vehicle and vehicle systems test programs including Multi-Purpose Crew Vehicle articles. Furthermore, a shuttle-derived, hydrogen core vehicle configuration offers performance benefits when trading evolutionary paths to maximum capability.

Creech, Dennis M.↗
NASA NTRS2011

Multidisciplinary Modeling Software for Analysis, Design, and Optimization of HRRLS Vehicles

The concept for Highly Reliable Reusable Launch Systems (HRRLS) under the NASA Hypersonics project is a two-stage-to-orbit, horizontal-take-off / horizontal-landing, (HTHL) architecture with an air-breathing first stage. The first stage vehicle is a slender body with an air-breathing propulsion system that is highly integrated with the airframe. The light weight slender body will deflect significantly during flight. This global deflection affects the flow over the vehicle and into the engine and thus the loads and moments on the vehicle. High-fidelity multi-disciplinary analyses that accounts for these fluid-structures-thermal interactions are required to accurately predict the vehicle loads and resultant response. These predictions of vehicle response to multi physics loads, calculated with fluid-structural-thermal interaction, are required in order to optimize the vehicle design over its full operating range. This contract with ResearchSouth addresses one of the primary objectives of the Vehicle Technology Integration (VTI) discipline: the development of high-fidelity multi-disciplinary analysis and optimization methods and tools for HRRLS vehicles. The primary goal of this effort is the development of an integrated software system that can be used for full-vehicle optimization. This goal was accomplished by: 1) integrating the master code, FEMAP, into the multidiscipline software network to direct the coupling to assure accurate fluid-structure-thermal interaction solutions; 2) loosely-coupling the Euler flow solver FEFLO to the available and proven aeroelasticity and large deformation (FEAP) code; 3) providing a coupled Euler-boundary layer capability for rapid viscous flow simulation; 4) developing and implementing improved Euler/RANS algorithms into the FEFLO CFD code to provide accurate shock capturing, skin friction, and heat-transfer predictions for HRRLS vehicles in hypersonic flow, 5) performing a Reynolds-averaged Navier-Stokes computation on an HRRLS configuration; 6) integrating the RANS solver with the FEAP code for coupled fluid-structure-thermal capability; and 7) integrating the existing NASA SRGULL propulsion flow path prediction software with the FEFLO software for quasi-3D propulsion flow path predictions, 8) improving and integrating into the network, an existing adjoint-based design optimization code.

Spradley, Lawrence W.↗
NASA NTRS2015

Assimilation of Wind Profiles from Multiple Doppler Radar Wind Profilers for Space Launch Vehicle Applications

Space launch vehicles utilize atmospheric winds in design of the vehicle and during day-of-launch (DOL) operations to assess affects of wind loading on the vehicle and to optimize vehicle performance during ascent. The launch ranges at NASA's Kennedy Space Center co-located with the United States Air Force's (USAF) Eastern Range (ER) at Cape Canaveral Air Force Station and USAF's Western Range (WR) at Vandenberg Air Force Base have extensive networks of in-situ and remote sensing instrumentation to measure atmospheric winds. Each instrument's technique to measure winds has advantages and disadvantages in regards to use for vehicle engineering assessments. Balloons measure wind at all altitudes necessary for vehicle assessments, but two primary disadvantages exist when applying balloon output on DOL. First, balloons need approximately one hour to reach required altitude. For vehicle assessments this occurs at 60 kft (18.3 km). Second, balloons are steered by atmospheric winds down range of the launch site that could significantly differ from those winds along the vehicle ascent trajectory. Figure 1 illustrates the spatial separation of balloon measurements from the surface up to approximately 55 kft (16.8 km) during the Space Shuttle launch on 10 December 2006. The balloon issues are mitigated by use of vertically pointing Doppler Radar Wind Profilers (DRWPs). However, multiple DRWP instruments are required to provide wind data up to 60 kft (18.3 km) for vehicle trajectory assessments. The various DRWP systems have different operating configurations resulting in different temporal and spatial sampling intervals. Therefore, software was developed to combine data from both DRWP-generated profiles into a single profile for use in vehicle trajectory analyses. Details on how data from various wind measurement systems are combined and sample output will be presented in the following sections.

Decker, Ryan K.↗
NASA NTRS2015

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

The engineering development of the National Aeronautics and Space Administration's (NASA) new Space Launch System (SLS) 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 nominal and off-nominal characteristics of SLS's elements and subsystems must be understood and 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 systems 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 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 FSW certification are an important focus of SLS's development effort to further ensure reliable detection and response to off-nominal vehicle states during all phases of vehicle operation from pre-launch through end of flight. To test and validate these M&FM algorithms a dedicated test-bed was developed for full Vehicle Management End-to-End Testing (VMET). For addressing fault management (FM) early in the development lifecycle for the SLS program, NASA formed the M&FM team as part of the Integrated Systems Health Management and Automation Branch under the Spacecraft Vehicle Systems Department at the Marshall Space Flight Center (MSFC). To support the development of the FM algorithms, the VMET developed by the M&FM team provides the ability to integrate the algorithms, perform test cases, and integrate vendor-supplied physics-based launch vehicle (LV) subsystem models. Additionally, the team has developed processes for implementing and validating the M&FM algorithms for concept validation and risk reduction. The flexibility of the VMET capabilities 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, GNC, and others. One of the principal functions 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 test and validation processes. In any software development process there is inherent risk in the interpretation and implementation of concepts from requirements and test cases into flight software compounded with potential human errors throughout the development and regression testing lifecycle. Risk reduction is addressed by the M&FM group but in particular by the Analysis Team working with other organizations such as S&MA, Structures and Environments, GNC, Orion, 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 (LOM) and Loss of Crew (LOC) probabilities. In addition, through state machine and diagnostic modeling, analysis efforts investigate a broader suite of failure effects and associated detection and responses to be tested in VMET to ensure reliable failure detection, and confirm 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 - the ARINC 6535-partitioned Operating System, 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 FSW. This enables the development of performance standards and test cases to characterize the M&FM algorithms and sets a benchmark from which to measure their effectiveness and performance in the exterior 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↗
NASA NTRS2015

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↗
NASA NTRS2018

The Evolution of Payload Data Capabilities on the Commercial Visiting Vehicles that Service the International Space Station

For over 10 years, NASA has been working with U.S.-based commercial companies to support the design, development, and operations of new commercial space vehicles. The purpose of these vehicles is to provide cargo and crew transportation services to the International Space Station (ISS) and to stimulate the commercial space transportation industry to Low-Earth Orbit (LEO). Along with the ability to provide a couple tons of cargo to the ISS each mission, the commercial visiting vehicles also provide the ability to transfer NASA payloads to and from the ISS in an active, powered state. To take advantage of this capability, NASA requirements for the data services that payloads need while they are integrated into the visiting vehicles have grown with each set of commercial contracts. Today, NASA desires for payload data services encompass a variety of capabilities including payload health and status (H&S) telemetry monitoring, visiting vehicle environment data monitoring, and payload commanding. The intent of these capabilities is to provide payload developers with situational awareness and the ability to quickly diagnose any problems with payload operations prior to vehicle docking or post-landing to support immediate troubleshooting response. As new requirements for payload data services have emerged over the years, the ISS Payload Operations Integration Center (POIC) at the NASA Marshall Space Flight Center (MSFC) has established ground segment interfaces to the visiting vehicle control centers to enable payload developers to use these services. Many technical and programmatic challenges have been faced while establishing these interfaces. The most significant challenge faced has been in finding the right balance amongst providing interfaces to payloads that are compatible with the ISS so that payload hardware or software changes are not necessary to ensure compatibility with the visiting vehicles; keeping POIC ground system development costs low by standardizing implementation approaches across commercial vehicle partners; and fostering commercialization through supporting vendor-unique implementations that are commercially economical. This paper will first detail the data services that will be available to payload users under each commercial visiting vehicle contract. Secondly, this paper will offer discussion of the most significant technical and programmatic challenges faced to-date in offering these new data services to payload developers.

Wiggins, Lindsay M.↗
NASA NTRS2020

Mars Ascent Vehicle Hybrid Propulsion Configuration

As part of a Mars Sample Return (MSR) campaign, two Mars Ascent Vehicle (MAV) configurations have been designed in parallel. Each ascent vehicle configuration has a different propulsion system which ultimately leads to two unique vehicle designs. As part of a Preliminary Architecture Assessment (PAA), these vehicle designs were developed to the same level of maturity in order to inform the selection of one of the vehicles as the point of departure design for the campaign. The selection will be made in November 2019. The initial MSR architecture called for a hybrid-based propulsion MAV. This type of propulsion system calls for a solid wax motor that would utilize liquid MON-25 as an oxidizer. Hybrid rocket propulsion allows for more flexibility than traditional solid or liquid propulsion options, and typically benefits from the advantages of both. A hybrid motor can be throttled and shut down easily, and avoids significant risk in manufacturing and handling. On a theoretical level, hybrid motors perform at a higher specific impulse (Isp) than solid motors. The primary disadvantage of hybrid motors comes from additional complexity and significantly less flight heritage and low Technology Readiness Level (TRL). This paper describes the design of the hybrid propulsion configuration. An additional paper will be published describing the design of the solid propulsion configuration1. The hybrid propulsion configuration MAV was developed in 2019 by NASA Marshall Space Flight Center (MSFC) in association with NASA Jet Propulsion Laboratory (JPL). It features a Single Stage to Orbit (SSTO) design with an SP7A solid wax fuel and MON-25 liquid oxidizer. The liquid portion of the vehicle allows for a Liquid Injection Thrust Vector Controller (LITVC) as well as hypergolic propellant additives for ignition. The vehicle was designed to deliver approximately 0.31kg of Martian geological samples to a circular orbit at Mars of 343km at a 25o inclination. Although hybrid propulsion in general has been used on launch vehicles in the past, the integrated vehicle subsystems that operate in conjunction with these propulsion elements do not typically operate in a Martian environment, which in this application can get as cold as -40oC. The PAA advanced the maturity of these subsystems by performing detailed design and analysis on the vehicle with respect to structures and mechanisms, Guidance/Navigation/Control (GNC) systems, avionics, Reaction Control System (RCS), LITVC, thermal environments, and advanced Computational Fluid Dynamics (CFD). This paper will summarize the results of these studies.

Yaghoubi, Darius↗
NASA NTRS2019

Measurement and Analysis of Terminal Shock Oscillation and Buffet Forcing Functions on a Launch Vehicle Payload Fairing

The buffet loads on a launch vehicle payload shroud can be impacted by the unsteadiness associated with a terminal shock at high subsonic speeds. At these conditions, flow accelerates to supersonic speeds on the nose of the payload fairing and is terminated by a normal shock on the cylindrical section downstream of the nose cone/cylinder shoulder. The location of the terminal shock and associated separated boundary layer is affected by the freestream Mach number, Reynolds number, and the pitch/yaw of the launch vehicle. Furthermore, even when the freestream conditions and vehicle attitude are constant, this terminal shock oscillates on the surface of the vehicle. The time-varying surface pressure associated with the terminal shock results in unsteady aerodynamic loads that may interact with vehicle structural dynamic modes and the guidance and control of the vehicle. Buffet testing of a 3-percent scale rigid buffet model of a launch vehicle cargo configuration with a tangent-ogive payload shroud was conducted in 2012 and in 2016. Initial buffet forcing functions (BFFs) utilized a coarse pressure sensor distribution on the vehicle surface in which a single longitudinal station with eight sensors observed the terminal shock environment at Mach 0.90. An examination of these circumferential pressures reveal large impulse-like pressure fluctuations and an asymmetry in pressure when the vehicle is at a nonzeroangle of attack that result in high BFFs. Revisions to the shock integration region were made based on computational fluid dynamics and shadowgraph video of shock motion to better represent the BFFs and reduce the high loads resulting from this environment. To more clearly understand this terminal shock environment, a second wind tunnel test was conducted with a dense distribution of 256 sensors at the terminal shock location. These sensor arrays presents a unique opportunity to observe the unsteady terminal shock environment and to characterize the impact of various integration schemes on the BFFs. This paper presents a summary of the development of BFFs for this terminal shock and a detailed analyses of shock region pressure coefficients, coherence, BFFs, shock location time histories, and power spectral density to help guide development of BFFs for other launch vehicle test and analysis programs.

Piatak, David J.↗