Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Flight”

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 1,369 records · Page 76
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Rehabilitation After International Space Station Flights

Rehabilitating U.S. crew members to preflight status following flights on the Russian Mir Space Station required longer than six months for full functional recovery of some of the seven crew members. Additional exercise hardware has been added on the International Space Station as well as a rehabilitative emphasis on functional fitness/agility and proprioception. The authors will describe and present the results of the rehabilitation program for ISS and evaluate rehabilitative needs for longer missions. Pre- and in-flight programs emphasize strength and aerobic conditioning. One year before launch, crew members are assigned an Astronaut Strength and Conditioning specialist. Crew members are scheduled for 2 hours, 3 days a week, for pre-flight training and 2.5 hours, six days a week, for in-flight training. Crewmembers are tested on functional fitness, agility, isokinetic strength, and submaximal cycle ergometer evaluation before and after flight. The information from these tests is used for exercise prescriptions, comparison, and evaluation of the astronaut and training programs. The rehabilitation program lasts for 45 days and is scheduled for 2 hours during each crew workday. Phase 1 of the rehabilitation program starts on landing day and places emphasis on ambulation, flexibility, and muscle strengthening. Phase 2 adds proprioceptive exercise and cardiovascular conditioning. Phase 3 (the longest phase) focuses on functional development. All programs are tailored specifically for each individual according to their test results, preferred recreational activities, and mission roles and duties. Most crew members reached or exceeded their preflight test values 45 days after flight. Some crew members subjectively indicated the need for a longer rehabilitation period. The current rehabilitation program for returning ISS crew members seems adequate in content but may need to be extended for longer expeditions.

Chauvin, S. J.↗
NASA NTRS2011

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

Ares I-X First Flight Loss of Vehicle Probability Analysis

As part of the Constellation (Cx) Program development effort, several test flights were planned to prove concepts and operational capabilities of the new vehicles being developed. The first test, involving the Eastern Test Range, is the Ares I-X launched in 2009. As part of this test, the risk to the general public was addressed to ensure it is within Air Force requirements. This paper describes the methodology used to develop first flight estimates of overall loss of vehicle (LOV) failure probability, specifically for the Ares I-X. The method described in this report starts with the Air Force s generic failure probability estimate for first flight and adjusts the value based on the complexity of the vehicle as compared to the complexity of a generic vehicle. The results estimate a 1 in 9 probability of failure. The paper also describes traditional PRA methods used in this assessment, which were then combined with the updated first flight risk methodology to generate inputs required by the malfunction turn analysis to support estimate of casualty (Ec) calculations as part of the Final Flight Data Package (FFDP) delivered to the Eastern Range for Final Flight Plan Approval.

Bigler, Mark A.↗
NASA NTRS2011

DBD Plasma Actuators for Flow Control in Air Vehicles and Jet Engines - Simulation of Flight Conditions in Test Chambers by Density Matching

Dielectric Barrier Discharge (DBD) Plasma actuators for active flow control in aircraft and jet engines need to be tested in the laboratory to characterize their performance at flight operating conditions. DBD plasma actuators generate a wall-jet electronically by creating weakly ionized plasma, therefore their performance is affected by gas discharge properties, which, in turn, depend on the pressure and temperature at the actuator placement location. Characterization of actuators is initially performed in a laboratory chamber without external flow. The pressure and temperature at the actuator flight operation conditions need to be simultaneously set in the chamber. A simplified approach is desired. It is assumed that the plasma discharge depends only on the gas density, while other temperature effects are assumed to be negligible. Therefore, tests can be performed at room temperature with chamber pressure set to yield the same density as in operating flight conditions. The needed chamber pressures are shown for altitude flight of an air vehicle and for jet engines at sea-level takeoff and altitude cruise conditions. Atmospheric flight conditions are calculated from standard atmosphere with and without shock waves. The engine data was obtained from four generic engine models; 300-, 150-, and 50-passenger (PAX) aircraft engines, and a military jet-fighter engine. The static and total pressure, temperature, and density distributions along the engine were calculated for sea-level takeoff and for altitude cruise conditions. The corresponding chamber pressures needed to test the actuators were calculated. The results show that, to simulate engine component flows at in-flight conditions, plasma actuator should be tested over a wide range of pressures. For the four model engines the range is from 12.4 to 0.03 atm, depending on the placement of the actuator in the engine. For example, if a DBD plasma actuator is to be placed at the compressor exit of a 300 PAX engine, it has to be tested at 12.4 atm for takeoff, and 6 atm for cruise conditions. If it is to be placed at the low-pressure turbine, it has to be tested at 0.5 and 0.2 atm, respectively. These results have implications for the feasibility and design of DBD plasma actuators for jet engine flow control applications. In addition, the distributions of unit Reynolds number, Mach number, and velocity along the engine are provided. The engine models are non-proprietary and this information can be used for evaluation of other types of actuators and for other purposes.

Ashpis, David E.↗
NASA NTRS2006

Flight-Tested Prototype of BEAM Software

Researchers at JPL have completed a software prototype of BEAM (Beacon-based Exception Analysis for Multi-missions) and successfully tested its operation in flight onboard a NASA research aircraft. BEAM (see NASA Tech Briefs, Vol. 26, No. 9; and Vol. 27, No. 3) is an ISHM (Integrated Systems Health Management) technology that automatically analyzes sensor data and classifies system behavior as either nominal or anomalous, and further characterizes anomalies according to strength, duration, and affected signals. BEAM (see figure) can be used to monitor a wide variety of physical systems and sensor types in real time. In this series of tests, BEAM monitored the engines of a Dryden Flight Research Center F-18 aircraft, and performed onboard, unattended analysis of 26 engine sensors from engine startup to shutdown. The BEAM algorithm can detect anomalies based solely on the sensor data, which includes but is not limited to sensor failure, performance degradation, incorrect operation such as unplanned engine shutdown or flameout in this example, and major system faults. BEAM was tested on an F-18 simulator, static engine tests, and 25 individual flights totaling approximately 60 hours of flight time. During these tests, BEAM successfully identified planned anomalies (in-flight shutdowns of one engine) as well as minor unplanned anomalies (e.g., transient oil- and fuel-pressure drops), with no false alarms or suspected false-negative results for the period tested. BEAM also detected previously unknown behavior in the F- 18 compressor section during several flights. This result, confirmed by direct analysis of the raw data, serves as a significant test of BEAM's capability.

Mackey, Ryan↗
NASA NTRS2011

Comparison of Ares I-X Wind-Tunnel Derived Buffet Environment with Flight Data

The Ares I-X Flight Test Vehicle (FTV), launched in October 2009, carried with it over 243 buffet verification pressure sensors and was one of the most heavily instrumented launch vehicle flight tests. This flight test represented a unique opportunity for NASA and its partners to compare the wind-tunnel derived buffet environment with that measured during the flight of Ares I-X. It is necessary to define the launch vehicle buffet loads to ensure that structural components and vehicle subsystems possess adequate strength, stress, and fatigue margins when the vehicle structural dynamic response to buffet forcing functions are considered. Ares I-X buffet forcing functions were obtained via wind-tunnel testing of a rigid buffet model (RBM) instrumented with hundreds of unsteady pressure transducers designed to measure the buffet environment across the desired frequency range. This paper discusses the comparison of RBM and FTV buffet environments, including fluctuating pressure coefficient and normalized sectional buffet forcing function root-mean-square magnitudes, frequency content of power-spectral density functions, and force magnitudes of an alternating flow phenomena. Comparison of wind-tunnel model and flight test vehicle buffet environments show very good agreement with root-mean-square magnitudes of buffet forcing functions at the majority of vehicle stations. Spectra proved a challenge to compare because of different wind-tunnel and flight test conditions and data acquisition rates. However, meaningful and promising comparisons of buffet spectra are presented. Lastly, the buffet loads resulting from the transition of subsonic separated flow to supersonic attached flow were significantly over-predicted by wind-tunnel results.

Piatak, David J.↗
NASA NTRS2011

The Legacy of Space Shuttle Flight Software

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

Hickey, Christopher J.↗
NASA NTRS2011

The Final Count Down: A Review of Three Decades of Flight Controller Training Methods for Space Shuttle Mission Operations

Operations of human spaceflight systems is extremely complex; therefore, the training and certification of operations personnel is a critical piece of ensuring mission success. Mission Control Center (MCC-H), at the Lyndon B. Johnson Space Center in Houston, Texas, manages mission operations for the Space Shuttle Program, including the training and certification of the astronauts and flight control teams. An overview of a flight control team s makeup and responsibilities during a flight, and details on how those teams are trained and certified, reveals that while the training methodology for developing flight controllers has evolved significantly over the last thirty years the core goals and competencies have remained the same. In addition, the facilities and tools used in the control center have evolved. Changes in methodology and tools have been driven by many factors, including lessons learned, technology, shuttle accidents, shifts in risk posture, and generational differences. Flight controllers share their experiences in training and operating the space shuttle. The primary training method throughout the program has been mission simulations of the orbit, ascent, and entry phases, to truly train like you fly. A review of lessons learned from flight controller training suggests how they could be applied to future human spaceflight endeavors, including missions to the moon or to Mars. The lessons learned from operating the space shuttle for over thirty years will help the space industry build the next human transport space vehicle.

Dittermore, Gary↗
NASA NTRS2011

Nonlinear Dynamic Inversion Baseline Control Law: Flight-Test Results for the Full-scale Advanced Systems Testbed F/A-18 Airplane

A model reference nonlinear dynamic inversion control law has been developed to provide a baseline controller for research into simple adaptive elements for advanced flight control laws. This controller has been implemented and tested in a hardware-in-the-loop simulation and in flight. The flight results agree well with the simulation predictions and show good handling qualities throughout the tested flight envelope with some noteworthy deficiencies highlighted both by handling qualities metrics and pilot comments. Many design choices and implementation details reflect the requirements placed on the system by the nonlinear flight environment and the desire to keep the system as simple as possible to easily allow the addition of the adaptive elements. The flight-test results and how they compare to the simulation predictions are discussed, along with a discussion about how each element affected pilot opinions. Additionally, aspects of the design that performed better than expected are presented, as well as some simple improvements that will be suggested for follow-on work.

Miller, Christopher J.↗
NASA NTRS2010

Experimental Validation of L1 Adaptive Control: Rohrs' Counterexample in Flight

The paper presents new results on the verification and in-flight validation of an L1 adaptive flight control system, and proposes a general methodology for verification and validation of adaptive flight control algorithms. The proposed framework is based on Rohrs counterexample, a benchmark problem presented in the early 80s to show the limitations of adaptive controllers developed at that time. In this paper, the framework is used to evaluate the performance and robustness characteristics of an L1 adaptive control augmentation loop implemented onboard a small unmanned aerial vehicle. Hardware-in-the-loop simulations and flight test results confirm the ability of the L1 adaptive controller to maintain stability and predictable performance of the closed loop adaptive system in the presence of general (artificially injected) unmodeled dynamics. The results demonstrate the advantages of L1 adaptive control as a verifiable robust adaptive control architecture with the potential of reducing flight control design costs and facilitating the transition of adaptive control into advanced flight control systems.

Xargay, Enric↗
NASA NTRS2005

Designing Flight Deck Procedures

Three reports address the design of flight-deck procedures and various aspects of human interaction with cockpit systems that have direct impact on flight safety. One report, On the Typography of Flight- Deck Documentation, discusses basic research about typography and the kind of information needed by designers of flight deck documentation. Flight crews reading poorly designed documentation may easily overlook a crucial item on the checklist. The report surveys and summarizes the available literature regarding the design and typographical aspects of printed material. It focuses on typographical factors such as proper typefaces, character height, use of lower- and upper-case characters, line length, and spacing. Graphical aspects such as layout, color coding, fonts, and character contrast are discussed; and several cockpit conditions such as lighting levels and glare are addressed, as well as usage factors such as angular alignment, paper quality, and colors. Most of the insights and recommendations discussed in this report are transferable to paperless cockpit systems of the future and computer-based procedure displays (e.g., "electronic flight bag") in aerospace systems and similar systems that are used in other industries such as medical, nuclear systems, maritime operations, and military systems.

Degani, Asaf↗
NASA NTRS2011

The First Flight Decision for New Human Spacecraft Vehicles - A General Approach

Determining when it is safe to fly a crew on a launch vehicle/spacecraft for the first time, especially when the test flight is a part of the overall system certification process, has long been a challenge for program decision makers. The decision on first flight is ultimately the judgment of the program and agency management in conjunction with the design and operations team. To aid in this decision process, a NASA team undertook the task to develop a generic framework for evaluating whether any given program or commercial provider has sufficiently complete and balanced plans in place to allow crewmembers to safely fly on human spaceflight systems for the first time. It was the team s goal to establish a generic framework that could easily be applied to any new system, although the system design and intended mission would require specific assessment. Historical data shows that there are multiple approaches that have been successful in first flight with crew. These approaches have always been tailored to the specific system design, mission objectives, and launch environment. Because specific approaches may vary significantly between different system designs and situations, prescriptive instructions or thorough checklists cannot be provided ahead of time. There are, however, certain general approaches that should be applied in thinking through the decision for first flight. This paper addresses some of the most important factors to consider when developing a new system or evaluating an existing system for whether or not it is safe to fly humans to/from space. In the simplest terms, it is time to fly crew for the first time when it is safe to do so and the benefit of the crewed flight is greater than the residual risk. This is rarely a straight-forward decision. The paper describes the need for experience, sound judgment, close involvement of the technical and management teams, and established decision processes. In addition, the underlying level of confidence the manager has in making the decision will also be discussed. By applying the outlined thought processes and approaches to a specific design, test program and mission objectives, a project team will be better able to focus the debate and discussion on critical areas for consideration and added scrutiny -- allowing decision makers to adequately address the first crewed flight decision.

Schaible, Dawn M.↗
NASA NTRS2011

Fused Reality for Enhanced Flight Test Capabilities

The feasibility of using Fused Reality-based simulation technology to enhance flight test capabilities has been investigated. In terms of relevancy to piloted evaluation, there remains no substitute for actual flight tests, even when considering the fidelity and effectiveness of modern ground-based simulators. In addition to real-world cueing (vestibular, visual, aural, environmental, etc.), flight tests provide subtle but key intangibles that cannot be duplicated in a ground-based simulator. There is, however, a cost to be paid for the benefits of flight in terms of budget, mission complexity, and safety, including the need for ground and control-room personnel, additional aircraft, etc. A Fused Reality(tm) (FR) Flight system was developed that allows a virtual environment to be integrated with the test aircraft so that tasks such as aerial refueling, formation flying, or approach and landing can be accomplished without additional aircraft resources or the risk of operating in close proximity to the ground or other aircraft. Furthermore, the dynamic motions of the simulated objects can be directly correlated with the responses of the test aircraft. The FR Flight system will allow real-time observation of, and manual interaction with, the cockpit environment that serves as a frame for the virtual out-the-window scene.

Bachelder, Ed↗
NASA NTRS2012

A Semi-Empirical Noise Modeling Method for Helicopter Maneuvering Flight Operations

A new model for Blade-Vortex Interaction noise generation during maneuvering flight is developed in this paper. Acoustic and performance data from both flight and wind tunnels are used to derive a non-dimensional and analytical performance/acoustic model that describes BVI noise in steady flight. The model is extended to transient maneuvering flight (pure pitch and roll transients) by using quasisteady assumptions throughout the prescribed maneuvers. Ground noise measurements, taken during maneuvering flight of a Bell 206B helicopter, show that many of the noise radiation details are captured. The result is a computationally efficient Blade-Vortex Interaction noise model with sufficient accuracy to account for transient maneuvering flight. The code can be run in real time to predict transient maneuver noise and is suitable for use in an acoustic mission-planning tool.

Greenwood, Eric↗
NASA NTRS2012

Towards an Improved Pilot-Vehicle Interface for Highly Automated Aircraft: Evaluation of the Haptic Flight Control System

The control automation and interaction paradigm (e.g., manual, autopilot, flight management system) used on virtually all large highly automated aircraft has long been an exemplar of breakdowns in human factors and human-centered design. An alternative paradigm is the Haptic Flight Control System (HFCS) that is part of NASA Langley Research Center s Naturalistic Flight Deck Concept. The HFCS uses only stick and throttle for easily and intuitively controlling the actual flight of the aircraft without losing any of the efficiency and operational benefits of the current paradigm. Initial prototypes of the HFCS are being evaluated and this paper describes one such evaluation. In this evaluation we examined claims regarding improved situation awareness, appropriate workload, graceful degradation, and improved pilot acceptance. Twenty-four instrument-rated pilots were instructed to plan and fly four different flights in a fictitious airspace using a moderate fidelity desktop simulation. Three different flight control paradigms were tested: Manual control, Full Automation control, and a simplified version of the HFCS. Dependent variables included both subjective (questionnaire) and objective (SAGAT) measures of situation awareness, workload (NASA-TLX), secondary task performance, time to recognize automation failures, and pilot preference (questionnaire). The results showed a statistically significant advantage for the HFCS in a number of measures. Results that were not statistically significant still favored the HFCS. The results suggest that the HFCS does offer an attractive and viable alternative to the tactical components of today s FMS/autopilot control system. The paper describes further studies that are planned to continue to evaluate the HFCS.

Schutte, Paul↗
NASA NTRS2012

Simulation and Flight Test Capability for Testing Prototype Sense and Avoid System Elements

NASA Langley Research Center (LaRC) and The MITRE Corporation (MITRE) have developed, and successfully demonstrated, an integrated simulation-to-flight capability for evaluating sense and avoid (SAA) system elements. This integrated capability consists of a MITRE developed fast-time computer simulation for evaluating SAA algorithms, and a NASA LaRC surrogate unmanned aircraft system (UAS) equipped to support hardware and software in-the-loop evaluation of SAA system elements (e.g., algorithms, sensors, architecture, communications, autonomous systems), concepts, and procedures. The fast-time computer simulation subjects algorithms to simulated flight encounters/ conditions and generates a fitness report that records strengths, weaknesses, and overall performance. Reviewed algorithms (and their fitness report) are then transferred to NASA LaRC where additional (joint) airworthiness evaluations are performed on the candidate SAA system-element configurations, concepts, and/or procedures of interest; software and hardware components are integrated into the Surrogate UAS research systems; and flight safety and mission planning activities are completed. Onboard the Surrogate UAS, candidate SAA system element configurations, concepts, and/or procedures are subjected to flight evaluations and in-flight performance is monitored. The Surrogate UAS, which can be controlled remotely via generic Ground Station uplink or automatically via onboard systems, operates with a NASA Safety Pilot/Pilot in Command onboard to permit safe operations in mixed airspace with manned aircraft. An end-to-end demonstration of a typical application of the capability was performed in non-exclusionary airspace in October 2011; additional research, development, flight testing, and evaluation efforts using this integrated capability are planned throughout fiscal year 2012 and 2013.

Howell, Charles T.↗
NASA NTRS2012

Towards Validation of an Adaptive Flight Control Simulation Using Statistical Emulation

Traditional validation of flight control systems is based primarily upon empirical testing. Empirical testing is sufficient for simple systems in which a.) the behavior is approximately linear and b.) humans are in-the-loop and responsible for off-nominal flight regimes. A different possible concept of operation is to use adaptive flight control systems with online learning neural networks (OLNNs) in combination with a human pilot for off-nominal flight behavior (such as when a plane has been damaged). Validating these systems is difficult because the controller is changing during the flight in a nonlinear way, and because the pilot and the control system have the potential to co-adapt in adverse ways traditional empirical methods are unlikely to provide any guarantees in this case. Additionally, the time it takes to find unsafe regions within the flight envelope using empirical testing means that the time between adaptive controller design iterations is large. This paper describes a new concept for validating adaptive control systems using methods based on Bayesian statistics. This validation framework allows the analyst to build nonlinear models with modal behavior, and to have an uncertainty estimate for the difference between the behaviors of the model and system under test.

He, Yuning↗
NASA NTRS2012

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

The NASA Orion Flight Test Office was tasked with conducting a series of flight tests in several launch abort scenarios to certify that the Orion Launch Abort System is capable of delivering astronauts aboard the Orion Crew Module to a safe environment, away from a failed booster. The first of this series was the Orion Pad Abort 1 Flight-Test Vehicle, which was successfully flown on May 6, 2010 at the White Sands Missile Range in New Mexico. This paper provides a brief overview of the three propulsive subsystems used on the Pad Abort 1 Flight-Test Vehicle. An overview of the propulsive systems originally planned for future flight-test vehicles is also provided, which also includes the cold gas Reaction Control System within the Crew Module, and the Peacekeeper first stage rocket motor encased within the Abort Test Booster aeroshell. Although the Constellation program has been cancelled and the operational role of the Orion spacecraft has significantly evolved, lessons learned from Pad Abort 1 and the other flight-test vehicles could certainly contribute to the vehicle architecture of many future human-rated space launch vehicles.

Jones, Daniel S.↗