The development of a Flight Test Engineer's Workstation for the Automated Flight Test Management System

NASA Technical Reports Server (NTRS)

Tartt, David M.; Hewett, Marle D.; Duke, Eugene L.; Cooper, James A.; Brumbaugh, Randal W.

1989-01-01

The Automated Flight Test Management System (ATMS) is being developed as part of the NASA Aircraft Automation Program. This program focuses on the application of interdisciplinary state-of-the-art technology in artificial intelligence, control theory, and systems methodology to problems of operating and flight testing high-performance aircraft. The development of a Flight Test Engineer's Workstation (FTEWS) is presented, with a detailed description of the system, technical details, and future planned developments. The goal of the FTEWS is to provide flight test engineers and project officers with an automated computer environment for planning, scheduling, and performing flight test programs. The FTEWS system is an outgrowth of the development of ATMS and is an implementation of a component of ATMS on SUN workstations.

F-111E IPCS in flight

NASA Technical Reports Server (NTRS)

1975-01-01

This NASA Dryden Flight Research Center photograph taken in 1975 shows the General Dynamic IPCS/F-111E Aardvark with a camouflage paint pattern. This prototype F-111E was used during the flight testing of the Integrated Propulsion Control System (IPCS). The wings of the IPCS/F-111E are swept back to near 60 degrees for supersonic flight. During the same period as F-111 TACT program, an F-111E Aardvark (#67-0115) was flown at the NASA Flight Research Center to investigate an electronic versus a conventional hydro-mechanical controlled engine. The program called integrated propulsion control system (IPCS) was a joint effort by NASA's Lewis Research Center and Flight Research Center, the Air Force's Flight Propulsion Laboratory and the Boeing, Honeywell and Pratt & Whitney companies. The left engine of the F-111E was selected for modification to an all electronic system. A Pratt & Whitney TF30-P-9 engine was modified and extensively laboratory, and ground-tested before installation into the F-111E. There were 14 IPCS flights made from 1975 through 1976. The flight demonstration program proved an engine could be controlled electronically, leading to a more efficient Digital Electronic Engine Control System flown in the F-15.

Performance seeking control program overview

NASA Technical Reports Server (NTRS)

Orme, John S.

1995-01-01

The Performance Seeking Control (PSC) program evolved from a series of integrated propulsion-flight control research programs flown at NASA Dryden Flight Research Center (DFRC) on an F-15. The first of these was the Digital Electronic Engine Control (DEEC) program and provided digital engine controls suitable for integration. The DEEC and digital electronic flight control system of the NASA F-15 were ideally suited for integrated controls research. The Advanced Engine Control System (ADECS) program proved that integrated engine and aircraft control could improve overall system performance. The objective of the PSC program was to advance the technology for a fully integrated propulsion flight control system. Whereas ADECS provided single variable control for an average engine, PSC controlled multiple propulsion system variables while adapting to the measured engine performance. PSC was developed as a model-based, adaptive control algorithm and included four optimization modes: minimum fuel flow at constant thrust, minimum turbine temperature at constant thrust, maximum thrust, and minimum thrust. Subsonic and supersonic flight testing were conducted at NASA Dryden covering the four PSC optimization modes and over the full throttle range. Flight testing of the PSC algorithm, conducted in a series of five flight test phases, has been concluded at NASA Dryden covering all four of the PSC optimization modes. Over a three year period and five flight test phases 72 research flights were conducted. The primary objective of flight testing was to exercise each PSC optimization mode and quantify the resulting performance improvements.

Preliminary flight test results of a fly-by-throttle emergency flight control system on an F-15 airplane

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Maine, Trindel A.; Fullerton, C. G.; Wells, Edward A.

1993-01-01

A multi-engine aircraft, with some or all of the flight control system inoperative, may use engine thrust for control. NASA Dryden has conducted a study of the capability and techniques for this emergency flight control method for the F-15 airplane. With an augmented control system, engine thrust, along with appropriate feedback parameters, is used to control flightpath and bank angle. Extensive simulation studies have been followed by flight tests. This paper discusses the principles of throttles-only control, the F-15 airplane, the augmented system, and the flight results including landing approaches with throttles-only control to within 10 ft of the ground.

Aircraft Flight Modeling During the Optimization of Gas Turbine Engine Working Process

NASA Astrophysics Data System (ADS)

Tkachenko, A. Yu; Kuz'michev, V. S.; Krupenich, I. N.

2018-01-01

The article describes a method for simulating the flight of the aircraft along a predetermined path, establishing a functional connection between the parameters of the working process of gas turbine engine and the efficiency criteria of the aircraft. This connection is necessary for solving the optimization tasks of the conceptual design stage of the engine according to the systems approach. Engine thrust level, in turn, influences the operation of aircraft, thus making accurate simulation of the aircraft behavior during flight necessary for obtaining the correct solution. The described mathematical model of aircraft flight provides the functional connection between the airframe characteristics, working process of gas turbine engines (propulsion system), ambient and flight conditions and flight profile features. This model provides accurate results of flight simulation and the resulting aircraft efficiency criteria, required for optimization of working process and control function of a gas turbine engine.

NASA Tests 2nd RS-25 Flight Engine for Space Launch System

NASA Image and Video Library

2018-01-16

On Jan. 16, 2018, engineers at NASA’s Stennis Space Center in Mississippi conducted a certification test of another RS-25 engine flight controller on the A-1 Test Stand at Stennis Space Center. The 365-second, full-duration test came a month after the space agency capped a year of RS-25 testing with a flight controller test in mid-December. For the “green run” test the flight controller was installed on RS-25 developmental engine E0528 and fired just as during an actual launch. Once certified, the flight controller will be removed and installed on a flight engine for use by NASA’s new deep-space rocket, the Space Launch System (SLS).

Simulator Evaluation of Simplified Propulsion-Only Emergency Flight Control Systems on Transport Aircraft

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Kaneshige, John; Bull, John; Maine, Trindel A.

1999-01-01

With the advent of digital engine control systems, considering the use of engine thrust for emergency flight control has become feasible. Many incidents have occurred in which engine thrust supplemented or replaced normal aircraft flight controls. In most of these cases, a crash has resulted, and more than 1100 lives have been lost. The NASA Dryden Flight Research Center has developed a propulsion-controlled aircraft (PCA) system in which computer-controlled engine thrust provides emergency flight control capability. Using this PCA system, an F-15 and an MD-11 airplane have been landed without using any flight controls. In simulations, C-17, B-757, and B-747 PCA systems have also been evaluated successfully. These tests used full-authority digital electronic control systems on the engines. Developing simpler PCA systems that can operate without full-authority engine control, thus allowing PCA technology to be installed on less capable airplanes or at lower cost, is also a desire. Studies have examined simplified ?PCA Ultralite? concepts in which thrust control is provided using an autothrottle system supplemented by manual differential throttle control. Some of these concepts have worked well. The PCA Ultralite study results are presented for simulation tests of MD-11, B-757, C-17, and B-747 aircraft.

Next-Generation RS-25 Engines for the NASA Space Launch System

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2017-01-01

The utilization of heritage RS-25 engines, also known as the Space Shuttle Main Engine (SSME), has enabled rapid progress in the development and certification of the NASA Space Launch System (SLS) toward operational flight status. The RS-25 brings design maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over 1 million seconds total accumulated hot-fire time. In addition, there were also 16 flight engines and 2 development engines remaining from the Space Shuttle program that could be leveraged to support the first four flights. Beyond these initial SLS flights, NASA must have a renewed supply of RS-25 engines that must reflect program affordability imperatives as well as technical requirements imposed by the SLS Block-1B vehicle (i.e., 111% RPL power level, reduced service life). Recognizing the long lead times needed for the fabrication, assembly and acceptance testing of flight engines, design activities are underway to improve system affordability and eliminate obsolescence concerns. These key objectives are enabled largely by utilizing modern materials and fabrication technologies, but also by innovations in systems engineering and integration (SE&I) practices.

Career Profile: Flight Operations Engineer (Airborne Science) Robert Rivera

NASA Image and Video Library

2015-05-14

Operations engineers at NASA's Armstrong Flight Research Center help to advance science, technology, aeronautics, and space exploration by managing operational aspects of a flight research project. They serve as the governing authority on airworthiness related to the modification, operation, or maintenance of specialized research or support aircraft so those aircraft can be flown safely without jeopardizing the pilots, persons on the ground or the flight test project. With extensive aircraft modifications often required to support new research and technology development efforts, operations engineers are key leaders from technical concept to flight to ensure flight safety and mission success. Other responsibilities of an operations engineer include configuration management, performing systems design and integration, system safety analysis, coordinating flight readiness activities, and providing real-time flight support. This video highlights the responsibilities and daily activities of NASA Armstrong operations engineer Robert Rivera during the preparation and execution of the Global Hawk airborne missions under NASA's Science Mission Directorate.

Spacecraft Design Thermal Control Subsystem

NASA Technical Reports Server (NTRS)

Miyake, Robert N.

2008-01-01

The Thermal Control Subsystem engineers task is to maintain the temperature of all spacecraft components, subsystems, and the total flight system within specified limits for all flight modes from launch to end-of-mission. In some cases, specific stability and gradient temperature limits will be imposed on flight system elements. The Thermal Control Subsystem of "normal" flight systems, the mass, power, control, and sensing systems mass and power requirements are below 10% of the total flight system resources. In general the thermal control subsystem engineer is involved in all other flight subsystem designs.

Flight evaluation of an extended engine life mode on an F-15 airplane

NASA Technical Reports Server (NTRS)

Myers, Lawrence P.; Conners, Timothy R.

1992-01-01

An integrated flight and propulsion control system designed to reduce the rate of engine deterioration was developed and evaluated in flight on the NASA Dryden F-15 research aircraft. The extended engine life mode increases engine pressure ratio while reducing engine airflow to lower the turbine temperature at constant thrust. The engine pressure ratio uptrim is modulated in real time based on airplane maneuver requirements, flight conditions, and engine information. The extended engine life mode logic performed well, significantly reducing turbine operating temperature. Reductions in fan turbine inlet temperature of up to 80 F were obtained at intermediate power and up to 170 F at maximum augmented power with no appreciable loss in thrust. A secondary benefit was the considerable reduction in thrust-specific fuel consumption. The success of the extended engine life mode is one example of the advantages gained from integrating aircraft flight and propulsion control systems.

Flight evaluation results for a digital electronic engine control in an F-15 airplane

NASA Technical Reports Server (NTRS)

Burcham, F. W., Jr.; Myers, L. P.; Walsh, K. R.

1983-01-01

A digital electronic engine control (DEEC) system on an F100 engine in an F-15 airplane was evaluated in flight. Thirty flights were flown in a four-phase program from June 1981 to February 1983. Significant improvements in the operability and performance of the F100 engine were developed as a result of the flight evaluation: the augmentor envelope was increased by 15,000 ft, the airstart envelope was improved by 75 knots, and the need to periodically trim the engine was eliminated. The hydromechanical backup control performance was evaluated and was found to be satisfactory. Two system failures were encountered in the test program; both were detected and accommodated successfully. No transfers to the backup control system were required, and no automatic transfers occurred. As a result of the successful DEEC flight evaluation, the DEEC system has entered the full-scale development phase.

Flight Avionics Sequencing Telemetry (FAST) DIV Latching Display

NASA Technical Reports Server (NTRS)

Moore, Charlotte

2010-01-01

The NASA Engineering (NE) Directorate at Kennedy Space Center provides engineering services to major programs such as: Space Shuttle, Inter national Space Station, and the Launch Services Program (LSP). The Av ionics Division within NE, provides avionics and flight control syste ms engineering support to LSP. The Launch Services Program is respons ible for procuring safe and reliable services for transporting critical, one of a kind, NASA payloads into orbit. As a result, engineers mu st monitor critical flight events during countdown and launch to asse ss anomalous behavior or any unexpected occurrence. The goal of this project is to take a tailored Systems Engineering approach to design, develop, and test Iris telemetry displays. The Flight Avionics Sequen cing Telemetry Delta-IV (FAST-D4) displays will provide NASA with an improved flight event monitoring tool to evaluate launch vehicle heal th and performance during system-level ground testing and flight. Flight events monitored will include data from the Redundant Inertial Fli ght Control Assembly (RIFCA) flight computer and launch vehicle comma nd feedback data. When a flight event occurs, the flight event is ill uminated on the display. This will enable NASA Engineers to monitor c ritical flight events on the day of launch. Completion of this project requires rudimentary knowledge of launch vehicle Guidance, Navigatio n, and Control (GN&C) systems, telemetry, and console operation. Work locations for the project include the engineering office, NASA telem etry laboratory, and Delta launch sites.

Career Profile: Flight Operations Engineer (Airborne Science) Matthew Berry

NASA Image and Video Library

2014-11-05

Operations engineers at NASA's Armstrong Flight Research Center help to advance science, technology, aeronautics, and space exploration by managing operational aspects of a flight research project. They serve as the governing authority on airworthiness related to the modification, operation, or maintenance of specialized research or support aircraft so those aircraft can be flown safely without jeopardizing the pilots, persons on the ground or the flight test project. With extensive aircraft modifications often required to support new research and technology development efforts, operations engineers are key leaders from technical concept to flight to ensure flight safety and mission success. Other responsibilities of an operations engineer include configuration management, performing systems design and integration, system safety analysis, coordinating flight readiness activities, and providing real-time flight support. This video highlights the responsibilities and daily activities of NASA Armstrong operations engineer Matthew Berry during the preparation and execution of flight tests in support of aeronautics research. http://www.nasa.gov/centers/armstrong/home/ http://www.nasa.gov/

Career Profile: Flight Operations Engineer (Aeronautics) Brian Griffin

NASA Image and Video Library

2014-10-17

Operations engineers at NASA's Armstrong Flight Research Center help to advance science, technology, aeronautics, and space exploration by managing operational aspects of a flight research project. They serve as the governing authority on airworthiness related to the modification, operation, or maintenance of specialized research or support aircraft so those aircraft can be flown safely without jeopardizing the pilots, persons on the ground or the flight test project. With extensive aircraft modifications often required to support new research and technology development efforts, operations engineers are key leaders from technical concept to flight to ensure flight safety and mission success. Other responsibilities of an operations engineer include configuration management, performing systems design and integration, system safety analysis, coordinating flight readiness activities, and providing real-time flight support. This video highlights the responsibilities and daily activities of NASA Armstrong operations engineer Brian Griffin during the preparation and execution of flight tests in support of aeronautics research. http://www.nasa.gov/centers/armstrong/home/ http://www.nasa.gov/

Digital electronic engine control F-15 overview

NASA Technical Reports Server (NTRS)

Kock, B.

1984-01-01

A flight test evaluation of the digital elctronic engine control (DEEC) system was conducted. An overview of the flight program is presented. The roles of the participating parties, the system, and the flight program objectives are described. The test program approach is discussed, and the engine performance benefits are summarized. A description of the follow-on programs is included.

Digital electronic engine control fault detection and accommodation flight evaluation

NASA Technical Reports Server (NTRS)

Baer-Ruedhart, J. L.

1984-01-01

The capabilities and performance of various fault detection and accommodation (FDA) schemes in existing and projected engine control systems were investigated. Flight tests of the digital electronic engine control (DEEC) in an F-15 aircraft show discrepancies between flight results and predictions based on simulation and altitude testing. The FDA methodology and logic in the DEEC system, and the results of the flight failures which occurred to date are described.

Video File - NASA on a Roll Testing Space Launch System Flight Engines

NASA Image and Video Library

2017-08-09

Just two weeks after conducting another in a series of tests on new RS-25 rocket engine flight controllers for NASA’s Space Launch System (SLS) rocket, engineers at NASA’s Stennis Space Center in Mississippi completed one more hot-fire test of a flight controller on August 9, 2017. With the hot fire, NASA has moved a step closer in completing testing on the four RS-25 engines which will power the first integrated flight of the SLS rocket and Orion capsule known as Exploration Mission 1.

Evolution of the Systems Engineering Education Development (SEED) Program at NASA Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Bagg, Thomas C., III; Brumfield, Mark D.; Jamison, Donald E.; Granata, Raymond L.; Casey, Carolyn A.; Heller, Stuart

2003-01-01

The Systems Engineering Education Development (SEED) Program at NASA Goddard Space Flight Center develops systems engineers from existing discipline engineers. The program has evolved significantly since the report to INCOSE in 2003. This paper describes the SEED Program as it is now, outlines the changes over the last year, discusses current status and results, and shows the value of human systems and leadership skills for practicing systems engineers.

Integrated Flight-propulsion Control Concepts for Supersonic Transport Airplanes

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Gilyard, Glenn B.; Gelhausen, Paul A.

1990-01-01

Integration of propulsion and flight control systems will provide significant performance improvements for supersonic transport airplanes. Increased engine thrust and reduced fuel consumption can be obtained by controlling engine stall margin as a function of flight and engine operating conditions. Improved inlet pressure recovery and decreased inlet drag can result from inlet control system integration. Using propulsion system forces and moments to augment the flight control system and airplane stability can reduce the flight control surface and tail size, weight, and drag. Special control modes may also be desirable for minimizing community noise and for emergency procedures. The overall impact of integrated controls on the takeoff gross weight for a generic high speed civil transport is presented.

SSME component assembly and life management expert system

NASA Technical Reports Server (NTRS)

Ali, M.; Dietz, W. E.; Ferber, H. J.

1989-01-01

The space shuttle utilizes several rocket engine systems, all of which must function with a high degree of reliability for successful mission completion. The space shuttle main engine (SSME) is by far the most complex of the rocket engine systems and is designed to be reusable. The reusability of spacecraft systems introduces many problems related to testing, reliability, and logistics. Components must be assembled from parts inventories in a manner which will most effectively utilize the available parts. Assembly must be scheduled to efficiently utilize available assembly benches while still maintaining flight schedules. Assembled components must be assigned to as many contiguous flights as possible, to minimize component changes. Each component must undergo a rigorous testing program prior to flight. In addition, testing and assembly of flight engines and components must be done in conjunction with the assembly and testing of developmental engines and components. The development, testing, manufacture, and flight assignments of the engine fleet involves the satisfaction of many logistical and operational requirements, subject to many constraints. The purpose of the SSME Component Assembly and Life Management Expert System (CALMES) is to assist the engine assembly and scheduling process, and to insure that these activities utilize available resources as efficiently as possible.

Design and utilization of a Flight Test Engineering Database Management System at the NASA Dryden Flight Research Facility

NASA Technical Reports Server (NTRS)

Knighton, Donna L.

1992-01-01

A Flight Test Engineering Database Management System (FTE DBMS) was designed and implemented at the NASA Dryden Flight Research Facility. The X-29 Forward Swept Wing Advanced Technology Demonstrator flight research program was chosen for the initial system development and implementation. The FTE DBMS greatly assisted in planning and 'mass production' card preparation for an accelerated X-29 research program. Improved Test Plan tracking and maneuver management for a high flight-rate program were proven, and flight rates of up to three flights per day, two times per week were maintained.

Final RS-25 Engine Test of the Summer

NASA Image and Video Library

2017-08-30

On Aug. 30, engineers at our Stennis Space Center wrapped up a summer of hot fire testing for flight controllers on RS-25 engines that will help power the new Space Launch System rocket being built to carry astronauts to deep-space destinations, including Mars. The 500-second hot fire of a flight controller or “brain” of the engine marked another step toward the nation’s return to human deep-space exploration missions. Four RS-25 engines, equipped with flight-worthy controllers will help power the first integrated flight of our Space Launch System rocket with our Orion spacecraft, known as Exploration Mission One.

Design Challenges Encountered in a Propulsion-Controlled Aircraft Flight Test Program

NASA Technical Reports Server (NTRS)

Maine, Trindel; Burken, John; Burcham, Frank; Schaefer, Peter

1994-01-01

The NASA Dryden Flight Research Center conducted flight tests of a propulsion-controlled aircraft system on an F-15 airplane. This system was designed to explore the feasibility of providing safe emergency landing capability using only the engines to provide flight control in the event of a catastrophic loss of conventional flight controls. Control laws were designed to control the flightpath and bank angle using only commands to the throttles. Although the program was highly successful, this paper highlights some of the challenges associated with using engine thrust as a control effector. These challenges include slow engine response time, poorly modeled nonlinear engine dynamics, unmodeled inlet-airframe interactions, and difficulties with ground effect and gust rejection. Flight and simulation data illustrate these difficulties.

Design of an expert-system flight status monitor

NASA Technical Reports Server (NTRS)

Regenie, V. A.; Duke, E. L.

1985-01-01

The modern advanced avionics in new high-performance aircraft strains the capability of current technology to safely monitor these systems for flight test prior to their generalized use. New techniques are needed to improve the ability of systems engineers to understand and analyze complex systems in the limited time available during crucial periods of the flight test. The Dryden Flight Research Facility of NASA's Ames Research Center is involved in the design and implementation of an expert system to provide expertise and knowledge to aid the flight systems engineer. The need for new techniques in monitoring flight systems and the conceptual design of an expert-system flight status monitor is discussed. The status of the current project and its goals are described.

Development and Flight Test of an Emergency Flight Control System Using Only Engine Thrust on an MD-11 Transport Airplane

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Burken, John J.; Maine, Trindel A.; Fullerton, C. Gordon

1997-01-01

An emergency flight control system that uses only engine thrust, called the propulsion-controlled aircraft (PCA) system, was developed and flight tested on an MD-11 airplane. The PCA system is a thrust-only control system, which augments pilot flightpath and track commands with aircraft feedback parameters to control engine thrust. The PCA system was implemented on the MD-11 airplane using only software modifications to existing computers. Results of a 25-hr flight test show that the PCA system can be used to fly to an airport and safely land a transport airplane with an inoperative flight control system. In up-and-away operation, the PCA system served as an acceptable autopilot capable of extended flight over a range of speeds, altitudes, and configurations. PCA approaches, go-arounds, and three landings without the use of any normal flight controls were demonstrated, including ILS-coupled hands-off landings. PCA operation was used to recover from an upset condition. The PCA system was also tested at altitude with all three hydraulic systems turned off. This paper reviews the principles of throttles-only flight control, a history of accidents or incidents in which some or all flight controls were lost, the MD-11 airplane and its systems, PCA system development, operation, flight testing, and pilot comments.

Engines-only flight control system

NASA Technical Reports Server (NTRS)

Burcham, Frank W. (Inventor); Gilyard, Glenn B (Inventor); Conley, Joseph L. (Inventor); Stewart, James F. (Inventor); Fullerton, Charles G. (Inventor)

1994-01-01

A backup flight control system for controlling the flightpath of a multi-engine airplane using the main drive engines is introduced. The backup flight control system comprises an input device for generating a control command indicative of a desired flightpath, a feedback sensor for generating a feedback signal indicative of at least one of pitch rate, pitch attitude, roll rate and roll attitude, and a control device for changing the output power of at least one of the main drive engines on each side of the airplane in response to the control command and the feedback signal.

Program Aids Design Of Fluid-Circulating Systems

NASA Technical Reports Server (NTRS)

Bacskay, Allen; Dalee, Robert

1992-01-01

Computer Aided Systems Engineering and Analysis (CASE/A) program is interactive software tool for trade study and analysis, designed to increase productivity during all phases of systems engineering. Graphics-based command-driven software package provides user-friendly computing environment in which engineer analyzes performance and interface characteristics of ECLS/ATC system. Useful during all phases of spacecraft-design program, from initial conceptual design trade studies to actual flight, including pre-flight prediction and in-flight analysis of anomalies. Written in FORTRAN 77.

Performance improvements of an F-15 airplane with an integrated engine-flight control system

NASA Technical Reports Server (NTRS)

Myers, Lawrence P.; Walsh, Kevin R.

1988-01-01

An integrated flight and propulsion control system has been developed and flight demonstrated on the NASA Ames-Dryden F-15 research aircraft. The highly integrated digital control (HIDEC) system provides additional engine thrust by increasing engine pressure ratio (EPR) at intermediate and afterburning power. The amount of EPR uptrim is modulated based on airplane maneuver requirements, flight conditions, and engine information. Engine thrust was increased as much as 10.5 percent at subsonic flight conditions by uptrimming EPR. The additional thrust significantly improved aircraft performance. Rate of climb was increased 14 percent at 40,000 ft and the time to climb from 10,000 to 40,000 ft was reduced 13 percent. A 14 and 24 percent increase in acceleration was obtained at intermediate and maximum power, respectively. The HIDEC logic performed fault free. No engine anomalies were encountered for EPR increases up to 12 percent and for angles of attack and sideslip of 32 and 11 deg, respectively.

Performance improvements of an F-15 airplane with an integrated engine-flight control system

NASA Technical Reports Server (NTRS)

Myers, Lawrence P.; Walsh, Kevin R.

1988-01-01

An integrated flight and propulsion control system has been developed and flight demonstrated on the NASA Ames-Dryden F-15 research aircraft. The highly integrated digital control (HIDEC) system provides additional engine thrust by increasing engine pressure ratio (EPR) at intermediate and afterburning power. The amount of EPR uptrim is modulated based on airplane maneuver requirements, flight conditions, and engine information. Engine thrust was increased as much as 10.5 percent at subsonic flight conditions by uptrimming EPR. The additional thrust significantly improved aircraft performance. Rate of climb was increased 14 percent at 40,000 ft and the time to climb from 10,000 to 40,000 ft was reduced 13 percent. A 14 and 24 percent increase in acceleration was obtained at intermediate and maximum power, respectively. The HIDEC logic performed fault free. No engine anomalies were encountered for EPR increases up to 12 percent and for angles of attack and sideslip of 32 and 11 degrees, respectively.

Real-time in-flight engine performance and health monitoring techniques for flight research application

NASA Technical Reports Server (NTRS)

Ray, Ronald J.; Hicks, John W.; Wichman, Keith D.

1991-01-01

Procedures for real time evaluation of the inflight health and performance of gas turbine engines and related systems were developed to enhance flight test safety and productivity. These techniques include the monitoring of the engine, the engine control system, thrust vectoring control system health, and the detection of engine stalls. Real time performance techniques were developed for the determination and display of inflight thrust and for aeroperformance drag polars. These new methods were successfully shown on various research aircraft at NASA-Dryden. The capability of NASA's Western Aeronautical Test Range and the advanced data acquisition systems were key factors for implementation and real time display of these methods.

Next-Generation RS-25 Engines for the NASA Space Launch System

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2017-01-01

The utilization of heritage RS-25 engine, also known as the Space Shuttle Main Engine (SSME), has enabled rapid progress in the development and certification of the NASA Space Launch System (SLS) toward operational flight status. The RS-25 brings design maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over a million seconds total accumulated hot-fire time. In addition, there were also over a dozen functional flight assets remaining from the Space Shuttle program that could be leveraged to support the first four flights. Beyond these initial SLS flights, NASA must have a renewed supply of RS-25 engines that must reflect program affordability imperatives as well as technical requirements imposed by the SLS Block-1B vehicle (i.e., 111% RPL power level, reduced service life). Recognizing the long lead times needed for the fabrication, assembly and acceptance testing of flight engines, design activities are underway at NASA and the RS-25 engine provider, Aerojet Rocketdyne, to improve system affordability and eliminate obsolescence concerns. This paper describes how the achievement of these key objectives are enabled largely by utilizing modern materials and fabrication technologies, but also by innovations in systems engineering and integration (SE&I) practices.

A Synopsis of Ion Propulsion Development Projects in the United States: SERT 1 to Deep Space I

NASA Technical Reports Server (NTRS)

Sovey, James S.; Rawlin, Vincent K.; Patterson, Michael J.

1999-01-01

The historical background and characteristics of the experimental flights of ion propulsion systems and the major ground-based technology demonstrations were reviewed. The results of the first successful ion engine flight in 1964, SERT I which demonstrated ion beam neutralization, are discussed along with the extended operation of SERT II starting in 1970. These results together with the technology employed on the early cesium engine flights. the Applications Technology Satellite (ATS) series, and the ground-test demonstrations, have provided the evolutionary path for the development of xenon ion thruster component technologies, control systems, and power circuit implementations. In the 1997-1999 period, the communication satellite flights using ion engine systems and the Deep Space I flight confirmed that these auxiliary and primary propulsion systems have advanced to a high-level of flight-readiness.

Ion Propulsion Development Projects in US: Space Electric Rocket Test I to Deep Space 1

NASA Technical Reports Server (NTRS)

Sovey, James S.; Rawlin, Vincent K.; Patterson, Michael J.

2001-01-01

The historical background and characteristics of the experimental flights of ion propulsion systems and the major ground-based technology demonstrations are reviewed. The results of the first successful ion engine flight in 1964, Space Electric Rocket Test (SERT) I, which demonstrated ion beam neutralization, are discussed along with the extended operation of SERT II starting in 1970. These results together with the technologies employed on the early cesium engine flights, the applications technology satellite series, and the ground-test demonstrations, have provided the evolutionary path for the development of xenon ion thruster component technologies, control systems, and power circuit implementations. In the 1997-1999 period, the communication satellite flights using ion engine systems and the Deep Space 1 flight confirmed that these auxiliary and primary propulsion systems have advanced to a high level of flight readiness.

Hybrid Kalman Filter: A New Approach for Aircraft Engine In-Flight Diagnostics

NASA Technical Reports Server (NTRS)

Kobayashi, Takahisa; Simon, Donald L.

2006-01-01

In this paper, a uniquely structured Kalman filter is developed for its application to in-flight diagnostics of aircraft gas turbine engines. The Kalman filter is a hybrid of a nonlinear on-board engine model (OBEM) and piecewise linear models. The utilization of the nonlinear OBEM allows the reference health baseline of the in-flight diagnostic system to be updated to the degraded health condition of the engines through a relatively simple process. Through this health baseline update, the effectiveness of the in-flight diagnostic algorithm can be maintained as the health of the engine degrades over time. Another significant aspect of the hybrid Kalman filter methodology is its capability to take advantage of conventional linear and nonlinear Kalman filter approaches. Based on the hybrid Kalman filter, an in-flight fault detection system is developed, and its diagnostic capability is evaluated in a simulation environment. Through the evaluation, the suitability of the hybrid Kalman filter technique for aircraft engine in-flight diagnostics is demonstrated.

NASA Lewis F100 engine testing

NASA Technical Reports Server (NTRS)

Werner, R. A.; Willoh, R. G., Jr.; Abdelwahab, M.

1984-01-01

Two builds of an F100 engine model derivative (EMD) engine were evaluated for improvements in engine components and digital electronic engine control (DEEC) logic. Two DEEC flight logics were verified throughout the flight envelope in support of flight clearance for the F100 engine model derivative program (EMPD). A nozzle instability and a faster augmentor transient capability was investigated in support of the F-15 DEEC flight program. Off schedule coupled system mode fan flutter, DEEC nose-boom pressure correlation, DEEC station six pressure comparison, and a new fan inlet variable vane (CIVV) schedule are identified.

MD-11 PCA - Research flight team photo

NASA Technical Reports Server (NTRS)

1995-01-01

On Aug. 30, 1995, a the McDonnell Douglas MD-11 transport aircraft landed equipped with a computer-assisted engine control system that has the potential to increase flight safety. In landings at NASA Dryden Flight Research Center, Edwards, California, on August 29 and 30, the aircraft demonstrated software used in the aircraft's flight control computer that essentially landed the MD-11 without a need for the pilot to manipulate the flight controls significantly. In partnership with McDonnell Douglas Aerospace (MDA), with Pratt & Whitney and Honeywell helping to design the software, NASA developed this propulsion-controlled aircraft (PCA) system following a series of incidents in which hydraulic failures resulted in the loss of flight controls. This new system enables a pilot to operate and land the aircraft safely when its normal, hydraulically-activated control surfaces are disabled. This August 29, 1995, photo shows the MD-11 team. Back row, left to right: Tim Dingen, MDA pilot; John Miller, MD-11 Chief pilot (MDA); Wayne Anselmo, MD-11 Flight Test Engineer (MDA); Gordon Fullerton, PCA Project pilot; Bill Burcham, PCA Chief Engineer; Rudey Duran, PCA Controls Engineer (MDA); John Feather, PCA Controls Engineer (MDA); Daryl Townsend, Crew Chief; Henry Hernandez, aircraft mechanic; Bob Baron, PCA Project Manager; Don Hermann, aircraft mechanic; Jerry Cousins, aircraft mechanic; Eric Petersen, PCA Manager (Honeywell); Trindel Maine, PCA Data Engineer; Jeff Kahler, PCA Software Engineer (Honeywell); Steve Goldthorpe, PCA Controls Engineer (MDA). Front row, left to right: Teresa Hass, Senior Project Management Analyst; Hollie Allingham (Aguilera), Senior Project Management Analyst; Taher Zeglum, PCA Data Engineer (MDA); Drew Pappas, PCA Project Manager (MDA); John Burken, PCA Control Engineer.

Knowledge-Acquisition Tool For Expert System

NASA Technical Reports Server (NTRS)

Disbrow, James D.; Duke, Eugene L.; Regenie, Victoria A.

1988-01-01

Digital flight-control systems monitored by computer program that evaluates and recommends. Flight-systems engineers for advanced, high-performance aircraft use knowlege-acquisition tool for expert-system flight-status monitor suppling interpretative data. Interpretative function especially important in time-critical, high-stress situations because it facilitates problem identification and corrective strategy. Conditions evaluated and recommendations made by ground-based engineers having essential knowledge for analysis and monitoring of performances of advanced aircraft systems.

Energy Efficient Engine Flight Propulsion System Preliminary Analysis and Design Report

NASA Technical Reports Server (NTRS)

Bisset, J. W.; Howe, D. C.

1983-01-01

The final design and analysis of the flight propulsion system is presented. This system is the conceptual study engine defined to meet the performance, economic and environmental goals established for the Energy Efficient Engine Program. The design effort included a final definition of the engine, major components, internal subsystems, and nacelle. Various analytical representations and results from component technology programs are used to verify aerodynamic and structural design concepts and to predict performance. Specific design goals and specifications, reflecting future commercial aircraft propulsion system requirements for the mid-1980's, are detailed by NASA and used as guidelines during engine definition. Information is also included which details salient results from a separate study to define a turbofan propulsion system, known as the maximum efficiency engine, which reoptimized the advanced fuel saving technologies for improved fuel economy and direct operating costs relative to the flight propulsion system.

High Stability Engine Control (HISTEC) Flight Test Results

NASA Technical Reports Server (NTRS)

Southwick, Robert D.; Gallops, George W.; Kerr, Laura J.; Kielb, Robert P.; Welsh, Mark G.; DeLaat, John C.; Orme, John S.

1998-01-01

The High Stability Engine Control (HISTEC) Program, managed and funded by the NASA Lewis Research Center, is a cooperative effort between NASA and Pratt & Whitney (P&W). The program objective is to develop and flight demonstrate an advanced high stability integrated engine control system that uses real-time, measurement-based estimation of inlet pressure distortion to enhance engine stability. Flight testing was performed using the NASA Advanced Controls Technologies for Integrated Vehicles (ACTIVE) F-15 aircraft at the NASA Dryden Flight Research Center. The flight test configuration, details of the research objectives, and the flight test matrix to achieve those objectives are presented. Flight test results are discussed that show the design approach can accurately estimate distortion and perform real-time control actions for engine accommodation.

HIDEC adaptive engine control system flight evaluation results

NASA Technical Reports Server (NTRS)

Yonke, W. A.; Landy, R. J.; Stewart, J. F.

1987-01-01

An integrated flight propulsion control mode, the Adaptive Engine Control System (ADECS), has been developed and flight tested on an F-15 aircraft as part of the NASA Highly Integrated Digital Electronic Control program. The ADECS system realizes additional engine thrust by increasing the engine pressure ratio (EPR) at intermediate and afterburning power, with the amount of EPR uptrim modulated using a predictor scheme for angle-of-attack and sideslip angle. Substantial improvement in aircraft and engine performance was demonstrated, with a 16 percent rate of climb increase, a 14 percent reduction in time to climb, and a 15 percent reduction in time to accelerate. Significant EPR uptrim capability was found with angles-of-attack up to 20 degrees.

Energy efficient engine flight propulsion system: Aircraft/engine integration evaluation

NASA Technical Reports Server (NTRS)

Patt, R. F.

1980-01-01

Results of aircraft/engine integration studies conducted on an advanced flight propulsion system are reported. Economic evaluations of the preliminary design are included and indicate that program goals will be met. Installed sfc, DOC, noise, and emissions were evaluated. Aircraft installation considerations and growth were reviewed.

Energy efficient engine flight propulsion system: Aircraft/engine integration evaluation

DOE Office of Scientific and Technical Information (OSTI.GOV)

Patt, R.F.

Results of aircraft/engine integration studies conducted on an advanced flight propulsion system are reported. Economic evaluations of the preliminary design are included and indicate that program goals will be met. Installed sfc, DOC, noise, and emissions were evaluated. Aircraft installation considerations and growth were reviewed.

Flight Test of a Propulsion-Based Emergency Control System on the MD-11 Airplane with Emphasis on the Lateral Axis

NASA Technical Reports Server (NTRS)

Burken, John J.; Burcham, Frank W., Jr.; Maine, Trindel A.; Feather, John; Goldthorpe, Steven; Kahler, Jeffrey A.

1996-01-01

A large, civilian, multi-engine transport MD-11 airplane control system was recently modified to perform as an emergency backup controller using engine thrust only. The emergency backup system, referred to as the propulsion-controlled aircraft (PCA) system, would be used if a major primary flight control system fails. To allow for longitudinal and lateral-directional control, the PCA system requires at least two engines and is implemented through software modifications. A flight-test program was conducted to evaluate the PCA system high-altitude flying characteristics and to demonstrate its capacity to perform safe landings. The cruise flight conditions, several low approaches and one landing without any aerodynamic flight control surface movement, were demonstrated. This paper presents results that show satisfactory performance of the PCA system in the longitudinal axis. Test results indicate that the lateral-directional axis of the system performed well at high attitude but was sluggish and prone to thermal upsets during landing approaches. Flight-test experiences and test techniques are also discussed with emphasis on the lateral-directional axis because of the difficulties encountered in flight test.

Propulsion system performance resulting from an integrated flight/propulsion control design

NASA Technical Reports Server (NTRS)

Mattern, Duane; Garg, Sanjay

1992-01-01

Propulsion-system-specific results are presented from the application of the integrated methodology for propulsion and airframe control (IMPAC) design approach to integrated flight/propulsion control design for a 'short takeoff and vertical landing' (STOVL) aircraft in transition flight. The IMPAC method is briefly discussed and the propulsion system specifications for the integrated control design are examined. The structure of a linear engine controller that results from partitioning a linear centralized controller is discussed. The details of a nonlinear propulsion control system are presented, including a scheme to protect the engine operational limits: the fan surge margin and the acceleration/deceleration schedule that limits the fuel flow. Also, a simple but effective multivariable integrator windup protection scheme is examined. Nonlinear closed-loop simulation results are presented for two typical pilot commands for transition flight: acceleration while maintaining flightpath angle and a change in flightpath angle while maintaining airspeed. The simulation nonlinearities include the airframe/engine coupling, the actuator and sensor dynamics and limits, the protection scheme for the engine operational limits, and the integrator windup protection. Satisfactory performance of the total airframe plus engine system for transition flight, as defined by the specifications, was maintained during the limit operation of the closed-loop engine subsystem.

Propulsion at the Marshall Space Flight Center - A brief history

NASA Technical Reports Server (NTRS)

Jones, L. W.; Fisher, M. F.; Mccool, A. A.; Mccarty, J. P.

1991-01-01

The history of propulsion development at the NASA Marshall Space Flight Center is summarized, beginning with the development of the propulsion system for the Redstone missile. This course of propulsion development continues through the Jupiter IRBM, the Saturn family of launch vehicles and the engines that powered them, the Centaur upper stage and RL-10 engine, the Reactor In-Flight Test stage and the NERVA nuclear engine. The Space Shuttle Main Engine and Solid Rocket Boosters are covered, as are spacecraft propulsion systems, including the reaction control systems for the High Energy Astronomy Observatory and the Space Station. The paper includes a description of several technology efforts such as those in high pressure turbomachinery, aerospike engines, and the AS203 cyrogenic fluid management flight experiment. These and other propulsion projects are documented, and the scope of activities in support of these efforts at Marshall delineated.

Fault detection and accommodation testing on an F100 engine in an F-15 airplane

NASA Technical Reports Server (NTRS)

Myers, L. P.; Baer-Riedhart, J. L.; Maxwell, M. D.

1985-01-01

The fault detection and accommodation (FDA) methodology for digital engine-control systems may range from simple comparisons of redundant parameters to the more complex and sophisticated observer models of the entire engine system. Evaluations of the various FDA schemes are done using analytical methods, simulation, and limited-altitude-facility testing. Flight testing of the FDA logic has been minimal because of the difficulty of inducing realistic faults in flight. A flight program was conducted to evaluate the fault detection and accommodation capability of a digital electronic engine control in an F-15 aircraft. The objective of the flight program was to induce selected faults and evaluate the resulting actions of the digital engine controller. Comparisons were made between the flight results and predictions. Several anomalies were found in flight and during the ground test. Simulation results showed that the inducement of dual pressure failures was not feasible since the FDA logic was not designed to accommodate these types of failures.

Propulsion system-flight control integration-flight evaluation and technology transition

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Gilyard, Glenn B.; Myers, Lawrence P.

1990-01-01

Integration of propulsion and flight control systems and their optimization offering significant performance improvement are assessed. In particular, research programs conducted by NASA on flight control systems and propulsion system-flight control interactions on the YF-12 and F-15 aircraft are addressed; these programs have demonstrated increased thrust, reduced fuel consumption, increased engine life, and improved aircraft performance. Focus is placed on altitude control, speed-Mach control, integrated controller design, as well as flight control systems and digital electronic engine control. A highly integrated digital electronic control program is analyzed and compared with a performance seeking control program. It is shown that the flight evaluation and demonstration of these technologies have been a key part in the transition of the concepts to production and operational use on a timely basis.

Hyper-X Flight Engine Ground Testing for X-43 Flight Risk Reduction

NASA Technical Reports Server (NTRS)

Huebner, Lawrence D.; Rock, Kenneth E.; Ruf, Edward G.; Witte, David W.; Andrews, Earl H., Jr.

2001-01-01

Airframe-integrated scramjet engine testing has been completed at Mach 7 flight conditions in the NASA Langley 8-Foot High Temperature Tunnel as part of the NASA Hyper-X program. This test provided engine performance and operability data, as well as design and database verification, for the Mach 7 flight tests of the Hyper-X research vehicle (X-43), which will provide the first-ever airframe-integrated scramjet data in flight. The Hyper-X Flight Engine, a duplicate Mach 7 X-43 scramjet engine, was mounted on an airframe structure that duplicated the entire three-dimensional propulsion flowpath from the vehicle leading edge to the vehicle trailing edge. This model was also tested to verify and validate the complete flight-like engine system. This paper describes the subsystems that were subjected to flight-like conditions and presents supporting data. The results from this test help to reduce risk for the Mach 7 flights of the X-43.

Man-vehicle systems research facility advanced aircraft flight simulator throttle mechanism

NASA Technical Reports Server (NTRS)

Kurasaki, S. S.; Vallotton, W. C.

1985-01-01

The Advanced Aircraft Flight Simulator is equipped with a motorized mechanism that simulates a two engine throttle control system that can be operated via a computer driven performance management system or manually by the pilots. The throttle control system incorporates features to simulate normal engine operations and thrust reverse and vary the force feel to meet a variety of research needs. While additional testing to integrate the work required is principally now in software design, since the mechanical aspects function correctly. The mechanism is an important part of the flight control system and provides the capability to conduct human factors research of flight crews with advanced aircraft systems under various flight conditions such as go arounds, coupled instrument flight rule approaches, normal and ground operations and emergencies that would or would not normally be experienced in actual flight.

A Study on Aircraft Engine Control Systems for Integrated Flight and Propulsion Control

NASA Astrophysics Data System (ADS)

Yamane, Hideaki; Matsunaga, Yasushi; Kusakawa, Takeshi

A flyable FADEC system engineering model incorporating Integrated Flight and Propulsion Control (IFPC) concept is developed for a highly maneuverable aircraft and a fighter-class engine. An overview of the FADEC system and functional assignments for its components such as the Engine Control Unit (ECU) and the Integrated Control Unit (ICU) are described. Overall system reliability analysis, convex analysis and multivariable controller design for the engine, fault detection/redundancy management, and response characteristics of a fuel system are addressed. The engine control performance of the FADEC is demonstrated by hardware-in-the-loop simulation for fast acceleration and thrust transient characteristics.

78 FR 14722 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-03-07

... capability on one engine, and in-flight shutdown of the engine. This action revises that NPRM by proposing to... maintenance planning data (MPD) document. We are proposing this supplemental NPRM to detect and correct... feed system, followed by loss of fuel system suction feed capability on one engine, and in-flight...

Propulsion control experience used in the Highly Integrated Digital Electronic Control (HIDEC) program

NASA Technical Reports Server (NTRS)

Myers, L. P.; Burcham, F. W., Jr.

1984-01-01

The highly integrated digital electronic control (HIDEC) program will integrate the propulsion and flight control systems on an F-15 airplane at NASA Ames Research Center's Dryden Flight Research Facility. Ames-Dryden has conducted several propulsion control programs that have contributed to the HIDEC program. The digital electronic engine control (DEEC) flight evaluation investigated the performance and operability of the F100 engine equipped with a full-authority digital electronic control system. Investigations of nozzle instability, fault detection and accommodation, and augmentor transient capability provided important information for the HIDEC program. The F100 engine model derivative (EMD) was also flown in the F-15 airplane, and airplane performance was significantly improved. A throttle response problem was found and solved with a software fix to the control logic. For the HIDEC program, the F100 EMD engines equipped with DEEC controls will be integrated with the digital flight control system. The control modes to be implemented are an integrated flightpath management mode and an integrated adaptive engine control system mode. The engine control experience that will be used in the HIDEC program is discussed.

The Curiosity Mars Rover's Fault Protection Engine

NASA Technical Reports Server (NTRS)

Benowitz, Ed

2014-01-01

The Curiosity Rover, currently operating on Mars, contains flight software onboard to autonomously handle aspects of system fault protection. Over 1000 monitors and 39 responses are present in the flight software. Orchestrating these behaviors is the flight software's fault protection engine. In this paper, we discuss the engine's design, responsibilities, and present some lessons learned for future missions.

F-15 HiDEC in flight over Mojave desert

NASA Technical Reports Server (NTRS)

1990-01-01

NASA's F-15 HIDEC (Highly Integrated Digital Electronic Control) research aircraft cruises over California's Mojave Desert at sunset on a flight out of the Dryden Flight Research Center, Edwards, California. The aircraft was used to carry out research on engine and flight control systems and most recently demonstrated the use of computer-assisted engine controls as a means of landing an aircraft safely with only engine power if its normal control surfaces such as elevators, rudders or ailerons are disabled. The aircraft also tested and evaluated a computerized self-repair flight control system for the Air Force that detects damaged or failed flight control surfaces, and then reconfigures undamaged flight surfaces so the mission can continue or the aircraft is landed safely. Nearly all research being carried out in the HIDEC program is applicable to future civilian and military aircraft.

Flight evaluation of modifications to a digital electronic engine control system in an F-15 airplane

NASA Technical Reports Server (NTRS)

Burcham, F. W., Jr.; Myers, L. P.; Zeller, J. R.

1983-01-01

The third phase of a flight evaluation of a digital electronic engine control system in an F-15 has recently been completed. It was found that digital electronic engine control software logic changes and augmentor hardware improvements resulted in significant improvements in engine operation. For intermediate to maximum power throttle transients, an increase in altitude capability of up to 8000 ft was found, and for idle to maximum transients, an increase of up to 4000 ft was found. A nozzle instability noted in earlier flight testing was investigated on a test engine at NASA Lewis Research Center, a digital electronic engine control software logic change was developed and evaluated, and no instability occurred in the Phase 3 flight evaluation. The backup control airstart modification was evaluated, and gave an improvement of airstart capability by reducing the minimum airspeed for successful airstarts by 50 to 75 knots.

An American knowledge base in England - Alternate implementations of an expert system flight status monitor

NASA Technical Reports Server (NTRS)

Butler, G. F.; Graves, A. T.; Disbrow, J. D.; Duke, E. L.

1989-01-01

A joint activity between the Dryden Flight Research Facility of the NASA Ames Research Center (Ames-Dryden) and the Royal Aerospace Establishment (RAE) on knowledge-based systems has been agreed. Under the agreement, a flight status monitor knowledge base developed at Ames-Dryden has been implemented using the real-time AI (artificial intelligence) toolkit MUSE, which was developed in the UK. Here, the background to the cooperation is described and the details of the flight status monitor and a prototype MUSE implementation are presented. It is noted that the capabilities of the expert-system flight status monitor to monitor data downlinked from the flight test aircraft and to generate information on the state and health of the system for the test engineers provides increased safety during flight testing of new systems. Furthermore, the expert-system flight status monitor provides the systems engineers with ready access to the large amount of information required to describe a complex aircraft system.

Flight testing the Digital Electronic Engine Control (DEEC) A unique management experience

NASA Technical Reports Server (NTRS)

Putnam, T. W.; Burcham, F. W., Jr.; Kock, B. M.

1983-01-01

The concept for the DEEC had its origin in the early 1970s. At that time it was recognized that the F100 engine performance, operability, reliability, and cost could be substantially improved by replacing the original mechanical/supervisory electronic control system with a full-authority digital control system. By 1978, the engine manufacturer had designed and initiated the procurement of flight-qualified control system hardware. As a precursor to an integrated controls program, a flight evaluation of the DEEC system on the F-15 aircraft was proposed. Questions regarding the management of the DEEC flight evaluation program are discussed along with the program elements, the technical results of the F-15 evaluation, and the impact of the flight evaluation on after-burning turbofan controls technology and its use in and application to military aircraft. The lessons learned through the conduct of the program are discussed.

Highly integrated digital engine control system on an F-15 airplane

NASA Technical Reports Server (NTRS)

Burcham, F. W., Jr.; Haering, E. A., Jr.

1984-01-01

The highly integrated digital electronic control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine-airframe control systems. This system is being used on the F-15 airplane at the Dryden Flight Research Facility of NASA Ames Research Center. An integrated flightpath management mode and an integrated adaptive engine stall margin mode are being implemented into the system. The adaptive stall margin mode is a highly integrated mode in which the airplane flight conditions, the resulting inlet distortion, and the engine stall margin are continuously computed; the excess stall margin is used to uptrim the engine for more thrust. The integrated flightpath management mode optimizes the flightpath and throttle setting to reach a desired flight condition. The increase in thrust and the improvement in airplane performance is discussed in this paper.

Integrated flight/propulsion control - Adaptive engine control system mode

NASA Technical Reports Server (NTRS)

Yonke, W. A.; Terrell, L. A.; Meyers, L. P.

1985-01-01

The adaptive engine control system mode (ADECS) which is developed and tested on an F-15 aircraft with PW1128 engines, using the NASA sponsored highly integrated digital electronic control program, is examined. The operation of the ADECS mode, as well as the basic control logic, the avionic architecture, and the airframe/engine interface are described. By increasing engine pressure ratio (EPR) additional thrust is obtained at intermediate power and above. To modulate the amount of EPR uptrim and to prevent engine stall, information from the flight control system is used. The performance benefits, anticipated from control integration are shown for a range of flight conditions and power settings. It is found that at higher altitudes, the ADECS mode can increase thrust as much as 12 percent, which is used for improved acceleration, improved turn rate, or sustained turn angle.

Flight-Tested Prototype of BEAM Software

NASA Technical Reports Server (NTRS)

Mackey, Ryan; Tikidjian, Raffi; James, Mark; Wang, David

2006-01-01

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.

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2014 CFR

2014-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2010 CFR

2010-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2013 CFR

2013-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

14 CFR Appendix K to Part 25 - Extended Operations (ETOPS)

Code of Federal Regulations, 2012 CFR

2012-01-01

... that is time-limited. K25.1.4Propulsion systems. (a) Fuel system design. Fuel necessary to complete an... does not apply to airplanes with a required flight engineer. (b) APU design. If an APU is needed to..., whichever is lower, and run for the remainder of any flight . (c) Engine oil tank design. The engine oil...

Observations, Ideas, and Opinions: Systems Engineering and Integration for Return to Flight

NASA Technical Reports Server (NTRS)

Gafka, George K.

2006-01-01

This presentation addresses project management and systems engineering and integration challenges for return to flight, focusing on the Thermal Protection System Tile Repair Project (TRP). The program documentation philosophy, communication with program requirements flow and philosophy and planned deliverables and documentation are outlined. The development of TRP 'use-as-is' analytical tools is also highlighted and emphasis is placed on the use flight history to assess pre-flight and real-time risk. Additionally, an overview is provided of the repair procedure, including an outline of the logistics deployment chart.

Rocket University at KSC

NASA Technical Reports Server (NTRS)

Sullivan, Steven J.

2014-01-01

"Rocket University" is an exciting new initiative at Kennedy Space Center led by NASA's Engineering and Technology Directorate. This hands-on experience has been established to develop, refine & maintain targeted flight engineering skills to enable the Agency and KSC strategic goals. Through "RocketU", KSC is developing a nimble, rapid flight engineering life cycle systems knowledge base. Ongoing activities in RocketU develop and test new technologies and potential customer systems through small scale vehicles, build and maintain flight experience through balloon and small-scale rocket missions, and enable a revolving fresh perspective of engineers with hands on expertise back into the large scale NASA programs, providing a more experienced multi-disciplined set of systems engineers. This overview will define the Program, highlight aspects of the training curriculum, and identify recent accomplishments and activities.

Effect of steady flight loads on JT9D-7 performance deterioration

NASA Technical Reports Server (NTRS)

Jay, A.; Todd, E. S.

1978-01-01

Short term engine deterioration occurs in less than 250 flights on a new engine and in the first flights following engine repair; while long term deterioration involves primarily hot section distress and compression system losses which occur at a somewhat slower rate. The causes for short-term deterioration are associated with clearance changes which occur in the flight environment. Analytical techniques utilized to examine the effects of flight loads and engine operating conditions on performance deterioration are presented. The role of gyroscopic, gravitational, and aerodynamic loads are discussed along with the effect of variations in engine build clearances. These analytical results are compared to engine test data along with the correlation between analytically predicted and measured clearances and rub patterns. Conclusions are drawn and important issues are discussed.

Piloted simulation study of the effects of an automated trim system on flight characteristics of a light twin-engine airplane with one engine inoperative

NASA Technical Reports Server (NTRS)

Stewart, E. C.; Brown, P. W.; Yenni, K. R.

1986-01-01

A simulation study was conducted to investigate the piloting problems associated with failure of an engine on a generic light twin-engine airplane. A primary piloting problem for a light twin-engine airplane after an engine failure is maintaining precise control of the airplane in the presence of large steady control forces. To address this problem, a simulated automatic trim system which drives the trim tabs as an open-loop function of propeller slipstream measurements was developed. The simulated automatic trim system was found to greatly increase the controllability in asymmetric powered flight without having to resort to complex control laws or an irreversible control system. However, the trim-tab control rates needed to produce the dramatic increase in controllability may require special design consideration for automatic trim system failures. Limited measurements obtained in full-scale flight tests confirmed the fundamental validity of the proposed control law.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

F-15 HiDEC taxi on ramp at sunrise

NASA Image and Video Library

1991-09-23

NASA's highly modified F-15A (Serial #71-0287) used for digital electronic flight and engine control systems research, at sunrise on the ramp at the Dryden Flight Research Facility, Edwards, California. The F-15 was called the HIDEC (Highly Integrated Digital Electronic Control) flight facility. Research programs flown on the testbed vehicle have demonstrated improved rates of climb, fuel savings, and engine thrust by optimizing systems performance. The aircraft also tested and evaluated a computerized self-repairing flight control system for the Air Force that detects damaged or failed flight control surfaces. The system then reconfigures undamaged control surfaces so the mission can continue or the aircraft is landed safely.

Integrated Main Propulsion System Performance Reconstruction Process/Models

NASA Technical Reports Server (NTRS)

Lopez, Eduardo; Elliott, Katie; Snell, Steven; Evans, Michael

2013-01-01

The Integrated Main Propulsion System (MPS) Performance Reconstruction process provides the MPS post-flight data files needed for postflight reporting to the project integration management and key customers to verify flight performance. This process/model was used as the baseline for the currently ongoing Space Launch System (SLS) work. The process utilizes several methodologies, including multiple software programs, to model integrated propulsion system performance through space shuttle ascent. It is used to evaluate integrated propulsion systems, including propellant tanks, feed systems, rocket engine, and pressurization systems performance throughout ascent based on flight pressure and temperature data. The latest revision incorporates new methods based on main engine power balance model updates to model higher mixture ratio operation at lower engine power levels.

B747/JT9D flight loads and their effect on engine running clearances and performance deterioration; BCAC NAIL/P and WA JT9D engine diagnostics programs

NASA Technical Reports Server (NTRS)

Olsson, W. J.; Martin, R. L.

1982-01-01

Flight loads on the 747 propulsion system and resulting JT9D blade to outer airseal running clearances during representative acceptance flight and revenue flight sequences were measured. The resulting rub induced clearance changes, and engine performance changes were then analyzed to validate and refine the JT9D-7A short term performance deterioration model.

R and T report: Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Soffen, Gerald A. (Editor)

1993-01-01

The 1993 Research and Technology Report for Goddard Space Flight Center is presented. Research covered areas such as (1) flight projects; (2) space sciences including cosmology, high energy, stars and galaxies, and the solar system; (3) earth sciences including process modeling, hydrology/cryology, atmospheres, biosphere, and solid earth; (4) networks, planning, and information systems including support for mission operations, data distribution, advanced software and systems engineering, and planning/scheduling; and (5) engineering and materials including spacecraft systems, material and testing, optics and photonics and robotics.

An overview of integrated flight-propulsion controls flight research on the NASA F-15 research airplane

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Gatlin, Donald H.; Stewart, James F.

1995-01-01

The NASA Dryden Flight Research Center has been conducting integrated flight-propulsion control flight research using the NASA F-15 airplane for the past 12 years. The research began with the digital electronic engine control (DEEC) project, followed by the F100 Engine Model Derivative (EMD). HIDEC (Highly Integrated Digital Electronic Control) became the umbrella name for a series of experiments including: the Advanced Digital Engine Controls System (ADECS), a twin jet acoustics flight experiment, self-repairing flight control system (SRFCS), performance-seeking control (PSC), and propulsion controlled aircraft (PCA). The upcoming F-15 project is ACTIVE (Advanced Control Technology for Integrated Vehicles). This paper provides a brief summary of these activities and provides background for the PCA and PSC papers, and includes a bibliography of all papers and reports from the NASA F-15 project.

Emergency Flight Control Using Only Engine Thrust and Lateral Center-of-Gravity Offset: A First Look

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Burken, John; Maine, Trindel A.; Bull, John

1997-01-01

Normally, the damage that results in a total loss of the primary flight controls of a jet transport airplane, including all engines on one side, would be catastrophic. In response, NASA Dryden has conceived an emergency flight control system that uses only the thrust of a wing-mounted engine along with a lateral center-of-gravity (CGY) offset from fuel transfer. Initial analysis and simulation studies indicate that such a system works, and recent high-fidelity simulation tests on the MD-11 and B-747 suggest that the system provides enough control for a survivable landing. This paper discusses principles of flight control using only a wing engine thrust and CGY offset, along with the amount of CGY offset capability of some transport airplanes. The paper also presents simulation results of the throttle-only control capability and closed-loop control of ground track using computer-controlled thrust.

Improving System Engineering Excellence at NASA's Marshall Space Flight Center

NASA Technical Reports Server (NTRS)

Takada, Pamela Wallace; Newton, Steve; Gholston, Sampson; Thomas, Dale (Technical Monitor)

2001-01-01

NASA's Marshall Space Flight Center (MSFC) management feels that sound system engineering practices are essential for successful project management, NASA studies have concluded that recent project failures could be attributed in part to inadequate systems engineering. A recent survey of MSFC project managers and system engineers' resulted in the recognition of a need for training in Systems Engineering Practices, particularly as they relate to MSFC projects. In response to this survey, an internal pilot short-course was developed to reinforce accepted practices for system engineering at MSFC. The desire of the MSFC management is to begin with in-house training and offer additional educational opportunities to reinforce sound system engineering principles to the more than 800 professionals who are involved with system engineering and project management. A Systems Engineering Development Plan (SEDP) has been developed to address the longer-term systems engineering development needs of MSFC. This paper describes the survey conducted and the training course that was developed in response to that survey.

An inventory of aeronautical ground research facilities. Volume 4: Engineering flight simulation facilities

NASA Technical Reports Server (NTRS)

Pirrello, C. J.; Hardin, R. D.; Capelluro, L. P.; Harrison, W. D.

1971-01-01

The general purpose capabilities of government and industry in the area of real time engineering flight simulation are discussed. The information covers computer equipment, visual systems, crew stations, and motion systems, along with brief statements of facility capabilities. Facility construction and typical operational costs are included where available. The facilities provide for economical and safe solutions to vehicle design, performance, control, and flying qualities problems of manned and unmanned flight systems.

Optimum Design of Hypersonic Airbreathing Propulsion

NASA Astrophysics Data System (ADS)

Kobayashi, Hiroaki; Sato, Tetsuya; Tanatsugu, Nobuhiro

The flight of Spaceplane is always under accelarating in the assent way and always under decelarating in the desent way and yet cruising in the return way. Besides, its flight envelope is considerably wider than that of airplane. Thus the integrated design method is required to build the best transportation system optimized taking into account the propulsion system and the airframe under the entire flight conditions. In this paper it is shown an optimization method on TSTO spaceplane system. Genetic algorithm (GA) was applied to optimize design parameters of engine, airframe, and trajectory simultaneously. Several types of engine were quantitatively compared using payload ratio as an evaluating function. It was concluded that precooled turbojets is the most promising engine for TSTO among Turbine Based Combined Cycle (TBCC) engines.

14 CFR 25.857 - Cargo compartment classification.

Code of Federal Regulations, 2012 CFR

2012-01-01

... detector or fire detector system to give warning at the pilot or flight engineer station. (c) Class C. A... compartment but in which— (1) There is a separate approved smoke detector or fire detector system to give... a separate approved smoke or fire detector system to give warning at the pilot or flight engineer...

14 CFR 25.857 - Cargo compartment classification.

Code of Federal Regulations, 2010 CFR

2010-01-01

... detector or fire detector system to give warning at the pilot or flight engineer station. (c) Class C. A... compartment but in which— (1) There is a separate approved smoke detector or fire detector system to give... a separate approved smoke or fire detector system to give warning at the pilot or flight engineer...

14 CFR 25.857 - Cargo compartment classification.

Code of Federal Regulations, 2013 CFR

2013-01-01

... detector or fire detector system to give warning at the pilot or flight engineer station. (c) Class C. A... compartment but in which— (1) There is a separate approved smoke detector or fire detector system to give... a separate approved smoke or fire detector system to give warning at the pilot or flight engineer...

14 CFR 25.857 - Cargo compartment classification.

Code of Federal Regulations, 2014 CFR

2014-01-01

... detector or fire detector system to give warning at the pilot or flight engineer station. (c) Class C. A... compartment but in which— (1) There is a separate approved smoke detector or fire detector system to give... a separate approved smoke or fire detector system to give warning at the pilot or flight engineer...

14 CFR 25.857 - Cargo compartment classification.

Code of Federal Regulations, 2011 CFR

2011-01-01

... detector or fire detector system to give warning at the pilot or flight engineer station. (c) Class C. A... compartment but in which— (1) There is a separate approved smoke detector or fire detector system to give... a separate approved smoke or fire detector system to give warning at the pilot or flight engineer...

Software Engineering for Human Spaceflight

NASA Technical Reports Server (NTRS)

Fredrickson, Steven E.

2014-01-01

The Spacecraft Software Engineering Branch of NASA Johnson Space Center (JSC) provides world-class products, leadership, and technical expertise in software engineering, processes, technology, and systems management for human spaceflight. The branch contributes to major NASA programs (e.g. ISS, MPCV/Orion) with in-house software development and prime contractor oversight, and maintains the JSC Engineering Directorate CMMI rating for flight software development. Software engineering teams work with hardware developers, mission planners, and system operators to integrate flight vehicles, habitats, robotics, and other spacecraft elements. They seek to infuse automation and autonomy into missions, and apply new technologies to flight processor and computational architectures. This presentation will provide an overview of key software-related projects, software methodologies and tools, and technology pursuits of interest to the JSC Spacecraft Software Engineering Branch.

Resilient Propulsion Control Research for the NASA Integrated Resilient Aircraft Control (IRAC) Project

NASA Technical Reports Server (NTRS)

Guo, Ten-Huei; Litt, Jonathan S.

2007-01-01

Gas turbine engines are designed to provide sufficient safety margins to guarantee robust operation with an exceptionally long life. However, engine performance requirements may be drastically altered during abnormal flight conditions or emergency maneuvers. In some situations, the conservative design of the engine control system may not be in the best interest of overall aircraft safety; it may be advantageous to "sacrifice" the engine to "save" the aircraft. Motivated by this opportunity, the NASA Aviation Safety Program is conducting resilient propulsion research aimed at developing adaptive engine control methodologies to operate the engine beyond the normal domain for emergency operations to maximize the possibility of safely landing the damaged aircraft. Previous research studies and field incident reports show that the propulsion system can be an effective tool to help control and eventually land a damaged aircraft. Building upon the flight-proven Propulsion Controlled Aircraft (PCA) experience, this area of research will focus on how engine control systems can improve aircraft safe-landing probabilities under adverse conditions. This paper describes the proposed research topics in Engine System Requirements, Engine Modeling and Simulation, Engine Enhancement Research, Operational Risk Analysis and Modeling, and Integrated Flight and Propulsion Controller Designs that support the overall goal.

Developmental Flight Instrumentation System for the Crew Launch Vehicle

NASA Technical Reports Server (NTRS)

Crawford, Kevin; Thomas, John

2006-01-01

The National Aeronautics and Space Administration is developing a new launch vehicle to replace the Space Shuttle. The Crew Launch Vehicle (CLV) will be a combination of new design hardware and heritage Apollo and Space Shuttle hardware. The current CLV configuration is a 5 segment solid rocket booster first stage and a new upper stage design with a modified Apollo era J-2 engine. The current schedule has two test flights with a first stage and a structurally identical, but without engine, upper stage. Then there will be two more test flights with a full complement of flight hardware. After the completion of the test flights, the first manned flight to the International Space Station is scheduled for late 2012. To verify the CLV's design margins a developmental flight instrumentation (DFI) system is needed. The DFI system will collect environmental and health data from the various CLV subsystem's and either transmit it to the ground or store it onboard for later evaluation on the ground. The CLV consists of 4 major elements: the first stage, the upper stage, the upper stage engine and the integration of the first stage, upper stage and upper stage engine. It is anticipated that each of CLVs elements will have some version of DFI. This paper will discuss a conceptual DFI design for each element and also of an integrated CLV DFI system.

Knowledge-based decision support for Space Station assembly sequence planning

NASA Astrophysics Data System (ADS)

1991-04-01

A complete Personal Analysis Assistant (PAA) for Space Station Freedom (SSF) assembly sequence planning consists of three software components: the system infrastructure, intra-flight value added, and inter-flight value added. The system infrastructure is the substrate on which software elements providing inter-flight and intra-flight value-added functionality are built. It provides the capability for building representations of assembly sequence plans and specification of constraints and analysis options. Intra-flight value-added provides functionality that will, given the manifest for each flight, define cargo elements, place them in the National Space Transportation System (NSTS) cargo bay, compute performance measure values, and identify violated constraints. Inter-flight value-added provides functionality that will, given major milestone dates and capability requirements, determine the number and dates of required flights and develop a manifest for each flight. The current project is Phase 1 of a projected two phase program and delivers the system infrastructure. Intra- and inter-flight value-added were to be developed in Phase 2, which has not been funded. Based on experience derived from hundreds of projects conducted over the past seven years, ISX developed an Intelligent Systems Engineering (ISE) methodology that combines the methods of systems engineering and knowledge engineering to meet the special systems development requirements posed by intelligent systems, systems that blend artificial intelligence and other advanced technologies with more conventional computing technologies. The ISE methodology defines a phased program process that begins with an application assessment designed to provide a preliminary determination of the relative technical risks and payoffs associated with a potential application, and then moves through requirements analysis, system design, and development.

Knowledge-based decision support for Space Station assembly sequence planning

NASA Technical Reports Server (NTRS)

1991-01-01

A complete Personal Analysis Assistant (PAA) for Space Station Freedom (SSF) assembly sequence planning consists of three software components: the system infrastructure, intra-flight value added, and inter-flight value added. The system infrastructure is the substrate on which software elements providing inter-flight and intra-flight value-added functionality are built. It provides the capability for building representations of assembly sequence plans and specification of constraints and analysis options. Intra-flight value-added provides functionality that will, given the manifest for each flight, define cargo elements, place them in the National Space Transportation System (NSTS) cargo bay, compute performance measure values, and identify violated constraints. Inter-flight value-added provides functionality that will, given major milestone dates and capability requirements, determine the number and dates of required flights and develop a manifest for each flight. The current project is Phase 1 of a projected two phase program and delivers the system infrastructure. Intra- and inter-flight value-added were to be developed in Phase 2, which has not been funded. Based on experience derived from hundreds of projects conducted over the past seven years, ISX developed an Intelligent Systems Engineering (ISE) methodology that combines the methods of systems engineering and knowledge engineering to meet the special systems development requirements posed by intelligent systems, systems that blend artificial intelligence and other advanced technologies with more conventional computing technologies. The ISE methodology defines a phased program process that begins with an application assessment designed to provide a preliminary determination of the relative technical risks and payoffs associated with a potential application, and then moves through requirements analysis, system design, and development.

Flight test of a full authority Digital Electronic Engine Control system in an F-15 aircraft

NASA Technical Reports Server (NTRS)

Barrett, W. J.; Rembold, J. P.; Burcham, F. W.; Myers, L.

1981-01-01

The Digital Electronic Engine Control (DEEC) system considered is a relatively low cost digital full authority control system containing selectively redundant components and fault detection logic with capability for accommodating faults to various levels of operational capability. The DEEC digital control system is built around a 16-bit, 1.2 microsecond cycle time, CMOS microprocessor, microcomputer system with approximately 14 K of available memory. Attention is given to the control mode, component bench testing, closed loop bench testing, a failure mode and effects analysis, sea-level engine testing, simulated altitude engine testing, flight testing, the data system, cockpit, and real time display.

The Systems Engineering Process for Human Support Technology Development

NASA Technical Reports Server (NTRS)

Jones, Harry

2005-01-01

Systems engineering is designing and optimizing systems. This paper reviews the systems engineering process and indicates how it can be applied in the development of advanced human support systems. Systems engineering develops the performance requirements, subsystem specifications, and detailed designs needed to construct a desired system. Systems design is difficult, requiring both art and science and balancing human and technical considerations. The essential systems engineering activity is trading off and compromising between competing objectives such as performance and cost, schedule and risk. Systems engineering is not a complete independent process. It usually supports a system development project. This review emphasizes the NASA project management process as described in NASA Procedural Requirement (NPR) 7120.5B. The process is a top down phased approach that includes the most fundamental activities of systems engineering - requirements definition, systems analysis, and design. NPR 7120.5B also requires projects to perform the engineering analyses needed to ensure that the system will operate correctly with regard to reliability, safety, risk, cost, and human factors. We review the system development project process, the standard systems engineering design methodology, and some of the specialized systems analysis techniques. We will discuss how they could apply to advanced human support systems development. The purpose of advanced systems development is not directly to supply human space flight hardware, but rather to provide superior candidate systems that will be selected for implementation by future missions. The most direct application of systems engineering is in guiding the development of prototype and flight experiment hardware. However, anticipatory systems engineering of possible future flight systems would be useful in identifying the most promising development projects.

Expanded study of feasibility of measuring in-flight 747/JT9D loads, performance, clearance, and thermal data

NASA Technical Reports Server (NTRS)

Sallee, G. P.; Martin, R. L.

1980-01-01

The JT9D jet engine exhibits a TSFC loss of about 1 percent in the initial 50 flight cycles of a new engine. These early losses are caused by seal-wear induced opening of running clearances in the engine gas path. The causes of this seal wear have been identified as flight induced loads which deflect the engine cases and rotors, causing the rotating blades to rub against the seal surfaces, producing permanent clearance changes. The real level of flight loads encountered during airplane acceptance testing and revenue service and the engine's response in the dynamic flight environment were investigated. The feasibility of direct measurement of these flight loads and their effects by concurrent measurement of 747/JT9D propulsion system aerodynamic and inertia loads and the critical engine clearance and performance changes during 747 flight and ground operations was evaluated. A number of technical options were examined in relation to the total estimated program cost to facilitate selection of the most cost effective option. It is concluded that a flight test program meeting the overall objective of determining the levels of aerodynamic and inertia load levels to which the engine is exposed during the initial flight acceptance test and normal flight maneuvers is feasible and desirable. A specific recommended flight test program, based on the evaluation of cost effectiveness, is defined.

78 FR 52838 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-08-27

... Maintenance Planning Data (MPD) Document. Repeat the test thereafter at intervals not to exceed 7,500 flight... by loss of fuel system suction feed capability on one engine, and in-flight shutdown of the engine...-101, before further flight, perform all related testing and corrective actions, and repeat the...

Flight testing the digital electronic engine control in the F-15 airplane

NASA Technical Reports Server (NTRS)

Myers, L. P.

1984-01-01

The digital electronic engine control (DEEC) is a full-authority digital engine control developed for the F100-PW-100 turbofan engine which was flight tested on an F-15 aircraft. The DEEC hardware and software throughout the F-15 flight envelope was evaluated. Real-time data reduction and data display systems were implemented. New test techniques and stronger coordination between the propulsion test engineer and pilot were developed which produced efficient use of test time, reduced pilot work load, and greatly improved quality data. The engine pressure ratio (EPR) control mode is demonstrated. It is found that the nonaugmented throttle transients and engine performance are satisfactory.

Performance improvements of a highly integrated digital electronic control system for an F-15 airplane

NASA Technical Reports Server (NTRS)

Putnam, T. W.; Burcham, F. W., Jr.; Andries, M. G.; Kelly, J. B.

1985-01-01

The NASA highly integrated digital electronic control (HIDEC) program is structured to conduct flight research into the benefits of integrating an aircraft flight control system with the engine control system. A brief description of the HIDEC system installed on an F-15 aircraft is provided. The adaptive engine control system (ADECS) mode is described in detail, together with simulation results and analyses that show the significant excess thrust improvements achievable with the ADECS mode. It was found that this increased thrust capability is accompanied by reduced fan stall margin and can be realized during flight conditions where engine face distortion is low. The results of analyses and simulations also show that engine thrust response is improved and that fuel consumption can be reduced. Although the performance benefits that accrue because of airframe and engine control integration are being demonstrated on an F-15 aircraft, the principles are applicable to advanced aircraft such as the advanced tactical fighter and advanced tactical aircraft.

The implementation and operation of a variable-response electronic throttle control system for a TF-104G aircraft

NASA Technical Reports Server (NTRS)

Neal, Bradford; Sengupta, Upal

1989-01-01

During some flight programs, researchers have encountered problems in the throttle response characteristics of high-performance aircraft. To study and to help solve these problems, the National Aeronautics and Space Administration Ames Research Center's Dryden Flight Research Facility (Ames-Dryden) conducted a study using a TF-104G airplane modified with a variable-response electronic throttle control system. Ames-Dryden investigated the effects of different variables on engine response and handling qualities. The system provided transport delay, lead and lag filters, second-order lags, command rate and position limits, and variable gain between the pilot's throttle command and the engine fuel controller. These variables could be tested individually or in combination. Ten research flights were flown to gather data on engine response and to obtain pilot ratings of the various system configurations. The results should provide design criteria for engine-response characteristics. The variable-response throttle components and how they were installed in the TF-104G aircraft are described. How the variable-response throttle was used in flight and some of the results of using this system are discussed.

CSBF Engineering Overview

NASA Astrophysics Data System (ADS)

Orr, Dwayne

The Columbia Scientific Balloon Facility (CSBF) at Palestine, Texas provides operational and engineering support for the launch of NASA Scientific Balloons. Over the years with the support of the NASA Balloon Program Office, CSBF has developed unique flight systems with the focus of providing a highly reliable, cost effective medium for giving Scientist's access to a near space environment. This paper will provide an overview of the CSBF flight systems with an emphasis on recent developments and plans for the future including: RIP Stitch -Parachute Shock Attenuation system, MIP -Micro Instrumentation Package, GAPR -Gondola Automatic Parachute Release system, NASA TDRSS High Gain Antenna system, Superpressure flight video systems

Energy efficient engine: Propulsion system-aircraft integration evaluation

NASA Technical Reports Server (NTRS)

Owens, R. E.

1979-01-01

Flight performance and operating economics of future commercial transports utilizing the energy efficient engine were assessed as well as the probability of meeting NASA's goals for TSFC, DOC, noise, and emissions. Results of the initial propulsion systems aircraft integration evaluation presented include estimates of engine performance, predictions of fuel burns, operating costs of the flight propulsion system installed in seven selected advanced study commercial transports, estimates of noise and emissions, considerations of thrust growth, and the achievement-probability analysis.

14 CFR 25.933 - Reversing systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... reversal in flight the engine will produce no more than flight idle thrust. In addition, it must be shown... kind of failure is extremely remote. (3) Each system must have means to prevent the engine from... alone, under the most critical reversing condition expected in operation. (b) For propeller reversing...

14 CFR 25.933 - Reversing systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

... reversal in flight the engine will produce no more than flight idle thrust. In addition, it must be shown... kind of failure is extremely remote. (3) Each system must have means to prevent the engine from... alone, under the most critical reversing condition expected in operation. (b) For propeller reversing...

14 CFR 25.933 - Reversing systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

... reversal in flight the engine will produce no more than flight idle thrust. In addition, it must be shown... kind of failure is extremely remote. (3) Each system must have means to prevent the engine from... alone, under the most critical reversing condition expected in operation. (b) For propeller reversing...

Summary of the effects of engine throttle response on airplane formation-flying qualities

NASA Technical Reports Server (NTRS)

Walsh, Kevin R.

1992-01-01

A flight evaluation as conducted to determine the effect of engine throttle response characteristics on precision formation-flying qualities. A variable electronic throttle control system was developed and flight-tested on a TF-104G airplane with a J79-11B engine at the NASA Dryden Flight Research Facility. Ten research flights were flown to evaluate the effects of throttle gain, time delay, and fuel control rate limiting on engine handling qualities during a demanding precision wing formation task. Handling quality effects of lag filters and lead compensation time delays were also evaluated. Data from pilot ratings and comments indicate that throttle control system time delays and rate limits cause significant degradations in handling qualities. Threshold values for satisfactory (level 1) and adequate (level 2) handling qualities of these key variables are presented.

Flight-determined engine exhaust characteristics of an F404 engine in an F-18 airplane

NASA Technical Reports Server (NTRS)

Ennix, Kimberly A.; Burcham, Frank W., Jr.; Webb, Lannie D.

1993-01-01

Personnel at the NASA Langley Research Center (NASA-Langley) and the NASA Dryden Flight Research Facility (NASA-Dryden) recently completed a joint acoustic flight test program. Several types of aircraft with high nozzle pressure ratio engines were flown to satisfy a twofold objective. First, assessments were made of subsonic climb-to-cruise noise from flights conducted at varying altitudes in a Mach 0.30 to 0.90 range. Second, using data from flights conducted at constant altitude in a Mach 0.30 to 0.95 range, engineers obtained a high quality noise database. This database was desired to validate the Aircraft Noise Prediction Program and other system noise prediction codes. NASA-Dryden personnel analyzed the engine data from several aircraft that were flown in the test program to determine the exhaust characteristics. The analysis of the exhaust characteristics from the F-18 aircraft are reported. An overview of the flight test planning, instrumentation, test procedures, data analysis, engine modeling codes, and results are presented.

Toward a Model-Based Approach to Flight System Fault Protection

NASA Technical Reports Server (NTRS)

Day, John; Murray, Alex; Meakin, Peter

2012-01-01

Fault Protection (FP) is a distinct and separate systems engineering sub-discipline that is concerned with the off-nominal behavior of a system. Flight system fault protection is an important part of the overall flight system systems engineering effort, with its own products and processes. As with other aspects of systems engineering, the FP domain is highly amenable to expression and management in models. However, while there are standards and guidelines for performing FP related analyses, there are not standards or guidelines for formally relating the FP analyses to each other or to the system hardware and software design. As a result, the material generated for these analyses are effectively creating separate models that are only loosely-related to the system being designed. Development of approaches that enable modeling of FP concerns in the same model as the system hardware and software design enables establishment of formal relationships that has great potential for improving the efficiency, correctness, and verification of the implementation of flight system FP. This paper begins with an overview of the FP domain, and then continues with a presentation of a SysML/UML model of the FP domain and the particular analyses that it contains, by way of showing a potential model-based approach to flight system fault protection, and an exposition of the use of the FP models in FSW engineering. The analyses are small examples, inspired by current real-project examples of FP analyses.

X-33 Attitude Control Using the XRS-2200 Linear Aerospike Engine

NASA Technical Reports Server (NTRS)

Hall, Charles E.; Panossian, Hagop V.

1999-01-01

The Vehicle Control Systems Team at Marshall Space Flight Center, Structures and Dynamics Laboratory, Guidance and Control Systems Division is designing, under a cooperative agreement with Lockheed Martin Skunkworks, the Ascent, Transition, and Entry flight attitude control systems for the X-33 experimental vehicle. Test flights, while suborbital, will achieve sufficient altitudes and Mach numbers to test Single Stage To Orbit, Reusable Launch Vehicle technologies. Ascent flight control phase, the focus of this paper, begins at liftoff and ends at linear aerospike main engine cutoff (MECO). The X-33 attitude control system design is confronted by a myriad of design challenges: a short design cycle, the X-33 incremental test philosophy, the concurrent design philosophy chosen for the X-33 program, and the fact that the attitude control system design is, as usual, closely linked to many other subsystems and must deal with constraints and requirements from these subsystems. Additionally, however, and of special interest, the use of the linear aerospike engine is a departure from the gimbaled engines traditionally used for thrust vector control (TVC) in launch vehicles and poses certain design challenges. This paper discusses the unique problem of designing the X-33 attitude control system with the linear aerospike engine, requirements development, modeling and analyses that verify the design.

F-15 HiDEC landing

NASA Technical Reports Server (NTRS)

1993-01-01

NASA's HIDEC (Highly Integrated Digital Electronic Control) F-15 aircraft nears the runway after a flight out of NASA's Dryden Flight Research Center, Edwards, California. The last project it was used for at Dryden was development of a computer-assisted engine control system that lets a plane land safely with only engine power if its normal control surfaces such as elevators, rudders or ailerons are disabled. The flight control system helps the pilot control the engines to turn the aircraft, climb, descend and eventually land safely by varying the speed of the engines one at a time or together. The HIDEC F-15A, built as the number eight prototype (Serial #71-0287), has now been retired.

Use of the flight simulator in the design of a STOL research aircraft.

NASA Technical Reports Server (NTRS)

Spitzer, R. E.; Rumsey, P. C.; Quigley, H. C.

1972-01-01

Piloted simulator tests on the NASA-Ames Flight Simulator for Advanced Aircraft motion base played a major role in guiding the design of the Modified C-8A 'Buffalo' augmentor wing jet flap STOL research airplane. Design results are presented for the flight control systems, lateral-directional SAS, hydraulic systems, and engine and thrust vector controls. Emphasis is given to lateral control characteristics on STOL landing approach, engine-out control and recovery techniques in the powered-lift regime, and operational flight procedures which affected airplane design.

Preliminary supersonic flight test evaluation of performance seeking control

NASA Technical Reports Server (NTRS)

Orme, John S.; Gilyard, Glenn B.

1993-01-01

Digital flight and engine control, powerful onboard computers, and sophisticated controls techniques may improve aircraft performance by maximizing fuel efficiency, maximizing thrust, and extending engine life. An adaptive performance seeking control system for optimizing the quasi-steady state performance of an F-15 aircraft was developed and flight tested. This system has three optimization modes: minimum fuel, maximum thrust, and minimum fan turbine inlet temperature. Tests of the minimum fuel and fan turbine inlet temperature modes were performed at a constant thrust. Supersonic single-engine flight tests of the three modes were conducted using varied after burning power settings. At supersonic conditions, the performance seeking control law optimizes the integrated airframe, inlet, and engine. At subsonic conditions, only the engine is optimized. Supersonic flight tests showed improvements in thrust of 9 percent, increases in fuel savings of 8 percent, and reductions of up to 85 deg R in turbine temperatures for all three modes. The supersonic performance seeking control structure is described and preliminary results of supersonic performance seeking control tests are given. These findings have implications for improving performance of civilian and military aircraft.

The nature of operating flight loads and their effect on propulsion system structures

NASA Technical Reports Server (NTRS)

Dickenson, K. H.; Martin, R. L.

1981-01-01

Past diagnostics studies revealed the primary causes of performance deterioration of high by-pass turbofan engines to be flight loads, erosion, and thermal distortion. The various types of airplane loads that are imposed on the engine throughout the lifetime of an airplane are examined. These include flight loads from gusts and maneuvers and ground loads from takeoff, landing, and taxi conditions. Clarification is made in definitions of the airframer's limit and ultimate design loads and the engine manufacturer's operating design loads. Finally, the influence of these loads on the propulsion system structures is discussed.

Development of HIDEC adaptive engine control systems

NASA Technical Reports Server (NTRS)

Landy, R. J.; Yonke, W. A.; Stewart, J. F.

1986-01-01

The purpose of NASA's Highly Integrated Digital Electronic Control (HIDEC) flight research program is the development of integrated flight propulsion control modes, and the evaluation of their benefits aboard an F-15 test aircraft. HIDEC program phases are discussed, with attention to the Adaptive Engine Control System (ADECS I); this involves the upgrading of PW1128 engines for operation at higher engine pressure ratios and the production of greater thrust. ADECS II will involve the development of a constant thrust mode which will significantly reduce turbine operating temperatures.

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

NASA Technical Reports Server (NTRS)

Dischinger, H. Charles, Jr.; Stambolian, Damon B.; Miller, Darcy H.

2008-01-01

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.

Feasibility of using a knowledge-based system concept for in-flight primary flight display research

NASA Technical Reports Server (NTRS)

Ricks, Wendell R.

1991-01-01

A study was conducted to determine the feasibility of using knowledge-based systems architectures for inflight research of primary flight display information management issues. The feasibility relied on the ability to integrate knowledge-based systems with existing onboard aircraft systems. And, given the hardware and software platforms available, the feasibility also depended on the ability to use interpreted LISP software with the real time operation of the primary flight display. In addition to evaluating these feasibility issues, the study determined whether the software engineering advantages of knowledge-based systems found for this application in the earlier workstation study extended to the inflight research environment. To study these issues, two integrated knowledge-based systems were designed to control the primary flight display according to pre-existing specifications of an ongoing primary flight display information management research effort. These two systems were implemented to assess the feasibility and software engineering issues listed. Flight test results were successful in showing the feasibility of using knowledge-based systems inflight with actual aircraft data.

Engineering flight and guest pilot evaluation report, phase 2. [DC 8 aircraft

NASA Technical Reports Server (NTRS)

Morrison, J. A.; Anderson, E. B.; Brown, G. W.; Schwind, G. K.

1974-01-01

Prior to the flight evaluation, the two-segment profile capabilities of the DC-8-61 were evaluated and flight procedures were developed in a flight simulator at the UA Flight Training Center in Denver, Colorado. The flight evaluation reported was conducted to determine the validity of the simulation results, further develop the procedures and use of the area navigation system in the terminal area, certify the system for line operation, and obtain evaluations of the system and procedures by a number of pilots from the industry. The full area navigation capabilities of the special equipment installed were developed to provide terminal area guidance for two-segment approaches. The objectives of this evaluation were: (1) perform an engineering flight evaluation sufficient to certify the two-segment system for the six-month in-service evaluation; (2) evaluate the suitability of a modified RNAV system for flying two-segment approaches; and (3) provide evaluation of the two-segment approach by management and line pilots.

Automated flight test management system

NASA Technical Reports Server (NTRS)

Hewett, M. D.; Tartt, D. M.; Agarwal, A.

1991-01-01

The Phase 1 development of an automated flight test management system (ATMS) as a component of a rapid prototyping flight research facility for artificial intelligence (AI) based flight concepts is discussed. The ATMS provides a flight engineer with a set of tools that assist in flight test planning, monitoring, and simulation. The system is also capable of controlling an aircraft during flight test by performing closed loop guidance functions, range management, and maneuver-quality monitoring. The ATMS is being used as a prototypical system to develop a flight research facility for AI based flight systems concepts at NASA Ames Dryden.

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

NASA Technical Reports Server (NTRS)

Dubon, Lydia P.

2006-01-01

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

TRENDS: The aeronautical post-test database management system

NASA Technical Reports Server (NTRS)

Bjorkman, W. S.; Bondi, M. J.

1990-01-01

TRENDS, an engineering-test database operating system developed by NASA to support rotorcraft flight tests, is described. Capabilities and characteristics of the system are presented, with examples of its use in recalling and analyzing rotorcraft flight-test data from a TRENDS database. The importance of system user-friendliness in gaining users' acceptance is stressed, as is the importance of integrating supporting narrative data with numerical data in engineering-test databases. Considerations relevant to the creation and maintenance of flight-test database are discussed and TRENDS' solutions to database management problems are described. Requirements, constraints, and other considerations which led to the system's configuration are discussed and some of the lessons learned during TRENDS' development are presented. Potential applications of TRENDS to a wide range of aeronautical and other engineering tests are identified.

Apollo 16, LM-11 descent propulsion system final flight evaluation

NASA Technical Reports Server (NTRS)

Avvenire, A. T.

1974-01-01

The performance of the LM-11 descent propulsion system during the Apollo 16 missions was evaluated and found satisfactory. The average engine effective specific impulse was 0.1 second higher than predicted, but well within the predicted one sigma uncertainty of 0.2 seconds. Several flight measurement discrepancies existed during the flight as follows: (1) the chamber pressure transducer had a noticeable drift, exhibiting a maximum error of about 1.5 psi at approximately 130 seconds after engine ignition, (2) the fuel and oxidizer interface pressure measurements appeared to be low during the entire flight, and (3) the fuel propellant quantity gaging system did not perform within expected accuracies.

Orion Flight Test 1 Architecture: Observed Benefits of a Model Based Engineering Approach

NASA Technical Reports Server (NTRS)

Simpson, Kimberly A.; Sindiy, Oleg V.; McVittie, Thomas I.

2012-01-01

This paper details how a NASA-led team is using a model-based systems engineering approach to capture, analyze and communicate the end-to-end information system architecture supporting the first unmanned orbital flight of the Orion Multi-Purpose Crew Exploration Vehicle. Along with a brief overview of the approach and its products, the paper focuses on the observed program-level benefits, challenges, and lessons learned; all of which may be applied to improve system engineering tasks for characteristically similarly challenges

X-43C Flight Demonstrator Project Overview

NASA Technical Reports Server (NTRS)

Moses, Paul L.

2003-01-01

The X-43C Flight Demonstrator Project is a joint NASA-USAF hypersonic propulsion technology flight demonstration project that will expand the hypersonic flight envelope for air-breathing engines. The Project will demonstrate sustained accelerating flight through three flights of expendable X-43C Demonstrator Vehicles (DVs). The approximately 16-foot long X-43C DV will be boosted to the starting test conditions, separate from the booster, and accelerate from Mach 5 to Mach 7 under its own power and autonomous control. The DVs will be powered by a liquid hydrocarbon-fueled, fuel-cooled, dual-mode, airframe integrated scramjet engine system developed under the USAF HyTech Program. The Project is managed by NASA Langley Research Center as part of NASA's Next Generation Launch Technology Program. Flight tests will be conducted by NASA Dryden Flight Research Center off the coast of California over water in the Pacific Test Range. The NASA/USAF/industry project is a natural extension of the Hyper-X Program (X-43A), which will demonstrate short duration (approximately 10 seconds) gaseous hydrogen-fueled scramjet powered flight at Mach 7 and Mach 10 using a heavy-weight, largely heat sink construction, experimental engine. The X-43C Project will demonstrate sustained accelerating flight from Mach 5 to Mach 7 (approximately 4 minutes) using a flight-weight, fuel-cooled, scramjet engine powered by much denser liquid hydrocarbon fuel. The X-43C DV design flows from integrating USAF HyTech developed engine technologies with a NASA Air-Breathing Launch Vehicle accelerator-class configuration and Hyper-X heritage vehicle systems designs. This paper describes the X-43C Project and provides the background for NASA's current hypersonic flight demonstration efforts.

A knowledge-based system design/information tool for aircraft flight control systems

NASA Technical Reports Server (NTRS)

Mackall, Dale A.; Allen, James G.

1989-01-01

Research aircraft have become increasingly dependent on advanced control systems to accomplish program goals. These aircraft are integrating multiple disciplines to improve performance and satisfy research objectives. This integration is being accomplished through electronic control systems. Because of the number of systems involved and the variety of engineering disciplines, systems design methods and information management have become essential to program success. The primary objective of the system design/information tool for aircraft flight control system is to help transfer flight control system design knowledge to the flight test community. By providing all of the design information and covering multiple disciplines in a structured, graphical manner, flight control systems can more easily be understood by the test engineers. This will provide the engineers with the information needed to thoroughly ground test the system and thereby reduce the likelihood of serious design errors surfacing in flight. The secondary objective is to apply structured design techniques to all of the design domains. By using the techniques in the top level system design down through the detailed hardware and software designs, it is hoped that fewer design anomalies will result. The flight test experiences of three highly complex, integrated aircraft programs are reviewed: the X-29 forward-swept wing, the advanced fighter technology integration (AFTI) F-16, and the highly maneuverable aircraft technology (HiMAT) program. Significant operating anomalies and the design errors which cause them, are examined to help identify what functions a system design/information tool should provide to assist designers in avoiding errors.

Health management and controls for earth to orbit propulsion systems

NASA Technical Reports Server (NTRS)

Bickford, R. L.

1992-01-01

Fault detection and isolation for advanced rocket engine controllers are discussed focusing on advanced sensing systems and software which significantly improve component failure detection for engine safety and health management. Aerojet's Space Transportation Main Engine controller for the National Launch System is the state of the art in fault tolerant engine avionics. Health management systems provide high levels of automated fault coverage and significantly improve vehicle delivered reliability and lower preflight operations costs. Key technologies, including the sensor data validation algorithms and flight capable spectrometers, have been demonstrated in ground applications and are found to be suitable for bridging programs into flight applications.

The Max Launch Abort System - Concept, Flight Test, and Evolution

NASA Technical Reports Server (NTRS)

Gilbert, Michael G.

2014-01-01

The NASA Engineering and Safety Center (NESC) is an independent engineering analysis and test organization providing support across the range of NASA programs. In 2007 NASA was developing the launch escape system for the Orion spacecraft that was evolved from the traditional tower-configuration escape systems used for the historic Mercury and Apollo spacecraft. The NESC was tasked, as a programmatic risk-reduction effort to develop and flight test an alternative to the Orion baseline escape system concept. This project became known as the Max Launch Abort System (MLAS), named in honor of Maxime Faget, the developer of the original Mercury escape system. Over the course of approximately two years the NESC performed conceptual and tradeoff analyses, designed and built full-scale flight test hardware, and conducted a flight test demonstration in July 2009. Since the flight test, the NESC has continued to further develop and refine the MLAS concept.

Instrumentation for In-Flight SSME Rocket Engine Plume Spectroscopy

NASA Technical Reports Server (NTRS)

Madzsar, George C.; Bickford, Randall L.; Duncan, David B.

1994-01-01

This paper describes instrumentation that is under development for an in-flight demonstration of a plume spectroscopy system on the space shuttle main engine. The instrumentation consists of a nozzle mounted optical probe for observation of the plume, and a spectrometer for identification and quantification of plume content. This instrumentation, which is intended for use as a diagnostic tool to detect wear and incipient failure in rocket engines, will be validated by a hardware demonstration on the Technology Test Bed engine at the Marshall Space Flight Center.

Flight Testing the Linear Aerospike SR-71 Experiment (LASRE)

NASA Technical Reports Server (NTRS)

Corda, Stephen; Neal, Bradford A.; Moes, Timothy R.; Cox, Timothy H.; Monaghan, Richard C.; Voelker, Leonard S.; Corpening, Griffin P.; Larson, Richard R.; Powers, Bruce G.

1998-01-01

The design of the next generation of space access vehicles has led to a unique flight test that blends the space and flight research worlds. The new space vehicle designs, such as the X-33 vehicle and Reusable Launch Vehicle (RLV), are powered by linear aerospike rocket engines. Conceived of in the 1960's, these aerospike engines have yet to be flown, and many questions remain regarding aerospike engine performance and efficiency in flight. To provide some of these data before flying on the X-33 vehicle and the RLV, a spacecraft rocket engine has been flight-tested atop the NASA SR-71 aircraft as the Linear Aerospike SR-71 Experiment (LASRE). A 20 percent-scale, semispan model of the X-33 vehicle, the aerospike engine, and all the required fuel and oxidizer tanks and propellant feed systems have been mounted atop the SR-71 airplane for this experiment. A major technical objective of the LASRE flight test is to obtain installed-engine performance flight data for comparison to wind-tunnel results and for the development of computational fluid dynamics-based design methodologies. The ultimate goal of firing the aerospike rocket engine in flight is still forthcoming. An extensive design and development phase of the experiment hardware has been completed, including approximately 40 ground tests. Five flights of the LASRE and firing the rocket engine using inert liquid nitrogen and helium in place of liquid oxygen and hydrogen have been successfully completed.

14 CFR 33.69 - Ignitions system.

Code of Federal Regulations, 2010 CFR

2010-01-01

... Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION AIRCRAFT AIRWORTHINESS STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.69 Ignitions system. Each engine must be equipped with an ignition system for starting the engine on the ground and in flight. An...

14 CFR 33.69 - Ignitions system.

Code of Federal Regulations, 2011 CFR

2011-01-01

... Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION AIRCRAFT AIRWORTHINESS STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.69 Ignitions system. Each engine must be equipped with an ignition system for starting the engine on the ground and in flight. An...

User type certification for advanced flight control systems

NASA Technical Reports Server (NTRS)

Gilson, Richard D.; Abbott, David W.

1994-01-01

Advanced avionics through flight management systems (FMS) coupled with autopilots can now precisely control aircraft from takeoff to landing. Clearly, this has been the most important improvement in aircraft since the jet engine. Regardless of the eventual capabilities of this technology, it is doubtful that society will soon accept pilotless airliners with the same aplomb they accept driverless passenger trains. Flight crews are still needed to deal with inputing clearances, taxiing, in-flight rerouting, unexpected weather decisions, and emergencies; yet it is well known that the contribution of human errors far exceed those of current hardware or software systems. Thus human errors remain, and are even increasing in percentage as the largest contributor to total system error. Currently, the flight crew is regulated by a layered system of certification: by operation, e.g., airline transport pilot versus private pilot; by category, e.g., airplane versus helicopter; by class, e.g., single engine land versus multi-engine land; and by type (for larger aircraft and jet powered aircraft), e.g., Boeing 767 or Airbus A320. Nothing in the certification process now requires an in-depth proficiency with specific types of avionics systems despite their prominent role in aircraft control and guidance.

Summary of the effects of engine throttle response on airplane formation-flying qualities

NASA Technical Reports Server (NTRS)

Walsh, Kevin R.

1993-01-01

A flight evaluation was conducted to determine the effect of engine throttle response characteristics on precision formation-flying qualities. A variable electronic throttle control system was developed and flight-tested on a TF-104G airplane with a J79-11B engine at the NASA Dryden Flight Research Facility. This airplane was chosen because of its known, very favorable thrust response characteristics. Ten research flights were flown to evaluate the effects of throttle gain, time delay, and fuel control rate limiting on engine handling qualities during a demanding precision wing formation task. Handling quality effects of lag filters and lead compensation time delays were also evaluated. The Cooper and Harper Pilot Rating Scale was used to assign levels of handling quality. Data from pilot ratings and comments indicate that throttle control system time delays and rate limits cause significant degradations in handling qualities. Threshold values for satisfactory (level 1) and adequate (level 2) handling qualities of these key variables are presented. These results may provide engine manufacturers with guidelines to assure satisfactory handling qualities in future engine designs.

PSL Icing Facility Upgrade Overview

NASA Technical Reports Server (NTRS)

Griffin, Thomas A.; Dicki, Dennis J.; Lizanich, Paul J.

2014-01-01

The NASA Glenn Research Center Propulsion Systems Lab (PSL) was recently upgraded to perform engine inlet ice crystal testing in an altitude environment. The system installed 10 spray bars in the inlet plenum for ice crystal generation using 222 spray nozzles. As an altitude test chamber, the PSL is capable of simulating icing events at altitude in a groundtest facility. The system was designed to operate at altitudes from 4,000 to 40,000 ft at Mach numbers up to 0.8M and inlet total temperatures from -60 to +15 degF. This paper and presentation will be part of a series of presentations on PSL Icing and will cover the development of the icing capability through design, developmental testing, installation, initial calibration, and validation engine testing. Information will be presented on the design criteria and process, spray bar developmental testing at Cox and Co., system capabilities, and initial calibration and engine validation test. The PSL icing system was designed to provide NASA and the icing community with a facility that could be used for research studies of engine icing by duplicating in-flight events in a controlled ground-test facility. With the system and the altitude chamber we can produce flight conditions and cloud environments to simulate those encountered in flight. The icing system can be controlled to set various cloud uniformities, droplet median volumetric diameter (MVD), and icing water content (IWC) through a wide variety of conditions. The PSL chamber can set altitudes, Mach numbers, and temperatures of interest to the icing community and also has the instrumentation capability of measuring engine performance during icing testing. PSL last year completed the calibration and initial engine validation of the facility utilizing a Honeywell ALF502-R5 engine and has duplicated in-flight roll back conditions experienced during flight testing. This paper will summarize the modifications and buildup of the facility to accomplish these tests.

Aerospike Engine Post-Test Diagnostic System Delivered to Rocketdyne

NASA Technical Reports Server (NTRS)

Meyer, Claudia M.

2000-01-01

The NASA Glenn Research Center at Lewis Field, in cooperation with Rocketdyne, has designed, developed, and implemented an automated Post-Test Diagnostic System (PTDS) for the X-33 linear aerospike engine. The PTDS was developed to reduce analysis time and to increase the accuracy and repeatability of rocket engine ground test fire and flight data analysis. This diagnostic system provides a fast, consistent, first-pass data analysis, thereby aiding engineers who are responsible for detecting and diagnosing engine anomalies from sensor data. It uses analytical methods modeled after the analysis strategies used by engineers. Glenn delivered the first version of PTDS in September of 1998 to support testing of the engine s power pack assembly. The system was used to analyze all 17 power pack tests and assisted Rocketdyne engineers in troubleshooting both data acquisition and test article anomalies. The engine version of PTDS, which was delivered in June of 1999, will support all single-engine, dual-engine, and flight firings of the aerospike engine.

Fault detection and accommodation testing on an F100 engine in an F-15 airplane. [digital engine control system

NASA Technical Reports Server (NTRS)

Myers, L. P.; Baer-Riedhart, J. L.; Maxwell, M. D.

1985-01-01

The fault detection and accommodation (FDA) methods that can be used for digital engine control systems are presently subjected to a flight test program in the case of the F-15 fighter's F100 engine electronic controls, inducing selected faults and then evaluating the resulting digital engine control responses. In general, flight test results were found to compare well with both ground tests and predictions. It is noted that the inducement of dual-pressure failures was not feasible, since FDA logic was not designed to accommodate them.

Flight evaluation of a hydromechanical backup control for the digital electronic engine control system in an F100 engine

NASA Technical Reports Server (NTRS)

Walsh, K. R.; Burcham, F. W.

1984-01-01

The backup control (BUC) features, the operation of the BUC system, the BUC control logic, and the BUC flight test results are described. The flight test results include: (1) transfers to the BUC at military and maximum power settings; (2) a military power acceleration showing comparisons bvetween flight and simulation for BUC and primary modes; (3) steady-state idle power showing idle compressor speeds at different flight conditions; and (4) idle-to-military power BUC transients showing where cpmpressor stalls occurred for different ramp rates and idle speeds. All the BUC transfers which occur during the DEEC flight program are initiated by the pilot. Automatic transfers to the BUC do not occur.

Flight test summary of modified fuel systems

NASA Technical Reports Server (NTRS)

Barrett, B. G.

1976-01-01

Two different aircraft designs, each with two modified fuel control systems, were evaluated. Each aircraft was evaluated in a given series of defined ground and flight conditions while quantitative and qualitative observations were made. During this program, some ten flights were completed, and a total of about 13 hours of engine run time was accumulated by the two airplanes. The results of these evaluations with emphasis on the operational and safety aspects were analyzed. Ground tests of the engine alone were not able to predict acceptable limiting lean mixture settings for the flight envelopes of the Cessna Models 150 and T337.

Integrated Testing Approaches for the NASA Ares I Crew Launch Vehicle

NASA Technical Reports Server (NTRS)

Taylor, James L.; Cockrell, Charles E.; Tuma, Margaret L.; Askins, Bruce R.; Bland, Jeff D.; Davis, Stephan R.; Patterson, Alan F.; Taylor, Terry L.; Robinson, Kimberly L.

2008-01-01

The Ares I crew launch vehicle is being developed by the U.S. National Aeronautics and Space Administration (NASA) to provide crew and cargo access to the International Space Station (ISS) and, together with the Ares V cargo launch vehicle, serves as a critical component of NASA's future human exploration of the Moon. During the preliminary design phase, NASA defined and began implementing plans for integrated ground and flight testing necessary to achieve the first human launch of Ares I. The individual Ares I flight hardware elements - including the first stage five segment booster (FSB), upper stage, and J-2X upper stage engine - will undergo extensive development, qualification, and certification testing prior to flight. Key integrated system tests include the upper stage Main Propulsion Test Article (MPTA), acceptance tests of the integrated upper stage and upper stage engine assembly, a full-scale integrated vehicle ground vibration test (IVGVT), aerodynamic testing to characterize vehicle performance, and integrated testing of the avionics and software components. The Ares I-X development flight test will provide flight data to validate engineering models for aerodynamic performance, stage separation, structural dynamic performance, and control system functionality. The Ares I-Y flight test will validate ascent performance of the first stage, stage separation functionality, validate the ability of the upper stage to manage cryogenic propellants to achieve upper stage engine start conditions, and a high-altitude demonstration of the launch abort system (LAS) following stage separation. The Orion 1 flight test will be conducted as a full, un-crewed, operational flight test through the entire ascent flight profile prior to the first crewed launch.

Flight Test of Propulsion Monitoring and Diagnostic System

NASA Technical Reports Server (NTRS)

Gabel, Steve; Elgersma, Mike

2002-01-01

The objective of this program was to perform flight tests of the propulsion monitoring and diagnostic system (PMDS) technology concept developed by Honeywell under the NASA Advanced General Aviation Transport Experiment (AGATE) program. The PMDS concept is intended to independently monitor the performance of the engine, providing continuous status to the pilot along with warnings if necessary as well as making the data available to ground maintenance personnel via a special interface. These flight tests were intended to demonstrate the ability of the PMDS concept to detect a class of selected sensor hardware failures, and the ability to successfully model the engine for the purpose of engine diagnosis.

Cost effective launch operations of the SSME

NASA Technical Reports Server (NTRS)

Klatt, F. P.

1985-01-01

The Space Shuttle Main Engine (SSME) represents the beginning of reusable rocket engine operations in the space transportation system (STS). Steps taken to reduce the overall cost of flight operations of the SSME by improving turnaround operations, extending the life of the engine, and improving the cost effectiveness of overhaul operations at the Canoga Park home plant are described. Ground certification testing to ensure safe launch operations is described, as well as certification extension testing that leads to a service life equivalent to 40 flights. The proven flight record of the SSME, which has demonstrated the utility of the SSME as a key component of America's space transportation system, is discussed.

Enhanced Bank of Kalman Filters Developed and Demonstrated for In-Flight Aircraft Engine Sensor Fault Diagnostics

NASA Technical Reports Server (NTRS)

Kobayashi, Takahisa; Simon, Donald L.

2005-01-01

In-flight sensor fault detection and isolation (FDI) is critical to maintaining reliable engine operation during flight. The aircraft engine control system, which computes control commands on the basis of sensor measurements, operates the propulsion systems at the demanded conditions. Any undetected sensor faults, therefore, may cause the control system to drive the engine into an undesirable operating condition. It is critical to detect and isolate failed sensors as soon as possible so that such scenarios can be avoided. A challenging issue in developing reliable sensor FDI systems is to make them robust to changes in engine operating characteristics due to degradation with usage and other faults that can occur during flight. A sensor FDI system that cannot appropriately account for such scenarios may result in false alarms, missed detections, or misclassifications when such faults do occur. To address this issue, an enhanced bank of Kalman filters was developed, and its performance and robustness were demonstrated in a simulation environment. The bank of filters is composed of m + 1 Kalman filters, where m is the number of sensors being used by the control system and, thus, in need of monitoring. Each Kalman filter is designed on the basis of a unique fault hypothesis so that it will be able to maintain its performance if a particular fault scenario, hypothesized by that particular filter, takes place.

Spacecraft Design Thermal Control Subsystem

NASA Technical Reports Server (NTRS)

Miyake, Robert N.

2003-01-01

This slide presentation reviews the functions of the thermal control subsystem engineers in the design of spacecraft. The goal of the thermal control subsystem that will be used in a spacecraft is to maintain the temperature of all spacecraft components, subsystems, and all the flight systems within specified limits for all flight modes from launch to the end of the mission. For most thermal control subsystems the mass, power and control and sensing systems must be kept below 10% of the total flight system resources. This means that the thermal control engineer is involved in all other flight systems designs. The two concepts of thermal control, passive and active are reviewed and the use of thermal modeling tools are explained. The testing of the thermal control is also reviewed.

An Assessment Methodology to Evaluate In-Flight Engine Health Management Effectiveness

NASA Astrophysics Data System (ADS)

Maggio, Gaspare; Belyeu, Rebecca; Pelaccio, Dennis G.

2002-01-01

flight effectiveness of candidate engine health management system concepts. A next generation engine health management system will be required to be both reliable and robust in terms of anomaly detection capability. The system must be able to operate successfully in the hostile, high-stress engine system environment. This implies that its system components, such as the instrumentation, process and control, and vehicle interface and support subsystems, must be highly reliable. Additionally, the system must be able to address a vast range of possible engine operation anomalies through a host of different types of measurements supported by a fast algorithm/architecture processing capability that can identify "true" (real) engine operation anomalies. False anomaly condition reports for such a system must be essentially eliminated. The accuracy of identifying only real anomaly conditions has been an issue with the Space Shuttle Main Engine (SSME) in the past. Much improvement in many of the technologies to address these areas is required. The objectives of this study were to identify and demonstrate a consistent assessment methodology that can evaluate the capability of next generation engine health management system concepts to respond in a correct, timely manner to alleviate an operational engine anomaly condition during flight. Science Applications International Corporation (SAIC), with support from NASA Marshall Space Flight Center, identified a probabilistic modeling approach to assess engine health management system concept effectiveness using a deterministic anomaly-time event assessment modeling approach that can be applied in the engine preliminary design stage of development to assess engine health management system concept effectiveness. Much discussion in this paper focuses on the formulation and application approach in performing this assessment. This includes detailed discussion of key modeling assumptions, the overall assessment methodology approach identified, and the identification of key supporting engine health management system concept design/operation and fault mode information required to utilize this methodology. At the paper's conclusion, discussion focuses on a demonstration benchmark study that applied this methodology to the current SSME health management system. A summary of study results and lessons learned are provided. Recommendations for future work in this area are also identified at the conclusion of the paper. * Please direct all correspondence/communication pertaining to this paper to Dennis G. Pelaccio, Science

Performance deterioration due to acceptance testing and flight loads; JT90 jet engine diagnostic program

NASA Technical Reports Server (NTRS)

Olsson, W. J.

1982-01-01

The results of a flight loads test of the JT9D-7 engine are presented. The goals of this test program were to: measure aerodynamic and inertia loads on the engine during flight, explore the effects of airplane gross weight and typical maneuvers on these flight loads, simultaneously measure the changes in engine running clearances and performance resulting from the maneuvers, make refinements of engine performance deterioration prediction models based on analytical results of the tests, and make recommendations to improve propulsion system performance retention. The test program included a typical production airplane acceptance test plus additional flights and maneuvers to encompass the range of flight loads in revenue service. The test results indicated that aerodynamic loads, primarily at take-off, were the major cause of rub-indicated that aerodynamic loads, primarily at take-off, were the major cause of rub-induced deterioration in the cold sectin of the engine. Differential thermal expansion between rotating and static parts plus aerodynamic loads combined to cause blade-to-seal rubs in the turbine.

NASA Conducts Final RS-25 Rocket Engine Test of 2017

NASA Image and Video Library

2017-12-13

NASA engineers at Stennis Space Center capped a year of Space Launch System testing with a final RS-25 rocket engine hot fire on Dec. 13. The 470-second test on the A-1 Test Stand was a “green run” test of an RS-25 flight controller. The engine tested also included a large 3-D-printed part, a pogo accumulator assembly, scheduled for use on future RS-25 flight engines.

Verification and Implementation of Operations Safety Controls for Flight Missions

NASA Technical Reports Server (NTRS)

Smalls, James R.; Jones, Cheryl L.; Carrier, Alicia S.

2010-01-01

There are several engineering disciplines, such as reliability, supportability, quality assurance, human factors, risk management, safety, etc. Safety is an extremely important engineering specialty within NASA, and the consequence involving a loss of crew is considered a catastrophic event. Safety is not difficult to achieve when properly integrated at the beginning of each space systems project/start of mission planning. The key is to ensure proper handling of safety verification throughout each flight/mission phase. Today, Safety and Mission Assurance (S&MA) operations engineers continue to conduct these flight product reviews across all open flight products. As such, these reviews help ensure that each mission is accomplished with safety requirements along with controls heavily embedded in applicable flight products. Most importantly, the S&MA operations engineers are required to look for important design and operations controls so that safety is strictly adhered to as well as reflected in the final flight product.

NLS Flight Simulation Laboratory (FSL) documentation

NASA Technical Reports Server (NTRS)

1995-01-01

The Flight Simulation Laboratory (FSL) Electronic Documentation System design consists of modification and utilization of the MSFC Integrated Engineering System (IES), translation of the existing FSL documentation to an electronic format, and generation of new drawings to represent the Engine Flight Simulation Laboratory design and implementation. The intent of the electronic documentation is to provide ease of access, local print/plot capabilities, as well as the ability to correct and/or modify the stored data by network users who are authorized to access this information.

Incorporating Manual and Autonomous Code Generation

NASA Technical Reports Server (NTRS)

McComas, David

1998-01-01

Code can be generated manually or using code-generated software tools, but how do you interpret the two? This article looks at a design methodology that combines object-oriented design with autonomic code generation for attitude control flight software. Recent improvements in space flight computers are allowing software engineers to spend more time engineering the applications software. The application developed was the attitude control flight software for an astronomical satellite called the Microwave Anisotropy Probe (MAP). The MAP flight system is being designed, developed, and integrated at NASA's Goddard Space Flight Center. The MAP controls engineers are using Integrated Systems Inc.'s MATRIXx for their controls analysis. In addition to providing a graphical analysis for an environment, MATRIXx includes an autonomic code generation facility called AutoCode. This article examines the forces that shaped the final design and describes three highlights of the design process: (1) Defining the manual to autonomic code interface; (2) Applying object-oriented design to the manual flight code; (3) Implementing the object-oriented design in C.

Government Competitive Test Utility Tactical Transport Aircraft System (UTTAS). Sikorsky YUH-60A Helicopter

DTIC Science & Technology

1976-11-01

Box 209, St. Louis, Missouri 63166. UNITED STATES ARMY AVIATION ENGINEERING FLIGHT ACTIVITY EDWARDS AIR FORCE BASE, CALIFORNIA 93523 81 9 18 0 8,L...ELEMENT. PROJECT. TASKAR EA A WORK UNIT "UMBERS US ARMY AVIATION ENGINEERING FLIGHT ACTIV IU EDWARDS AIR FORCE BASE. CALIFORNIA 93523 68-T-UA022-0-68-EC...It. CONTROLLI~NG OFFICE NAME AND ADDRESS 12. REPORT DATE US ARMY AVIATION ENGINEERING FLIGHT ACTIVITY NOVEMBER 1976 EDWARDS AIR FORCE BASE

NASA Conducts 2nd RS-25 Engine Hot Fire of 2018

NASA Image and Video Library

2018-02-01

A 365-second hot fire test on Feb. 1, 2018, at NASA’s Stennis Space Center in Mississippi marks the completion of “green run” testing, or flight certification, for all new RS-25 engine flight controllers slated for Exploration Mission-2, the first Space Launch System mission with astronauts on board. In addition to the flight controller, the Feb. 1 hot fire also marked the third test of a 3D printed pogo accumulator assembly for the RS-25 engine.

Development of Supersonic Vehicle for Demonstration of a Precooled Turbojet Engine

NASA Astrophysics Data System (ADS)

Sawai, Shujiro; Fujita, Kazuhisa; Kobayashi, Hiroaki; Sakai, Shin'ichiro; Bando, Nobutaka; Kadooka, Shouhei; Tsuboi, Nobuyuki; Miyaji, Koji; Uchiyama, Taku; Hashimoto, Tatsuaki

JAXA is developing Mach 5 hypersonic turbojet engine technology that can be applied in a future hypersonic transport. Now, Jet Engine Technology Research Center of JAXA conducts the experimental study using a 1 / 10 scale-model engine. In parallel to engine development activities, a new supersonic flight-testing vehicle for the hypersonic turbojet engine is under development since 2004. In this paper, the system configuration of the flight-testing vehicle is outlined and development status is reported.

Integrated System Test Approaches for the NASA Ares I Crew Launch Vehicle

NASA Technical Reports Server (NTRS)

Cockrell, Charles E., Jr.; Askins, Bruce R.; Bland, Jeffrey; Davis, Stephan; Holladay, Jon B.; Taylor, James L.; Taylor, Terry L.; Robinson, Kimberly F.; Roberts, Ryan E.; Tuma, Margaret

2007-01-01

The Ares I Crew Launch Vehicle (CLV) is being developed by the U.S. National Aeronautics and Space Administration (NASA) to provide crew access to the International Space Station (ISS) and, together with the Ares V Cargo Launch Vehicle (CaLV), serves as one component of a future launch capability for human exploration of the Moon. During the system requirements definition process and early design cycles, NASA defined and began implementing plans for integrated ground and flight testing necessary to achieve the first human launch of Ares I. The individual Ares I flight hardware elements: the first stage five segment booster (FSB), upper stage, and J-2X upper stage engine, will undergo extensive development, qualification, and certification testing prior to flight. Key integrated system tests include the Main Propulsion Test Article (MPTA), acceptance tests of the integrated upper stage and upper stage engine assembly, a full-scale integrated vehicle dynamic test (IVDT), aerodynamic testing to characterize vehicle performance, and integrated testing of the avionics and software components. The Ares I-X development flight test will provide flight data to validate engineering models for aerodynamic performance, stage separation, structural dynamic performance, and control system functionality. The Ares I-Y flight test will validate ascent performance of the first stage, stage separation functionality, and a highaltitude actuation of the launch abort system (LAS) following separation. The Orion-1 flight test will be conducted as a full, un-crewed, operational flight test through the entire ascent flight profile prior to the first crewed launch.

14 CFR 25.933 - Reversing systems.

Code of Federal Regulations, 2010 CFR

2010-01-01

... analysis or testing, or both, for propeller systems that allow propeller blades to move from the flight low... reversal in flight the engine will produce no more than flight idle thrust. In addition, it must be shown... position; and (ii) The airplane is capable of continued safe flight and landing under any possible position...

14 CFR 25.933 - Reversing systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

... analysis or testing, or both, for propeller systems that allow propeller blades to move from the flight low... reversal in flight the engine will produce no more than flight idle thrust. In addition, it must be shown... position; and (ii) The airplane is capable of continued safe flight and landing under any possible position...

Tailoring Systems Engineering Projects for Small Satellite Missions

NASA Technical Reports Server (NTRS)

Horan, Stephen; Belvin, Keith

2013-01-01

NASA maintains excellence in its spaceflight systems by utilizing rigorous engineering processes based on over 50 years of experience. The NASA systems engineering process for flight projects described in NPR 7120.5E was initially developed for major flight projects. The design and development of low-cost small satellite systems does not entail the financial and risk consequences traditionally associated with spaceflight projects. Consequently, an approach is offered to tailoring of the processes such that the small satellite missions will benefit from the engineering rigor without overly burdensome overhead. In this paper we will outline the approaches to tailoring the standard processes for these small missions and describe how it will be applied in a proposed small satellite mission.

Emergency Flight Control Using Computer-Controlled Thrust

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Fullerton, C. Gordon; Stewart, James F.; Gilyard, Glenn B.; Conley, Joseph A.

1995-01-01

Propulsion Controlled Aircraft (PCA) systems are digital electronic control systems undergoing development to provide limited maneuvering ability through variations of individual engine thrusts in multiple-engine airplanes. Provide landing capability when control surfaces inoperable. Incorporated on existing and future airplanes that include digital engine controls, digital flight controls, and digital data buses, adding no weight for additional hardware to airplane. Possible to handle total failure of hydraulic system, depending on how surfaces respond to loss of hydraulic pressure, and broken control cables or linkages. Future airplanes incorporate data from Global Positioning System for guidance to any suitable emergency runway in world.

Video File - NASA Conducts 2nd RS-25 Engine Hot Fire of 2018 - 2018-02-01

NASA Image and Video Library

2018-02-01

NASA Conducts 2nd RS-25 Engine Hot Fire of 2018. A 365-second hot fire test on Feb. 1, 2018, at NASA’s Stennis Space Center in Mississippi marks the completion of “green run” testing, or flight certification, for all new RS-25 engine flight controllers slated for Exploration Mission-2, the first Space Launch System mission with astronauts on board. In addition to the flight controller, the Feb. 1 hot fire also marked the third test of a 3D printed pogo accumulator assembly for the RS-25 engine.

The History and Promise of Combined Cycle Engines for Access to Space Applications

NASA Technical Reports Server (NTRS)

Clark, Casie

2010-01-01

For the summer of 2010, I have been working in the Aerodynamics and Propulsion Branch at NASA Dryden Flight Research Center studying combined-cycle engines, a high speed propulsion concept. Combined cycle engines integrate multiple propulsion systems into a single engine capable of running in multiple modes. These different modes allow the engine to be extremely versatile and efficient in varied flight conditions. The two most common types of combined cycle engines are Rocket-Based Combined Cycle (RBCC) and Turbine Based Combined Cycle (TBCC). The RBCC essentially combines a rocket and ramjet engine, while the TBCC integrates a turbojet and ramjet1. These two engines are able to switch between different propulsion modes to achieve maximum performance. Extensive conceptual and ground test studies of RBCC engines have been undertaken; however, an RBCC engine has never, to my knowledge, been demonstrated in flight. RBCC engines are of particular interest because they could potentially power a reusable launch vehicle (RLV) into space. The TBCC has been flight tested and shown to be effective at reaching supersonic speeds, most notably in the SR-71 Blackbird2.

Ames Engineering Directorate

NASA Technical Reports Server (NTRS)

Phillips, Veronica J.

2017-01-01

The Ames Engineering Directorate is the principal engineering organization supporting aerospace systems and spaceflight projects at NASA's Ames Research Center in California's Silicon Valley. The Directorate supports all phases of engineering and project management for flight and mission projects-from R&D to Close-out-by leveraging the capabilities of multiple divisions and facilities.The Mission Design Center (MDC) has full end-to-end mission design capability with sophisticated analysis and simulation tools in a collaborative concurrent design environment. Services include concept maturity level (CML) maturation, spacecraft design and trades, scientific instruments selection, feasibility assessments, and proposal support and partnerships. The Engineering Systems Division provides robust project management support as well as systems engineering, mechanical and electrical analysis and design, technical authority and project integration support to a variety of programs and projects across NASA centers. The Applied Manufacturing Division turns abstract ideas into tangible hardware for aeronautics, spaceflight and science applications, specializing in fabrication methods and management of complex fabrication projects. The Engineering Evaluation Lab (EEL) provides full satellite or payload environmental testing services including vibration, temperature, humidity, immersion, pressure/altitude, vacuum, high G centrifuge, shock impact testing and the Flight Processing Center (FPC), which includes cleanrooms, bonded stores and flight preparation resources. The Multi-Mission Operations Center (MMOC) is composed of the facilities, networks, IT equipment, software and support services needed by flight projects to effectively and efficiently perform all mission functions, including planning, scheduling, command, telemetry processing and science analysis.

High Stability Engine Control (HISTEC): Flight Demonstration Results

NASA Technical Reports Server (NTRS)

Delaat, John C.; Southwick, Robert D.; Gallops, George W.; Orme, John S.

1998-01-01

Future aircraft turbine engines, both commercial and military, must be able to accommodate expected increased levels of steady-state and dynamic engine-face distortion. The current approach of incorporating sufficient design stall margin to tolerate these increased levels of distortion would significantly reduce performance. The High Stability Engine Control (HISTEC) program has developed technologies for an advanced, integrated engine control system that uses measurement- based estimates of distortion to enhance engine stability. The resulting distortion tolerant control reduces the required design stall margin, with a corresponding increase in performance and/or decrease in fuel burn. The HISTEC concept was successfully flight demonstrated on the F-15 ACTIVE aircraft during the summer of 1997. The flight demonstration was planned and carried out in two parts, the first to show distortion estimation, and the second to show distortion accommodation. Post-flight analysis shows that the HISTEC technologies are able to successfully estimate and accommodate distortion, transiently setting the stall margin requirement on-line and in real-time. Flight demonstration of the HISTEC technologies has significantly reduced the risk of transitioning the technology to tactical and commercial engines.

Video File - NASA Conducts Final RS-25 Rocket Engine Test of 2017

NASA Image and Video Library

2017-12-13

NASA engineers at Stennis Space Center capped a year of Space Launch System testing with a final RS-25 rocket engine hot fire on Dec. 13. The 470-second test on the A-1 Test Stand was a “green run” test of an RS-25 flight controller. The engine tested also included a large 3-D-printed part, a pogo accumulator assembly, scheduled for use on future RS-25 flight engines.

EC94-42645-9

NASA Image and Video Library

1994-06-27

The modified F-18 High Alpha Research Vehicle (HARV) carries out air flow studies on a flight from the Dryden Flight Research Center, Edwards, California. Using oil, researchers were able to track the air flow across the wing at different speeds and angles of attack. A thrust vectoring system had been installed on the engines' exhaust nozzles for the high angle of attack research program. The thrust vectoring system, linked to the aircraft's flight control system, moves a set of three paddles on each engine to redirect thrust for directional control and increased maneuverability at angles of attack at up to 70 degrees.

14 CFR 135.415 - Service difficulty reports.

Code of Federal Regulations, 2014 CFR

2014-01-01

...; (4) An exhaust system that causes damage during flight to the engine, adjacent structure, equipment... or aircraft structure occurs; (8) Engine shutdown during flight due to foreign object ingestion or... structure that requires major repair; (15) Cracks, permanent deformation, or corrosion of aircraft...

14 CFR 135.415 - Service difficulty reports.

Code of Federal Regulations, 2013 CFR

2013-01-01

...; (4) An exhaust system that causes damage during flight to the engine, adjacent structure, equipment... or aircraft structure occurs; (8) Engine shutdown during flight due to foreign object ingestion or... structure that requires major repair; (15) Cracks, permanent deformation, or corrosion of aircraft...

14 CFR 135.415 - Service difficulty reports.

Code of Federal Regulations, 2012 CFR

2012-01-01

...; (4) An exhaust system that causes damage during flight to the engine, adjacent structure, equipment... or aircraft structure occurs; (8) Engine shutdown during flight due to foreign object ingestion or... structure that requires major repair; (15) Cracks, permanent deformation, or corrosion of aircraft...

Republic P-47G Thunderbolt and the NACA Flight Operations Crew

NASA Image and Video Library

1944-03-21

The Flight Operations crew stands before a Republic P-47G Thunderbolt at the National Advisory Committee for Aeronautics (NACA) Aircraft Engine Research Laboratory in Cleveland, Ohio. The laboratory’s Flight Research Section was responsible for conducting a variety of research flights. During World War II most of the test flights complemented the efforts in ground-based facilities to improve engine cooling systems or study advanced fuel mixtures. The Republic P–47G was loaned to the laboratory to test NACA modifications to the Wright R–2800 engine’s cooling system at higher altitudes. The laboratory has always maintained a fleet of aircraft so different research projects were often conducted concurrently. The flight research program requires an entire section of personnel to accomplish its work. This staff generally consists of a flight operations group, which includes the section chief, pilots and administrative staff; a flight maintenance group with technicians and mechanics responsible for inspecting aircraft, performing checkouts and installing and removing flight instruments; and a flight research group that integrates the researchers’ experiments into the aircraft. The staff at the time of this March 1944 photograph included 3 pilots, 16 planning and analysis engineers, 36 mechanics and technicians, 10 instrumentation specialists, 6 secretaries and 5 computers.

Highly integrated digital engine control system on an F-15 airplane

NASA Technical Reports Server (NTRS)

Burcham, F. W., Jr.; Haering, E. A., Jr.

1984-01-01

The Highly Integrated Digital Electronic Control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine/airframe control systems. This system is being used on the F-15 airplane. An integrated flightpath management mode and an integrated adaptive engine stall margin mode are implemented into the system. The adaptive stall margin mode is a highly integrated mode in which the airplane flight conditions, the resulting inlet distortion, and the engine stall margin are continuously computed; the excess stall margin is used to uptrim the engine for more thrust. The integrated flightpath management mode optimizes the flightpath and throttle setting to reach a desired flight condition. The increase in thrust and the improvement in airplane performance is discussed.

Control Design for an Advanced Geared Turbofan Engine

NASA Technical Reports Server (NTRS)

Chapman, Jeffryes W.; Litt, Jonathan S.

2017-01-01

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 lbf thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 ft and from 0 to 0.8 Mach. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller integrated with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding system operational limits.

MD-11 PCA - First Landing at Edwards

NASA Technical Reports Server (NTRS)

1995-01-01

This McDonnell Douglas MD-11 transport aircraft approaches its first landing under engine power only on Aug. 29, 1995, at NASA's Dryden Flight Research Center, Edwards, California. The milestone flight, flown by NASA research pilot and former astronaut Gordon Fullerton, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. The Propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple--for pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

MD-11 PCA - First Landing at Edwards

NASA Technical Reports Server (NTRS)

1995-01-01

This McDonnell Douglas MD-11 approaches the first landing ever of a transport aircraft under engine power only on Aug. 29, 1995, at NASA's Dryden Flight Research Center, Edwards, California. The milestone flight, flown by NASA research pilot and former astronaut Gordon Fullerton, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when it normal control surfaces are disabled. The Propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple--for pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

Linear Aerospike SR-71 Experiment (LASRE) dumps water after first in-flight cold flow test

NASA Image and Video Library

1998-03-04

The NASA SR-71A successfully completed its first cold flow flight as part of the NASA/Rocketdyne/Lockheed Martin Linear Aerospike SR-71 Experiment (LASRE) at NASA's Dryden Flight Research Center, Edwards, California on March 4, 1998. During a cold flow flight, gaseous helium and liquid nitrogen are cycled through the linear aerospike engine to check the engine's plumbing system for leaks and to check the engine operating characterisitics. Cold-flow tests must be accomplished successfully before firing the rocket engine experiment in flight. The SR-71 took off at 10:16 a.m. PST. The aircraft flew for one hour and fifty-seven minutes, reaching a maximum speed of Mach 1.58 before landing at Edwards at 12:13 p.m. PST. "I think all in all we had a good mission today," Dryden LASRE Project Manager Dave Lux said. Flight crew member Bob Meyer agreed, saying the crew "thought it was a really good flight." Dryden Research Pilot Ed Schneider piloted the SR-71 during the mission. Lockheed Martin LASRE Project Manager Carl Meade added, "We are extremely pleased with today's results. This will help pave the way for the first in-flight engine data-collection flight of the LASRE."

14 CFR 33.68 - Induction system icing.

Code of Federal Regulations, 2010 CFR

2010-01-01

... Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION AIRCRAFT AIRWORTHINESS STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.68 Induction system icing. Each engine, with all icing protection systems operating, must— (a) Operate throughout its flight power...

14 CFR 33.68 - Induction system icing.

Code of Federal Regulations, 2011 CFR

2011-01-01

... Aeronautics and Space FEDERAL AVIATION ADMINISTRATION, DEPARTMENT OF TRANSPORTATION AIRCRAFT AIRWORTHINESS STANDARDS: AIRCRAFT ENGINES Design and Construction; Turbine Aircraft Engines § 33.68 Induction system icing. Each engine, with all icing protection systems operating, must— (a) Operate throughout its flight power...

Multicriteria Gain Tuning for Rotorcraft Flight Controls (also entitled The Development of the Conduit Advanced Control System Design and Evaluation Interface with a Case Study Application Fly by Wire Helicopter Design)

NASA Technical Reports Server (NTRS)

Biezad, Daniel

1997-01-01

Handling qualities analysis and control law design would seem to be naturally complimenting components of aircraft flight control system design, however these two closely coupled disciplines are often not well integrated in practice. Handling qualities engineers and control system engineers may work in separate groups within an aircraft company. Flight control system engineers and handling quality specialists may come from different backgrounds and schooling and are often not aware of the other group's research. Thus while the handling qualities specifications represent desired aircraft response characteristics, these are rarely incorporated directly in the control system design process. Instead modem control system design techniques are based on servo-loop robustness specifications, and simple representations of the desired control response. Comprehensive handling qualities analysis is often left until the end of the design cycle and performed as a check of the completed design for satisfactory performance. This can lead to costly redesign or less than satisfactory aircraft handling qualities when the flight testing phase is reached. The desire to integrate the fields of handling qualities and flight,control systems led to the development of the CONDUIT system. This tool facilitates control system designs that achieve desired handling quality requirements and servo-loop specifications in a single design process. With CONDUIT, the control system engineer is now able to directly design and control systems to meet the complete handling specifications. CONDUIT allows the designer to retain a preferred control law structure, but then tunes the system parameters to meet the handling quality requirements.

An Intelligent Propulsion Control Architecture to Enable More Autonomous Vehicle Operation

NASA Technical Reports Server (NTRS)

Litt, Jonathan S.; Sowers, T. Shane; Simon, Donald L.; Owen, A. Karl; Rinehart, Aidan W.; Chicatelli, Amy K.; Acheson, Michael J.; Hueschen, Richard M.; Spiers, Christopher W.

2018-01-01

This paper describes an intelligent propulsion control architecture that coordinates with the flight control to reduce the amount of pilot intervention required to operate the vehicle. Objectives of the architecture include the ability to: automatically recognize the aircraft operating state and flight phase; configure engine control to optimize performance with knowledge of engine condition and capability; enhance aircraft performance by coordinating propulsion control with flight control; and recognize off-nominal propulsion situations and to respond to them autonomously. The hierarchical intelligent propulsion system control can be decomposed into a propulsion system level and an individual engine level. The architecture is designed to be flexible to accommodate evolving requirements, adapt to technology improvements, and maintain safety.

Propulsion Flight-Test Fixture

NASA Technical Reports Server (NTRS)

Palumbo, Nate; Vachon, M. Jake; Richwine, Dave; Moes, Tim; Creech, Gray

2003-01-01

NASA Dryden Flight Research Center s new Propulsion Flight Test Fixture (PFTF), designed in house, is an airborne engine-testing facility that enables engineers to gather flight data on small experimental engines. Without the PFTF, it would be necessary to obtain such data from traditional wind tunnels, ground test stands, or laboratory test rigs. Traditionally, flight testing is reserved for the last phase of engine development. Generally, engines that embody new propulsion concepts are not put into flight environments until their designs are mature: in such cases, either vehicles are designed around the engines or else the engines are mounted in or on missiles. However, a captive carry capability of the PFTF makes it possible to test engines that feature air-breathing designs (for example, designs based on the rocket-based combined cycle) economically in subscale experiments. The discovery of unknowns made evident through flight tests provides valuable information to engine designers early in development, before key design decisions are made, thereby potentially affording large benefits in the long term. This is especially true in the transonic region of flight (from mach 0.9 to around 1.2), where it can be difficult to obtain data from wind tunnels and computational fluid dynamics. In January 2002, flight-envelope expansion to verify the design and capabilities of the PFTF was completed. The PFTF was flown on a specially equipped supersonic F-15B research testbed airplane, mounted on the airplane at a center-line attachment fixture, as shown in Figure 1. NASA s F-15B testbed has been used for several years as a flight-research platform. Equipped with extensive research air-data, video, and other instrumentation systems, the airplane carries externally mounted test articles. Traditionally, the majority of test articles flown have been mounted at the centerline tank-attachment fixture, which is a hard-point (essentially, a standardized weapon-mounting fixture). This hard-point has large weight margins, and, because it is located near the center of gravity of the airplane, the weight of equipment mounted there exerts a minimal effect on the stability and controllability of the airplane. The PFTF (see Figure 2) includes a one-piece aluminum structure that contains space for instrumentation, propellant tanks, and feed-system components. The PFTF also houses a force balance, on which is mounted the subscale engine or other experimental apparatus that is to be the subject of a flight test. The force balance measures a combination of inertial and aerodynamic forces and moments acting on the experimental apparatus.

Pilot-in-the-Loop Analysis of Propulsive-Only Flight Control Systems

NASA Technical Reports Server (NTRS)

Chou, Hwei-Lan; Biezad, Daniel J.

1996-01-01

Longitudinal control system architectures are presented which directly couple flight stick motions to throttle commands for a multi-engine aircraft. This coupling enables positive attitude control with complete failure of the flight control system. The architectures chosen vary from simple feedback gains to classical lead-lag compensators with and without prefilters. Each architecture is reviewed for its appropriateness for piloted flight. The control systems are then analyzed with pilot-in-the-loop metrics related to bandwidth required for landing. Results indicate that current and proposed bandwidth requirements should be modified for throttles only flight control. Pilot ratings consistently showed better ratings than predicted by analysis. Recommendations are made for more robust design and implementation. The use of Quantitative Feedback Theory for compensator design is discussed. Although simple and effective augmented control can be achieved in a wide variety of failed configurations, a few configuration characteristics are dominant for pilot-in-the-loop control. These characteristics will be tested in a simulator study involving failed flight controls for a multi-engine aircraft.

Quiet Clean Short-haul Experimental Engine (QCSEE) preliminary over-the-wing flight propulsion system analysis report

NASA Technical Reports Server (NTRS)

Howard, D. F.

1977-01-01

The preliminary design of the over-the-wing flight propulsion system installation and nacelle component and systems design features of a short-haul, powered lift aircraft are presented. Economic studies are also presented and show that high bypass, low pressure ratio turbofan engines have the potential of providing an economical propulsion system for achieving the very quiet aircraft noise level of 95 EPNdB on a 152.4 m sideline.

Design, analysis and control of large transports so that control of engine thrust can be used as a back-up of the primary flight controls. Ph.D. Thesis

NASA Technical Reports Server (NTRS)

Roskam, Jan; Ackers, Deane E.; Gerren, Donna S.

1995-01-01

A propulsion controlled aircraft (PCA) system has been developed at NASA Dryden Flight Research Center at Edwards Air Force Base, California, to provide safe, emergency landing capability should the primary flight control system of the aircraft fail. As a result of the successful PCA work being done at NASA Dryden, this project investigated the possibility of incorporating the PCA system as a backup flight control system in the design of a large, ultra-high capacity megatransport in such a way that flight path control using only the engines is not only possible, but meets MIL-Spec Level 1 or Level 2 handling quality requirements. An 800 passenger megatransport aircraft was designed and programmed into the NASA Dryden simulator. Many different analysis methods were used to evaluate the flying qualities of the megatransport while using engine thrust for flight path control, including: (1) Bode and root locus plot analysis to evaluate the frequency and damping ratio response of the megatransport; (2) analysis of actual simulator strip chart recordings to evaluate the time history response of the megatransport; and (3) analysis of Cooper-Harper pilot ratings by two NaSA test pilots.

Basic principles of flight test instrumentation engineering, volume 1, issue 2

NASA Technical Reports Server (NTRS)

Borek, Robert W., Sr. (Editor); Pool, A. (Editor)

1994-01-01

Volume 1 of the AG 300 series on 'Flight Test Instrumentation' gives a general introduction to the basic principles of flight test instrumentation. The other volumes in the series provide more detailed treatments of selected topics on flight test instrumentation. Volume 1, first published in 1974, has been used extensively as an introduction for instrumentation courses and symposia, as well as being a reference work on the desk of most flight test and instrumentation engineers. It is hoped that this second edition, fully revised, will be used with as much enthusiasm as the first edition. In this edition a flight test system is considered to include both the data collection and data processing systems. In order to obtain an optimal data flow, the overall design of these two subsystems must be carefully matched; the detail development and the operation may have to be done by separate groups of specialists. The main emphasis is on the large automated instrumentation systems used for the initial flight testing of modern military and civil aircraft. This is done because there, many of the problems, which are discussed here, are more critical. It does not imply, however, that smaller systems with manual data processing are no longer used. In general, the systems should be designed to provide the required results at the lowest possible cost. For many tests which require only a few parameters, relatively simple systems are justified, especially if no complex equipment is available to the user. Although many of the aspects discussed in this volume apply to both small and large systems, aspects of the smaller systems are mentioned only when they are of special interest. The volume has been divided into three main parts. Part 1 defines the main starting points for the design of a flight test instrumentation system, as seen from the points of view of the flight test engineer and the instrumentation engineer. In Part 2 the discussion is concentrated on those aspects which apply to each individual measuring channel, and in Part 3 the main emphasis is on the integration of the individual data channels into one data collection system and on those aspects of the data processing which apply to the complete system.

Computer-Aided Systems Engineering for Flight Research Projects Using a Workgroup Database

NASA Technical Reports Server (NTRS)

Mizukami, Masahi

2004-01-01

An online systems engineering tool for flight research projects has been developed through the use of a workgroup database. Capabilities are implemented for typical flight research systems engineering needs in document library, configuration control, hazard analysis, hardware database, requirements management, action item tracking, project team information, and technical performance metrics. Repetitive tasks are automated to reduce workload and errors. Current data and documents are instantly available online and can be worked on collaboratively. Existing forms and conventional processes are used, rather than inventing or changing processes to fit the tool. An integrated tool set offers advantages by automatically cross-referencing data, minimizing redundant data entry, and reducing the number of programs that must be learned. With a simplified approach, significant improvements are attained over existing capabilities for minimal cost. By using a workgroup-level database platform, personnel most directly involved in the project can develop, modify, and maintain the system, thereby saving time and money. As a pilot project, the system has been used to support an in-house flight experiment. Options are proposed for developing and deploying this type of tool on a more extensive basis.

Flight software issues in onboard automated planning: lessons learned on EO-1

NASA Technical Reports Server (NTRS)

Tran, Daniel; Chien, Steve; Rabideau, Gregg; Cichy, Benjamin

2004-01-01

This paper focuses on the onboard planner and scheduler CASPER, whose core planning engine is based on the ground system ASPEN. Given the challenges of developing flight software, we discuss several of the issues encountered in preparing the planner for flight, including reducing the code image size, determining what data to place within the engineering telemetry packet, and performing long term planning.

Flight Engineer Budarin uses a laptop computer in the SM during Expedition Six

NASA Image and Video Library

2003-03-21

ISS006-E-45279 (21 March 2003) --- Cosmonaut Nikolai M. Budarin, Expedition Six flight engineer, uses a computer as he talks on a communication system in the Zvezda Service Module on the International Space Station (ISS). Budarin represents Rosaviakosmos.

Flight Engineer Budarin is changing a part in the water recycling system in the SM

NASA Image and Video Library

2003-03-21

ISS006-E-45275 (21 March 2003) --- Cosmonaut Nikolai M. Budarin, Expedition Six flight engineer, holds a piece of hardware near a worktable in the Zvezda Service Module on the International Space Station (ISS). Budarin represents Rosaviakosmos.

Energy efficient engine flight propulsion system preliminary analysis and design report

NASA Technical Reports Server (NTRS)

Gardner, W. B.

1979-01-01

A flight propulsion system preliminary design was established that meets the program goals of at least a 12 percent reduction in thrust specific fuel consumption, at least a five percent reduction in direct operating cost, and one-half the performance deterioration rate of the most efficient current commercial engines. The engine provides a high probability of meeting the 1978 noise rule goal. Smoke and gaseous emissions defined by the EPA proposed standards for engines newly certified after 1 January 1981 are met with the exception of NOx, despite incorporation of all known NOx reduction technology.

X-33 Combustion-Wave Ignition System Tested

NASA Technical Reports Server (NTRS)

Liou, Larry C.

1999-01-01

The NASA Lewis Research Center, in cooperation with Rocketdyne, the Boeing Company, tested a novel rocket engine ignition system, called the combustion-wave ignition system, in its Research Combustion Laboratory. This ignition system greatly simplifies ignition in rocket engines that have a large number of combustors. The particular system tested was designed and fabricated by Rocketdyne for the national experimental spacecraft, X-33, which uses Rocketdyne s aerospike rocket engines. The goal of the tests was to verify the system design and define its operational characteristics. Results will contribute to the eventual successful flight of X-33. Furthermore, the combustion-wave ignition system, after it is better understood and refined on the basis of the test results and, later, flight-proven onboard X-33, could become an important candidate engine ignition system for our Nation s next-generation reusable launch vehicle.

Preparing for Flight Engine Test

NASA Image and Video Library

2015-11-04

The first RS-25 flight engine, engine No. 2059, is lifted onto the A-1 Test Stand at Stennis Space Center on Nov. 4, 2015. The engine was tested in early 2016 to certify it for use on NASA’s new Space Launch System (SLS). The SLS core stage will be powered by four RS-25 engines, all tested at Stennis Space Center. NASA is developing the SLS to carry humans deeper into space than ever before, including on a journey to Mars.

Systems Engineering in NASA's R&TD Programs

NASA Technical Reports Server (NTRS)

Jones, Harry

2005-01-01

Systems engineering is largely the analysis and planning that support the design, development, and operation of systems. The most common application of systems engineering is in guiding systems development projects that use a phased process of requirements, specifications, design, and development. This paper investigates how systems engineering techniques should be applied in research and technology development programs for advanced space systems. These programs should include anticipatory engineering of future space flight systems and a project portfolio selection process, as well as systems engineering for multiple development projects.

Space Shuttle Main Engine - The Relentless Pursuit of Improvement

NASA Technical Reports Server (NTRS)

VanHooser, Katherine P.; Bradley, Douglas P.

2011-01-01

The Space Shuttle Main Engine (SSME) is the only reusable large liquid rocket engine ever developed. The specific impulse delivered by the staged combustion cycle, substantially higher than previous rocket engines, minimized volume and weight for the integrated vehicle. The dual pre-burner configuration permitted precise mixture ratio and thrust control while the fully redundant controller and avionics provided a very high degree of system reliability and health diagnosis. The main engine controller design was the first rocket engine application to incorporate digital processing. The engine was required to operate at a high chamber pressure to minimize engine volume and weight. Power level throttling was required to minimize structural loads on the vehicle early in flight and acceleration levels on the crew late in ascent. Fatigue capability, strength, ease of assembly and disassembly, inspectability, and materials compatibility were all major considerations in achieving a fully reusable design. During the multi-decade program the design evolved substantially using a series of block upgrades. A number of materials and manufacturing challenges were encountered throughout SSME s history. Significant development was required for the final configuration of the high pressure turbopumps. Fracture control was implemented to assess life limits of critical materials and components. Survival in the hydrogen environment required assessment of hydrogen embrittlement. Instrumentation systems were a challenge due to the harsh thermal and dynamic environments within the engine. Extensive inspection procedures were developed to assess the engine components between flights. The Space Shuttle Main Engine achieved a remarkable flight performance record. All flights were successful with only one mission requiring an ascent abort condition, which still resulted in an acceptable orbit and mission. This was achieved in large part via extensive ground testing to fully characterize performance and to establish acceptable life limits. During the program over a million seconds of accumulated test and flight time was achieved. Post flight inspection and assessment was a key part of assuring proper performance of the flight hardware. By the end of the program the predicted reliability had improved by a factor of four. These unique challenges, evolution of the design, and the resulting reliability will be discussed in this paper.

NASA on a Strong Roll in Preparing Space Launch System Flight Engines

NASA Image and Video Library

2017-08-09

NASA is on a roll when it comes to testing engines for its new Space Launch System (SLS) rocket that will send astronauts to deep-space destinations, including Mars. Just two weeks after the third test of a new RS-25 engine flight controller, the space agency recorded its fourth full-duration controller test Aug. 9 at Stennis Space Center near Bay St. Louis, Mississippi. Engineers conducted a 500-second test of the RS-25 engine controller on the A-1 Test Stand at Stennis. The test involved installing the controller on an RS-25 development engine and firing it in the same manner, and for the same length of time, as needed during an actual SLS launch. The test marked another milestone toward launch of the first integrated flight of the SLS rocket and Orion crew vehicle. Exploration Mission-1 will be an uncrewed mission into lunar orbit, designed to provide a final check-out test of rocket and Orion capabilities before astronauts are returned to deep space. The SLS rocket will be powered at launch by four RS-25 engines, providing a combined 2 million pounds of thrust, and with a pair of solid rocket boosters, providing more than 8 million pounds of total thrust. The RS-25 engines for the initial SLS flights are former space shuttle main engines that are now being used to launch the larger and heavier SLS rocket and with the new controller. The controller is a critical component that operates as the engine “brain” that communicates with SLS flight computers to receive operation performance commands and to provide diagnostic data on engine health and status. Engineers conducted early prototype tests at Stennis to collect data for development of the new controller by NASA, RS-25 prime contractor Aerojet Rocketdyne and subcontractor Honeywell. Testing of actual flight controllers began at Stennis in March. NASA is testing all controllers and engines designated for the EM-1 flight at Stennis. It also will test the SLS core stage for the flight at Stennis, which will involve installing the stage on the B-2 Test Stand and firing its four RS-25 engines simultaneously, as during an actual launch. RS-25 tests at Stennis are conducted by a team of NASA, Aerojet Rocketdyne and Syncom Space Services engineers and operators. Aerojet Rocketdyne is the RS-25 prime contractor. Syncom Space Services is the prime contractor for Stennis facilities and operations.

Key Reliability Drivers of Liquid Propulsion Engines and A Reliability Model for Sensitivity Analysis

NASA Technical Reports Server (NTRS)

Huang, Zhao-Feng; Fint, Jeffry A.; Kuck, Frederick M.

2005-01-01

This paper is to address the in-flight reliability of a liquid propulsion engine system for a launch vehicle. We first establish a comprehensive list of system and sub-system reliability drivers for any liquid propulsion engine system. We then build a reliability model to parametrically analyze the impact of some reliability parameters. We present sensitivity analysis results for a selected subset of the key reliability drivers using the model. Reliability drivers identified include: number of engines for the liquid propulsion stage, single engine total reliability, engine operation duration, engine thrust size, reusability, engine de-rating or up-rating, engine-out design (including engine-out switching reliability, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction), propellant specific hazards, engine start and cutoff transient hazards, engine combustion cycles, vehicle and engine interface and interaction hazards, engine health management system, engine modification, engine ground start hold down with launch commit criteria, engine altitude start (1 in. start), Multiple altitude restart (less than 1 restart), component, subsystem and system design, manufacturing/ground operation support/pre and post flight check outs and inspection, extensiveness of the development program. We present some sensitivity analysis results for the following subset of the drivers: number of engines for the propulsion stage, single engine total reliability, engine operation duration, engine de-rating or up-rating requirements, engine-out design, catastrophic fraction, preventable failure fraction, unnecessary shutdown fraction, and engine health management system implementation (basic redlines and more advanced health management systems).

cFE/CFS (Core Flight Executive/Core Flight System)

NASA Technical Reports Server (NTRS)

Wildermann, Charles P.

2008-01-01

This viewgraph presentation describes in detail the requirements and goals of the Core Flight Executive (cFE) and the Core Flight System (CFS). The Core Flight Software System is a mission independent, platform-independent, Flight Software (FSW) environment integrating a reusable core flight executive (cFE). The CFS goals include: 1) Reduce time to deploy high quality flight software; 2) Reduce project schedule and cost uncertainty; 3) Directly facilitate formalized software reuse; 4) Enable collaboration across organizations; 5) Simplify sustaining engineering (AKA. FSW maintenance); 6) Scale from small instruments to System of Systems; 7) Platform for advanced concepts and prototyping; and 7) Common standards and tools across the branch and NASA wide.

Subsonic flight test evaluation of a propulsion system parameter estimation process for the F100 engine

NASA Technical Reports Server (NTRS)

Orme, John S.; Gilyard, Glenn B.

1992-01-01

Integrated engine-airframe optimal control technology may significantly improve aircraft performance. This technology requires a reliable and accurate parameter estimator to predict unmeasured variables. To develop this technology base, NASA Dryden Flight Research Facility (Edwards, CA), McDonnell Aircraft Company (St. Louis, MO), and Pratt & Whitney (West Palm Beach, FL) have developed and flight-tested an adaptive performance seeking control system which optimizes the quasi-steady-state performance of the F-15 propulsion system. This paper presents flight and ground test evaluations of the propulsion system parameter estimation process used by the performance seeking control system. The estimator consists of a compact propulsion system model and an extended Kalman filter. The extended Laman filter estimates five engine component deviation parameters from measured inputs. The compact model uses measurements and Kalman-filter estimates as inputs to predict unmeasured propulsion parameters such as net propulsive force and fan stall margin. The ability to track trends and estimate absolute values of propulsion system parameters was demonstrated. For example, thrust stand results show a good correlation, especially in trends, between the performance seeking control estimated and measured thrust.

Flight-vehicle structures education in the US: Assessment and recommendations

NASA Technical Reports Server (NTRS)

Noor, Ahmed K.

1987-01-01

An assessment is made of the technical contents of flight-vehicle structures curricula at 41 U.S. universities with accredited aerospace engineering programs. The assessment is based on the technical needs for new and projected aeronautical and space systems as well as on the likely characteristics of the aerospace engineering work environment. A number of deficiencies and areas of concern are identified and recommendations are presented for enhancing the effectiveness of flight-vehicle structures education. A number of government supported programs that can help aerospace engineering education are listed in the appendix.

Implementation of Insight Responsibilities in Process Engineering

NASA Technical Reports Server (NTRS)

Osborne, Deborah M.

1997-01-01

This report describes an approach for evaluating flight readiness (COFR) and contractor performance evaluation (award fee) as part of the insight role of NASA Process Engineering at Kennedy Space Center. Several evaluation methods are presented, including systems engineering evaluations and use of systems performance data. The transition from an oversight function to the insight function is described. The types of analytical tools appropriate for achieving the flight readiness and contractor performance evaluation goals are described and examples are provided. Special emphasis is placed upon short and small run statistical quality control techniques. Training requirements for system engineers are delineated. The approach described herein would be equally appropriate in other directorates at Kennedy Space Center.

Propellant Feed Subsystem for the X-34 Main Propulsion System

NASA Technical Reports Server (NTRS)

McDonald, J. P.; Minor, R. B.; Knight, K. C.; Champion, R. H., Jr.; Russell, F. J., Jr.

1998-01-01

The Orbital Sciences Corporation X-34 vehicle demonstrates technologies and operations key to future reusable launch vehicles. The general flight performance goal of this unmanned rocket plane is Mach 8 flight at an altitude of 250,000 feet. The Main Propulsion System supplies liquid propellants to the main engine, which provides the primary thrust for attaining mission goals. Major NMS design and operational goals are aircraft-like ground operations, quick turnaround between missions, and low initial/operational costs. This paper reviews major design and analysis aspects of the X-34 propellant feed subsystem of the X-34 Main Propulsion System. Topics include system requirements, system design, the integration of flight and feed system performance, propellant acquisition at engine start, and propellant tank terminal drain.

Research and Technology Report. Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Soffen, Gerald (Editor); Truszkowski, Walter (Editor); Ottenstein, Howard (Editor); Frost, Kenneth (Editor); Maran, Stephen (Editor); Walter, Lou (Editor); Brown, Mitch (Editor)

1996-01-01

This issue of Goddard Space Flight Center's annual report highlights the importance of mission operations and data systems covering mission planning and operations; TDRSS, positioning systems, and orbit determination; ground system and networks, hardware and software; data processing and analysis; and World Wide Web use. The report also includes flight projects, space sciences, Earth system science, and engineering and materials.

The High Stability Engine Control (HISTEC) Program: Flight Demonstration Phase

NASA Technical Reports Server (NTRS)

DeLaat, John C.; Southwick, Robert D.; Gallops, George W.; Orme, John S.

1998-01-01

Future aircraft turbine engines, both commercial and military, must be able to accommodate expected increased levels of steady-state and dynamic engine-face distortion. The current approach of incorporating sufficient design stall margin to tolerate these increased levels of distortion would significantly reduce performance. The objective of the High Stability Engine Control (HISTEC) program is to design, develop, and flight-demonstrate an advanced, integrated engine control system that uses measurement-based estimates of distortion to enhance engine stability. The resulting distortion tolerant control reduces the required design stall margin, with a corresponding increase in performance and decrease in fuel burn. The HISTEC concept has been developed and was successfully flight demonstrated on the F-15 ACTIVE aircraft during the summer of 1997. The flight demonstration was planned and carried out in two phases, the first to show distortion estimation, and the second to show distortion accommodation. Post-flight analysis shows that the HISTEC technologies are able to successfully estimate and accommodate distortion, transiently setting the stall margin requirement on-line and in real-time. This allows the design stall margin requirement to be reduced, which in turn can be traded for significantly increased performance and/or decreased weight. Flight demonstration of the HISTEC technologies has significantly reduced the risk of transitioning the technology to tactical and commercial engines.

Shuttle Radar Topography Mission (SRTM) Flight System Design and Operations Overview

NASA Technical Reports Server (NTRS)

Shen, Yuhsyen; Shaffer, Scott J.; Jordan, Rolando L.

2000-01-01

This paper provides an overview of the Shuttle Radar Topography Mission (SRTM), with emphasis on flight system implementation and mission operations from systems engineering perspective. Successfully flown in February, 2000, the SRTM's primary payload consists of several subsystems to form the first spaceborne dual-frequency (C-band and X-band) fixed baseline interferometric synthetic aperture radar (InSAR) system, with the mission objective to acquire data sets over 80% of Earth's landmass for height reconstruction. The paper provides system architecture, unique design features, engineering budgets, design verification, in-flight checkout and data acquisition of the SRTM payload, in particular for the C-band system. Mission operation and post-mission data processing activities are also presented. The complexity of the SRTM as a system, the ambitious mission objective, the demanding requirements and the high interdependency between multi-disciplined subsystems posed many challenges. The engineering experience and the insight thus gained have important implications for future spaceborne interferometric SAR mission design and implementation.

The development and use of a computer-interactive data acquisition and display system in a flight environment

NASA Technical Reports Server (NTRS)

Bever, G. A.

1981-01-01

The flight test data requirements at the NASA Dryden Flight Research Center increased in complexity, and more advanced instrumentation became necessary to accomplish mission goals. This paper describes the way in which an airborne computer was used to perform real-time calculations on critical flight test parameters during a flight test on a winglet-equipped KC-135A aircraft. With the computer, an airborne flight test engineer can select any sensor for airborne display in several formats, including engineering units. The computer is able to not only calculate values derived from the sensor outputs but also to interact with the data acquisition system. It can change the data cycle format and data rate, and even insert the derived values into the pulse code modulation (PCM) bit stream for recording.

Rocket Engine Health Management: Early Definition of Critical Flight Measurements

NASA Technical Reports Server (NTRS)

Christenson, Rick L.; Nelson, Michael A.; Butas, John P.

2003-01-01

The NASA led Space Launch Initiative (SLI) program has established key requirements related to safety, reliability, launch availability and operations cost to be met by the next generation of reusable launch vehicles. Key to meeting these requirements will be an integrated vehicle health management ( M) system that includes sensors, harnesses, software, memory, and processors. Such a system must be integrated across all the vehicle subsystems and meet component, subsystem, and system requirements relative to fault detection, fault isolation, and false alarm rate. The purpose of this activity is to evolve techniques for defining critical flight engine system measurements-early within the definition of an engine health management system (EHMS). Two approaches, performance-based and failure mode-based, are integrated to provide a proposed set of measurements to be collected. This integrated approach is applied to MSFC s MC-1 engine. Early identification of measurements supports early identification of candidate sensor systems whose design and impacts to the engine components must be considered in engine design.

Energy Efficient Engine: Flight propulsion system final design and analysis

NASA Technical Reports Server (NTRS)

Davis, Donald Y.; Stearns, E. Marshall

1985-01-01

The Energy Efficient Engine (E3) is a NASA program to create fuel saving technology for future transport engines. The Flight Propulsion System (FPS) is the engine designed to achieve E3 goals. Achieving these goals required aerodynamic, mechanical and system technologies advanced beyond that of current production engines. These technologies were successfully demonstrated in component rigs, a core engine and a turbofan ground test engine. The design and benefits of the FPS are presented. All goals for efficiency, environmental considerations, and economic payoff were met. The FPS has, at maximum cruise, 10.67 km (35,000 ft), M0.8, standard day, a 16.9 percent lower installed specific fuel consumption than a CF6-50C. It provides an 8.6 percent reduction in direct operating cost for a short haul domestic transport and a 16.2 percent reduction for an international long distance transport.

Control Design for an Advanced Geared Turbofan Engine

NASA Technical Reports Server (NTRS)

Chapman, Jeffryes W.; Litt, Jonathan S.

2017-01-01

This paper describes the design process for the control system of an advanced geared turbofan engine. This process is applied to a simulation that is representative of a 30,000 pound-force thrust class concept engine with two main spools, ultra-high bypass ratio, and a variable area fan nozzle. Control system requirements constrain the non-linear engine model as it operates throughout its flight envelope of sea level to 40,000 feet and from 0 to 0.8 Mach. The purpose of this paper is to review the engine control design process for an advanced turbofan engine configuration. The control architecture selected for this project was developed from literature and reflects a configuration that utilizes a proportional integral controller with sets of limiters that enable the engine to operate safely throughout its flight envelope. Simulation results show the overall system meets performance requirements without exceeding operational limits.

Early Program Development

NASA Image and Video Library

2004-04-15

This artist's concept illustrates the NERVA (Nuclear Engine for Rocket Vehicle Application) engine's hot bleed cycle in which a small amount of hydrogen gas is diverted from the thrust nozzle, thus eliminating the need for a separate system to drive the turbine. The NERVA engine, based on KIWI nuclear reactor technology, would power a RIFT (Reactor-In-Flight-Test) nuclear stage, for which the Marshall Space Flight Center had development responsibility.

Space flight hazards catalog

NASA Technical Reports Server (NTRS)

1975-01-01

The most significant hazards identified on manned space flight programs are listed. This summary is of special value to system safety engineers in developing safety checklists and otherwise tailoring safety tasks to specific systems and subsystems.

Advanced Concept

NASA Image and Video Library

2002-01-01

An artist's rendering of the air-breathing, hypersonic X-43B, the third and largest of NASA's Hyper-X series flight demonstrators, which could fly later this decade. Revolutionizing the way we gain access to space is NASA's primary goal for the Hypersonic Investment Area, managed for NASA by the Advanced Space Transportation Program at the Marshall Space Flight Center in Huntsville, Alabama. The Hypersonic Investment area, which includes leading-edge partners in industry and academia, will support future generation reusable vehicles and improved access to space. These technology demonstrators, intended for flight testing by decade's end, are expected to yield a new generation of vehicles that routinely fly about 100,000 feet above Earth's surface and reach sustained speeds in excess of Mach 5 (3,750 mph), the point at which "supersonic" flight becomes "hypersonic" flight. The flight demonstrators, the Hyper-X series, will be powered by air-breathing rocket or turbine-based engines, and ram/scramjets. Air-breathing engines, known as combined-cycle systems, achieve their efficiency gains over rocket systems by getting their oxygen for combustion from the atmosphere, as opposed to a rocket that must carry its oxygen. Once a hypersonic vehicle has accelerated to more than twice the speed of sound, the turbine or rockets are turned off, and the engine relies solely on oxygen in the atmosphere to burn fuel. When the vehicle has accelerated to more than 10 to 15 times the speed of sound, the engine converts to a conventional rocket-powered system to propel the craft into orbit or sustain it to suborbital flight speed. NASA's series of hypersonic flight demonstrators includes three air-breathing vehicles: the X-43A, X-43B and X-43C.

Design, analysis, and control of large transport aircraft utilizing engine thrust as a backup system for the primary flight controls

NASA Technical Reports Server (NTRS)

Gerren, Donna S.

1993-01-01

A review of accidents that involved the loss of hydraulic flight control systems serves as an introduction to this project. In each of the accidents--involving transport aircraft such as the DC-10, the C-5A, the L-1011, and the Boeing 747--the flight crew attempted to control the aircraft by means of thrust control. Although these incidents had tragic endings, in the absence of control power due to primary control system failure, control power generated by selective application of engine thrust has proven to be a viable alternative. NASA Dryden has demonstrated the feasibility of controlling an aircraft during level flight, approach, and landing conditions using an augmented throttles-only control system. This system has been successfully flown in the flight test simulator for the B-720 passenger transport and the F-15 air superiority fighter and in actual flight tests for the F-15 aircraft. The Douglas Aircraft Company is developing a similar system for the MD-11 aircraft. The project's ultimate goal is to provide data for the development of thrust control systems for mega-transports (600+ passengers).

Systems Engineering Management Plan NASA Traffic Aware Planner Integration Into P-180 Airborne Test-Bed

NASA Technical Reports Server (NTRS)

Maris, John

2015-01-01

NASA's Traffic Aware Planner (TAP) is a cockpit decision support tool that provides aircrew with vertical and lateral flight-path optimizations with the intent of achieving significant fuel and time savings, while automatically avoiding traffic, weather, and restricted airspace conflicts. A key step towards the maturation and deployment of TAP concerned its operational evaluation in a representative flight environment. This Systems Engineering Management Plan (SEMP) addresses the test-vehicle design, systems integration, and flight-test planning for the first TAP operational flight evaluations, which were successfully completed in November 2013. The trial outcomes are documented in the Traffic Aware Planner (TAP) flight evaluation paper presented at the 14th AIAA Aviation Technology, Integration, and Operations Conference, Atlanta, GA. (AIAA-2014-2166, Maris, J. M., Haynes, M. A., Wing, D. J., Burke, K. A., Henderson, J., & Woods, S. E., 2014).

Propulsion System for Very High Altitude Subsonic Unmanned Aircraft

NASA Technical Reports Server (NTRS)

Bents, David J.; Mockler, Ted; Maldonado, Jaime; Harp, James L., Jr.; King, Joseph F.; Schmitz, Paul C.

1998-01-01

This paper explains why a spark ignited gasoline engine, intake pressurized with three cascaded stages of turbocharging, was selected to power NASA's contemplated next generation of high altitude atmospheric science aircraft. Beginning with the most urgent science needs (the atmospheric sampling mission) and tracing through the mission requirements which dictate the unique flight regime in which this aircraft has to operate (subsonic flight at greater then 80 kft) we briefly explore the physical problems and constraints, the available technology options and the cost drivers associated with developing a viable propulsion system for this highly specialized aircraft. The paper presents the two available options (the turbojet and the turbocharged spark ignited engine) which are discussed and compared in the context of the flight regime. We then show how the unique nature of the sampling mission, coupled with the economic considerations pursuant to aero engine development, point to the spark ignited engine as the only cost effective solution available. Surprisingly, this solution compares favorably with the turbojet in the flight regime of interest. Finally, some remarks are made about NASA's present state of development, and future plans to flight demonstrate the three stage turbocharged powerplant.

14 CFR 63.42 - Flight engineer certificate issued on basis of a foreign flight engineer license.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 2 2013-01-01 2013-01-01 false Flight engineer certificate issued on basis of a foreign flight engineer license. 63.42 Section 63.42 Aeronautics and Space FEDERAL AVIATION... PILOTS Flight Engineers § 63.42 Flight engineer certificate issued on basis of a foreign flight engineer...

14 CFR 63.42 - Flight engineer certificate issued on basis of a foreign flight engineer license.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 2 2011-01-01 2011-01-01 false Flight engineer certificate issued on basis of a foreign flight engineer license. 63.42 Section 63.42 Aeronautics and Space FEDERAL AVIATION... PILOTS Flight Engineers § 63.42 Flight engineer certificate issued on basis of a foreign flight engineer...

14 CFR 63.42 - Flight engineer certificate issued on basis of a foreign flight engineer license.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 2 2012-01-01 2012-01-01 false Flight engineer certificate issued on basis of a foreign flight engineer license. 63.42 Section 63.42 Aeronautics and Space FEDERAL AVIATION... PILOTS Flight Engineers § 63.42 Flight engineer certificate issued on basis of a foreign flight engineer...

14 CFR 63.42 - Flight engineer certificate issued on basis of a foreign flight engineer license.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 2 2014-01-01 2014-01-01 false Flight engineer certificate issued on basis of a foreign flight engineer license. 63.42 Section 63.42 Aeronautics and Space FEDERAL AVIATION... PILOTS Flight Engineers § 63.42 Flight engineer certificate issued on basis of a foreign flight engineer...

14 CFR 63.42 - Flight engineer certificate issued on basis of a foreign flight engineer license.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 2 2010-01-01 2010-01-01 false Flight engineer certificate issued on basis of a foreign flight engineer license. 63.42 Section 63.42 Aeronautics and Space FEDERAL AVIATION... PILOTS Flight Engineers § 63.42 Flight engineer certificate issued on basis of a foreign flight engineer...

RDD-100 and the systems engineering process

NASA Technical Reports Server (NTRS)

Averill, Robert D.

1994-01-01

An effective systems engineering approach applied through the project life cycle can help Langley produce a better product. This paper demonstrates how an enhanced systems engineering process for in-house flight projects assures that each system will achieve its goals with quality performance and within planned budgets and schedules. This paper also describes how the systems engineering process can be used in combination with available software tools.

Process Based on SysML for New Launchers System and Software Developments

NASA Astrophysics Data System (ADS)

Hiron, Emmanuel; Miramont, Philippe

2010-08-01

The purpose of this paper is to present the Astrium-ST engineering process based on SysML. This process is currently set-up in the frame of common CNES /Astrium-ST R&T studies related to the Ariane 5 electrical system and flight software modelling. The tool used to set up this process is Rhapsody release 7.3 from IBM-Software firm [1]. This process focuses on the system engineering phase dedicated to Software with the objective to generate both System documents (sequential system design and flight control) and Software specifications.

A Data Filter for Identifying Steady-State Operating Points in Engine Flight Data for Condition Monitoring Applications

NASA Technical Reports Server (NTRS)

Simon, Donald L.; Litt, Jonathan S.

2010-01-01

This paper presents an algorithm that automatically identifies and extracts steady-state engine operating points from engine flight data. It calculates the mean and standard deviation of select parameters contained in the incoming flight data stream. If the standard deviation of the data falls below defined constraints, the engine is assumed to be at a steady-state operating point, and the mean measurement data at that point are archived for subsequent condition monitoring purposes. The fundamental design of the steady-state data filter is completely generic and applicable for any dynamic system. Additional domain-specific logic constraints are applied to reduce data outliers and variance within the collected steady-state data. The filter is designed for on-line real-time processing of streaming data as opposed to post-processing of the data in batch mode. Results of applying the steady-state data filter to recorded helicopter engine flight data are shown, demonstrating its utility for engine condition monitoring applications.

Design, analysis, and control of a large transport aircraft utilizing selective engine thrust as a backup system for the primary flight control. Ph.D. Thesis

NASA Technical Reports Server (NTRS)

Gerren, Donna S.

1995-01-01

A study has been conducted to determine the capability to control a very large transport airplane with engine thrust. This study consisted of the design of an 800-passenger airplane with a range of 5000 nautical miles design and evaluation of a flight control system, and design and piloted simulation evaluation of a thrust-only backup flight control system. Location of the four wing-mounted engines was varied to optimize the propulsive control capability, and the time constant of the engine response was studied. The goal was to provide level 1 flying qualities. The engine location and engine time constant did not have a large effect on the control capability. The airplane design did meet level 1 flying qualities based on frequencies, damping ratios, and time constants in the longitudinal and lateral-directional modes. Project pilots consistently rated the flying qualities as either level 1 or level 2 based on Cooper-Harper ratings. However, because of the limited control forces and moments, the airplane design fell short of meeting the time required to achieve a 30 deg bank and the time required to respond a control input.

The use of an automated flight test management system in the development of a rapid-prototyping flight research facility

NASA Technical Reports Server (NTRS)

Duke, Eugene L.; Hewett, Marle D.; Brumbaugh, Randal W.; Tartt, David M.; Antoniewicz, Robert F.; Agarwal, Arvind K.

1988-01-01

An automated flight test management system (ATMS) and its use to develop a rapid-prototyping flight research facility for artificial intelligence (AI) based flight systems concepts are described. The ATMS provides a flight test engineer with a set of tools that assist in flight planning and simulation. This system will be capable of controlling an aircraft during the flight test by performing closed-loop guidance functions, range management, and maneuver-quality monitoring. The rapid-prototyping flight research facility is being developed at the Dryden Flight Research Facility of the NASA Ames Research Center (Ames-Dryden) to provide early flight assessment of emerging AI technology. The facility is being developed as one element of the aircraft automation program which focuses on the qualification and validation of embedded real-time AI-based systems.

NASA Hispanic Heritage Month Employee Profile- Gustavo Martinez - Marshall Space Flight Center

NASA Image and Video Library

2016-10-19

In observance of National Hispanic Heritage Month, Gustavo Martinez, a propulsion engineer at NASA’s Marshall Space Flight Center, is featured in this video profile. Martinez, a first-generation American of Mexican descent, earned his bachelors and masters in mechanical engineering from the University of Texas at El Paso. He works in the Liquid Engine System Branch of Marshall’s Propulsion Systems Department, supporting RS-25 engine systems analysis and test preparations for NASA’s Space Launch System. National Hispanic Heritage Month honors the cultures and contributions of Americans whose ancestors originated from Spain, Mexico, the Caribbean and Central and South America. The observation started in 1968 as Hispanic Heritage Week under President Lyndon Johnson and was expanded into law by President Ronald Reagan in 1988.

X-43C Plans and Status

NASA Technical Reports Server (NTRS)

Moses, Paul L.

2003-01-01

X-43C Project is a hypersonic flight demonstration being executed as a collaboration between the National Aeronautics and Space Administration (NASA) and the United States Air Force (USAF). X-43C will expand the hypersonic flight envelope for air breathing engines beyond the history making efforts of the Hyper-X Program (X-43A). X-43C will demonstrate sustained accelerating flight during three flight tests of expendable X-43C Demonstrator Vehicles (DVs). The approximately 16-foot long X-43C DV will be boosted to the starting test conditions, separate from the booster, and accelerate from Mach 5 to Mach 7 under its own power and autonomous control. The DVs are to be powered by a liquid hydrocarbon-fueled, fuel-cooled, dual-mode, airframe integrated scramjet engine system developed under the USAF HyTech Program. The Project is managed by NASA Langley Research Center as part of NASA s Next Generation Launch Technology Program. Flight tests will be conducted by NASA Dryden Flight Research Center over water off the coast of California in the Pacific Test Range. The NASA/USAF/industry project is a natural extension of the Hyper-X Program (X-43A), which will demonstrate short duration ( 10 seconds) gaseous hydrogen-fueled scramjet powered flight at Mach 7 and Mach 10 using a heavyweight, largely heat sink construction, experimental engine. The X-43C Project will demonstrate sustained accelerating flight from Mach 5 to Mach 7 ( 4 minutes) using a flight-weight, fuel-cooled, scramjet engine powered by much denser liquid hydrocarbon fuel. The X-43C DV design flows from integrating USAF HyTech developed engine technologies with a NASA Air Breathing Launch Vehicle accelerator-class configuration and Hyper-X heritage vehicle systems designs. This paper describes the X-43C Project and provides background for NASA s current hypersonic flight demonstration efforts.

Auto-Coding UML Statecharts for Flight Software

NASA Technical Reports Server (NTRS)

Benowitz, Edward G; Clark, Ken; Watney, Garth J.

2006-01-01

Statecharts have been used as a means to communicate behaviors in a precise manner between system engineers and software engineers. Hand-translating a statechart to code, as done on some previous space missions, introduces the possibility of errors in the transformation from chart to code. To improve auto-coding, we have developed a process that generates flight code from UML statecharts. Our process is being used for the flight software on the Space Interferometer Mission (SIM).

Test Report for NASA MSFC Support of the Linear Aerospike SR-71 Experiment (LASRE)

NASA Technical Reports Server (NTRS)

Elam, S. K.

2000-01-01

The Linear Aerospike SR-71 Experiment (LASRE) was performed in support of the Reusable Launch Vehicle (RLV) program to help develop a linear aerospike engine. The objective of this program was to operate a small aerospike engine at various speeds and altitudes to determine how slipstreams affect the engine's performance. The joint program between government and industry included NASA!s Dryden Flight Research Center, The Air Force's Phillips Laboratory, NASA's Marshall Space Flight Center, Lockheed Martin Skunkworks, Lockheed-Martin Astronautics, and Rocketdyne Division of Boeing North American. Ground testing of the LASRE engine produced two successful hot-fire tests, along with numerous cold flows to verify sequencing and operation before mounting the assembly on the SR-71. Once installed on the aircraft, flight testing performed several cold flows on the engine system at altitudes ranging from 30,000 to 50,000 feet and Mach numbers ranging from 0.9 to 1.5. The program was terminated before conducting hot-fires in flight because excessive leaks in the propellant supply systems could not be fixed to meet required safety levels without significant program cost and schedule impacts.

Health management and controls for Earth-to-orbit propulsion systems

NASA Astrophysics Data System (ADS)

Bickford, R. L.

1995-03-01

Avionics and health management technologies increase the safety and reliability while decreasing the overall cost for Earth-to-orbit (ETO) propulsion systems. New ETO propulsion systems will depend on highly reliable fault tolerant flight avionics, advanced sensing systems and artificial intelligence aided software to ensure critical control, safety and maintenance requirements are met in a cost effective manner. Propulsion avionics consist of the engine controller, actuators, sensors, software and ground support elements. In addition to control and safety functions, these elements perform system monitoring for health management. Health management is enhanced by advanced sensing systems and algorithms which provide automated fault detection and enable adaptive control and/or maintenance approaches. Aerojet is developing advanced fault tolerant rocket engine controllers which provide very high levels of reliability. Smart sensors and software systems which significantly enhance fault coverage and enable automated operations are also under development. Smart sensing systems, such as flight capable plume spectrometers, have reached maturity in ground-based applications and are suitable for bridging to flight. Software to detect failed sensors has reached similar maturity. This paper will discuss fault detection and isolation for advanced rocket engine controllers as well as examples of advanced sensing systems and software which significantly improve component failure detection for engine system safety and health management.

Flight-determined benefits of integrated flight-propulsion control systems

NASA Technical Reports Server (NTRS)

Stewart, James F.; Burcham, Frank W., Jr.; Gatlin, Donald H.

1992-01-01

The fundamentals of control integration for propulsion are reviewed giving practical illustrations of its use to demonstrate the advantages of integration. Attention is given to the first integration propulsion-control systems (IPCSs) which was developed for the F-111E, and the integrated controller design is described that NASA developed for the YF-12C aircraft. The integrated control systems incorporate a range of aircraft components including the engine, inlet controls, autopilot, autothrottle, airdata, navigation, and/or stability-augmentation systems. Also described are emergency-control systems, onboard engine optimization, and thrust-vectoring control technologies developed for the F-18A and the F-15. Integrated flight-propulsion control systems are shown to enhance the thrust, range, and survivability of the aircraft while reducing fuel consumption and maintenance.

Energy efficient engine fan component detailed design report

NASA Technical Reports Server (NTRS)

Halle, J. E.; Michael, C. J.

1981-01-01

The fan component which was designed for the energy efficient engine is an advanced high performance, single stage system and is based on technology advancements in aerodynamics and structure mechanics. Two fan components were designed, both meeting the integrated core/low spool engine efficiency goal of 84.5%. The primary configuration, envisioned for a future flight propulsion system, features a shroudless, hollow blade and offers a predicted efficiency of 87.3%. A more conventional blade was designed, as a back up, for the integrated core/low spool demonstrator engine. The alternate blade configuration has a predicted efficiency of 86.3% for the future flight propulsion system. Both fan configurations meet goals established for efficiency surge margin, structural integrity and durability.

Video File - RS-25 Engine Test 2017-08-30

NASA Image and Video Library

2017-08-30

NASA engineers closed a summer of hot fire testing Aug. 30 for flight controllers on RS-25 engines that will help power the new Space Launch System (SLS) rocket being built to carry astronauts to deep-space destinations, including Mars. The 500-second hot fire an RS-25 engine flight controller unit on the A-1 Test Stand at Stennis Space Center near Bay St. Louis, Mississippi marked another step toward the nation’s return to human deep-space exploration missions.

Novitskiy performs in-flight maintenance on the TVIS

NASA Image and Video Library

2013-01-23

ISS034-E-033549 (23 Jan. 2013) --- Russian cosmonaut Oleg Novitskiy, Expedition 34 flight engineer, performs routine in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

MD-11 PCA - View of aircraft on ramp

NASA Technical Reports Server (NTRS)

1995-01-01

This McDonnell Douglas MD-11 is taxiing to a position on the flightline at NASA's Dryden Flight Research Center, Edwards, California, following its completion of the first and second landings ever performed by a transport aircraft under engine power only (on Aug. 29, 1995). The milestone flight, with NASA research pilot and former astronaut Gordon Fullerton at the controls, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. The Propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple. For pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

MD-11 PCA - First Landing at Edwards

NASA Technical Reports Server (NTRS)

1995-01-01

A transport aircraft lands for the first time under engine power only, as this McDonnell Douglas MD-11 touches down at 11:38 a.m., Aug. 29, 1995, at NASA's Dryden Flight Research Center, Edwards, California. The milestone flight, flown by NASA research pilot and former astronaut Gordon Fullerton, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. The propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple--for pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

MD-11 PCA - Closeup view of aircraft on ramp

NASA Technical Reports Server (NTRS)

1995-01-01

This McDonnell Douglas MD-11 has taxied to a position on the flightline at NASA's Dryden Flight Research Center, Edwards, California, following its completion of the first and second landings ever performed by a transport aircraft under engine power only (on Aug. 29, 1995). The milestone flight, with NASA research pilot and former astronaut Gordon Fullerton at the controls, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. The Propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple. For pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

MD-11 PCA - First Landing at Edwards

NASA Technical Reports Server (NTRS)

1995-01-01

A transport aircraft lands for the first time under engine power only, as this McDonnell Douglas MD-11 touches down at 11:38 a.m., Aug. 29, 1995, at NASA's Dryden Flight Research Center, Edwards, California. The milestone flight, flown by NASA research pilot and former astronaut Gordon Fullerton, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. The Propulsion-Controlled Aircraft (PCA) system uses standard autopilot controls already present in the cockpit, together with the new programming in the aircraft's flight control computers. The PCA concept is simple--for pitch control, the program increases thrust to climb and reduces thrust to descend. To turn right, the autopilot increases the left engine thrust while decreasing the right engine thrust. The initial Propulsion-Controlled Aircraft studies by NASA were carried out at Dryden with a modified twin-engine F-15 research aircraft.

Antimisting kerosene JT3 engine fuel system integration study

NASA Technical Reports Server (NTRS)

Fiorentino, A.

1987-01-01

An analytical study and laboratory tests were conducted to assist NASA in determining the safety and mission suitability of the modified fuel system and flight tests for the Full-Scale Transport Controlled Impact Demonstration (CID) program. This twelve-month study reviewed and analyzed both the use of antimisting kerosene (AMK) fuel and the incorporation of a fuel degrader on the operational and performance characteristics of the engines tested. Potential deficiencies and/or failures were identified and approaches to accommodate these deficiencies were recommended to NASA Ames -Dryden Flight Research Facility. The result of flow characterization tests on degraded AMK fuel samples indicated levels of degradation satisfactory for the planned missions of the B-720 aircraft. The operability and performance with the AMK in a ground test engine and in the aircraft engines during the test flights were comparable to those with unmodified Jet A. For the final CID test, the JT-3C-7 engines performed satisfactorily while operating on AMK right up to impact.

Engineering Aerothermal Analysis for X-34 Thermal Protection System Design

NASA Technical Reports Server (NTRS)

Wurster, Kathryn E.; Riley, Christopher J.; Zoby, E. Vincent

1998-01-01

Design of the thermal protection system for any hypersonic flight vehicle requires determination of both the peak temperatures over the surface and the heating-rate history along the flight profile. In this paper, the process used to generate the aerothermal environments required for the X-34 Testbed Technology Demonstrator thermal protection system design is described as it has evolved from a relatively simplistic approach based on engineering methods applied to critical areas to one of detailed analyses over the entire vehicle. A brief description of the trajectory development leading to the selection of the thermal protection system design trajectory is included. Comparisons of engineering heating predictions with wind-tunnel test data and with results obtained using a Navier-Stokes flowfield code and an inviscid/boundary layer method are shown. Good agreement is demonstrated among all these methods for both the ground-test condition and the peak heating flight condition. Finally, the detailed analysis using engineering methods to interpolate the surface-heating-rate results from the inviscid/boundary layer method to predict the required thermal environments is described and results presented.

Engineering Aerothermal Analysis for X-34 Thermal Protection System Design

NASA Technical Reports Server (NTRS)

Wurster, Kathryn E.; Riley, Christopher J.; Zoby, E. Vincent

1998-01-01

Design of the thermal protection system for any hypersonic flight vehicle requires determination of both the peak temperatures over the surface and the heating-rate history along the flight profile. In this paper, the process used to generate the aerothermal environments required for the X-34 Testbed Technology Demonstrator thermal protection system design is described as it has evolved from a relatively simplistic approach based on engineering methods applied to critical areas to one of detailed analyses over the entire vehicle. A brief description of the trajectory development leading to the selection of the thermal protection system design trajectory is included. Comparisons of engineering heating predictions with wind-tunnel test data and with results obtained using a Navier- Stokes flowfield code and an inviscid/boundary layer method are shown. Good agreement is demonstrated among all these methods for both the ground-test condition and the peak heating flight condition. Finally, the detailed analysis using engineering methods to interpolate the surface-heating-rate results from the inviscid/boundary layer method to predict the required thermal environments is described and results presented.

Optical Fiber Assemblies for Space Flight from the NASA Goddard Space Flight Center, Photonics Group

NASA Technical Reports Server (NTRS)

Ott, Melanie N.; Thoma, William Joe; LaRocca, Frank; Chuska, Richard; Switzer, Robert; Day, Lance

2009-01-01

The Photonics Group at NASA Goddard Space Flight Center in the Electrical Engineering Division of the Advanced Engineering and Technologies Directorate has been involved in the design, development, characterization, qualification, manufacturing, integration and anomaly analysis of optical fiber subsystems for over a decade. The group supports a variety of instrumentation across NASA and outside entities that build flight systems. Among the projects currently supported are: The Lunar Reconnaissance Orbiter, the Mars Science Laboratory, the James Webb Space Telescope, the Express Logistics Carrier for the International Space Station and the NASA Electronic Parts. and Packaging Program. A collection of the most pertinent information gathered during project support over the past year in regards to space flight performance of optical fiber components is presented here. The objective is to provide guidance for future space flight designs of instrumentation and communication systems.

NASA Hardware Heads to Kennedy For Flight Preparations

NASA Image and Video Library

2018-01-24

The Orion stage adapter will be part of the first integrated flight of NASA's heavy-lift rocket, the Space Launch System, and the Orion spacecraft. The adapter, approximately 5 feet tall and 18 feet in diameter, was designed and built at NASA's Marshall Space Flight Center in Huntsville, Alabama, with advanced friction stir welding technology. It will connect the SLS interim cryogenic propulsion stage to Orion on the first flight that will help engineers check out and verify the agency's new deep-space exploration systems. Inside the adapter, engineers installed special brackets and cabling for the 13 CubeSats that will fly as secondary payloads. The Cubesats are boot-box-sized science and technology investigations that will help pave the way for future human exploration in deep space. The Orion stage adapter flight article recently finished major testing of the avionics system that will deploy the CubeSats. Technicians at NASA's Kennedy Space Center, Florida, will install the secondary payloads and engineers will examine the hardware before it is stacked on the interim cryogenic propulsion stage in the Vehicle Assembly Building prior to launch. For more information about SLS hardware, visit nasa.gov/sls.

NASA C-17 Usage Overview

NASA Technical Reports Server (NTRS)

Miller, Christopher R.

2008-01-01

The usage and integrated vehicle health management of the NASA C-17. Propulsion health management flight objectives for the aircraft include mapping of the High Pressure Compressor in order to calibrate a Pratt and Whitney engine model and the fusion of data collected from existing sensors and signals to develop models, analysis methods and information fusion algorithms. An additional health manage flight objective is to demonstrate that the Commercial Modular Aero-Propulsion Systems Simulation engine model can successfully execute in real time onboard the C-17 T-1 aircraft using engine and aircraft flight data as inputs. Future work will address aircraft durability and aging, airframe health management, and propulsion health management research in the areas of gas path and engine vibration.

Nuclear Thermal Propulsion (NTP) Development Activities at the NASA Marshall Space Flight Center - 2006 Accomplishments

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2007-01-01

In 2005-06, the Prometheus program funded a number of tasks at the NASA-Marshall Space Flight Center (MSFC) to support development of a Nuclear Thermal Propulsion (NTP) system for future manned exploration missions. These tasks include the following: 1. NTP Design Develop Test & Evaluate (DDT&E) Planning 2. NTP Mission & Systems Analysis / Stage Concepts & Engine Requirements 3. NTP Engine System Trade Space Analysis and Studies 4. NTP Engine Ground Test Facility Assessment 5. Non-Nuclear Environmental Simulator (NTREES) 6. Non-Nuclear Materials Fabrication & Evaluation 7. Multi-Physics TCA Modeling. This presentation is a overview of these tasks and their accomplishments

Flight-vehicle structures education in the United States Assessment and recommendations

NASA Technical Reports Server (NTRS)

Noor, Ahmed K.; Dixon, S. C.

1987-01-01

An assessment is made of the technical contents of flight-vehicle structures curricula at 41 U.S. universities with accredited aerospace engineering programs. The assessment is based on the technical needs for the new and projected aeronautical and space systems as well as on the likely characteristics of the aerospace engineering work environment. A number of deficiencies and areas of concern are identified and recommendations are presented for enhancing the effectiveness of flight-vehicle structures education. A number of government supported programs that can help aerospace engineering education are listed in the appendix.

Capability and flight record of the versatile space shuttle OMS engine

NASA Astrophysics Data System (ADS)

Judd, D. Craig

The development contract for Aerojet's Orbital Manuevering Subsystem (OMS) engine was awarded in February 1974. This paper provides a description of the OMS subcomponents along with a summary of the OMS development program and subsequent flight record. The major subcomponents include the platelet injector, regeneratively cooled chamber, radiation cooled nozzle extension, bipropellant valve, thrust mount, gimbal actuator assembly, and propellant feedlines. The OMS engine underwent an extensive development program between 1974 and 1978 that included approximately 3680 tests performed on 21 separate engines on components for a total duration of more than 19,000 seconds. This was followed with qualification testing of two engines with another 521 tests and 18,504 seconds of hot fire testing. The Space Shuttle system has completed 45 orbital flights with the OMS engines having fired a total of 356 times with a cumulative duration of 38,094 seconds. In all cases, the OMS engine has performed as required because of its maturity, simplicity, and built-in redundancy. Also described are the results of studies performed to increase the performance of the OMS engine either by using LOX/hydrocarbon propellants or by converting to a pump fed system to increase chamber pressure and area ratio.

Multivariable control altitude demonstration on the F100 turbofan engine

NASA Technical Reports Server (NTRS)

Lehtinen, B.; Dehoff, R. L.; Hackney, R. D.

1979-01-01

The F100 Multivariable control synthesis (MVCS) program, was aimed at demonstrating the benefits of LGR synthesis theory in the design of a multivariable engine control system for operation throughout the flight envelope. The advantages of such procedures include: (1) enhanced performance from cross-coupled controls, (2) maximum use of engine variable geometry, and (3) a systematic design procedure that can be applied efficiently to new engine systems. The control system designed, under the MVCS program, for the Pratt & Whitney F100 turbofan engine is described. Basic components of the control include: (1) a reference value generator for deriving a desired equilibrium state and an approximate control vector, (2) a transition model to produce compatible reference point trajectories during gross transients, (3) gain schedules for producing feedback terms appropriate to the flight condition, and (4) integral switching logic to produce acceptable steady-state performance without engine operating limit exceedance.

NASA Earth-to-Orbit Engineering Design Challenges: Thermal Protection Systems

ERIC Educational Resources Information Center

National Aeronautics and Space Administration (NASA), 2010

2010-01-01

National Aeronautics and Space Administration (NASA) Engineers at Marshall Space Flight Center, Dryden Flight Research Center, and their partners at other NASA centers and in private industry are currently developing X-33, a prototype to test technologies for the next generation of space transportation. This single-stage-to-orbit reusable launch…

Advanced Earth-to-orbit propulsion technology program overview: Impact of civil space technology initiative

NASA Technical Reports Server (NTRS)

Stephenson, Frank W., Jr.

1988-01-01

The NASA Earth-to-Orbit (ETO) Propulsion Technology Program is dedicated to advancing rocket engine technologies for the development of fully reusable engine systems that will enable space transportation systems to achieve low cost, routine access to space. The program addresses technology advancements in the areas of engine life extension/prediction, performance enhancements, reduced ground operations costs, and in-flight fault tolerant engine operations. The primary objective is to acquire increased knowledge and understanding of rocket engine chemical and physical processes in order to evolve more realistic analytical simulations of engine internal environments, to derive more accurate predictions of steady and unsteady loads, and using improved structural analyses, to more accurately predict component life and performance, and finally to identify and verify more durable advanced design concepts. In addition, efforts were focused on engine diagnostic needs and advances that would allow integrated health monitoring systems to be developed for enhanced maintainability, automated servicing, inspection, and checkout, and ultimately, in-flight fault tolerant engine operations.

Binding Procurement

NASA Technical Reports Server (NTRS)

Rao, Gopalakrishna M.; Vaidyanathan, Hari

2007-01-01

This viewgraph presentation reviews the use of the binding procurement process in purchasing Aerospace Flight Battery Systems. NASA Engineering and Safety Center (NESC) requested NASA Aerospace Flight Battery Systems Working Group to develop a set of guideline requirements document for Binding Procurement Contracts.

An engine trade study for a supersonic STOVL fighter-attack aircraft, volume 1

NASA Technical Reports Server (NTRS)

Beard, B. B.; Foley, W. H.

1982-01-01

The best main engine for an advanced STOVL aircraft flight demonstrator was studied. The STOVL aircraft uses ejectors powered by engine bypass flow together with vectored core exhaust to achieve vertical thrust capability. Bypass flow and core flow are exhausted through separate nozzles during wingborne flight. Six near term turbofan engines were examined for suitability for this aircraft concept. Fan pressure ratio, thrust split between bypass and core flow, and total thrust level were used to compare engines. One of the six candidate engines was selected for the flight demonstrator configuration. Propulsion related to this aircraft concept was studied. A preliminary candidate for the aircraft reaction control system for hover attitude control was selected. A mathematical model of transfer of bypass thrust from ejectors to aft directed nozzle during the transition to wingborne flight was developed. An equation to predict ejector secondary air flow rate and ram drag is derived. Additional topics discussed include: nozzle area control, ejector to engine inlet reingestion, bypass/core thrust split variation, and gyroscopic behavior during hover.

An engineering evaluation of the Space Shuttle OMS engine after 5 orbital flights

NASA Technical Reports Server (NTRS)

David, D.

1983-01-01

Design features, performances on the first five flights, and condition of the Shuttle OMS engines are summarized. The engines were designed to provide a vacuum-fed 6000 lb of thrust and a 310 sec specific impulse, fueled by a combination of N2O4 and monomethylhydrazine (MMH) at a mixture ratio of 1.65. The design lifetime is 1000 starts and 15 hr of cumulative firing duration. The engine assembly is throat gimballed and features yaw actuators. No degradation of the hot components was observed during the first five flights, and the injector pattern maintained a uniform, enduring level of performance. An increase in the take-off loads have led to enhancing the wall thickness in the nozzle in affected areas. The engine is concluded to be performing to design specifications and is considered an operational system.

Single-Lever Power Control for General Aviation Aircraft Promises Improved Efficiency and Simplified Pilot Controls

NASA Technical Reports Server (NTRS)

Musgrave, Jeffrey L.

1997-01-01

General aviation research is leading to major advances in internal combustion engine control systems for single-engine, single-pilot aircraft. These advances promise to increase engine performance and fuel efficiency while substantially reducing pilot workload and increasing flight safety. One such advance is a single-lever power control (SLPC) system, a welcome departure from older, less user-friendly, multilever engine control systems. The benefits of using single-lever power controls for general aviation aircraft are improved flight safety through advanced engine diagnostics, simplified powerplant operations, increased time between overhauls, and cost-effective technology (extends fuel burn and reduces overhaul costs). The single-lever concept has proven to be so effective in preliminary studies that general aviation manufacturers are making plans to retrofit current aircraft with the technology and are incorporating it in designs for future aircraft.

Advanced Concept

NASA Image and Video Library

2003-12-01

This photo gives an overhead look at an RS-88 development rocket engine being test fired at NASA's Marshall Space Flight Center in Huntsville, Alabama, in support of the Pad Abort Demonstration (PAD) test flights for NASA's Orbital Space Plane (OSP). The tests could be instrumental in developing the first crew launch escape system in almost 30 years. Paving the way for a series of integrated PAD test flights, the engine tests support development of a system that could pull a crew safely away from danger during liftoff. A series of 16 hot fire tests of a 50,000-pound thrust RS-88 rocket engine were conducted, resulting in a total of 55 seconds of successful engine operation. The engine is being developed by the Rocketdyne Propulsion and Power unit of the Boeing Company. Integrated launch abort demonstration tests in 2005 will use four RS-88 engines to separate a test vehicle from a test platform, simulating pulling a crewed vehicle away from an aborted launch. Four 156-foot parachutes will deploy and carry the vehicle to landing. Lockheed Martin is building the vehicles for the PAD tests. Seven integrated tests are plarned for 2005 and 2006.

Advanced Concept

NASA Image and Video Library

2003-12-01

In this photo, an RS-88 development rocket engine is being test fired at NASA's Marshall Space Flight Center in Huntsville, Alabama, in support of the Pad Abort Demonstration (PAD) test flights for NASA's Orbital Space Plane (OSP). The tests could be instrumental in developing the first crew launch escape system in almost 30 years. Paving the way for a series of integrated PAD test flights, the engine tests support development of a system that could pull a crew safely away from danger during liftoff. A series of 16 hot fire tests of a 50,000-pound thrust RS-88 rocket engine were conducted, resulting in a total of 55 seconds of successful engine operation. The engine is being developed by the Rocketdyne Propulsion and Power unit of the Boeing Company. Integrated launch abort demonstration tests in 2005 will use four RS-88 engines to separate a test vehicle from a test platform, simulating pulling a crewed vehicle away from an aborted launch. Four 156-foot parachutes will deploy and carry the vehicle to landing. Lockheed Martin is building the vehicles for the PAD tests. Seven integrated tests are plarned for 2005 and 2006.

New Mass Properties Engineers Aerospace Ballasting Challenge Facilitated by the SAWE Community

NASA Technical Reports Server (NTRS)

Cutright, Amanda; Shaughnessy, Brendan

2010-01-01

The discipline of Mass Properties Engineering tends to find the engineers; not typically vice versa. In this case, two engineers quickly found their new responsibilities deep in many aspects of mass properties engineering and required to meet technical challenges in a fast paced environment. As part of NASA's Constellation Program, a series of flight tests will be conducted to evaluate components of the new spacecraft launch vehicles. One of these tests is the Pad Abort 1 (PA-1) flight test which will test the Launch Abort System (LAS), a system designed to provide escape for astronauts in the event of an emergency. The Flight Test Articles (FTA) used in this flight test are required to match mass properties corresponding to the operational vehicle, which has a continually evolving design. Additionally, since the structure and subsystems for the Orion Crew Module (CM) FTA are simplified versions of the final product, thousands of pounds of ballast are necessary to achieve the desired mass properties. These new mass properties engineers are responsible for many mass properties aspects in support of the flight test, including meeting the ballasting challenge for the CM Boilerplate FTA. SAWE expert and experienced mass properties engineers, both those that are directly on the team and many that supported via a variety of Society venues, significantly contributed to facilitating the success of addressing this particular mass properties ballasting challenge, in addition to many other challenges along the way. This paper discusses the details regarding the technical aspects of this particular mass properties challenge, as well as identifies recommendations for new mass properties engineers that were learned from the SAWE community along the way.

Energy efficient engine component development and integration program

NASA Technical Reports Server (NTRS)

1982-01-01

The development of the technology to improve energy efficiency of propulsion systems for subsonic commercial aircrafts was examined. Goals established include: (1) fuel consumption, reduction in flight propulsion system; (2) direct operation cost; (3) noise, with provision for engine growth corresponding to future engine application; and (4) emissions, EPA new engine standards.

14 CFR 29.1093 - Induction system icing protection.

Code of Federal Regulations, 2014 CFR

2014-01-01

... prevent icing has a preheater that can provide a heat rise of 100 °F. (b) Turbine engines. (1) It must be shown that each turbine engine and its air inlet system can operate throughout the flight power range of... engine operation, within the limitations established for the rotorcraft. (2) Each turbine engine must...

14 CFR 29.1093 - Induction system icing protection.

Code of Federal Regulations, 2011 CFR

2011-01-01

... prevent icing has a preheater that can provide a heat rise of 100 °F. (b) Turbine engines. (1) It must be shown that each turbine engine and its air inlet system can operate throughout the flight power range of... engine operation, within the limitations established for the rotorcraft. (2) Each turbine engine must...

14 CFR 29.1093 - Induction system icing protection.

Code of Federal Regulations, 2012 CFR

2012-01-01

... prevent icing has a preheater that can provide a heat rise of 100 °F. (b) Turbine engines. (1) It must be shown that each turbine engine and its air inlet system can operate throughout the flight power range of... engine operation, within the limitations established for the rotorcraft. (2) Each turbine engine must...

14 CFR 29.1093 - Induction system icing protection.

Code of Federal Regulations, 2013 CFR

2013-01-01

... prevent icing has a preheater that can provide a heat rise of 100 °F. (b) Turbine engines. (1) It must be shown that each turbine engine and its air inlet system can operate throughout the flight power range of... engine operation, within the limitations established for the rotorcraft. (2) Each turbine engine must...

The Direct Measurement of Engine Power on an Airplane in Flight with a Hub Type Dynamometer

NASA Technical Reports Server (NTRS)

Gove, W D; Green, M W

1927-01-01

This report describes tests made to obtain direct measurements of engine power in flight. Tests were made with a Bendemann hub dynamometer installed on a modified DH-4 Airplane, Liberty 12 Engine, to determine the suitability of this apparatus. This dynamometer unit, which was designed specially for use with a liberty 12 engine, is a special propeller hub in which is incorporated a system of pistons and cylinders interposed between the propeller and the engine crankshaft. The torque and thrust forces are balanced by fluid pressures, which are recorded by instruments in the cockpit. These tests have shown the suitability of this type of hub dynamometer for measurement of power in flight and for the determination of the torque and power coefficients of the propeller. (author)

An RL10A-3-3A rocket engine model using the rocket engine transient simulator (ROCETS) software

NASA Technical Reports Server (NTRS)

Binder, Michael

1993-01-01

Steady-state and transient computer models of the RL10A-3-3A rocket engine have been created using the Rocket Engine Transient Simulation (ROCETS) code. These models were created for several purposes. The RL10 engine is a critical component of past, present, and future space missions; the model will give NASA an in-house capability to simulate the performance of the engine under various operating conditions and mission profiles. The RL10 simulation activity is also an opportunity to further validate the ROCETS program. The ROCETS code is an important tool for modeling rocket engine systems at NASA Lewis. ROCETS provides a modular and general framework for simulating the steady-state and transient behavior of any desired propulsion system. Although the ROCETS code is being used in a number of different analysis and design projects within NASA, it has not been extensively validated for any system using actual test data. The RL10A-3-3A has a ten year history of test and flight applications; it should provide sufficient data to validate the ROCETS program capability. The ROCETS models of the RL10 system were created using design information provided by Pratt & Whitney, the engine manufacturer. These models are in the process of being validated using test-stand and flight data. This paper includes a brief description of the models and comparison of preliminary simulation output against flight and test-stand data.

The X-43A Hyper-X Mach 7 Flight 2 Guidance, Navigation, and Control Overview and Flight Test Results

NASA Technical Reports Server (NTRS)

Bahm, Catherine; Baumann, Ethan; Martin, John; Bose, David; Beck, Roger E.; Strovers, Brian

2005-01-01

The objective of the Hyper-X program was to flight demonstrate an airframe-integrated hypersonic vehicle. On March 27, 2004, the Hyper-X program team successfully conducted flight 2 and achieved all of the research objectives. The Hyper-X research vehicle successfully separated from the Hyper-X launch vehicle and achieved the desired engine test conditions before the experiment began. The research vehicle rejected the disturbances caused by the cowl door opening and the fuel turning on and off and maintained the engine test conditions throughout the experiment. After the engine test was complete, the vehicle recovered and descended along a trajectory while performing research maneuvers. The last data acquired showed that the vehicle maintained control to the water. This report will provide an overview of the research vehicle guidance and control systems and the performance of the vehicle during the separation event and engine test. The research maneuvers were performed to collect data for aerodynamics and flight controls research. This report also will provide an overview of the flight controls related research and results.

Applying Ada to Beech Starship avionics

NASA Technical Reports Server (NTRS)

Funk, David W.

1986-01-01

As Ada solidified in its development, it became evident that it offered advantages for avionics systems because of it support for modern software engineering principles and real time applications. An Ada programming support environment was developed for two major avionics subsystems in the Beech Starship. The two subsystems include electronic flight instrument displays and the flight management computer system. Both of these systems use multiple Intel 80186 microprocessors. The flight management computer provides flight planning, navigation displays, primary flight display of checklists and other pilot advisory information. Together these systems represent nearly 80,000 lines of Ada source code and to date approximately 30 man years of effort. The Beech Starship avionics systems are in flight testing.

NASA develops new digital flight control system

NASA Technical Reports Server (NTRS)

Mewhinney, Michael

1994-01-01

This news release reports on the development and testing of a new integrated flight and propulsion automated control system that aerospace engineers at NASA's Ames Research Center have been working on. The system is being tested in the V/STOL (Vertical/Short Takeoff and Landing) Systems Research Aircraft (VSRA).

Real-time open-loop frequency response analysis of flight test data

NASA Technical Reports Server (NTRS)

Bosworth, J. T.; West, J. C.

1986-01-01

A technique has been developed to compare the open-loop frequency response of a flight test aircraft real time with linear analysis predictions. The result is direct feedback to the flight control systems engineer on the validity of predictions and adds confidence for proceeding with envelope expansion. Further, gain and phase margins can be tracked for trends in a manner similar to the techniques used by structural dynamics engineers in tracking structural modal damping.

Approximation of Engine Casing Temperature Constraints for Casing Mounted Electronics

NASA Technical Reports Server (NTRS)

Kratz, Jonathan L.; Culley, Dennis E.; Chapman, Jeffryes W.

2017-01-01

The performance of propulsion engine systems is sensitive to weight and volume considerations. This can severely constrain the configuration and complexity of the control system hardware. Distributed Engine Control technology is a response to these concerns by providing more flexibility in designing the control system, and by extension, more functionality leading to higher performing engine systems. Consequently, there can be a weight benefit to mounting modular electronic hardware on the engine core casing in a high temperature environment. This paper attempts to quantify the in-flight temperature constraints for engine casing mounted electronics. In addition, an attempt is made at studying heat soak back effects. The Commercial Modular Aero Propulsion System Simulation 40k (C-MAPSS40k) software is leveraged with real flight data as the inputs to the simulation. A two-dimensional (2-D) heat transfer model is integrated with the engine simulation to approximate the temperature along the length of the engine casing. This modification to the existing C-MAPSS40k software will provide tools and methodologies to develop a better understanding of the requirements for the embedded electronics hardware in future engine systems. Results of the simulations are presented and their implications on temperature constraints for engine casing mounted electronics is discussed.

Approximation of Engine Casing Temperature Constraints for Casing Mounted Electronics

NASA Technical Reports Server (NTRS)

Kratz, Jonathan; Culley, Dennis; Chapman, Jeffryes

2016-01-01

The performance of propulsion engine systems is sensitive to weight and volume considerations. This can severely constrain the configuration and complexity of the control system hardware. Distributed Engine Control technology is a response to these concerns by providing more flexibility in designing the control system, and by extension, more functionality leading to higher performing engine systems. Consequently, there can be a weight benefit to mounting modular electronic hardware on the engine core casing in a high temperature environment. This paper attempts to quantify the in-flight temperature constraints for engine casing mounted electronics. In addition, an attempt is made at studying heat soak back effects. The Commercial Modular Aero Propulsion System Simulation 40k (C-MAPSS40k) software is leveraged with real flight data as the inputs to the simulation. A two-dimensional (2-D) heat transfer model is integrated with the engine simulation to approximate the temperature along the length of the engine casing. This modification to the existing C-MAPSS40k software will provide tools and methodologies to develop a better understanding of the requirements for the embedded electronics hardware in future engine systems. Results of the simulations are presented and their implications on temperature constraints for engine casing mounted electronics is discussed.

The Federal Aviation Administration Plan for Research, Engineering and Development. Volume 1. Program Plan

DTIC Science & Technology

1989-01-01

Mid * Advanced Propulsion System Far * Rotor Burst Protection Reports Mid 11.4 Flight Safety / * Aircraft Icing Handbook Near Atmospheric Hazards...with operating the national aviation system include air traffic controllers, flight service specialists, maintenance technicians, safety inspectors...address the design and certification of flight deck systems and revised crew training requirements. In FY 1988, studies of safety data were initiated to

Causal Factors and Adverse Events of Aviation Accidents and Incidents Related to Integrated Vehicle Health Management

NASA Technical Reports Server (NTRS)

Reveley, Mary S.; Briggs, Jeffrey L.; Evans, Joni K.; Jones, Sharon M.; Kurtoglu, Tolga; Leone, Karen M.; Sandifer, Carl E.

2011-01-01

Causal factors in aviation accidents and incidents related to system/component failure/malfunction (SCFM) were examined for Federal Aviation Regulation Parts 121 and 135 operations to establish future requirements for the NASA Aviation Safety Program s Integrated Vehicle Health Management (IVHM) Project. Data analyzed includes National Transportation Safety Board (NSTB) accident data (1988 to 2003), Federal Aviation Administration (FAA) incident data (1988 to 2003), and Aviation Safety Reporting System (ASRS) incident data (1993 to 2008). Failure modes and effects analyses were examined to identify possible modes of SCFM. A table of potential adverse conditions was developed to help evaluate IVHM research technologies. Tables present details of specific SCFM for the incidents and accidents. Of the 370 NTSB accidents affected by SCFM, 48 percent involved the engine or fuel system, and 31 percent involved landing gear or hydraulic failure and malfunctions. A total of 35 percent of all SCFM accidents were caused by improper maintenance. Of the 7732 FAA database incidents affected by SCFM, 33 percent involved landing gear or hydraulics, and 33 percent involved the engine and fuel system. The most frequent SCFM found in ASRS were turbine engine, pressurization system, hydraulic main system, flight management system/flight management computer, and engine. Because the IVHM Project does not address maintenance issues, and landing gear and hydraulic systems accidents are usually not fatal, the focus of research should be those SCFMs that occur in the engine/fuel and flight control/structures systems as well as power systems.

A Model-based Health Monitoring and Diagnostic System for the UH-60 Helicopter. Appendix D

NASA Technical Reports Server (NTRS)

Patterson-Hine, Ann; Hindson, William; Sanderfer, Dwight; Deb, Somnath; Domagala, Chuck

2001-01-01

Model-based reasoning techniques hold much promise in providing comprehensive monitoring and diagnostics capabilities for complex systems. We are exploring the use of one of these techniques, which utilizes multi-signal modeling and the TEAMS-RT real-time diagnostic engine, on the UH-60 Rotorcraft Aircrew Systems Concepts Airborne Laboratory (RASCAL) flight research aircraft. We focus on the engine and transmission systems, and acquire sensor data across the 1553 bus as well as by direct analog-to-digital conversion from sensors to the QHuMS (Qualtech health and usage monitoring system) computer. The QHuMS computer uses commercially available components and is rack-mounted in the RASCAL facility. A multi-signal model of the transmission and engine subsystems enables studies of system testability and analysis of the degree of fault isolation available with various instrumentation suites. The model and examples of these analyses will be described and the data architectures enumerated. Flight tests of this system will validate the data architecture and provide real-time flight profiles to be further analyzed in the laboratory.

A knowledge-based system design/information tool for aircraft flight control systems

NASA Technical Reports Server (NTRS)

Mackall, Dale A.; Allen, James G.

1991-01-01

Research aircraft have become increasingly dependent on advanced electronic control systems to accomplish program goals. These aircraft are integrating multiple disciplines to improve performance and satisfy research objective. This integration is being accomplished through electronic control systems. Systems design methods and information management have become essential to program success. The primary objective of the system design/information tool for aircraft flight control is to help transfer flight control system design knowledge to the flight test community. By providing all of the design information and covering multiple disciplines in a structured, graphical manner, flight control systems can more easily be understood by the test engineers. This will provide the engineers with the information needed to thoroughly ground test the system and thereby reduce the likelihood of serious design errors surfacing in flight. The secondary object is to apply structured design techniques to all of the design domains. By using the techniques in the top level system design down through the detailed hardware and software designs, it is hoped that fewer design anomalies will result. The flight test experiences are reviewed of three highly complex, integrated aircraft programs: the X-29 forward swept wing; the advanced fighter technology integration (AFTI) F-16; and the highly maneuverable aircraft technology (HiMAT) program. Significant operating technologies, and the design errors which cause them, is examined to help identify what functions a system design/informatin tool should provide to assist designers in avoiding errors.

Peroxide Propulsion at the Turn of the Century

NASA Technical Reports Server (NTRS)

Anderson, William E.; Butler, Kathy; Crocket, Dave; Lewis, Tim; McNeal, Curtis

2000-01-01

A resurgence of interest in peroxide propulsion has occurred in the last years of the 21st Century. This interest is driven by the need for lower cost propulsion systems and the need for storable reusable propulsion systems to meet future space transportation system architectures. NASA and the Air Force are jointly developing two propulsion systems for flight demonstration early in the 21st Century. One system will be a development of Boeing's AR2-3 engine, which was successfully fielded in the 1960s. The other is a new pressure-fed design by Orbital Sciences Corporation for expendable mission requirements. Concurrently NASA and industry are pursuing the key peroxide technologies needed to design, fabricate, and test advanced peroxide engines to meet the mission needs beyond 2005. This paper will present a description of the AR2-3, report the status of its current test program, and describe its intended flight demonstration. This paper will then describe the Orbital 10K engine, the status of its test program, and describe its planned flight demonstration. Finally the paper will present a plan, or technology roadmap, for the development of an advanced peroxide engine for the 21st Century.

Research flight software engineering and MUST, an integrated system of support tools

NASA Technical Reports Server (NTRS)

Straeter, T. A.; Foudriat, E. C.; Will, R. W.

1977-01-01

Consideration is given to software development to support NASA flight research. The Multipurpose User-Oriented Software Technology (MUST) program, designed to integrate digital systems into flight research, is discussed. Particular attention is given to the program's special interactive user interface, subroutine library, assemblers, compiler, automatic documentation tools, and test and simulation subsystems.

CSBF Engineering Overview

NASA Astrophysics Data System (ADS)

Orr, Dwayne

CSBF Engineering Overview Dwayne Orr (Presenting Author) Columbia Scientific Balloon Facility, Palestine, Texas (USA) Dwayne.Orr@csbf.nasa.gov The Columbia Scientific Balloon Facility (CSBF) at Palestine, Texas provides operational and engineering support for the launch of NASA Scientific Balloons. Over the years with the support of the NASA Balloon Program Office, CSBF has developed unique flight systems with the focus of providing a highly reliable, cost effective medium for giving Scientist’s access to a near space environment. This paper will provide an overview of the CSBF flight systems with an emphasis on recent developments and plans for the future.

NASA’s Space Launch System Engine Testing Heats Up

NASA Image and Video Library

2017-05-23

NASA engineers successfully conducted the second in a series of RS-25 flight controller tests on May 23, 2017, for the world’s most-powerful rocket. The 500-second test on the A-1 Test Stand at NASA’s Stennis Space Center in Mississippi marked another milestone toward launch of NASA’s new Space Launch System (SLS) rocket on its inaugural flight, the Exploration Mission-1 (EM-1). The SLS rocket, powered by four RS-25 engines, will provide 2 million pounds of thrust and work in conjunction with two solid rocket boosters. These are former space shuttle main engines, modified to perform at a higher level and with a new controller.

Linear Aerospike SR-71 Experiment (LASRE) dumps water after first in-flight cold flow test

NASA Technical Reports Server (NTRS)

1998-01-01

The NASA SR-71A successfully completed its first cold flow flight as part of the NASA/Rocketdyne/Lockheed Martin Linear Aerospike SR-71 Experiment (LASRE) at NASA's Dryden Flight Research Center, Edwards, California on March 4, 1998. During a cold flow flight, gaseous helium and liquid nitrogen are cycled through the linear aerospike engine to check the engine's plumbing system for leaks and to check the engine operating characterisitics. Cold-flow tests must be accomplished successfully before firing the rocket engine experiment in flight. The SR-71 took off at 10:16 a.m. PST. The aircraft flew for one hour and fifty-seven minutes, reaching a maximum speed of Mach 1.58 before landing at Edwards at 12:13 p.m. PST. 'I think all in all we had a good mission today,' Dryden LASRE Project Manager Dave Lux said. Flight crew member Bob Meyer agreed, saying the crew 'thought it was a really good flight.' Dryden Research Pilot Ed Schneider piloted the SR-71 during the mission. Lockheed Martin LASRE Project Manager Carl Meade added, 'We are extremely pleased with today's results. This will help pave the way for the first in-flight engine data-collection flight of the LASRE.' The LASRE experiment was designed to provide in-flight data to help Lockheed Martin evaluate the aerodynamic characteristics and the handling of the SR-71 linear aerospike experiment configuration. The goal of the project was to provide in-flight data to help Lockheed Martin validate the computational predictive tools it was using to determine the aerodynamic performance of a future reusable launch vehicle. The joint NASA, Rocketdyne (now part of Boeing), and Lockheed Martin Linear Aerospike SR-71 Experiment (LASRE) completed seven initial research flights at Dryden Flight Research Center. Two initial flights were used to determine the aerodynamic characteristics of the LASRE apparatus (pod) on the back of the SR-71. Five later flights focused on the experiment itself. Two were used to cycle gaseous helium and liquid nitrogen through the experiment to check its plumbing system for leaks and to test engine operational characteristics. During the other three flights, liquid oxygen was cycled through the engine. Two engine hot-firings were also completed on the ground. A final hot-fire test flight was canceled because of liquid oxygen leaks in the test apparatus. The LASRE experiment itself was a 20-percent-scale, half-span model of a lifting body shape (X-33) without the fins. It was rotated 90 degrees and equipped with eight thrust cells of an aerospike engine and was mounted on a housing known as the 'canoe,' which contained the gaseous hydrogen, helium, and instrumentation gear. The model, engine, and canoe together were called a 'pod.' The experiment focused on determining how a reusable launch vehicle's engine flume would affect the aerodynamics of its lifting-body shape at specific altitudes and speeds. The interaction of the aerodynamic flow with the engine plume could create drag; design refinements looked at minimizing this interaction. The entire pod was 41 feet in length and weighed 14,300 pounds. The experimental pod was mounted on one of NASA's SR-71s, which were at that time on loan to NASA from the U.S. Air Force. Lockheed Martin may use the information gained from the LASRE and X-33 Advanced Technology Demonstrator Projects to develop a potential future reusable launch vehicle. NASA and Lockheed Martin were partners in the X-33 program through a cooperative agreement. The goal of that program was to enable significant reductions in the cost of access to space and to promote creation and delivery of new space services and activities to improve the United States's economic competitiveness. In March 2001, however, NASA cancelled the X-33 program.

Test Results of the Modified Space Shuttle Main Engine at the Marshall Space Flight Center Technology Test Bed Facility

NASA Technical Reports Server (NTRS)

Cook, J.; Dumbacher, D.; Ise, M.; Singer, C.

1990-01-01

A modified space shuttle main engine (SSME), which primarily includes an enlarged throat main combustion chamber with the acoustic cavities removed and a main injector with the stability control baffles removed, was tested. This one-of-a-kind engine's design changes are being evaluated for potential incorporation in the shuttle flight program in the mid-1990's. Engine testing was initiated on September 15, 1988 and has accumulated 1,915 seconds and 19 starts. Testing is being conducted to characterize the engine system performance, combustion stability with the baffle-less injector, and both low pressure oxidizer turbopump (LPOTP) and high pressure oxidizer turbopump (HPOTP) for suction performance. These test results are summarized and compared with the SSME flight configuration data base. Testing of this new generation SSME is the first product from the technology test bed (TTB). Figure test plans for the TTB include the highly instrumented flight configuration SSME and advanced liquid propulsion technology items.

Verification and Implementation of Operations Safety Controls for Flight Missions

NASA Technical Reports Server (NTRS)

Jones, Cheryl L.; Smalls, James R.; Carrier, Alicia S.

2010-01-01

Approximately eleven years ago, the International Space Station launched the first module from Russia, the Functional Cargo Block (FGB). Safety and Mission Assurance (S&MA) Operations (Ops) Engineers played an integral part in that endeavor by executing strict flight product verification as well as continued staffing of S&MA's console in the Mission Evaluation Room (MER) for that flight mission. How were these engineers able to conduct such a complicated task? They conducted it based on product verification that consisted of ensuring that safety requirements were adequately contained in all flight products that affected crew safety. S&MA Ops engineers apply both systems engineering and project management principles in order to gain a appropriate level of technical knowledge necessary to perform thorough reviews which cover the subsystem(s) affected. They also ensured that mission priorities were carried out with a great detail and success.

The SEL Adapts to Meet Changing Times

NASA Technical Reports Server (NTRS)

Pajerski, Rose S.; Basili, Victor R.

1997-01-01

Since 1976, the Software Engineering Laboratory (SEL) has been dedicated to understanding and improving the way in which one NASA organization, the Flight Dynamics Division (FDD) at Goddard Space Flight Center, develops, maintains, and manages complex flight dynamics systems. It has done this by developing and refining a continual process improvement approach that allows an organization such as the FDD to fine-tune its process for its particular domain. Experimental software engineering and measurement play a significant role in this approach. The SEL is a partnership of NASA Goddard, its major software contractor, Computer Sciences Corporation (CSC), and the University of Maryland's (LTM) Department of Computer Science. The FDD primarily builds software systems that provide ground-based flight dynamics support for scientific satellites. They fall into two sets: ground systems and simulators. Ground systems are midsize systems that average around 250 thousand source lines of code (KSLOC). Ground system development projects typically last 1 - 2 years. Recent systems have been rehosted to workstations from IBM mainframes, and also contain significant new subsystems written in C and C++. The simulators are smaller systems averaging around 60 KSLOC that provide the test data for the ground systems. Simulator development lasts up to 1 year. Most of the simulators have been built in Ada on workstations. The SEL is responsible for the management and continual improvement of the software engineering processes used on these FDD projects.

Space shuttle main engine anomaly data and inductive knowledge based systems: Automated corporate expertise

NASA Technical Reports Server (NTRS)

Modesitt, Kenneth L.

1987-01-01

Progress is reported on the development of SCOTTY, an expert knowledge-based system to automate the analysis procedure following test firings of the Space Shuttle Main Engine (SSME). The integration of a large-scale relational data base system, a computer graphics interface for experts and end-user engineers, potential extension of the system to flight engines, application of the system for training of newly-hired engineers, technology transfer to other engines, and the essential qualities of good software engineering practices for building expert knowledge-based systems are among the topics discussed.

STS-111 Expedition Five Crew Training Clip

NASA Technical Reports Server (NTRS)

2002-01-01

The STS-111 Expedition Five Crew begins with training on payload operations. Flight Engineer Peggy Whitson and Mission Specialist Sandy Magnus are shown in Shuttle Remote Manipulator System (SRMS) procedures. Flight Engineer Sergei Treschev gets suited for Neutral Neutral Buoyancy Lab (NBL) training. Virtual Reality lab training is shown with Peggy Whitson. Habitation Equipment and procedures are also presented.

14 CFR 63.43 - Flight engineer courses.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 2 2013-01-01 2013-01-01 false Flight engineer courses. 63.43 Section 63...) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.43 Flight engineer courses. An applicant for approval of a flight engineer course must submit a letter to the Administrator...

14 CFR 63.43 - Flight engineer courses.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 2 2010-01-01 2010-01-01 false Flight engineer courses. 63.43 Section 63...) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.43 Flight engineer courses. An applicant for approval of a flight engineer course must submit a letter to the Administrator...

14 CFR 63.43 - Flight engineer courses.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 2 2012-01-01 2012-01-01 false Flight engineer courses. 63.43 Section 63...) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.43 Flight engineer courses. An applicant for approval of a flight engineer course must submit a letter to the Administrator...

14 CFR 63.43 - Flight engineer courses.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 2 2014-01-01 2014-01-01 false Flight engineer courses. 63.43 Section 63...) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.43 Flight engineer courses. An applicant for approval of a flight engineer course must submit a letter to the Administrator...

14 CFR 63.43 - Flight engineer courses.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 2 2011-01-01 2011-01-01 false Flight engineer courses. 63.43 Section 63...) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.43 Flight engineer courses. An applicant for approval of a flight engineer course must submit a letter to the Administrator...

NASA’s Stennis Space Center Conducts RS-25 Engine Test

NASA Image and Video Library

2017-03-24

On March 23, NASA conducted a test of an RS-25 engine at the agency’s Stennis Space Center in Bay St. Louis, Mississippi. Four RS-25’s will help power NASA’s Space Launch System (SLS) rocket to space. During this test, engineers evaluated the engine’s new controller or “brain”, which communicates with the SLS vehicle. Once test data is certified, the engine controller will be removed and installed on one of the four flight engines that will help power the first integrated flight of SLS and the Orion spacecraft.

Software Engineering Improvement Activities/Plan

NASA Technical Reports Server (NTRS)

2003-01-01

bd Systems personnel accomplished the technical responsibilities for this reporting period, as planned. A close working relationship was maintained with personnel of the MSFC Avionics Department Software Group (ED14). Work accomplishments included development, evaluation, and enhancement of a software cost model, performing literature search and evaluation of software tools available for code analysis and requirements analysis, and participating in other relevant software engineering activities. Monthly reports were submitted. This support was provided to the Flight Software Group/ED 1 4 in accomplishing the software engineering improvement engineering activities of the Marshall Space Flight Center (MSFC) Software Engineering Improvement Plan.

Development and Flight Evaluation of an Emergency Digital Flight Control System Using Only Engine Thrust on an F-15 Airplane

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Maine, Trindel A.; Fullerton, C. Gordon; Webb, Lannie Dean

1996-01-01

A propulsion-controlled aircraft (PCA) system for emergency flight control of aircraft with no flight controls was developed and flight tested on an F-15 aircraft at the NASA Dryden Flight Research Center. The airplane has been flown in a throttles-only manual mode and with an augmented system called PCA in which pilot thumbwheel commands and aircraft feedback parameters were used to drive the throttles. Results from a 36-flight evaluation showed that the PCA system can be used to safety land an airplane that has suffered a major flight control system failure. The PCA system was used to recover from a severe upset condition, descend, and land. Guest pilots have also evaluated the PCA system. This paper describes the principles of throttles-only flight control; a history of loss-of-control accidents; a description of the F-15 aircraft; the PCA system operation, simulation, and flight testing; and the pilot comments.

Embedded expert system for space shuttle main engine maintenance

NASA Technical Reports Server (NTRS)

Pooley, J.; Thompson, W.; Homsley, T.; Teoh, W.; Jones, J.; Lewallen, P.

1987-01-01

The SPARTA Embedded Expert System (SEES) is an intelligent health monitoring system that directs analysis by placing confidence factors on possible engine status and then recommends a course of action to an engineer or engine controller. The technique can prevent catastropic failures or costly rocket engine down time because of false alarms. Further, the SEES has potential as an on-board flight monitor for reusable rocket engine systems. The SEES methodology synergistically integrates vibration analysis, pattern recognition and communications theory techniques with an artificial intelligence technique - the Embedded Expert System (EES).

A US History of Airbreathing/Rocket Combined-Cycle (RBCC) Propulsion for Powering Future Aerospace Transports, with a Look Ahead to the Year 2020

NASA Technical Reports Server (NTRS)

Escher, William J. D.

1999-01-01

A technohistorical and forward-planning overview of U.S. developments in combined airbreathing/rocket propulsion for advanced aerospace vehicle applications is presented. Such system approaches fall into one of two categories: (1) Combination propulsion systems (separate, non-interacting engines installed), and (2) Combined-Cycle systems. The latter, and main subject, comprises a large family of closely integrated engine types, made up of both airbreathing and rocket derived subsystem hardware. A single vehicle-integrated, multimode engine results, one capable of operating efficiently over a very wide speed and altitude range, atmospherically and in space. While numerous combination propulsion systems have reached operational flight service, combined-cycle propulsion development, initiated ca. 1960, remains at the subscale ground-test engine level of development. However, going beyond combination systems, combined-cycle propulsion potentially offers a compelling set of new and unique capabilities. These capabilities are seen as enabling ones for the evolution of Spaceliner class aerospace transportation systems. The following combined-cycle hypersonic engine developments are reviewed: (1) RENE (rocket engine nozzle ejector), (2) Cryojet and LACE, (3) Ejector Ramjet and its derivatives, (4) the seminal NASA NAS7-377 study, (5) Air Force/Marquardt Hypersonic Ramjet, (6) Air Force/Lockheed-Marquardt Incremental Scramjet flight-test project, (7) NASA/Garrett Hypersonic Research Engine (HRE), (8) National Aero-Space Plane (NASP), (9) all past projects; and such current and planned efforts as (10) the NASA ASTP-ART RBCC project, (11) joint CIAM/NASA DNSCRAM flight test,(12) Hyper-X, (13) Trailblazer,( 14) W-Vehicle and (15) Spaceliner 100. Forward planning programmatic incentives, and the estimated timing for an operational Spaceliner powered by combined-cycle engines are discussed.

Flight test experience and controlled impact of a large, four-engine, remotely piloted airplane

NASA Technical Reports Server (NTRS)

Kempel, R. W.; Horton, T. W.

1985-01-01

A controlled impact demonstration (CID) program using a large, four engine, remotely piloted transport airplane was conducted. Closed loop primary flight control was performed from a ground based cockpit and digital computer in conjunction with an up/down telemetry link. Uplink commands were received aboard the airplane and transferred through uplink interface systems to a highly modified Bendix PB-20D autopilot. Both proportional and discrete commands were generated by the ground pilot. Prior to flight tests, extensive simulation was conducted during the development of ground based digital control laws. The control laws included primary control, secondary control, and racetrack and final approach guidance. Extensive ground checks were performed on all remotely piloted systems. However, manned flight tests were the primary method of verification and validation of control law concepts developed from simulation. The design, development, and flight testing of control laws and the systems required to accomplish the remotely piloted mission are discussed.

A Study on Aircraft Engine Control Systems for Integrated Flight and Propulsion Control

NASA Astrophysics Data System (ADS)

Yamane, Hideaki; Matsunaga, Yasushi; Kusakawa, Takeshi; Yasui, Hisako

The Integrated Flight and Propulsion Control (IFPC) for a highly maneuverable aircraft and a fighter-class engine with pitch/yaw thrust vectoring is described. Of the two IFPC functions the aircraft maneuver control utilizes the thrust vectoring based on aerodynamic control surfaces/thrust vectoring control allocation specified by the Integrated Control Unit (ICU) of a FADEC (Full Authority Digital Electronic Control) system. On the other hand in the Performance Seeking Control (PSC) the ICU identifies engine's various characteristic changes, optimizes manipulated variables and finally adjusts engine control parameters in cooperation with the Engine Control Unit (ECU). It is shown by hardware-in-the-loop simulation that the thrust vectoring can enhance aircraft maneuverability/agility and that the PSC can improve engine performance parameters such as SFC (specific fuel consumption), thrust and gas temperature.

EC97-44354-1

NASA Image and Video Library

1997-12-16

The F-16XL #1 (NASA 849) takes off for the first flight of the Digital Flight Control System (DFCS) on December 16, 1997. Like most first flight, the DFCS required months of preparations. During July 1997, crews worked on the engine, cockpit, canopy, seat, and instrumentation. By late August, the aircraft began combined systems tests and a flight readiness review. Although the Air Force Safety Review Board (AFSRB)- a group that provided double checks on all flight operations - approved the program in late November 1997, a problem with the aircraft flight computer delayed the functional check flight until mid-December.

Total energy based flight control system

NASA Technical Reports Server (NTRS)

Lambregts, Antonius A. (Inventor)

1985-01-01

An integrated aircraft longitudinal flight control system uses a generalized thrust and elevator command computation (38), which accepts flight path angle, longitudinal acceleration command signals, along with associated feedback signals, to form energy rate error (20) and energy rate distribution error (18) signals. The engine thrust command is developed (22) as a function of the energy rate distribution error and the elevator position command is developed (26) as a function of the energy distribution error. For any vertical flight path and speed mode the outerloop errors are normalized (30, 34) to produce flight path angle and longitudinal acceleration commands. The system provides decoupled flight path and speed control for all control modes previously provided by the longitudinal autopilot, autothrottle and flight management systems.

Concept Designed and Developed for Distortion- Tolerant, High-Stability Engine Control

NASA Technical Reports Server (NTRS)

1995-01-01

Engine Control Future aircraft turbine engines, both commercial and military, must be able to successfully accommodate expected increased levels of steady-state and dynamic engine-face distortion. Advanced tactical aircraft are likely to use thrust vectoring to enhance their maneuverability. As a result, the engines will see more extreme aircraft angles-of-attack and sideslip levels than are currently encountered with present-day aircraft. Also, the mixed-compression inlets needed for the High Speed Civil Transport will likely encounter disturbances similar to those seen by tactical aircraft, in addition to planar pulse, inlet buzz, and high distortion levels at low flight speed and off-design operation. The current approach of incorporating a sufficient component design stall margin to tolerate these increased levels of distortion would significantly reduce performance. The objective of the High Stability Engine Control (HISTEC) program is to design, develop, and flight demonstrate an advanced, high-stability, integrated engine-control system that uses measurement-based, real-time estimates of distortion to enhance engine stability. The resulting distortion-tolerant control reduces the required design stall margin, with a corresponding increase in performance and decrease in fuel burn. The HISTEC concept has been designed and developed, and the software implementing the concept has successfully accommodated time-varying distortion. The NASA Lewis Research Center is currently overseeing the development and validation of the hardware and software necessary to flight test the HISTEC concept. HISTEC is a contracted effort with Pratt & Whitney of West Palm Beach, Florida. The HISTEC approach includes two major systems: A Distortion Estimation System (DES) and Stability Management Control (SMC). DES is an aircraft-mounted, high-speed processor that estimates the amount and type of distortion present and its effect on the engine. It uses high-response pressure measurements at the engine face to calculate indicators of the type and extent of distortion in real time. From these indicators, DES determines the effects of distortion on the propulsion systems and the corresponding engine match point necessary to accommodate it. DES output consists of fan and compressor pressure ratio trim commands that are passed to the SMC. In addition, DES uses maneuver information, consisting of angle-of-attack and sideslip from the flight control, to anticipate high inlet distortion conditions. The SMC, which is contained in the engine-mounted, Improved Digital Electronic Engine Control (IDEEC), includes advanced control laws to directly control the fan and compressor transient operating line (pressure ratio). These advanced control laws, with a multivariable design, have the potential for higher bandwidth and the resulting more precise control of engine match. The ability to measure and assess the distortion effects in real time coupled with a high-response controller improves engine stability at high levels of distortion. The software algorithms implementing DES have been designed, developed, and demonstrated, and integration testing of the DES and SMC software has been completed. The results show that the HISTEC system will be able to sense inlet distortion, determine the effect on engine stability, and accommodate distortion by maintaining an adequate margin for engine surge. The Pratt &Whitney Comprehensive Engine Diagnostic Unit was chosen as the DES processor. An instrumented inlet case for sensing distortion was designed and fabricated. HISTEC is scheduled for flight test on the ACTIVE F-15 aircraft at the NASA Dryden Flight Research Center in Edwards, California, in late 1996.

14 CFR Appendix C to Part 135 - Helicopter Flight Recorder Specifications

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Helicopter Flight Recorder Specifications C.... C Appendix C to Part 135—Helicopter Flight Recorder Specifications Parameters Range Installed system... Maximum range +5% 1 1% 2 Engine torque Maximum range ±5% 1 1% 2 Flight Control—Hydraulic Pressure Primary...

Kenneth J. Szalai

NASA Technical Reports Server (NTRS)

1997-01-01

Kenneth J. Szalai was Director of the NASA Hugh L. Dryden Flight Research Center, Edwards, Calif., from January 1994 through July 1998. He retired from NASA at the end of July to join IBP Aerospace Group, Inc., as the company's new president and chief operating officer. As NASA's primary installation for flight research for more than half a century, Dryden is chartered to conceive and conduct experimental flight research for integrated flight and propulsion controls; advanced optical sensors and controls; viscous drag reduction; advanced configurations; high-altitude, long-endurance aircraft; remotely piloted vehicle technology; hypersonic vehicle experiments; high-speed research for civil transportation; atmospheric tests of advanced rocket and airbreathing propulsion concepts; instrumentation systems; and flight loads predictions. In carrying out this mission, Dryden operates some of the most advanced research aircraft in the nation. When Dryden was administratively a part of the NASA Ames Research Center, Moffett Field, Calif., Szalai was director and also held the position of Ames Deputy Director for Dryden from December 1990 until assuming his current position From 1982 until December 1990, Szalai directed the Dryden Research Engineering Division. He served as Associate Director of the Ames Research Center in 1989. Prior to 1982 he was chief of the Research Engineering Division's Dynamics and Control Branch, and chief of the Flight Control Section. Szalai began his NASA career at Dryden in 1964 following graduation from the University of Wisconsin, where he attended both the Milwaukee and Madison campuses. His bachelor of science degree is in electrical engineering. He also received a master of science degree in mechanical engineering from the University of Southern California in 1970. Szalai was principal investigator on the F-8 Digital Fly-By-Wire program, which successfully flew the first aircraft equipped with a digital electronic flight control system without any mechanical reversion capability. Szalai also held research and systems engineering positions on several research aircraft programs investigating flying qualities, integrated flight controls, and fault tolerant-flight critical systems. He was also flight test engineer and principal investigator on the NASA Airborne Simulator before assuming management positions within the Research Engineering Division. Szalai has worked in various technical and management positions on such programs as the F-111 IPCS, AFTI/F-16, HiMAT, F-15 DEEC, F-15 HIDEC, X-29, X-31, F-16XL Laminar Flow, Space Shuttle Orbiter, Pathfinder Solar Powered Aircraft, SR-71 Sonic Boom, F-15 and MD-11 Propulsion Controlled Aircraft, X-33, and X-38. Szalai has authored over 25 papers and reports and has been a lecturer for the NATO Advisory Group for Aeronautical Research and Development (AGARD). He has served on various technical committees and subcommittees for the American Institute of Aeronautics and Astronautics (AIAA) and Society of Automotive Engineers (SAE). Szalai, a Fellow of the AIAA, also served on the National Academy of Science's 'Aeronautics-2000' study. Among the awards Szalai has received are NASA's Exceptional Service Medal, the NASA Outstanding Leadership Medal, and the Presidential Meritorious and Distinguished Rank awards. Szalai was born June 1, 1942, in Milwaukee, Wisc., where he graduated from West Division High School.

DARPA/USAF/USN J-UCAS X-45A System Demonstration Program: A Review of Flight Test Site Processes and Personnel

NASA Technical Reports Server (NTRS)

Cosentino, Gary B.

2008-01-01

The Joint Unmanned Combat Air Systems (J-UCAS) program is a collaborative effort between the Defense Advanced Research Project Agency (DARPA), the US Air Force (USAF) and the US Navy (USN). Together they have reviewed X-45A flight test site processes and personnel as part of a system demonstration program for the UCAV-ATD Flight Test Program. The goal was to provide a disciplined controlled process for system integration and testing and demonstration flight tests. NASA's Dryden Flight Research Center (DFRC) acted as the project manager during this effort and was tasked with the responsibilities of range and ground safety, the provision of flight test support and infrastructure and the monitoring of technical and engineering tasks. DFRC also contributed their engineering knowledge through their contributions in the areas of autonomous ground taxi control development, structural dynamics testing and analysis and the provision of other flight test support including telemetry data, tracking radars, and communications and control support equipment. The Air Force Flight Test Center acted at the Deputy Project Manager in this effort and was responsible for the provision of system safety support and airfield management and air traffic control services, among other supporting roles. The T-33 served as a J-UCAS surrogate aircraft and demonstrated flight characteristics similar to that of the the X-45A. The surrogate served as a significant risk reduction resource providing mission planning verification, range safety mission assessment and team training, among other contributions.

Application of an integrated flight/propulsion control design methodology to a STOVL aircraft

NASA Technical Reports Server (NTRS)

Garg, Sanjay; Mattern, Duane L.

1991-01-01

Results are presented from the application of an emerging Integrated Flight/Propulsion Control (IFPC) design methodology to a Short Take Off and Vertical Landing (STOVL) aircraft in transition flight. The steps in the methodology consist of designing command shaping prefilters to provide the overall desired response to pilot command inputs. A previously designed centralized controller is first validated for the integrated airframe/engine plant used. This integrated plant is derived from a different model of the engine subsystem than the one used for the centralized controller design. The centralized controller is then partitioned in a decentralized, hierarchical structure comprising of airframe lateral and longitudinal subcontrollers and an engine subcontroller. Command shaping prefilters from the pilot control effector inputs are then designed and time histories of the closed loop IFPC system response to simulated pilot commands are compared to desired responses based on handling qualities requirements. Finally, the propulsion system safety and nonlinear limited protection logic is wrapped around the engine subcontroller and the response of the closed loop integrated system is evaluated for transients that encounter the propulsion surge margin limit.

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples. Volume 2: Software documentation

NASA Technical Reports Server (NTRS)

Moore, N. R.; Ebbeler, D. H.; Newlin, L. E.; Sutharshana, S.; Creager, M.

1992-01-01

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes, These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples, volume 1

NASA Technical Reports Server (NTRS)

Moore, N. R.; Ebbeler, D. H.; Newlin, L. E.; Sutharshana, S.; Creager, M.

1992-01-01

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes. These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

Space flight requirements for fiber optic components: qualification testing and lessons learned

NASA Astrophysics Data System (ADS)

Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam

2006-04-01

"Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.

Space Flight Requirements for Fiber Optic Components; Qualification Testing and Lessons Learned

NASA Technical Reports Server (NTRS)

Ott, Melanie N.; Jin, Xiaodan Linda; Chuska, Richard; Friedberg, Patricia; Malenab, Mary; Matuszeski, Adam

2007-01-01

"Qualification" of fiber optic components holds a very different meaning than it did ten years ago. In the past, qualification meant extensive prolonged testing and screening that led to a programmatic method of reliability assurance. For space flight programs today, the combination of using higher performance commercial technology, with shorter development schedules and tighter mission budgets makes long term testing and reliability characterization unfeasible. In many cases space flight missions will be using technology within years of its development and an example of this is fiber laser technology. Although the technology itself is not a new product the components that comprise a fiber laser system change frequently as processes and packaging changes occur. Once a process or the materials for manufacturing a component change, even the data that existed on its predecessor can no longer provide assurance on the newer version. In order to assure reliability during a space flight mission, the component engineer must understand the requirements of the space flight environment as well as the physics of failure of the components themselves. This can be incorporated into an efficient and effective testing plan that "qualifies" a component to specific criteria defined by the program given the mission requirements and the component limitations. This requires interaction at the very initial stages of design between the system design engineer, mechanical engineer, subsystem engineer and the component hardware engineer. Although this is the desired interaction what typically occurs is that the subsystem engineer asks the components or development engineers to meet difficult requirements without knowledge of the current industry situation or the lack of qualification data. This is then passed on to the vendor who can provide little help with such a harsh set of requirements due to high cost of testing for space flight environments. This presentation is designed to guide the engineers of design, development and components, and vendors of commercial components with how to make an efficient and effective qualification test plan with some basic generic information about many space flight requirements. Issues related to the physics of failure, acceptance criteria and lessons learned will also be discussed to assist with understanding how to approach a space flight mission in an ever changing commercial photonics industry.

Systems analysis of solid fuel nuclear engines in cislunar space

NASA Astrophysics Data System (ADS)

Thomas, U.; Koelle, H. H.; Balzer-Sieb, R.; Bernau, D.; Czarnitzki, J.; Floete, A.; Goericke, D.; Lindenthal, A.; Protsch, R.; Teschner, O.

1984-12-01

The use of nuclear engines in cislunar space was studied and the restrictions imposed on nuclear ferries by the chemical Earth to lower Earth orbit (LEO) transportation system were analyzed. The operating conditions are best met by tungsten-water-moderated reactors due to a high specific impulse and long durability. Specific transportation cost for LEO to geostationary orbit (GEO) and LEO to lunar orbit flights were calculated for a transportation system life of 50 yr. Average transportation costs are estimated to be 141 $/kg. No difference is made for both routes. An additional analysis of smaller and larger flight units shows only small cost reductions by employing larger ferries but a significant cost increase in case smaller flight units are used.

Modular Software for Spacecraft Navigation Using the Global Positioning System (GPS)

NASA Technical Reports Server (NTRS)

Truong, S. H.; Hartman, K. R.; Weidow, D. A.; Berry, D. L.; Oza, D. H.; Long, A. C.; Joyce, E.; Steger, W. L.

1996-01-01

The Goddard Space Flight Center Flight Dynamics and Mission Operations Divisions have jointly investigated the feasibility of engineering modular Global Positioning SYSTEM (GPS) navigation software to support both real time flight and ground postprocessing configurations. The goals of this effort are to define standard GPS data interfaces and to engineer standard, reusable navigation software components that can be used to build a broad range of GPS navigation support applications. The paper discusses the GPS modular software (GMOD) system and operations concepts, major requirements, candidate software architecture, feasibility assessment and recommended software interface standards. In additon, ongoing efforts to broaden the scope of the initial study and to develop modular software to support autonomous navigation using GPS are addressed,

14 CFR 23.933 - Reversing systems.

Code of Federal Regulations, 2013 CFR

2013-01-01

... analysis and testing completed by the engine and propeller manufacturers. [Doc. No. 26344, 58 FR 18971, Apr... only must be designed so that, during any reversal in flight, the engine will produce no more than... engine from producing more than idle thrust when the reversing system malfunctions; except that it may...

14 CFR 23.933 - Reversing systems.

Code of Federal Regulations, 2014 CFR

2014-01-01

... analysis and testing completed by the engine and propeller manufacturers. [Doc. No. 26344, 58 FR 18971, Apr... only must be designed so that, during any reversal in flight, the engine will produce no more than... engine from producing more than idle thrust when the reversing system malfunctions; except that it may...

14 CFR 23.933 - Reversing systems.

Code of Federal Regulations, 2012 CFR

2012-01-01

... analysis and testing completed by the engine and propeller manufacturers. [Doc. No. 26344, 58 FR 18971, Apr... only must be designed so that, during any reversal in flight, the engine will produce no more than... engine from producing more than idle thrust when the reversing system malfunctions; except that it may...

14 CFR 23.933 - Reversing systems.

Code of Federal Regulations, 2011 CFR

2011-01-01

... analysis and testing completed by the engine and propeller manufacturers. [Doc. No. 26344, 58 FR 18971, Apr... only must be designed so that, during any reversal in flight, the engine will produce no more than... engine from producing more than idle thrust when the reversing system malfunctions; except that it may...

14 CFR 23.933 - Reversing systems.

Code of Federal Regulations, 2010 CFR

2010-01-01

... analysis and testing completed by the engine and propeller manufacturers. [Doc. No. 26344, 58 FR 18971, Apr... only must be designed so that, during any reversal in flight, the engine will produce no more than... engine from producing more than idle thrust when the reversing system malfunctions; except that it may...

What can formal methods offer to digital flight control systems design

NASA Technical Reports Server (NTRS)

Good, Donald I.

1990-01-01

Formal methods research begins to produce methods which will enable mathematic modeling of the physical behavior of digital hardware and software systems. The development of these methods directly supports the NASA mission of increasing the scope and effectiveness of flight system modeling capabilities. The conventional, continuous mathematics that is used extensively in modeling flight systems is not adequate for accurate modeling of digital systems. Therefore, the current practice of digital flight control system design has not had the benefits of extensive mathematical modeling which are common in other parts of flight system engineering. Formal methods research shows that by using discrete mathematics, very accurate modeling of digital systems is possible. These discrete modeling methods will bring the traditional benefits of modeling to digital hardware and hardware design. Sound reasoning about accurate mathematical models of flight control systems can be an important part of reducing risk of unsafe flight control.

Thermodynamic Cycle Analysis of Magnetohydrodynamic-Bypass Airbreathing Hypersonic Engines

NASA Technical Reports Server (NTRS)

Litchford, Ron J.; Bityurin, Valentine A.; Lineberry, John T.

1999-01-01

Established analyses of conventional ramjet/scramjet performance characteristics indicate that a considerable decrease in efficiency can be expected at off-design flight conditions. This can be explained, in large part, by the deterioration of intake mass flow and limited inlet compression at low flight speeds and by the onset of thrust degradation effects associated with increased burner entry temperature at high flight speeds. In combination, these effects tend to impose lower and upper Mach number limits for practical flight. It has been noted, however, that Magnetohydrodynamic (MHD) energy management techniques represent a possible means for extending the flight Mach number envelope of conventional engines. By transferring enthalpy between different stages of the engine cycle, it appears that the onset of thrust degradation may be delayed to higher flight speeds. Obviously, the introduction of additional process inefficiencies is inevitable with this approach, but it is believed that these losses are more than compensated through optimization of the combustion process. The fundamental idea is to use MHD energy conversion processes to extract and bypass a portion of the intake kinetic energy around the burner. We refer to this general class of propulsion system as an MHD-bypass engine. In this paper, we quantitatively assess the performance potential and scientific feasibility of MHD-bypass airbreathing hypersonic engines using ideal gasdynamics and fundamental thermodynamic principles.

SSME Post Test Diagnostic System: Systems Section

NASA Technical Reports Server (NTRS)

Bickmore, Timothy

1995-01-01

An assessment of engine and component health is routinely made after each test firing or flight firing of a Space Shuttle Main Engine (SSME). Currently, this health assessment is done by teams of engineers who manually review sensor data, performance data, and engine and component operating histories. Based on review of information from these various sources, an evaluation is made as to the health of each component of the SSME and the preparedness of the engine for another test or flight. The objective of this project - the SSME Post Test Diagnostic System (PTDS) - is to develop a computer program which automates the analysis of test data from the SSME in order to detect and diagnose anomalies. This report primarily covers work on the Systems Section of the PTDS, which automates the analyses performed by the systems/performance group at the Propulsion Branch of NASA Marshall Space Flight Center (MSFC). This group is responsible for assessing the overall health and performance of the engine, and detecting and diagnosing anomalies which involve multiple components (other groups are responsible for analyzing the behavior of specific components). The PTDS utilizes several advanced software technologies to perform its analyses. Raw test data is analyzed using signal processing routines which detect features in the data, such as spikes, shifts, peaks, and drifts. Component analyses are performed by expert systems, which use 'rules-of-thumb' obtained from interviews with the MSFC data analysts to detect and diagnose anomalies. The systems analysis is performed using case-based reasoning. Results of all analyses are stored in a relational database and displayed via an X-window-based graphical user interface which provides ranked lists of anomalies and observations by engine component, along with supporting data plots for each.

Specialized data analysis for the Space Shuttle Main Engine and diagnostic evaluation of advanced propulsion system components

NASA Technical Reports Server (NTRS)

1993-01-01

The Marshall Space Flight Center is responsible for the development and management of advanced launch vehicle propulsion systems, including the Space Shuttle Main Engine (SSME), which is presently operational, and the Space Transportation Main Engine (STME) under development. The SSME's provide high performance within stringent constraints on size, weight, and reliability. Based on operational experience, continuous design improvement is in progress to enhance system durability and reliability. Specialized data analysis and interpretation is required in support of SSME and advanced propulsion system diagnostic evaluations. Comprehensive evaluation of the dynamic measurements obtained from test and flight operations is necessary to provide timely assessment of the vibrational characteristics indicating the operational status of turbomachinery and other critical engine components. Efficient performance of this effort is critical due to the significant impact of dynamic evaluation results on ground test and launch schedules, and requires direct familiarity with SSME and derivative systems, test data acquisition, and diagnostic software. Detailed analysis and evaluation of dynamic measurements obtained during SSME and advanced system ground test and flight operations was performed including analytical/statistical assessment of component dynamic behavior, and the development and implementation of analytical/statistical models to efficiently define nominal component dynamic characteristics, detect anomalous behavior, and assess machinery operational condition. In addition, the SSME and J-2 data will be applied to develop vibroacoustic environments for advanced propulsion system components, as required. This study will provide timely assessment of engine component operational status, identify probable causes of malfunction, and indicate feasible engineering solutions. This contract will be performed through accomplishment of negotiated task orders.

Centaur space vehicle pressurized propellant feed system tests

NASA Technical Reports Server (NTRS)

1972-01-01

Engine firing tests, using a full-scale flight-weight vehicle, were performed to evaluate a pressurized propellant feed system for the Centaur. The pressurant gases used were helium and hydrogen. The system was designed to replace the boost pumps currently used on Centaur. Two liquid oxygen tank pressurization modes were studied: (1) directly into the ullage and (2) below the propellant surface. Test results showed the two Centaur RL10 engines could be started and run over the range of expected flight variables. No system instabilities were encountered. Measured pressurization gas quantities agreed well with analytically predicted values.

Perseus Post-flight

NASA Technical Reports Server (NTRS)

1991-01-01

Crew members check out the Perseus proof-of-concept vehicle on Rogers Dry Lake, adjacent to the Dryden Flight Research Center, Edwards, California, after a test flight in 1991. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Entry Atmospheric Flight Control Authority Impacts on GN and C and Trajectory Performance for Orion Exploration Flight Test 1

NASA Technical Reports Server (NTRS)

McNamara, Luke W.

2012-01-01

One of the key design objectives of NASA's Orion Exploration Flight Test 1 (EFT-1) is to execute a guided entry trajectory demonstrating GN&C capability. The focus of this paper is the ight control authority of the vehicle throughout the atmospheric entry ight to the target landing site and its impacts on GN&C, parachute deployment, and integrated performance. The vehicle's attitude control authority is obtained from thrusting 12 Re- action Control System (RCS) engines, with four engines to control yaw, four engines to control pitch, and four engines to control roll. The static and dynamic stability derivatives of the vehicle are determined to assess the inherent aerodynamic stability. The aerodynamic moments at various locations in the entry trajectory are calculated and compared to the available torque provided by the RCS system. Interaction between the vehicle's RCS engine plumes and the aerodynamic conditions are considered to assess thruster effectiveness. This document presents an assessment of Orion's ight control authority and its effectiveness in controlling the vehicle during critical events in the atmospheric entry trajectory.

Verification and Validation of Neural Networks for Aerospace Systems

NASA Technical Reports Server (NTRS)

Mackall, Dale; Nelson, Stacy; Schumman, Johann; Clancy, Daniel (Technical Monitor)

2002-01-01

The Dryden Flight Research Center V&V working group and NASA Ames Research Center Automated Software Engineering (ASE) group collaborated to prepare this report. The purpose is to describe V&V processes and methods for certification of neural networks for aerospace applications, particularly adaptive flight control systems like Intelligent Flight Control Systems (IFCS) that use neural networks. This report is divided into the following two sections: 1) Overview of Adaptive Systems; and 2) V&V Processes/Methods.

Verification and Validation of Neural Networks for Aerospace Systems

NASA Technical Reports Server (NTRS)

Mackall, Dale; Nelson, Stacy; Schumann, Johann

2002-01-01

The Dryden Flight Research Center V&V working group and NASA Ames Research Center Automated Software Engineering (ASE) group collaborated to prepare this report. The purpose is to describe V&V processes and methods for certification of neural networks for aerospace applications, particularly adaptive flight control systems like Intelligent Flight Control Systems (IFCS) that use neural networks. This report is divided into the following two sections: Overview of Adaptive Systems and V&V Processes/Methods.

Systems Engineering Leadership Development: Advancing Systems Engineering Excellence

NASA Technical Reports Server (NTRS)

Hall, Phil; Whitfield, Susan

2011-01-01

This slide presentation reviews the Systems Engineering Leadership Development Program, with particular emphasis on the work being done in the development of systems engineers at Marshall Space Flight Center. There exists a lack of individuals with systems engineering expertise, in particular those with strong leadership capabilities, to meet the needs of the Agency's exploration agenda. Therefore there is a emphasis on developing these programs to identify and train systems engineers. The presentation reviews the proposed MSFC program that includes course work, and developmental assignments. The formal developmental programs at the other centers are briefly reviewed, including the Point of Contact (POC)

Fiber optic (flight quality) sensors for advanced aircraft propulsion

NASA Technical Reports Server (NTRS)

Poppel, Gary L.

1994-01-01

Development of flight prototype, fiber-optic sensing system components for measuring nine sensed parameters (three temperatures, two speeds, three positions, and one flame) on an F404-400 aircraft engine is described. Details of each sensor's design, functionality, and environmental testing, and the electro-optics architecture for sensor signal conditioning are presented. Eight different optical sensing techniques were utilized. Design, assembly, and environmental testing of an engine-mounted, electro-optics chassis unit (EOU), providing MIL-C-1553 data output, are related. Interconnection cables and connectors between the EOU and the sensors are identified. Results of sensor/cable/circuitry integrated testing, and installation and ground testing of the sensor system on an engine in October 1993 and April 1994 are given, including comparisons with the engine control system's electrical sensors. Lessons learned about the design, fabrication, testing, and integration of the sensor system components are included.

GENERAL VIEW OF FLIGHT LINE BUILDINGS. FROM LEFT TO RIGHT, ...

Library of Congress Historic Buildings Survey, Historic Engineering Record, Historic Landscapes Survey

GENERAL VIEW OF FLIGHT LINE BUILDINGS. FROM LEFT TO RIGHT, JET ENGINE TEST CELL BUILDING (BUILDING 2820), MAINTENANCE DOCK, FLIGHT SYSTEM (BUILDING 2818)" AND MAINTENANCE DOCK (BUILDING 2793). VIEW TO SOUTHEAST - Plattsburgh Air Force Base, U.S. Route 9, Plattsburgh, Clinton County, NY

14 CFR 25.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2011 CFR

2011-01-01

... Design and Construction Fire Protection § 25.865 Fire protection of flight controls, engine mounts, and other flight structure. Essential flight controls, engine mounts, and other flight structures located in... 14 Aeronautics and Space 1 2011-01-01 2011-01-01 false Fire protection of flight controls, engine...

14 CFR 25.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2012 CFR

2012-01-01

... Design and Construction Fire Protection § 25.865 Fire protection of flight controls, engine mounts, and other flight structure. Essential flight controls, engine mounts, and other flight structures located in... 14 Aeronautics and Space 1 2012-01-01 2012-01-01 false Fire protection of flight controls, engine...

14 CFR 23.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2013 CFR

2013-01-01

... controls, engine mounts, and other flight structure. Flight controls, engine mounts, and other flight... 14 Aeronautics and Space 1 2013-01-01 2013-01-01 false Fire protection of flight controls, engine mounts, and other flight structure. 23.865 Section 23.865 Aeronautics and Space FEDERAL AVIATION...

14 CFR 25.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2010 CFR

2010-01-01

... Design and Construction Fire Protection § 25.865 Fire protection of flight controls, engine mounts, and other flight structure. Essential flight controls, engine mounts, and other flight structures located in... 14 Aeronautics and Space 1 2010-01-01 2010-01-01 false Fire protection of flight controls, engine...

14 CFR 23.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2012 CFR

2012-01-01

... controls, engine mounts, and other flight structure. Flight controls, engine mounts, and other flight... 14 Aeronautics and Space 1 2012-01-01 2012-01-01 false Fire protection of flight controls, engine mounts, and other flight structure. 23.865 Section 23.865 Aeronautics and Space FEDERAL AVIATION...

14 CFR 23.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2014 CFR

2014-01-01

... controls, engine mounts, and other flight structure. Flight controls, engine mounts, and other flight... 14 Aeronautics and Space 1 2014-01-01 2014-01-01 false Fire protection of flight controls, engine mounts, and other flight structure. 23.865 Section 23.865 Aeronautics and Space FEDERAL AVIATION...

14 CFR 23.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2011 CFR

2011-01-01

... controls, engine mounts, and other flight structure. Flight controls, engine mounts, and other flight... 14 Aeronautics and Space 1 2011-01-01 2011-01-01 false Fire protection of flight controls, engine mounts, and other flight structure. 23.865 Section 23.865 Aeronautics and Space FEDERAL AVIATION...

14 CFR 25.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2014 CFR

2014-01-01

... Design and Construction Fire Protection § 25.865 Fire protection of flight controls, engine mounts, and other flight structure. Essential flight controls, engine mounts, and other flight structures located in... 14 Aeronautics and Space 1 2014-01-01 2014-01-01 false Fire protection of flight controls, engine...

14 CFR 23.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2010 CFR

2010-01-01

... controls, engine mounts, and other flight structure. Flight controls, engine mounts, and other flight... 14 Aeronautics and Space 1 2010-01-01 2010-01-01 false Fire protection of flight controls, engine mounts, and other flight structure. 23.865 Section 23.865 Aeronautics and Space FEDERAL AVIATION...

14 CFR 25.865 - Fire protection of flight controls, engine mounts, and other flight structure.

Code of Federal Regulations, 2013 CFR

2013-01-01

... Design and Construction Fire Protection § 25.865 Fire protection of flight controls, engine mounts, and other flight structure. Essential flight controls, engine mounts, and other flight structures located in... 14 Aeronautics and Space 1 2013-01-01 2013-01-01 false Fire protection of flight controls, engine...

Kotov and Williams with SSRMS arm training session in Node 1 / Unity module

NASA Image and Video Library

2007-04-18

ISS014-E-19587 (17 April 2007) --- Cosmonaut Oleg V. Kotov (foreground), Expedition 15 flight engineer representing Russia's Federal Space Agency, and astronaut Sunita L. Williams, flight engineer, participate in a Space Station Remote Manipulator System (SSRMS) training session using the Robotic Onboard Trainer (ROBOT) simulator in the Unity node of the International Space Station.

Improving Legacy Aircraft Systems Through Condition-Based Maintenance: An H-60 Case Study

DTIC Science & Technology

2014-09-01

level functions. These decompositions are equivalent to a detailed design effort in systems engineering. NAMPSOPs have a common architectural structure...Assembly Power Available Spindle Cables No.1 Engine Load Demand Spindle Control Cables Engine Pneumatic Starters Auxiliary Power Unit IRCM FLIR Mission...Analysis Fuel System Main Rotor Head Main Module Main Gear Box Radiator Engine Output Shaft Auxiliary Power Unit Flight Control Cables Tail Landing

Research on hypersonic aircraft using pre-cooled turbojet engines

NASA Astrophysics Data System (ADS)

Taguchi, Hideyuki; Kobayashi, Hiroaki; Kojima, Takayuki; Ueno, Atsushi; Imamura, Shunsuke; Hongoh, Motoyuki; Harada, Kenya

2012-04-01

Systems analysis of a Mach 5 class hypersonic aircraft is performed. The aircraft can fly across the Pacific Ocean in 2 h. A multidisciplinary optimization program for aerodynamics, structure, propulsion, and trajectory is used in the analysis. The result of each element model is improved using higher accuracy analysis tools. The aerodynamic performance of the hypersonic aircraft is examined through hypersonic wind tunnel tests. A thermal management system based on the data of the wind tunnel tests is proposed. A pre-cooled turbojet engine is adopted as the propulsion system for the hypersonic aircraft. The engine can be operated continuously from take-off to Mach 5. This engine uses a pre-cooling cycle using cryogenic liquid hydrogen. The high temperature inlet air of hypersonic flight would be cooled by the same liquid hydrogen used as fuel. The engine is tested under sea level static conditions. The engine is installed on a flight test vehicle. Both liquid hydrogen fuel and gaseous hydrogen fuel are supplied to the engine from a tank and cylinders installed within the vehicle. The designed operation of major components of the engine is confirmed. A large amount of liquid hydrogen is supplied to the pre-cooler in order to make its performance sufficient for Mach 5 flight. Thus, fuel rich combustion is adopted at the afterburner. The experiments are carried out under the conditions that the engine is mounted upon an experimental airframe with both set up either horizontally or vertically. As a result, the operating procedure of the pre-cooled turbojet engine is demonstrated.

The Development and Use of a Flight Optimization System Model of a C-130E Transport Aircraft

NASA Technical Reports Server (NTRS)

Desch, Jeremy D.

1995-01-01

The Systems Analysis Branch at NASA Langley Research Center conducts a variety of aircraft design and analyses studies. These studies include the prediction of characteristics of a particular conceptual design, analyses of designs that already exist, and assessments of the impact of technology on current and future aircraft. The FLight OPtimization System (FLOPS) is a tool used for aircraft systems analysis and design. A baseline input model of a Lockheed C-130E was generated for the Flight Optimization System. This FLOPS model can be used to conduct design-trade studies and technology impact assessments. The input model was generated using standard input data such as basic geometries and mission specifications. All of the other data needed to determine the airplane performance is computed internally by FLOPS. The model was then calibrated to reproduce the actual airplane performance from flight test data. This allows a systems analyzer to change a specific item of geometry or mission definition in the FLOPS input file and evaluate the resulting change in performance from the output file. The baseline model of the C-130E was used to analyze the effects of implementing upper wing surface blowing on the airplane. This involved removing the turboprop engines that were on the C-130E and replacing them with turbofan engines. An investigation of the improvements in airplane performance with the new engines could be conducted within the Flight Optimization System. Although a thorough analysis was not completed, the impact of this change on basic mission performance was investigated.

Study of advanced fuel system concepts for commercial aircraft

NASA Technical Reports Server (NTRS)

Coffinberry, G. A.

1985-01-01

An analytical study was performed in order to assess relative performance and economic factors involved with alternative advanced fuel systems for future commercial aircraft operating with broadened property fuels. The DC-10-30 wide-body tri-jet aircraft and the CF6-8OX engine were used as a baseline design for the study. Three advanced systems were considered and were specifically aimed at addressing freezing point, thermal stability and lubricity fuel properties. Actual DC-10-30 routes and flight profiles were simulated by computer modeling and resulted in prediction of aircraft and engine fuel system temperatures during a nominal flight and during statistical one-day-per-year cold and hot flights. Emergency conditions were also evaluated. Fuel consumption and weight and power extraction results were obtained. An economic analysis was performed for new aircraft and systems. Advanced system means for fuel tank heating included fuel recirculation loops using engine lube heat and generator heat. Environmental control system bleed air heat was used for tank heating in a water recirculation loop. The results showed that fundamentally all of the three advanced systems are feasible but vary in their degree of compatibility with broadened-property fuel.

A Status Report on the Parachute Development for NASA's Next Manned Spacecraft

NASA Technical Reports Server (NTRS)

Sinclair, Robert

2008-01-01

NASA has determined that the parachute portion of the Landing System for the Crew Exploration Vehicle (CEV) will be Government Furnished Equipment (GFE). The Earth Landing System has been designated CEV Parachute Assembly System (CPAS). Thus a program team was developed consisting of NASA Johnson Space Center (JSC) and Jacobs Engineering through their Engineering and Science Contract Group (ESCG). Following a rigorous competitive phase, Airborne Systems North America was selected to provide the parachute design, testing and manufacturing role to support this team. The development program has begun with some early flight testing of a Generation 1 parachute system. Future testing will continue to refine the design and complete a qualification phase prior to manned flight of the spacecraft. The program team will also support early spacecraft system testing, including a Pad Abort Flight Test in the Fall of 2008

Doing Systems Engineering Without Thinking About It at NASA Dryden Flight Research Center

NASA Technical Reports Server (NTRS)

Bohn-Meyer, Marta; Kilp, Stephen; Chun, Peggy; Mizukami, Masashi

2004-01-01

When asked about his processes in designing a new airplane, Burt Rutan responded: ...there is always a performance requirement. So I start with the basic physics of an airplane that can get those requirements, and that pretty much sizes an airplane... Then I look at the functionality... And then I try a lot of different configurations to meet that, and then justify one at a time, throwing them out... Typically I'll have several different configurations... But I like to experiment, certainly. I like to see if there are other ways to provide the utility. This kind of thinking engineering as a total systems engineering approach is what is being instilled in all engineers at the NASA Dryden Flight Research Center.

Application and Evaluation of Control Modes for Risk-Based Engine Performance Enhancements

NASA Technical Reports Server (NTRS)

Liu, Yuan; Litt, Jonathan S.; Sowers, T. Shane; Owen, A. Karl (Compiler); Guo, Ten-Huei

2014-01-01

The engine control system for civil transport aircraft imposes operational limits on the propulsion system to ensure compliance with safety standards. However, during certain emergency situations, aircraft survivability may benefit from engine performance beyond its normal limits despite the increased risk of failure. Accordingly, control modes were developed to improve the maximum thrust output and responsiveness of a generic high-bypass turbofan engine. The algorithms were designed such that the enhanced performance would always constitute an elevation in failure risk to a consistent predefined likelihood. This paper presents an application of these risk-based control modes to a combined engine/aircraft model. Through computer and piloted simulation tests, the aim is to present a notional implementation of these modes, evaluate their effects on a generic airframe, and demonstrate their usefulness during emergency flight situations. Results show that minimal control effort is required to compensate for the changes in flight dynamics due to control mode activation. The benefits gained from enhanced engine performance for various runway incursion scenarios are investigated. Finally, the control modes are shown to protect against potential instabilities during propulsion-only flight where all aircraft control surfaces are inoperable.

Robust In-Flight Sensor Fault Diagnostics for Aircraft Engine Based on Sliding Mode Observers

PubMed Central

Chang, Xiaodong; Huang, Jinquan; Lu, Feng

2017-01-01

For a sensor fault diagnostic system of aircraft engines, the health performance degradation is an inevitable interference that cannot be neglected. To address this issue, this paper investigates an integrated on-line sensor fault diagnostic scheme for a commercial aircraft engine based on a sliding mode observer (SMO). In this approach, one sliding mode observer is designed for engine health performance tracking, and another for sensor fault reconstruction. Both observers are employed in in-flight applications. The results of the former SMO are analyzed for post-flight updating the baseline model of the latter. This idea is practical and feasible since the updating process does not require the algorithm to be regulated or redesigned, so that ground-based intervention is avoided, and the update process is implemented in an economical and efficient way. With this setup, the robustness of the proposed scheme to the health degradation is much enhanced and the latter SMO is able to fulfill sensor fault reconstruction over the course of the engine life. The proposed sensor fault diagnostic system is applied to a nonlinear simulation of a commercial aircraft engine, and its effectiveness is evaluated in several fault scenarios. PMID:28398255

Application and Evaluation of Control Modes for Risk-Based Engine Performance Enhancements

NASA Technical Reports Server (NTRS)

Liu, Yuan; Litt, Jonathan S.; Sowers, T. Shane; Owen, A. Karl; Guo, Ten-Huei

2015-01-01

The engine control system for civil transport aircraft imposes operational limits on the propulsion system to ensure compliance with safety standards. However, during certain emergency situations, aircraft survivability may benefit from engine performance beyond its normal limits despite the increased risk of failure. Accordingly, control modes were developed to improve the maximum thrust output and responsiveness of a generic high-bypass turbofan engine. The algorithms were designed such that the enhanced performance would always constitute an elevation in failure risk to a consistent predefined likelihood. This paper presents an application of these risk-based control modes to a combined engine/aircraft model. Through computer and piloted simulation tests, the aim is to present a notional implementation of these modes, evaluate their effects on a generic airframe, and demonstrate their usefulness during emergency flight situations. Results show that minimal control effort is required to compensate for the changes in flight dynamics due to control mode activation. The benefits gained from enhanced engine performance for various runway incursion scenarios are investigated. Finally, the control modes are shown to protect against potential instabilities during propulsion-only flight where all aircraft control surfaces are inoperable.

Robust In-Flight Sensor Fault Diagnostics for Aircraft Engine Based on Sliding Mode Observers.

PubMed

Chang, Xiaodong; Huang, Jinquan; Lu, Feng

2017-04-11

For a sensor fault diagnostic system of aircraft engines, the health performance degradation is an inevitable interference that cannot be neglected. To address this issue, this paper investigates an integrated on-line sensor fault diagnostic scheme for a commercial aircraft engine based on a sliding mode observer (SMO). In this approach, one sliding mode observer is designed for engine health performance tracking, and another for sensor fault reconstruction. Both observers are employed in in-flight applications. The results of the former SMO are analyzed for post-flight updating the baseline model of the latter. This idea is practical and feasible since the updating process does not require the algorithm to be regulated or redesigned, so that ground-based intervention is avoided, and the update process is implemented in an economical and efficient way. With this setup, the robustness of the proposed scheme to the health degradation is much enhanced and the latter SMO is able to fulfill sensor fault reconstruction over the course of the engine life. The proposed sensor fault diagnostic system is applied to a nonlinear simulation of a commercial aircraft engine, and its effectiveness is evaluated in several fault scenarios.

Energy efficient engine: Flight propulsion system, preliminary analysis and design update

NASA Technical Reports Server (NTRS)

Stearns, E. M.

1982-01-01

The preliminary design of General Electric's Energy Efficient Engine (E3) was reported in detail in 1980. Since then, the design has been refined and the components have been rig-tested. The changes which have occurred in the engine and a reassessment of the economic payoff are presented in this report. All goals for efficiency, environmental considerations, and economic payoff are being met. The E3 Flight Propulsion System has 14.9% lower sfc than a CF6-50C. It provides a 7.1% reduction in direct operating cost for a short haul domestic transport and 14.5% reduction for an international long distance transport.

Reuse fo a Cold War Surveillance Drone to Flight Test a NASA Rocket Based Combined Cycle Engine

NASA Technical Reports Server (NTRS)

Brown, T. M.; Smith, Norm

1999-01-01

Plans for and early feasibility investigations into the modification of a Lockheed D21B drone to flight test the DRACO Rocket Based Combined Cycle (RBCC) engine are discussed. Modifications include the addition of oxidizer tanks, modern avionics systems, actuators, and a vehicle recovery system. Current study results indicate that the D21B is a suitable candidate for this application and will allow demonstrations of all DRACO engine operating modes at Mach numbers between 0.8 and 4.0. Higher Mach numbers may be achieved with more extensive modification. Possible project risks include low speed stability and control, and recovery techniques.

SSME/side loads analysis for flight configuration, revision A. [structural analysis of space shuttle main engine under side load excitation

NASA Technical Reports Server (NTRS)

Holland, W.

1974-01-01

This document describes the dynamic loads analysis accomplished for the Space Shuttle Main Engine (SSME) considering the side load excitation associated with transient flow separation on the engine bell during ground ignition. The results contained herein pertain only to the flight configuration. A Monte Carlo procedure was employed to select the input variables describing the side load excitation and the loads were statistically combined. This revision includes an active thrust vector control system representation and updated orbiter thrust structure stiffness characteristics. No future revisions are planned but may be necessary as system definition and input parameters change.

Energy efficient engine: Flight propulsion system preliminary analysis and design

NASA Technical Reports Server (NTRS)

Johnston, R. P.; Beitler, R. S.; Bobinger, R. O.; Broman, C. L.; Gravitt, R. D.; Heineke, H.; Holloway, P. R.; Klem, J. S.; Nash, D. O.; Ortiz, P.

1980-01-01

The characteristics of an advanced flight propulsion system (FPS), suitable for introduction in the late 1980's to early 1990's, was more fully defined. It was determined that all goals for efficiency, environmental considerations, and economics could be met or exceeded with the possible exception of NOx emission. In evaluating the FPS, all aspects were considered including component design, performance, weight, initial cost, maintenance cost, engine system integration (including nacelle), and aircraft integration considerations. The current FPS installed specific fuel consumption was reduced 14.2% from that of the CF6-50C reference engine. When integrated into an advanced, subsonic, study transport, the FPS produced a fuel burn savings of 15 to 23% and a direct operating cost reduction of 5 to 12% depending on the mission and study aircraft characteristics relative to the reference engine.

Perseus High Altitude Remotely Piloted Aircraft on Ramp

NASA Technical Reports Server (NTRS)

1991-01-01

The Perseus proof-of-concept vehicle waits on Rogers Dry Lake in the pre-dawn darkness before a test flight at the Dryden Flight Research Center, Edwards, California. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus in Flight

NASA Technical Reports Server (NTRS)

1991-01-01

The Perseus proof-of-concept vehicle flies over Rogers Dry Lake at the Dryden Flight Research Center, Edwards, California, to test basic design concepts for the remotely-piloted, high-altitude vehicle. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B over Edwards AFB on a Development Flight

NASA Technical Reports Server (NTRS)

1998-01-01

A long, slender wing and a pusher propeller at the rear characterize the Perseus B remotely-piloted research aircraft, seen here during a test flight in April1998. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Hyper-X Research Vehicle (HXRV) Experimental Aerodynamics Test Program Overview

NASA Technical Reports Server (NTRS)

Holland, Scott D.; Woods, William C.; Engelund, Walter C.

2000-01-01

This paper provides an overview of the experimental aerodynamics test program to ensure mission success for the autonomous flight of the Hyper-X Research Vehicle (HXRV). The HXRV is a 12-ft long, 2700 lb lifting body technology demonstrator designed to flight demonstrate for the first time a fully airframe integrated scramjet propulsion system. Three flights are currently planned, two at Mach 7 and one at Mach 10, beginning in the fall of 2000. The research vehicles will be boosted to the prescribed scramjet engine test point where they will separate from the booster, stabilize. and initiate engine test. Following 5+ seconds of powered flight and 15 seconds of cowl-open tares, the cowl will close and the vehicle will fly a controlled deceleration trajectory which includes numerous control doublets for in-flight aerodynamic parameter identification. This paper reviews the preflight testing activities, wind tunnel models, test rationale. risk reduction activities, and sample results from wind tunnel tests supporting the flight trajectory of the HXRV from hypersonic engine test point through subsonic flight termination.

Hyper-X Research Vehicle (HXRV) Experimental Aerodynamics Test Program Overview

NASA Technical Reports Server (NTRS)

Holland, Scott D.; Woods, William C.; Engelund, Walter C.

2000-01-01

This paper provides an overview of the experimental aerodynamics test program to ensure mission success for the autonomous flight of the Hyper-X Research Vehicle (HXRV). The HXRV is a 12-ft long, 2700 lb lifting body technology demonstrator designed to flight demonstrate for the first time a fully airframe integrated scramjet propulsion system. Three flights are currently planned, two at Mach 7 and one at Mach 10, beginning in the fall of 2000. The research vehicles will be boosted to the prescribed scramjet engine test point where they will separate from the booster, stabilize, and initiate engine test. Following 5+ seconds of powered flight and 15 seconds of cow-open tares, the cowl will close and the vehicle will fly a controlled deceleration trajectory which includes numerous control doublets for in-flight aerodynamic parameter identification. This paper reviews the preflight testing activities, wind tunnel models, test rationale, risk reduction activities, and sample results from wind tunnel tests supporting the flight trajectory of the HXRV from hypersonic engine test point through subsonic flight termination.

NASA Concludes Summer of RS-25 Testing

NASA Image and Video Library

2017-08-30

NASA engineers closed a summer of hot fire testing Aug. 30 for flight controllers on RS-25 engines that will help power the new Space Launch System (SLS) rocket being built to carry astronauts to deep-space destinations, including Mars. The 500-second hot fire an RS-25 engine flight controller unit on the A-1 Test Stand at Stennis Space Center near Bay St. Louis, Mississippi marked another step toward the nation’s return to human deep-space exploration missions.

Accuracy and Speed of Response to Different Voice Types in a Cockpit Voice Warning System

DTIC Science & Technology

1983-09-01

military aircraft. Different levels of engine background noise, signal to noise ratio of the warning message, and precursor delivery formats were used. The...flight deck signals, the Society of Automotive Engineers stated that a unique, attention-getting sound (such as a chime, 4 etc.) together with voice...aircr,-ft wherein there is no flight engineer position" (cited in Thorburn, 1971, p. 3). The AFIAS letter cited several incidents in which the VWS had

MD-11 PCA - Research flight team egress

NASA Technical Reports Server (NTRS)

1995-01-01

This McDonnell Douglas MD-11 has parked on the flightline at NASA's Dryden Flight Research Center, Edwards, California, following its completion of the first and second landings ever performed by a transport aircraft under engine power only (on Aug. 29, 1995). The milestone flight, with NASA research pilot and former astronaut Gordon Fullerton at the controls, was part of a NASA project to develop a computer-assisted engine control system that enables a pilot to land a plane safely when its normal control surfaces are disabled. Coming down the steps from the aircraft are Gordon Fullerton (in front), followed by Bill Burcham, Propulsion Controlled Aircraft (PCA) project engineer at Dryden; NASA Dryden controls engineer John Burken; John Feather of McDonnell Douglas; and Drew Pappas, McDonnell Douglas' project manager for PCA.

Perseus A, Part of the ERAST Program, in Flight

NASA Technical Reports Server (NTRS)

1993-01-01

The Perseus A remotely-piloted research vehicle flies low over Rogers Dry Lake on its maiden voyage Dec. 21, 1993, at the Dryden Flight Research Center, Edwards, California. The Perseus, designed and built by Aurora Flight Sciences Corp., was towed into the air by a ground vehicle. At about 700 ft. the aircraft was released and the engine turned the propeller to take the plane to its desired altitude. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus A High Altitude Remotely Piloted Aircraft being Towed in Flight

NASA Technical Reports Server (NTRS)

1994-01-01

Perseus A, a remotely piloted, high-altitude research vehicle designed by Aurora Flight Sciences Corp., takes off from Rogers Dry Lake at the Dryden Flight Research Center, Edwards, California. The Perseus was towed into the air by a ground vehicle. At about 700 ft. the aircraft was released and the engine turned the propeller to take the plane to its desired altitude. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Future of Software Engineering Standards

NASA Technical Reports Server (NTRS)

Poon, Peter T.

1997-01-01

In the new millennium, software engineering standards are expected to continue to influence the process of producing software-intensive systems which are cost-effetive and of high quality. These sytems may range from ground and flight systems used for planetary exploration to educational support systems used in schools as well as consumer-oriented systems.

An Electronic Workshop on the Performance Seeking Control and Propulsion Controlled Aircraft Results of the F-15 Highly Integrated Digital Electronic Control Flight Research Program

NASA Technical Reports Server (NTRS)

Powers, Sheryll Goecke (Compiler)

1995-01-01

Flight research for the F-15 HIDEC (Highly Integrated Digital Electronic Control) program was completed at NASA Dryden Flight Research Center in the fall of 1993. The flight research conducted during the last two years of the HIDEC program included two principal experiments: (1) performance seeking control (PSC), an adaptive, real-time, on-board optimization of engine, inlet, and horizontal tail position on the F-15; and (2) propulsion controlled aircraft (PCA), an augmented flight control system developed for landings as well as up-and-away flight that used only engine thrust (flight controls locked) for flight control. In September 1994, the background details and results of the PSC and PCA experiments were presented in an electronic workshop, accessible through the Dryden World Wide Web (http://www.dfrc.nasa.gov/dryden.html) and as a compact disk.

An Innovative Instrument Flight Training Program.

ERIC Educational Resources Information Center

Caro, Paul W.

An innovative flight training program, its development, and initial administration are described. The program involves use of a commercially available training device in a twin-engine transition and instrument training course. Principal features of the training include redefinition of the flight instructor's role, and incentive award system,…

Integrated flight/propulsion control system design based on a decentralized, hierarchical approach

NASA Technical Reports Server (NTRS)

Mattern, Duane; Garg, Sanjay; Bullard, Randy

1989-01-01

A sample integrated flight/propulsion control system design is presented for the piloted longitudinal landing task with a modern, statistically unstable fighter aircraft. The design procedure is summarized. The vehicle model used in the sample study is described, and the procedure for partitioning the integrated system is presented along with a description of the subsystems. The high-level airframe performance specifications and control design are presented and the control performance is evaluated. The generation of the low-level (engine) subsystem specifications from the airframe requirements are discussed, and the engine performance specifications are presented along with the subsystem control design. A compensator to accommodate the influence of airframe outputs on the engine subsystem is also considered. Finally, the entire closed loop system performance and stability characteristics are examined.

Integrated flight/propulsion control system design based on a decentralized, hierarchical approach

NASA Technical Reports Server (NTRS)

Mattern, Duane; Garg, Sanjay; Bullard, Randy

1989-01-01

A sample integrated flight/propulsion control system design is presented for the piloted longitiudinal landing task with a modern, statistically unstable fighter aircraft. The design procedure is summarized, the vehicle model used in the sample study is described, and the procedure for partitioning the integrated system is presented along with a description of the subsystems. The high-level airframe performance specifications and control design are presented and the control performance is evaluated. The generation of the low-level (engine) subsystem specifications from the airframe requirements are discussed, and the engine performance specifications are presented along with the subsystem control design. A compensator to accommodate the influence of airframe outputs on the engine subsystem is also considered. Finally, the entire closed loop system performance and stability characteristics are examined.

Status of 'HIMES' reentry flight test project

NASA Astrophysics Data System (ADS)

Inatani, Yoshifumi; Kawaguchi, Jun'ichiro; Yonemoto, Koichi

1990-10-01

The salient features of the Highly Maneuverable Experimental Space (HIMES) vehicle which is being developed by the Institute of Space and Astronautical Science of Japan are discussed together with the results of tests conducted. Analytical studies carried out so far include system analyses, aerodynamic design, the navigation/guidance and control systems, the propulsion system, and structural studies. Results of flight tests conducted to verify these analyses include the low-speed gliding flight test and the atmospheric reentry flight test, as well as a ground firing test of the hydrogen-fueled propulsion system. Diagrams are presented of the HIMES vehicle and its propulsion engines.

Testing Strategies and Methodologies for the Max Launch Abort System

NASA Technical Reports Server (NTRS)

Schaible, Dawn M.; Yuchnovicz, Daniel E.

2011-01-01

The National Aeronautics and Space Administration (NASA) Engineering and Safety Center (NESC) was tasked to develop an alternate, tower-less launch abort system (LAS) as risk mitigation for the Orion Project. The successful pad abort flight demonstration test in July 2009 of the "Max" launch abort system (MLAS) provided data critical to the design of future LASs, while demonstrating the Agency s ability to rapidly design, build and fly full-scale hardware at minimal cost in a "virtual" work environment. Limited funding and an aggressive schedule presented a challenge for testing of the complex MLAS system. The successful pad abort flight demonstration test was attributed to the project s systems engineering and integration process, which included: a concise definition of, and an adherence to, flight test objectives; a solid operational concept; well defined performance requirements, and a test program tailored to reducing the highest flight test risks. The testing ranged from wind tunnel validation of computational fluid dynamic simulations to component ground tests of the highest risk subsystems. This paper provides an overview of the testing/risk management approach and methodologies used to understand and reduce the areas of highest risk - resulting in a successful flight demonstration test.

Flight testing of a fiber optic temperature sensor

NASA Technical Reports Server (NTRS)

Finney, M. J.; Tregay, G. W.; Calabrese, P. R.

1993-01-01

A fiber optic temperature sensor (FOTS) system consisting of an optical probe, a flexible fiber optic cable, and an electro-optic signal processor was fabricated to measure the gas temperature in a turbine engine. The optical probe contained an emissive source embedded in a sapphire lightguide coupled to a fiber-optic jumper cable and was retrofitted into an existing thermocouple probe housing. The flexible fiber optic cable was constructed with 200 micron core, polyimide-coated fiber and was ruggedized for an aircraft environment. The electro-optic signal processing unit was used to ratio the intensities of two wavelength intervals and provided an analog output value of the indicated temperature. Subsequently, this optical sensor system was installed on a NASA Dryden F-15 Highly Integrated Digital Electronic Control (HIDEC) Aircraft Engine and several flight tests were conducted. Over the course of flight testing, the FOTS system's response was proportional to the average of the existing thermocouples sensing the changes in turbine engine thermal conditions.

Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems

NASA Technical Reports Server (NTRS)

Trevino, Luis; Brown, Terry; Crumbley, R. T. (Technical Monitor)

2001-01-01

The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.

D-21B RBCC Modification Feasibility Study

NASA Technical Reports Server (NTRS)

1999-01-01

This report presents a feasibility study on the modifications required to re-engine the Lockheed D-21 Drone for use as a NASA RBCC engine. An introduction, background information, engine configuration and performance, propulsion system integration, loads/thermal analysis, avionics/systems, flight test results, costs and work schedule, and some conclusions are presented.

Ice Crystal Icing Engine Testing in the NASA Glenn Research Center's Propulsion Systems Laboratory: Altitude Investigation

NASA Technical Reports Server (NTRS)

Oliver, Michael J.

2014-01-01

The National Aeronautics and Space Administration (NASA) conducted a full scale ice crystal icing turbofan engine test using an obsolete Allied Signal ALF502-R5 engine in the Propulsion Systems Laboratory (PSL) at NASA Glenn Research Center. The test article used was the exact engine that experienced a loss of power event after the ingestion of ice crystals while operating at high altitude during a 1997 Honeywell flight test campaign investigating the turbofan engine ice crystal icing phenomena. The test plan included test points conducted at the known flight test campaign field event pressure altitude and at various pressure altitudes ranging from low to high throughout the engine operating envelope. The test article experienced a loss of power event at each of the altitudes tested. For each pressure altitude test point conducted the ambient static temperature was predicted using a NASA engine icing risk computer model for the given ambient static pressure while maintaining the engine speed.

X-33 Attitude Control System Design for Ascent, Transition, and Entry Flight Regimes

NASA Technical Reports Server (NTRS)

Hall, Charles E.; Gallaher, Michael W.; Hendrix, Neal D.

1998-01-01

The Vehicle Control Systems Team at Marshall Space Flight Center, Systems Dynamics Laboratory, Guidance and Control Systems Division is designing under a cooperative agreement with Lockheed Martin Skunkworks, the Ascent, Transition, and Entry flight attitude control system for the X-33 experimental vehicle. Ascent flight control begins at liftoff and ends at linear aerospike main engine cutoff (NECO) while Transition and Entry flight control begins at MECO and concludes at the terminal area energy management (TAEM) interface. TAEM occurs at approximately Mach 3.0. This task includes not only the design of the vehicle attitude control systems but also the development of requirements for attitude control system components and subsystems. The X-33 attitude control system design is challenged by a short design cycle, the design environment (Mach 0 to about Mach 15), and the X-33 incremental test philosophy. The X-33 design-to-launch cycle of less than 3 years requires a concurrent design approach while the test philosophy requires design adaptation to vehicle variations that are a function of Mach number and mission profile. The flight attitude control system must deal with the mixing of aerosurfaces, reaction control thrusters, and linear aerospike engine control effectors and handle parasitic effects such as vehicle flexibility and propellant sloshing from the uniquely shaped propellant tanks. The attitude control system design is, as usual, closely linked to many other subsystems and must deal with constraints and requirements from these subsystems.

The 2003 Goddard Rocket Replica Project: A Reconstruction of the World's First Functional Liquid Rocket System

NASA Technical Reports Server (NTRS)

Farr, R. A.; Elam, S. K.; Hicks, G. D.; Sanders, T. M.; London, J. R.; Mayne, A. W.; Christensen, D. L.

2003-01-01

As a part of NASA s 2003 Centennial of Flight celebration, engineers and technicians at Marshall Space Flight Center (MSFC), Huntsville, Alabama, in cooperation with the Alabama-Mississippi AIAA Section, have reconstructed historically accurate, functional replicas of Dr. Robert H. Goddard s 1926 first liquid- fuel rocket. The purposes of this project were to clearly understand, recreate, and document the mechanisms and workings of the 1926 rocket for exhibit and educational use, creating a vital resource for researchers studying the evolution of liquid rocketry for years to come. The MSFC team s reverse engineering activity has created detailed engineering-quality drawings and specifications describing the original rocket and how it was built, tested, and operated. Static hot-fire tests, as well as flight demonstrations, have further defined and quantified the actual performance and engineering actual performance and engineering challenges of this major segment in early aerospace history.

Development and Flight Test of an Augmented Thrust-Only Flight Control System on an MD-11 Transport Airplane

NASA Technical Reports Server (NTRS)

Burcham, Frank W., Jr.; Maine, Trindel A.; Burken, John J.; Pappas, Drew

1996-01-01

An emergency flight control system using only engine thrust, called Propulsion-Controlled Aircraft (PCA), has been developed and flight tested on an MD-11 airplane. In this thrust-only control system, pilot flight path and track commands and aircraft feedback parameters are used to control the throttles. The PCA system was installed on the MD-11 airplane using software modifications to existing computers. Flight test results show that the PCA system can be used to fly to an airport and safely land a transport airplane with an inoperative flight control system. In up-and-away operation, the PCA system served as an acceptable autopilot capable of extended flight over a range of speeds and altitudes. The PCA approaches, go-arounds, and three landings without the use of any non-nal flight controls have been demonstrated, including instrument landing system-coupled hands-off landings. The PCA operation was used to recover from an upset condition. In addition, PCA was tested at altitude with all three hydraulic systems turned off. This paper reviews the principles of throttles-only flight control; describes the MD-11 airplane and systems; and discusses PCA system development, operation, flight testing, and pilot comments.

Emergency flight control system using one engine and fuel transfer

NASA Technical Reports Server (NTRS)

Burcham, Jr., Frank W. (Inventor); Burken, John J. (Inventor); Le, Jeanette (Inventor)

2000-01-01

A system for emergency aircraft control uses at least one engine and lateral fuel transfer that allows a pilot to regain control over an aircraft under emergency conditions. Where aircraft propulsion is available only through engines on one side of the aircraft, lateral fuel transfer provides means by which the center of gravity of the aircraft can be moved over to the wing associated with the operating engine, thus inducing a moment that balances the moment from the remaining engine, allowing the pilot to regain control over the aircraft. By implementing the present invention in flight control programming associated with a flight control computer (FCC), control of the aircraft under emergency conditions can be linked to the yoke or autopilot knob of the aircraft. Additionally, the center of gravity of the aircraft can be shifted in order to effect maneuvers and turns by spacing such center of gravity either closer to or farther away from the propelling engine or engines. In an alternative embodiment, aircraft having a third engine associated with the tail section or otherwise are accommodated and implemented by the present invention by appropriately shifting the center of gravity of the aircraft. Alternatively, where a four-engine aircraft has suffered loss of engine control on one side of the plane, the lateral fuel transfer may deliver the center of gravity closer to the two remaining engines. Differential thrust between the two can then control the pitch and roll of the aircraft in conjunction with lateral fuel transfer.

Perseus Taxi

NASA Technical Reports Server (NTRS)

1991-01-01

The Perseus proof-of-concept vehicle is seen here as it taxis on Rogers Dry Lake, adjacent the Dryden Flight Research Center, Edwards, California. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B Parked on Ramp

NASA Technical Reports Server (NTRS)

1999-01-01

The long, slender wing of the Perseus B remotely piloted research aircraft can be clearly seen in this photo, taken on the ramp of NASA's Dryden Flight Research Center in September 1999. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B Parked on Ramp

NASA Technical Reports Server (NTRS)

1999-01-01

A long, slender wing and a pusher propeller at the rear characterize the Perseus B remotely piloted aircraft, seen here on the ramp at NASA's Dryden Flight Research Center, Edwards, California. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Test and evaluation of the HIDEC engine uptrim algorithm

NASA Technical Reports Server (NTRS)

Ray, R. J.; Myers, L. P.

1986-01-01

The highly integrated digital electronic control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine-airframe control systems. Performance improvements will result from an adaptive engine stall margin mode, a highly integrated mode that uses the airplane flight conditions and the resulting inlet distortion to continuously compute engine stall margin. When there is excessive stall margin, the engine is uptrimmed for more thrust by increasing engine pressure ratio (EPR). The EPR uptrim logic has been evaluated and implemented into computer simulations. Thrust improvements over 10 percent are predicted for subsonic flight conditions. The EPR uptrim was successfully demonstrated during engine ground tests. Test results verify model predictions at the conditions tested.

What's Happening in the Software Engineering Laboratory?

NASA Technical Reports Server (NTRS)

Pajerski, Rose; Green, Scott; Smith, Donald

1995-01-01

Since 1976 the Software Engineering Laboratory (SEL) has been dedicated to understanding and improving the way in which one NASA organization the Flight Dynamics Division (FDD) at Goddard Space Flight Center, develops, maintains, and manages complex flight dynamics systems. This paper presents an overview of recent activities and studies in SEL, using as a framework the SEL's organizational goals and experience based software improvement approach. It focuses on two SEL experience areas : (1) the evolution of the measurement program and (2) an analysis of three generations of Cleanroom experiments.

Identification of Spey engine dynamics in the augmentor wing jet STOL research aircraft from flight data

NASA Technical Reports Server (NTRS)

Dehoff, R. L.; Reed, W. B.; Trankle, T. L.

1977-01-01

The development and validation of a spey engine model is described. An analysis of the dynamical interactions involved in the propulsion unit is presented. The model was reduced to contain only significant effects, and was used, in conjunction with flight data obtained from an augmentor wing jet STOL research aircraft, to develop initial estimates of parameters in the system. The theoretical background employed in estimating the parameters is outlined. The software package developed for processing the flight data is described. Results are summarized.

The 1991 research and technology report, Goddard Space Flight Center

NASA Technical Reports Server (NTRS)

Soffen, Gerald (Editor); Ottenstein, Howard (Editor); Montgomery, Harry (Editor); Truszkowski, Walter (Editor); Frost, Kenneth (Editor); Sullivan, Walter (Editor); Boyle, Charles (Editor)

1991-01-01

The 1991 Research and Technology Report for Goddard Space Flight Center is presented. Research covered areas such as (1) earth sciences including upper atmosphere, lower atmosphere, oceans, hydrology, and global studies; (2) space sciences including solar studies, planetary studies, Astro-1, gamma ray investigations, and astrophysics; (3) flight projects; (4) engineering including robotics, mechanical engineering, electronics, imaging and optics, thermal and cryogenic studies, and balloons; and (5) ground systems, networks, and communications including data and networks, TDRSS, mission planning and scheduling, and software development and test.

iss028e034978

NASA Image and Video Library

2011-08-30

ISS028-E-034978 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

iss028e034993

NASA Image and Video Library

2011-08-30

ISS028-E-034993 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

iss028e034980

NASA Image and Video Library

2011-08-30

ISS028-E-034980 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

iss028e035002

NASA Image and Video Library

2011-08-30

ISS028-E-035002 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

iss028e034984

NASA Image and Video Library

2011-08-30

ISS028-E-034984 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

iss028e034992

NASA Image and Video Library

2011-08-30

ISS028-E-034992 (30 Aug. 2011) --- NASA astronaut Mike Fossum, Expedition 28 flight engineer, performs in-flight maintenance on the Muscle Atrophy Research & Exercise System (MARES) in the Columbus laboratory of the International Space Station.

Barrett during TVIS maintenance

NASA Image and Video Library

2009-04-21

ISS019-E-008750 (21 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barrett during TVIS maintenance

NASA Image and Video Library

2009-04-21

ISS019-E-008752 (21 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barrett during TVIS maintenance

NASA Image and Video Library

2009-04-21

ISS019-E-008767 (21 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barrett during TVIS maintenance

NASA Image and Video Library

2009-04-21

ISS019-E-008764 (21 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Lessons learned from the Space Flyer Unit (SFU) mission.

PubMed

Kuriki, Kyoichi; Ninomiya, Keiken; Takei, Mitsuru; Matsuoka, Shinobu

2002-11-01

The Space Flyer Unit (SFU) system and mission chronology are briefly introduced. Lessons learned from the SFU mission are categorized as programmatic and engineering lessons. In the programmatic category are dealt with both international and domestic collaborations. As for the engineering lessons safety design, orbital operation, in-flight anomaly, and post flight analyses are the major topics reviewed. c2002 Elsevier Science Ltd. All rights reserved.

Chiao performs in-flight maintenance on the TVIS in the SM during Expedition 10

NASA Image and Video Library

2005-02-15

ISS010-E-17815 (15 February 2005) --- Cosmonaut Salizhan S. Sharipov, Expedition 10 flight engineer representing Russia's Federal Space Agency, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station (ISS).

Thermodynamic Cycle Analysis of Magnetohydrodynamic-Bypass Hypersonic Airbreathing Engines

NASA Technical Reports Server (NTRS)

Litchford, R. J.; Cole, J. W.; Bityurin, V. A.; Lineberry, J. T.

2000-01-01

The prospects for realizing a magnetohydrodynamic (MHD) bypass hypersonic airbreathing engine are examined from the standpoint of fundamental thermodynamic feasibility. The MHD-bypass engine, first proposed as part of the Russian AJAX vehicle concept, is based on the idea of redistributing energy between various stages of the propulsion system flow train. The system uses an MHD generator to extract a portion of the aerodynamic heating energy from the inlet and an MHD accelerator to reintroduce this power as kinetic energy in the exhaust stream. In this way, the combustor entrance Mach number can be limited to a specified value even as the flight Mach number increases. Thus, the fuel and air can be efficiently mixed and burned within a practical combustor length, and the flight Mach number operating envelope can be extended. In this paper, we quantitatively assess the performance potential and scientific feasibility of MHD-bypass engines using a simplified thermodynamic analysis. This cycle analysis, based on a thermally and calorically perfect gas, incorporates a coupled MHD generator-accelerator system and accounts for aerodynamic losses and thermodynamic process efficiencies in the various engin components. It is found that the flight Mach number range can be significantly extended; however, overall performance is hampered by non-isentropic losses in the MHD devices.

SMAP Instrument Mechanical System Engineering

NASA Technical Reports Server (NTRS)

Slimko, Eric; French, Richard; Riggs, Benjamin

2013-01-01

The Soil Moisture Active Passive (SMAP) mission, scheduled for launch by the end of 2014, is being developed to measure the soil moisture and soil freeze/thaw state on a global scale over a three-year period. The accuracy, resolution, and global coverage of SMAP measurements are invaluable across many science and applications disciplines including hydrology, climate, carbon cycle, and the meteorological, environment, and ecology applications communities. The SMAP observatory is composed of a despun bus and a spinning instrument platform that includes both a deployable 6 meter aperture low structural frequency Astromesh reflector and a spin control system. The instrument section has engendered challenging mechanical system issues associated with the antenna deployment, flexible antenna pointing in the context of a multitude of disturbances, spun section mass properties, spin control system development, and overall integration with the flight system on both mechanical and control system levels. Moreover, the multitude of organizations involved, including two major vendors providing the spin subsystem and reflector boom assembly plus the flight system mechanical and guidance, navigation, and control teams, has led to several unique system engineering challenges. Capturing the key physics associated with the function of the flight system has been challenging due to the many different domains that are applicable. Key interfaces and operational concepts have led to complex negotiations because of the large number of organizations that integrate with the instrument mechanical system. Additionally, the verification and validation concerns associated with the mechanical system have had required far-reaching involvement from both the flight system and other subsystems. The SMAP instrument mechanical systems engineering issues and their solutions are described in this paper.

Large Liquid Rocket Testing: Strategies and Challenges

NASA Technical Reports Server (NTRS)

Rahman, Shamim A.; Hebert, Bartt J.

2005-01-01

Rocket propulsion development is enabled by rigorous ground testing in order to mitigate the propulsion systems risks that are inherent in space flight. This is true for virtually all propulsive devices of a space vehicle including liquid and solid rocket propulsion, chemical and non-chemical propulsion, boost stage and in-space propulsion and so forth. In particular, large liquid rocket propulsion development and testing over the past five decades of human and robotic space flight has involved a combination of component-level testing and engine-level testing to first demonstrate that the propulsion devices were designed to meet the specified requirements for the Earth to Orbit launchers that they powered. This was followed by a vigorous test campaign to demonstrate the designed propulsion articles over the required operational envelope, and over robust margins, such that a sufficiently reliable propulsion system is delivered prior to first flight. It is possible that hundreds of tests, and on the order of a hundred thousand test seconds, are needed to achieve a high-reliability, flight-ready, liquid rocket engine system. This paper overviews aspects of earlier and recent experience of liquid rocket propulsion testing at NASA Stennis Space Center, where full scale flight engines and flight stages, as well as a significant amount of development testing has taken place in the past decade. The liquid rocket testing experience discussed includes testing of engine components (gas generators, preburners, thrust chambers, pumps, powerheads), as well as engine systems and complete stages. The number of tests, accumulated test seconds, and years of test stand occupancy needed to meet varying test objectives, will be selectively discussed and compared for the wide variety of ground test work that has been conducted at Stennis for subscale and full scale liquid rocket devices. Since rocket propulsion is a crucial long-lead element of any space system acquisition or development, the appropriate plan and strategy must be put in place at the outset of the development effort. A deferment of this test planning, or inattention to strategy, will compromise the ability of the development program to achieve its systems reliability requirements and/or its development milestones. It is important for the government leadership and support team, as well as the vehicle and propulsion development team, to give early consideration to this aspect of space propulsion and space transportation work.

NASA Space Engineering Research Center for VLSI System Design

NASA Technical Reports Server (NTRS)

1993-01-01

This annual report outlines the activities of the past year at the NASA SERC on VLSI Design. Highlights for this year include the following: a significant breakthrough was achieved in utilizing commercial IC foundries for producing flight electronics; the first two flight qualified chips were designed, fabricated, and tested and are now being delivered into NASA flight systems; and a new technology transfer mechanism has been established to transfer VLSI advances into NASA and commercial systems.

Orion Flight Test Architecture Benefits of MBSE Approach

NASA Technical Reports Server (NTRS)

Reed, Don; Simpson, Kim

2012-01-01

Exploration Flight Test 1 (EFT-1) is an unmanned first orbital flight test of the Multi Purpose Crew Vehicle (MPCV) Mission s purpose is to: Test Orion s ascent, on-orbit and entry capabilities Monitor critical activities Provide ground control in support of contingency scenarios Requires development of a large scale end-to-end information system network architecture To effectively communicate the scope of the end-to-end system a model-based system engineering approach was chosen.

Modeling and HIL Simulation of Flight Conditions Simulating Control System for the Altitude Test Facility

NASA Astrophysics Data System (ADS)

Zhou, Jun; Shen, Li; Zhang, Tianhong

2016-12-01

Simulated altitude test is an essential exploring, debugging, verification and validation means during the development of aero-engine. Free-jet engine test can simulate actual working conditions of aero-engine more realistically than direct-connect engine test but with relatively lower cost compared to propulsion wind tunnel test, thus becoming an important developing area of simulated altitude test technology. The Flight Conditions Simulating Control System (FCSCS) is of great importance to the Altitude Test Facility (ATF) but the development of that is a huge challenge. Aiming at improving the design efficiency and reducing risks during the development of FCSCS for ATFs, a Hardware- in-the-Loop (HIL) simulation system was designed and the mathematical models of key components such as the pressure stabilizing chamber, free-jet nozzle, control valve and aero-engine were built in this paper. Moreover, some HIL simulation experiments were carried out. The results show that the HIL simulation system designed and established in this paper is reasonable and effective, which can be used to adjust control parameters conveniently and assess the software and hardware in the control system immediately.

Apollo 16 mission report. Supplement 2: Service Propulsion system final flight evaluation

NASA Technical Reports Server (NTRS)

Smith, R. J.; Wood, S. C.

1974-01-01

The Apollo 16 Mission was the sixteenth in a series of flights using Apollo flight hardware and included the fifth lunar landing of the Apollo Program. The Apollo 16 Mission utilized CSM 113 which was equipped with SPS Engine S/N 66 (Injector S/N 137). The engine configuration and expected performance characteristics are presented. Since previous flight results of the SPS have consistently shown the existence of a negative mixture ratio shift, SPS Engine S/N 66 was reorificed to increase the mixture ratio for this mission. The propellant unbalance for the two major engine firings is compared with the predicted unbalance. Although the unbalance at the end of the TEI burn is significantly different than the predicted unbalance, the propellant mixture ratio was well within limits. The SPS performed six burns during the mission, with a total burn duration of 575.3 seconds. The ignition time, burn duration and velocity gain for each of the six SPS burns are reported.

A Rainbow View of NASA's RS-25 Engine Test

NASA Image and Video Library

2017-02-22

NASA engineers conducted their first RS-25 test of 2017 on the A-1 Test Stand at Stennis Space Center near Bay St. Louis, Mississippi, on Feb. 22, continuing to collect data on the performance of the rocket engine that will help power the new Space Launch System (SLS) rocket. Shown from the viewpoint of an overhead drone, the test of development engine No. 0528 ran the scheduled 380 seconds (six minutes and 20 seconds), allowing engineers to monitor various engine operating conditions. The test represents another step forward in development of the rocket that will launch humans aboard Orion deeper into space than ever before. Four RS-25 engines, together with a pair of solid rocket boosters, will power the SLS at launch on its deep-space missions. The engines for the first four SLS flights are former space shuttle main engines, which were tested extensively at Stennis and are some of the most proven engines in the world. Engineers are conducting an ongoing series of tests this year for SLS on both development and flight engines for future flights to ensure the engine, outfitted with a new controller, can perform at the higher level under a variety of conditions and situations. Stennis is also preparing its B-2 Test Stand to test the core stage for the first SLS flight with Orion, known as Exploration Mission-1. That testing will involve installing the flight stage on the stand and firing its four RS-25 engines simultaneously, just as during an actual launch. The Feb. 22 test was conducted by Aerojet Rocketdyne and Syncom Space Services engineers and operators. Aerojet Rocketdyne is the prime contractor for the RS-25 engines. Syncom Space Services is the prime contractor for Stennis facilities and operations. PAO Name:Kim Henry Phone Number:256-544-1899 Email Address: kimberly.m.henry@nasa.gov

Military helicopter cockpit modernization

NASA Astrophysics Data System (ADS)

Hall, Andrew S.

2001-09-01

This paper describes some of the initiatives being progressed by Smiths Aerospace to enhance the operational effectiveness of military helicopters, with particular emphasis on the GWHL Lynx and EH Industries EH101 programs. The areas discussed include engine instrumentation, flight instrumentation and the mission system displays. Various Crew Stations are described which provide a suite of AMLCD displays which: -Integrate information from the aircraft engine, electrical power and hydraulic systems onto 5ATI displays -Integrate primary flight, navigation and mission system sensor information onto large area (61/4' square or 6' by 8') displays -Provide standby attitude and air data information in the event of major system failure on 3ATI displays.

An improved approach for flight readiness certification: Methodology for failure risk assessment and application examples. Volume 3: Structure and listing of programs

NASA Technical Reports Server (NTRS)

Moore, N. R.; Ebbeler, D. H.; Newlin, L. E.; Sutharshana, S.; Creager, M.

1992-01-01

An improved methodology for quantitatively evaluating failure risk of spaceflight systems to assess flight readiness and identify risk control measures is presented. This methodology, called Probabilistic Failure Assessment (PFA), combines operating experience from tests and flights with engineering analysis to estimate failure risk. The PFA methodology is of particular value when information on which to base an assessment of failure risk, including test experience and knowledge of parameters used in engineering analyses of failure phenomena, is expensive or difficult to acquire. The PFA methodology is a prescribed statistical structure in which engineering analysis models that characterize failure phenomena are used conjointly with uncertainties about analysis parameters and/or modeling accuracy to estimate failure probability distributions for specific failure modes. These distributions can then be modified, by means of statistical procedures of the PFA methodology, to reflect any test or flight experience. Conventional engineering analysis models currently employed for design of failure prediction are used in this methodology. The PFA methodology is described and examples of its application are presented. Conventional approaches to failure risk evaluation for spaceflight systems are discussed, and the rationale for the approach taken in the PFA methodology is presented. The statistical methods, engineering models, and computer software used in fatigue failure mode applications are thoroughly documented.

Global positioning system supported pilot's display

NASA Technical Reports Server (NTRS)

Scott, Marshall M., Jr.; Erdogan, Temel; Schwalb, Andrew P.; Curley, Charles H.

1991-01-01

The hardware, software, and operation of the Microwave Scanning Beam Landing System (MSBLS) Flight Inspection System Pilot's Display is discussed. The Pilot's Display is used in conjunction with flight inspection tests that certify the Microwave Scanning Beam Landing System used at Space Shuttle landing facilities throughout the world. The Pilot's Display was developed for the pilot of test aircraft to set up and fly a given test flight path determined by the flight inspection test engineers. This display also aids the aircraft pilot when hazy or cloud cover conditions exist that limit the pilot's visibility of the Shuttle runway during the flight inspection. The aircraft position is calculated using the Global Positioning System and displayed in the cockpit on a graphical display.

Engine systems analysis results of the Space Shuttle Main Engine redesigned powerhead initial engine level testing

NASA Technical Reports Server (NTRS)

Sander, Erik J.; Gosdin, Dennis R.

1992-01-01

Engineers regularly analyze SSME ground test and flight data with respect to engine systems performance. Recently, a redesigned SSME powerhead was introduced to engine-level testing in part to increase engine operational margins through optimization of the engine internal environment. This paper presents an overview of the MSFC personnel engine systems analysis results and conclusions reached from initial engine level testing of the redesigned powerhead, and further redesigns incorporated to eliminate accelerated main injector baffle and main combustion chamber hot gas wall degradation. The conclusions are drawn from instrumented engine ground test data and hardware integrity analysis reports and address initial engine test results with respect to the apparent design change effects on engine system and component operation.

Unmanned Aircraft Systems Traffic Management (UTM): Safely Enabling UAS Operations in Low-Altitude Airspace

NASA Technical Reports Server (NTRS)

Homola, Jeffrey; Owens, Brandon

2017-01-01

This is a presentation for a Cisco Internet of Things (IoT) Systems Engineering Virtual Training (SEVT) event. The presentation provides an overview of the UTM concept, architecture, flight test events, and lessons learned. Networking hardware used in support of flight tests is also described.

History of the Gas Turbine Engine in the United States: Bibliography

DTIC Science & Technology

1988-05-11

Space Administration, 1965. Aircraft Engine Acquisition. St. Louis, MO: US Army Aviation Systems Command, nad.. Aircraft Engine Health Monitoring System...Air Breathing Engines. 3d . Munich. 1976. Proceedings of the Third International Symposium on Air Breathing Engines, Munich, Germany, 7-12 March 1976...Curves." Flight Magazine 46 (February 1957):32. Manton, Grenville. "Salute to Seguin." Aeronautics 36 (June 1957):46. Morgan, P. F. "The Formation of

Near Earth Asteroid Scout Solar Sail Engineering Development Unit Test Suite

NASA Technical Reports Server (NTRS)

Lockett, Tiffany Russell; Few, Alexander; Wilson, Richard

2017-01-01

The Near Earth Asteroid (NEA) Scout project is a 6U reconnaissance mission to investigate a near Earth asteroid utilizing an 86m(sub 2) solar sail as the primary propulsion system. This will be the largest solar sail NASA has launched to date. NEA Scout is currently manifested on the maiden voyage of the Space Launch System in 2018. In development of the solar sail subsystem, design challenges were identified and investigated for packaging within a 6U form factor and deployment in cis-lunar space. Analysis was able to capture understanding of thermal, stress, and dynamics of the stowed system as well as mature an integrated sail membrane model for deployed flight dynamics. Full scale system testing on the ground is the optimal way to demonstrate system robustness, repeatability, and overall performance on a compressed flight schedule. To physically test the system, the team developed a flight sized engineering development unit with design features as close to flight as possible. The test suite included ascent vent, random vibration, functional deployments, thermal vacuum, and full sail deployments. All of these tests contributed towards development of the final flight unit. This paper will address several of the design challenges and lessons learned from the NEA Scout solar sail subsystem engineering development unit. Testing on the component level all the way to the integrated subsystem level. From optical properties of the sail material to fold and spooling the single sail, the team has developed a robust deployment system for the solar sail. The team completed several deployments of the sail system in preparation for flight at half scale (4m) and full scale (6.8m): boom only, half scale sail deployment, and full scale sail deployment. This paper will also address expected and received test results from ascent vent, random vibration, and deployment tests.

Comprehensive analysis of transport aircraft flight performance

NASA Astrophysics Data System (ADS)

Filippone, Antonio

2008-04-01

This paper reviews the state-of-the art in comprehensive performance codes for fixed-wing aircraft. The importance of system analysis in flight performance is discussed. The paper highlights the role of aerodynamics, propulsion, flight mechanics, aeroacoustics, flight operation, numerical optimisation, stochastic methods and numerical analysis. The latter discipline is used to investigate the sensitivities of the sub-systems to uncertainties in critical state parameters or functional parameters. The paper discusses critically the data used for performance analysis, and the areas where progress is required. Comprehensive analysis codes can be used for mission fuel planning, envelope exploration, competition analysis, a wide variety of environmental studies, marketing analysis, aircraft certification and conceptual aircraft design. A comprehensive program that uses the multi-disciplinary approach for transport aircraft is presented. The model includes a geometry deck, a separate engine input deck with the main parameters, a database of engine performance from an independent simulation, and an operational deck. The comprehensive code has modules for deriving the geometry from bitmap files, an aerodynamics model for all flight conditions, a flight mechanics model for flight envelopes and mission analysis, an aircraft noise model and engine emissions. The model is validated at different levels. Validation of the aerodynamic model is done against the scale models DLR-F4 and F6. A general model analysis and flight envelope exploration are shown for the Boeing B-777-300 with GE-90 turbofan engines with intermediate passenger capacity (394 passengers in 2 classes). Validation of the flight model is done by sensitivity analysis on the wetted area (or profile drag), on the specific air range, the brake-release gross weight and the aircraft noise. A variety of results is shown, including specific air range charts, take-off weight-altitude charts, payload-range performance, atmospheric effects, economic Mach number and noise trajectories at F.A.R. landing points.

DRACO Flowpath Performance and Environments

NASA Technical Reports Server (NTRS)

Komar, D. R.; McDonald, Jon

1999-01-01

The Advanced Space Transportation (AST) project office has challenged NASA to design, manufacture, ground-test and flight-test an axisymmetric, hydrocarbon-fueled, flight-weight, ejector-ramjet engine system testbed no later than 2005. To accomplish this, a multi-center NASA team has been assembled. The goal of this team, led by NASA-Marshall Space Flight Center (MSFC), is to develop propulsion technologies that demonstrate rocket and airbreathing combined-cycle operation (DRACO). Current technical activities include flowpath conceptual design, engine systems conceptual design, and feasibility studies investigating the integration and operation of the DRACO engine with a Lockheed D-21B drone. This paper focuses on the activities of the Flowpath Systems Product Development Team (PDT), led by NASA-Glenn Research Center (GRC) and supported by NASA-MSFC and TechLand Research, Inc. The objective of the Flowpath PDT at the start of the DRACO program was to establish a conceptual design of the flowpath aerodynamic lines, determine the preliminary performance, define the internal environments, and support the DRACO testbed concept feasibility studies. To accomplish these tasks, the PDT convened to establish a baseline flowpath concept. With the conceptual lines defined, cycle analysis tasks were planned and the flowpath performance and internal environments were defined. Additionally, sensitivity studies investigating the effects of inlet reference area, combustion performance, and combustor/nozzle materials selection were performed to support the Flowpath PDT design process. Results of these tasks are the emphasis of this paper and are intended to verify the feasibility of the DRACO flowpath and engine system as well as identify the primary technical challenges inherent in the flight-weight design of an advanced propulsion technology demonstration engine. Preliminary cycle performance decks were developed to support the testbed concept feasibility studies but are not discussed further in this paper.

A Reusable and Adaptable Software Architecture for Embedded Space Flight System: The Core Flight Software System (CFS)

NASA Technical Reports Server (NTRS)

Wilmot, Jonathan

2005-01-01

The contents include the following: High availability. Hardware is in harsh environment. Flight processor (constraints) very widely due to power and weight constraints. Software must be remotely modifiable and still operate while changes are being made. Many custom one of kind interfaces for one of a kind missions. Sustaining engineering. Price of failure is high, tens to hundreds of millions of dollars.

78 FR 39571 - Airworthiness Directives; The Boeing Company Airplanes

Federal Register 2010, 2011, 2012, 2013, 2014

2013-07-02

... 2800, Aircraft Fuel System. (e) Unsafe Condition This AD was prompted by reports of two in-service... system, followed by loss of fuel system suction feed capability on one engine, and in-flight shutdown of... and correct loss of the engine fuel suction feed capability of the fuel system, which, in the event of...

14 CFR 121.511 - Flight time limitations: Flight engineers: airplanes.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Flight time limitations: Flight engineers... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Flight Time Limitations: Supplemental Operations § 121.511 Flight time limitations: Flight engineers: airplanes. (a) In any operation in which one...

14 CFR 121.511 - Flight time limitations: Flight engineers: airplanes.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Flight time limitations: Flight engineers... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Flight Time Limitations: Supplemental Operations § 121.511 Flight time limitations: Flight engineers: airplanes. (a) In any operation in which one...

14 CFR 121.511 - Flight time limitations: Flight engineers: airplanes.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Flight time limitations: Flight engineers... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Flight Time Limitations: Supplemental Operations § 121.511 Flight time limitations: Flight engineers: airplanes. (a) In any operation in which one...

14 CFR 121.511 - Flight time limitations: Flight engineers: airplanes.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Flight time limitations: Flight engineers... OPERATING REQUIREMENTS: DOMESTIC, FLAG, AND SUPPLEMENTAL OPERATIONS Flight Time Limitations: Supplemental Operations § 121.511 Flight time limitations: Flight engineers: airplanes. (a) In any operation in which one...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2013 CFR

2013-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2014 CFR

2014-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2011 CFR

2011-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2010 CFR

2010-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

14 CFR 27.955 - Fuel flow.

Code of Federal Regulations, 2012 CFR

2012-01-01

... STANDARDS: NORMAL CATEGORY ROTORCRAFT Powerplant Fuel System § 27.955 Fuel flow. (a) General. The fuel system for each engine must be shown to provide the engine with at least 100 percent of the fuel required... to rotorcraft flight attitudes. (4) The critical fuel pump (for pump-fed systems) is installed to...

Development Activities on Airbreathing Combined Cycle Engines

NASA Technical Reports Server (NTRS)

McArthur, J. Craig; Lyles, Garry (Technical Monitor)

2000-01-01

Contents include the following: Advanced reusable transportation(ART); aerojet and rocketdyne tests, RBCC focused concept flowpaths,fabricate flight weigh, test select components, document ART project, Istar (Integrated system test of an airbreathing rocket); combined cycle propulsion testbed;hydrocarbon demonstrator tracebility; Istar engine system and vehicle system closure study; and Istar project planning.

USAF Evaluation of an Automated Adaptive Flight Training System

DTIC Science & Technology

1975-10-01

system. C. What is the most effective wav to utilize the system in ^jierational training’ Student opinion for this question JS equally divided...None Utility hydraulic failure Flap failure left engine failure Right engine failure Stah 2 aug failure No g\\ ro approach procedure, no MIDI

Quiet Clean Short-Haul Experimental Engine (QSCEE). Preliminary analyses and design report, volume 1

NASA Technical Reports Server (NTRS)

1974-01-01

The experimental propulsion systems to be built and tested in the 'quiet, clean, short-haul experimental engine' program are presented. The flight propulsion systems are also presented. The following areas are discussed: acoustic design; emissions control; engine cycle and performance; fan aerodynamic design; variable-pitch actuation systems; fan rotor mechanical design; fan frame mechanical design; and reduction gear design.

Barratt with TVIS in Service module

NASA Image and Video Library

2009-04-23

ISS019-E-009818 (23 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barratt with TVIS in Service module

NASA Image and Video Library

2009-04-23

ISS019-E-009857 (23 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barratt with TVIS in Service module

NASA Image and Video Library

2009-04-23

ISS019-E-009840 (23 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barratt with TVIS in Service module

NASA Image and Video Library

2009-04-23

ISS019-E-009856 (23 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Barratt with TVIS in Service module

NASA Image and Video Library

2009-04-23

ISS019-E-009819 (23 April 2009) --- Astronaut Michael Barratt, Expedition 19/20 flight engineer, performs in-flight maintenance on the Treadmill Vibration Isolation System (TVIS) in the Zvezda Service Module of the International Space Station.

Perseus B Taxi Tests in Preparation for a New Series of Flight Tests

NASA Technical Reports Server (NTRS)

1998-01-01

The Perseus B remotely piloted aircraft taxis on the runway at Edwards Air Force Base, California, before a series of development flights at NASA's Dryden flight Research Center. The Perseus B is the latest of three versions of the Perseus design developed by Aurora Flight Sciences under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B Taxi Tests in Preparation for a New Series of Flight Tests

NASA Technical Reports Server (NTRS)

1998-01-01

The Perseus B remotely piloted aircraft on the runway at Edwards Air Force Base, California at the conclusion of a development flight at NASA's Dryden flight Research Center. The Perseus B is the latest of three versions of the Perseus design developed by Aurora Flight Sciences under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Engine-Out Capabilities Assessment of Heavy Lift Launch Vehicles

NASA Technical Reports Server (NTRS)

Holladay, Jon; Baggett, Keithe; Thrasher, Chad; Bellamy, K. Scott; Feldman, Stuart

2012-01-01

Engine-out (EO) is a condition that might occur during flight due to the failure of one or more engines. Protection against this occurrence can be called engine-out capability (EOC) whereupon significantly improved loss of mission may occur, in addition to reduction in performance and increased cost. A standardized engine-out capability has not been studied exhaustively as it pertains to space launch systems. This work presents results for a specific vehicle design with specific engines, but also uniquely provides an approach to realizing the necessity of EOC for any launch vehicle system design. A derived top-level approach to engine-out philosophy for a heavy lift launch vehicle is given herein, based on an historical assessment of launch vehicle capabilities. The methodology itself is not intended to present a best path forward, but instead provides three parameters for assessment of a particular vehicle. Of the several parameters affected by this EOC, the three parameters of interest in this research are reliability (Loss of Mission (LOM) and Loss of Crew (LOC)), vehicle performance, and cost. The intent of this effort is to provide insight into the impacts of EO capability on these parameters. The effects of EOC on reliability, performance and cost are detailed, including how these important launch vehicle metrics can be combined to assess what could be considered overall launch vehicle affordability. In support of achieving the first critical milestone (Mission Concept Review) in the development of the Space Launch System (SLS), a team assessed two-stage, large-diameter vehicles that utilized liquid oxygen (LOX)-RP propellants in the First Stage and LOX/LH2 propellant in the Upper Stage. With multiple large thrust-class engines employed on the stages, engine-out capability could be a significant driver to mission success. It was determined that LOM results improve by a factor of five when assuming EOC for both Core Stage (CS) (first stage) and Upper Stage (US) EO, assuming a reference launch vehicle with 5 RP engines on the CS and 3 LOX/LH2 engines on the US. The benefit of adding both CS and US engine-out capability is significant. When adding EOC for either first or second stages, there is less than a 20% benefit. Performance analysis has shown that if the vehicle is not protected for EO during the first part of the flight and only protected in the later part of the flight, there is a diminishing performance penalty, as indicated by failures occurring in the first stage at different times. This work did not consider any options to abort. While adding an engine for EOC drives cost upward, the impact depends on the number of needed engines manufactured per year and the launch manifest. There is a significant cost savings if multiple flights occur within one year. Flying two flights per year would cost approximately $4,000 per pound less than the same configuration with one flight per year, assuming both CS and US EOC. The cost is within 15% of the cost of one flight per year with no engine-out capability for the same vehicle. This study can be extended to other launch vehicles. While the numbers given in this paper are specific to a certain vehicle configuration, the process requires only a high level of data to allow an analyst to draw conclusions. The weighting of each of the identified parameters will determine the optimization of each launch vehicle. The results of this engine-out assessment provide a means to understand this optimization while maintaining an unbiased perspective.

SSME to RS-25: Challenges of Adapting a Heritage Engine to a New Vehicle Architecture

NASA Technical Reports Server (NTRS)

Ballard, Richard O.

2015-01-01

Following the cancellation of the Constellation program and retirement of the Space Shuttle, NASA initiated the Space Launch System (SLS) program to provide next-generation heavy lift cargo and crew access to space. A key constituent of the SLS architecture is the RS-25 engine, also known as the Space Shuttle Main Engine (SSME). The RS-25 was selected to serve as the main propulsion system for the SLS core stage in conjunction with the solid rocket boosters. This selection was largely based on the maturity and extensive experience gained through 135 missions, 3000+ ground tests, and over a million seconds total accumulated hot-fire time. In addition, there were also over a dozen functional flight assets remaining from the Space Shuttle program that could be leveraged to support the first four flights. However, while the RS-25 is a highly mature system, simply unbolting it from the Space Shuttle boat-tail and installing it on the new SLS vehicle is not a "plug-and-play" operation. In addition to numerous technical integration details involving changes to significant areas such as the environments, interface conditions, technical performance requirements, operational constraints and so on, there were other challenges to be overcome in the area of replacing the obsolete engine control system (ECS). While the magnitude of accomplishing this effort was less than that needed to develop and field a new clean-sheet engine system, the path to the first flight of SLS has not been without unexpected challenges.

14 CFR 125.265 - Flight engineer requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 3 2010-01-01 2010-01-01 false Flight engineer requirements. 125.265... Requirements § 125.265 Flight engineer requirements. (a) No person may operate an airplane for which a flight engineer is required by the type certification requirements without a flight crewmember holding a current...

14 CFR 125.265 - Flight engineer requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Flight engineer requirements. 125.265... Requirements § 125.265 Flight engineer requirements. (a) No person may operate an airplane for which a flight engineer is required by the type certification requirements without a flight crewmember holding a current...

14 CFR 125.265 - Flight engineer requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Flight engineer requirements. 125.265... Requirements § 125.265 Flight engineer requirements. (a) No person may operate an airplane for which a flight engineer is required by the type certification requirements without a flight crewmember holding a current...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2013 CFR

2013-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2010 CFR

2010-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2012 CFR

2012-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 63.37 - Aeronautical experience requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... flight training in the duties of a flight engineer. (3) A degree in aeronautical, electrical, or... (CONTINUED) AIRMEN CERTIFICATION: FLIGHT CREWMEMBERS OTHER THAN PILOTS Flight Engineers § 63.37 Aeronautical...— (1) On which a flight engineer is required by this chapter; or (2) That has at least three engines...

14 CFR 125.265 - Flight engineer requirements.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Flight engineer requirements. 125.265... Requirements § 125.265 Flight engineer requirements. (a) No person may operate an airplane for which a flight engineer is required by the type certification requirements without a flight crewmember holding a current...

14 CFR 125.265 - Flight engineer requirements.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Flight engineer requirements. 125.265... Requirements § 125.265 Flight engineer requirements. (a) No person may operate an airplane for which a flight engineer is required by the type certification requirements without a flight crewmember holding a current...

Development and flight test experiences with a flight-crucial digital control system

NASA Technical Reports Server (NTRS)

Mackall, Dale A.

1988-01-01

Engineers and scientists in the advanced fighter technology integration (AFTI) F-16 program investigated the integration of emerging technologies into an advanced fighter aircraft. AFTI's three major technologies included: flight-crucial digital control, decoupled aircraft flight control, and integration of avionics, flight control, and pilot displays. In addition to investigating improvements in fighter performance, researchers studied the generic problems confronting the designers of highly integrated flight-crucial digital control. An overview is provided of both the advantages and problems of integration digital control systems. Also, an examination of the specification, design, qualification, and flight test life-cycle phase is provided. An overview is given of the fault-tolerant design, multimoded decoupled flight control laws, and integrated avionics design. The approach to qualifying the software and system designs is discussed, and the effects of design choices on system qualification are highlighted.

A Comprehensive Analysis of the X-15 Flight 3-65 Accident

NASA Technical Reports Server (NTRS)

Dennehy, Cornelius J.; Orr, Jeb S.; Barshi, Immanuel; Statler, Irving C.

2014-01-01

The November 15, 1967, loss of X-15 Flight 3-65-97 (hereafter referred to as Flight 3-65) was a unique incident in that it was the first and only aerospace flight accident involving loss of crew on a vehicle with an adaptive flight control system (AFCS). In addition, Flight 3-65 remains the only incidence of a single-pilot departure from controlled flight of a manned entry vehicle in a hypersonic flight regime. To mitigate risk to emerging aerospace systems, the NASA Engineering and Safety Center (NESC) proposed a comprehensive review of this accident. The goal of the assessment was to resolve lingering questions regarding the failure modes of the aircraft systems (including the AFCS) and thoroughly analyze the interactions among the human agents and autonomous systems that contributed to the loss of the pilot and aircraft. This document contains the outcome of the accident review.

Sliding Mode Control of the X-33 with an Engine Failure

NASA Technical Reports Server (NTRS)

Shtessel, Yuri B.; Hall, Charles E.

2000-01-01

Ascent flight control of the X-3 is performed using two XRS-2200 linear aerospike engines. in addition to aerosurfaces. The baseline control algorithms are PID with gain scheduling. Flight control using an innovative method. Sliding Mode Control. is presented for nominal and engine failed modes of flight. An easy to implement, robust controller. requiring no reconfiguration or gain scheduling is demonstrated through high fidelity flight simulations. The proposed sliding mode controller utilizes a two-loop structure and provides robust. de-coupled tracking of both orientation angle command profiles and angular rate command profiles in the presence of engine failure, bounded external disturbances (wind gusts) and uncertain matrix of inertia. Sliding mode control causes the angular rate and orientation angle tracking error dynamics to be constrained to linear, de-coupled, homogeneous, and vector valued differential equations with desired eigenvalues. Conditions that restrict engine failures to robustness domain of the sliding mode controller are derived. Overall stability of a two-loop flight control system is assessed. Simulation results show that the designed controller provides robust, accurate, de-coupled tracking of the orientation angle command profiles in the presence of external disturbances and vehicle inertia uncertainties, as well as the single engine failed case. The designed robust controller will significantly reduce the time and cost associated with flying new trajectory profiles or orbits, with new payloads, and with modified vehicles

Re-Educating Jet-Engine-Researchers to Stay Relevant

NASA Astrophysics Data System (ADS)

Gal-Or, Benjamin

2016-06-01

To stay relevantly supported, jet-engine researchers, designers and operators should follow changing uses of small and large jet engines, especially those anticipated to be used by/in the next generation, JET-ENGINE-STEERED ("JES") fleets of jet drones but fewer, JES-Stealth-Fighter/Strike Aircraft. In addition, some diminishing returns from isolated, non-integrating, jet-engine component studies, vs. relevant, supersonic, shock waves control in fluidic-JES-side-effects on compressor stall dynamics within Integrated Propulsion Flight Control ("IPFC"), and/or mechanical JES, constitute key relevant methods that currently move to China, India, South Korea and Japan. The central roles of the jet engine as primary or backup flight controller also constitute key relevant issues, especially under post stall conditions involving induced engine-stress while participating in crash prevention or minimal path-time maneuvers to target. And when proper instructors are absent, self-study of the JES-STVS REVOLUTION is an updating must, where STVS stands for wing-engine-airframe-integrated, embedded stealthy-jet-engine-inlets, restructured engines inside Stealth, Tailless, canard-less, Thrust Vectoring IFPC Systems. Anti-terror and Airliners Super-Flight-Safety are anticipated to overcome US legislation red-tape that obstructs JES-add-on-emergency-kits-use.

1300099

NASA Image and Video Library

2013-02-22

DURING HIS FEB. 22 VISIT TO THE NATIONAL CENTER FOR ADVANCED MANUFACTURING RAPID PROTOTYPING FACILITY AT NASA'S MARSHALL SPACE FLIGHT CENTER, NASA ADMINISTRATOR CHARLES BOLDEN, CENTER, TALKS WITH FRANK LEDBETTER, RIGHT, CHIEF OF THE NONMETALLIC MATERIALS AND MANUFACTURING DIVISION AT MARSHALL, ABOUT THE USE OF 3-D PRINTING AND PROTOTYPING TECHNOLOGY TO CREATE PARTS FOR THE SPACE LAUNCH SYSTEM. ALSO PARTICIPATING IN THE TOUR ARE, FROM BACK RIGHT, MARSHALL CENTER DIRECTOR PATRICK SCHEUERMANN; SHERRY KITTREDGE, DEPUTY MANAGER OF THE SLS LIQUID ENGINES OFFICE; MARSHALL FLIGHT SYSTEMS DESIGN ENGINEER ROB BLACK; AND JOHN VICKERS, MANAGER OF THE NATIONAL CENTER FOR ADVANCED MANUFACTURING.

Marshall Space Flight Center Test Capabilities

NASA Technical Reports Server (NTRS)

Hamilton, Jeffrey T.

2005-01-01

The Test Laboratory at NASA's Marshall Space Flight Center has over 50 facilities across 400+ acres inside a secure, fenced facility. The entire Center is located inside the boundaries of Redstone Arsenal, a 40,000 acre military reservation. About 150 Government and 250 contractor personnel operate facilities capable of all types of propulsion and structural testing, from small components to engine systems and structural strength, structural dynamic and environmental testing. We have tremendous engineering expertise in research, evaluation, analysis, design and development, and test of space transportation systems, subsystems, and components.

Aeronautical engineering. A continuing bibliography with indexes

NASA Technical Reports Server (NTRS)

1982-01-01

This bibliography lists 326 reports, articles, and other documents introduced into the NASA scientific and technical information system in January 1982. Topics on aeronautical engineering and aerodynamics such as flight control systems, avionics, computer programs, computational fluid dynamics and composite structures are covered.

Effective Software Engineering Leadership for Development Programs

ERIC Educational Resources Information Center

Cagle West, Marsha

2010-01-01

Software is a critical component of systems ranging from simple consumer appliances to complex health, nuclear, and flight control systems. The development of quality, reliable, and effective software solutions requires the incorporation of effective software engineering processes and leadership. Processes, approaches, and methodologies for…

Analysis of airframe/engine interactions in integrated flight and propulsion control

NASA Technical Reports Server (NTRS)

Schierman, John D.; Schmidt, David K.

1991-01-01

An analysis framework for the assessment of dynamic cross-coupling between airframe and engine systems from the perspective of integrated flight/propulsion control is presented. This analysis involves to determining the significance of the interactions with respect to deterioration in stability robustness and performance, as well as critical frequency ranges where problems may occur due to these interactions. The analysis illustrated here investigates both the airframe's effects on the engine control loops and the engine's effects on the airframe control loops in two case studies. The second case study involves a multi-input/multi-output analysis of the airframe. Sensitivity studies are performed on critical interactions to examine the degradations in the system's stability robustness and performance. Magnitudes of the interactions required to cause instabilities, as well as the frequencies at which the instabilities occur are recorded. Finally, the analysis framework is expanded to include control laws which contain cross-feeds between the airframe and engine systems.

Aircraft engine sensor fault diagnostics using an on-line OBEM update method.

PubMed

Liu, Xiaofeng; Xue, Naiyu; Yuan, Ye

2017-01-01

This paper proposed a method to update the on-line health reference baseline of the On-Board Engine Model (OBEM) to maintain the effectiveness of an in-flight aircraft sensor Fault Detection and Isolation (FDI) system, in which a Hybrid Kalman Filter (HKF) was incorporated. Generated from a rapid in-flight engine degradation, a large health condition mismatch between the engine and the OBEM can corrupt the performance of the FDI. Therefore, it is necessary to update the OBEM online when a rapid degradation occurs, but the FDI system will lose estimation accuracy if the estimation and update are running simultaneously. To solve this problem, the health reference baseline for a nonlinear OBEM was updated using the proposed channel controller method. Simulations based on the turbojet engine Linear-Parameter Varying (LPV) model demonstrated the effectiveness of the proposed FDI system in the presence of substantial degradation, and the channel controller can ensure that the update process finishes without interference from a single sensor fault.

Aircraft engine sensor fault diagnostics using an on-line OBEM update method

PubMed Central

Liu, Xiaofeng; Xue, Naiyu; Yuan, Ye

2017-01-01

This paper proposed a method to update the on-line health reference baseline of the On-Board Engine Model (OBEM) to maintain the effectiveness of an in-flight aircraft sensor Fault Detection and Isolation (FDI) system, in which a Hybrid Kalman Filter (HKF) was incorporated. Generated from a rapid in-flight engine degradation, a large health condition mismatch between the engine and the OBEM can corrupt the performance of the FDI. Therefore, it is necessary to update the OBEM online when a rapid degradation occurs, but the FDI system will lose estimation accuracy if the estimation and update are running simultaneously. To solve this problem, the health reference baseline for a nonlinear OBEM was updated using the proposed channel controller method. Simulations based on the turbojet engine Linear-Parameter Varying (LPV) model demonstrated the effectiveness of the proposed FDI system in the presence of substantial degradation, and the channel controller can ensure that the update process finishes without interference from a single sensor fault. PMID:28182692

14 CFR 25.903 - Engines.

Code of Federal Regulations, 2010 CFR

2010-01-01

... chapter. (2) Each turbine engine must comply with one of the following: (i) Sections 33.76, 33.77 and 33... any engine individually in flight, except that, for turbine engine installations, the means for... might be exposed to fire must be at least fire-resistant. If hydraulic propeller feathering systems are...

14 CFR 121.425 - Flight engineers: Initial and transition flight training.

Code of Federal Regulations, 2010 CFR

2010-01-01

... 14 Aeronautics and Space 3 2010-01-01 2010-01-01 false Flight engineers: Initial and transition flight training. 121.425 Section 121.425 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION... § 121.425 Flight engineers: Initial and transition flight training. (a) Initial and transition flight...

14 CFR 121.425 - Flight engineers: Initial and transition flight training.

Code of Federal Regulations, 2014 CFR

2014-01-01

... 14 Aeronautics and Space 3 2014-01-01 2014-01-01 false Flight engineers: Initial and transition flight training. 121.425 Section 121.425 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION... § 121.425 Flight engineers: Initial and transition flight training. (a) Initial and transition flight...

14 CFR 121.425 - Flight engineers: Initial and transition flight training.

Code of Federal Regulations, 2012 CFR

2012-01-01

... 14 Aeronautics and Space 3 2012-01-01 2012-01-01 false Flight engineers: Initial and transition flight training. 121.425 Section 121.425 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION... § 121.425 Flight engineers: Initial and transition flight training. (a) Initial and transition flight...

14 CFR 121.425 - Flight engineers: Initial and transition flight training.

Code of Federal Regulations, 2013 CFR

2013-01-01

... 14 Aeronautics and Space 3 2013-01-01 2013-01-01 false Flight engineers: Initial and transition flight training. 121.425 Section 121.425 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION... § 121.425 Flight engineers: Initial and transition flight training. (a) Initial and transition flight...

14 CFR 121.425 - Flight engineers: Initial and transition flight training.

Code of Federal Regulations, 2011 CFR

2011-01-01

... 14 Aeronautics and Space 3 2011-01-01 2011-01-01 false Flight engineers: Initial and transition flight training. 121.425 Section 121.425 Aeronautics and Space FEDERAL AVIATION ADMINISTRATION... § 121.425 Flight engineers: Initial and transition flight training. (a) Initial and transition flight...

Flight Test Engineering

NASA Technical Reports Server (NTRS)

Pavlock, Kate Maureen

2013-01-01

Although the scope of flight test engineering efforts may vary among organizations, all point to a common theme: flight test engineering is an interdisciplinary effort to test an asset in its operational flight environment. Upfront planning where design, implementation, and test efforts are clearly aligned with the flight test objective are keys to success. This chapter provides a top level perspective of flight test engineering for the non-expert. Additional research and reading on the topic is encouraged to develop a deeper understanding of specific considerations involved in each phase of flight test engineering.

STS-111 Flight Day 5 Highlights

NASA Astrophysics Data System (ADS)

2002-06-01

On Flight Day 5 of STS-111, the crew of Endeavour (Kenneth Cockrell, Commander; Paul Lockhart, Pilot; Franklin Chang-Diaz, Mission Specialist; Philippe Perrin, Mission Specialist) and the Expedition 5 crew (Valery Korzun, Commander; Peggy Whitson, Flight Engineer; Sergei Treschev, Flight Engineer) and Expedition 4 crew (Yury Onufrienko, Commander; Daniel Bursch, Flight Engineer; Carl Walz, Flight Engineer) are aboard the docked Endeavour and International Space Station (ISS). The ISS cameras show the station in orbit above the North African coast and the Mediterranean Sea, as Chang-Diaz and Perrin prepare for an EVA (extravehicular activity). The Canadarm 2 robotic arm is shown in motion in a wide-angle shot. The Quest Airlock is shown as it opens to allow the astronauts to exit the station. As orbital sunrise approaches, the astronauts are shown already engaged in their EVA activities. Chang-Diaz is shown removing the PDGF (Power and Data Grapple Fixture) from Endeavour's payload bay as Perrin prepares its installation position in the ISS's P6 truss structure; The MPLM is also visible. Following the successful detachment of the PDGF, Chang-Diaz carries it to the installation site as he is transported there by the robotic arm. The astronauts are then shown installing the PDGF, with video provided by helmet-mounted cameras. Following this task, the astronauts are shown preparing the MBS (Mobile Base System) for grappling by the robotic arm. It will be mounted to the Mobile Transporter (MT), which will traverse a railroad-like system along the truss structures of the ISS, and support astronaut activities as well as provide an eventual mobile base for the robotic arm.

Mission definition study for Stanford relativity satellite. Volume 2: Engineering flight test program

NASA Technical Reports Server (NTRS)

1971-01-01

The need is examined for orbital flight tests of gyroscope, dewar, and other components, in order to reduce the technical and financial risk in performing the relativity experiment. A program is described that would generate engineering data to permit prediction of final performance. Two flight tests are recommended. The first flight would test a dewar smaller than that required for the final flight, but of size and form sufficient to allow extrapolation to the final design. The second flight would use the same dewar design to carry a set of three gyroscopes, which would be evaluated for spinup and drift characteristics for a period of a month or more. A proportional gas control system using boiloff helium gas from the dewar, and having the ability to prevent sloshing of liquid helium, would also be tested.

KSC-2014-2830

NASA Image and Video Library

2014-05-30

CAPE CANAVERAL, Fla. -- Lockheed Martin technicians and engineers attach the heat shield to the Orion crew module inside the Operations and Checkout Building high bay at NASA's Kennedy Space Center in Florida. Technicians have installed more than 200 instrumentation sensors on the heat shield for Exploration Flight Test-1, or EFT-1. The flight test will provide engineers with data about the heat shield's ability to protect Orion and its future crews from the 4,000-degree heat of reentry and an ocean splashdown following the spacecraft’s 20,000-mph reentry from space. Data gathered during the flight will inform decisions about design improvements on the heat shield and other Orion systems, and authenticate existing computer models and new approaches to space systems design and development. This process is critical to reducing overall risks and costs of future Orion missions. Orion is the exploration spacecraft designed to carry astronauts to destinations not yet explored by humans, including an asteroid and Mars. It will have emergency abort capability, sustain the crew during space travel and provide safe re-entry from deep space return velocities. The first unpiloted test flight of the Orion is scheduled to launch later this year atop a Delta IV rocket from Cape Canaveral Air Force Station in Florida to an altitude of 3,600 miles above the Earth's surface. The two-orbit, four-hour flight test will help engineers evaluate the systems critical to crew safety including the heat shield, parachute system and launch abort system. For more information, visit http://www.nasa.gov/orion. Photo credit: NASA/Daniel Casper

KSC-2014-2831

NASA Image and Video Library

2014-05-30

CAPE CANAVERAL, Fla. -- Lockheed Martin technicians and engineers attach the heat shield to the Orion crew module inside the Operations and Checkout Building high bay at NASA's Kennedy Space Center in Florida. Technicians have installed more than 200 instrumentation sensors on the heat shield for Exploration Flight Test-1, or EFT-1. The flight test will provide engineers with data about the heat shield's ability to protect Orion and its future crews from the 4,000-degree heat of reentry and an ocean splashdown following the spacecraft’s 20,000-mph reentry from space. Data gathered during the flight will inform decisions about design improvements on the heat shield and other Orion systems, and authenticate existing computer models and new approaches to space systems design and development. This process is critical to reducing overall risks and costs of future Orion missions. Orion is the exploration spacecraft designed to carry astronauts to destinations not yet explored by humans, including an asteroid and Mars. It will have emergency abort capability, sustain the crew during space travel and provide safe re-entry from deep space return velocities. The first unpiloted test flight of the Orion is scheduled to launch later this year atop a Delta IV rocket from Cape Canaveral Air Force Station in Florida to an altitude of 3,600 miles above the Earth's surface. The two-orbit, four-hour flight test will help engineers evaluate the systems critical to crew safety including the heat shield, parachute system and launch abort system. For more information, visit http://www.nasa.gov/orion. Photo credit: NASA/Daniel Casper

Implementation of Enhanced Propulsion Control Modes for Emergency Flight Operation

NASA Technical Reports Server (NTRS)

Csank, Jeffrey T.; Chin, Jeffrey C.; May, Ryan D.; Litt, Jonathan S.; Guo, Ten-Huei

2011-01-01

Aircraft engines can be effective actuators to help pilots avert or recover from emergency situations. Emergency control modes are being developed to enhance the engines performance to increase the probability of recovery under these circumstances. This paper discusses a proposed implementation of an architecture that requests emergency propulsion control modes, allowing the engines to deliver additional performance in emergency situations while still ensuring a specified safety level. In order to determine the appropriate level of engine performance enhancement, information regarding the current emergency scenario (including severity) and current engine health must be known. This enables the engine to operate beyond its nominal range while minimizing overall risk to the aircraft. In this architecture, the flight controller is responsible for determining the severity of the event and the level of engine risk that is acceptable, while the engine controller is responsible for delivering the desired performance within the specified risk range. A control mode selector specifies an appropriate situation-specific enhanced mode, which the engine controller then implements. The enhanced control modes described in this paper provide additional engine thrust or response capabilities through the modification of gains, limits, and the control algorithm, but increase the risk of engine failure. The modifications made to the engine controller to enable the use of the enhanced control modes are described, as are the interaction between the various subsystems and importantly, the interaction between the flight controller/pilot and the propulsion control system. Simulation results demonstrate how the system responds to requests for enhanced operation and the corresponding increase in performance.

Evaluation of the Linear Aerospike SR-71 Experiment (LASRE) Oxygen Sensor

NASA Technical Reports Server (NTRS)

Ennix, Kimberly A.; Corpening, Griffin P.; Jarvis, Michele; Chiles, Harry R.

1999-01-01

The Linear Aerospike SR-71 Experiment (LASRE) was a propulsion flight experiment for advanced space vehicles such as the X-33 and reusable launch vehicle. A linear aerospike rocket engine was integrated into a semi-span of an X-33-like lifting body shape (model), and carried on top of an SR-71 aircraft at NASA Dryden Flight Research Center. Because no flight data existed for aerospike nozzles, the primary objective of the LASRE flight experiment was to evaluate flight effects on the engine performance over a range of altitudes and Mach numbers. Because it contained a large quantity of energy in the form of fuel, oxidizer, hypergolics, and gases at very high pressures, the LASRE propulsion system posed a major hazard for fire or explosion. Therefore, a propulsion-hazard mitigation system was created for LASRE that included a nitrogen purge system. Oxygen sensors were a critical part of the nitrogen purge system because they measured purge operation and effectiveness. Because the available oxygen sensors were not designed for flight testing, a laboratory study investigated oxygen-sensor characteristics and accuracy over a range of altitudes and oxygen concentrations. Laboratory test data made it possible to properly calibrate the sensors for flight. Such data also provided a more accurate error prediction than the manufacturer's specification. This predictive accuracy increased confidence in the sensor output during critical phases of the flight. This paper presents the findings of this laboratory test.

The MSFC Systems Engineering Guide: An Overview and Plan

NASA Technical Reports Server (NTRS)

Shelby, Jerry; Thomas, L. Dale

2007-01-01

This paper describes the guiding vision, progress to date and the plan forward for development of the Marshall Space Flight Center (MSFC) Systems Engineering Guide (SEG), a virtual systems engineering handbook and archive that describes the system engineering processes used by MSFC in the development of ongoing complex space systems such as the Ares launch vehicle and forthcoming ones as well. It is the intent of this website to be a "One Stop Shop' for MSFC systems engineers that will provide tutorial information, an overview of processes and procedures and links to assist system engineering with guidance and references, and provide an archive of relevant systems engineering artifacts produced by the many NASA projects developed and managed by MSFC over the years.

Space Shuttle redesign status

NASA Technical Reports Server (NTRS)

Brand, Vance D.

1986-01-01

NASA has conducted an extensive redesign effort for the Space Shutle in the aftermath of the STS 51-L Challenger accident, encompassing not only Shuttle vehicle and booster design but also such system-wide factors as organizational structure, management procedures, flight safety, flight operations, sustainable flight rate, and maintenance safeguards. Attention is presently given to Solid Rocket Booster redesign features, the Shuttle Main Engine's redesigned high pressure fuel and oxidizer turbopumps, the Shuttle Orbiter's braking and rollout (landing gear) system, the entry control mode of the flight control system, a 'split-S' abort maneuver for the Orbiter, and crew escape capsule proposals.

X-38 V-132 Free Flight 2 (This is a video tape)

NASA Technical Reports Server (NTRS)

Bordano, Aldo J.

2000-01-01

Mr. Aldo Bordano will be presenting details of some of the JSC flight mechanics involvement in the X-38 testing program. Focus shall be on the parafoil system with regards its testing, performance analysis, and GN&C. An excellent example of a recent flight test at Dryden Flight Research Center shall be shown which portrays the system characteristics, sequencing, performance, and testing techniques. The intent is to inform the scientific and engineering communities about the developments in the X-38 parafoil program, as well as invite feedback on potential improvements in testing or systems.

Hypersonic missile propulsion system

DOE Office of Scientific and Technical Information (OSTI.GOV)

Kazmar, R.R.

1998-11-01

Pratt and Whitney is developing the technology for hypersonic components and engines. A supersonic combustion ramjet (scramjet) database was developed using hydrogen fueled propulsion systems for space access vehicles and serves as a point of departure for the current development of hydrocarbon scramjets. The Air Force Hypersonic Technology (HyTech) Program has put programs in place to develop the technologies necessary to demonstrate the operability, performance and structural durability of an expendable, liquid hydrocarbon fueled scramjet system that operates from Mach 4 to 8. This program will culminate in a flight type engine test at representative flight conditions. The hypersonic technologymore » base that will be developed and demonstrated under HyTech will establish the foundation to enable hypersonic propulsion systems for a broad range of air vehicle applications from missiles to space access vehicles. A hypersonic missile flight demonstration is planned in the DARPA Affordable Rapid Response Missile Demonstrator (ARRMD) program in 2001.« less

KSC-2013-3544

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – Engineers from NASA's Marshall Space Flight Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3545

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – An engineer from NASA's Marshall Space Flight Center prep a remote-controlled aircraft for take-off. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined the Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

KSC-2013-3547

NASA Image and Video Library

2013-09-11

CAPE CANAVERAL, Fla. – An engineer from NASA's Marshall Space Flight Center watches the landing of remote-controlled aircraft. The aircraft is equipped with a unique set of sensors and software and was assembled by a team of engineers for a competition at the agency's Kennedy Space Center. Teams from Johnson Space Center and Marshall Space Flight Center joined a Kennedy team in competing in an unmanned aerial systems event to evaluate designs and work by engineers learning new specialties. The competition took place at the Shuttle Landing Facility at Kennedy. Photo credit: NASA/Dmitri Gerondidakis

NASA's Space Launch System: Progress Report

NASA Technical Reports Server (NTRS)

Cook, Jerry; Lyles, Garry

2017-01-01

NASA and its commercial industry team achieved significant progress in 2016 in manufacturing and testing of the Block 1 vehicle for the first launch of the Space Launch System (SLS). Test and flight article hardware for the liquid hydrogen fuel tank as well as the engine section for the core stage were completed at Michoud Assembly Facility (MAF) in New Orleans. Test stands neared completion at Marshall Space Flight Center for the propellant tanks, engine section, intertank and payload section. Stennis Space Center completed major structural renovations on the B2 test stand, where the core stage "green run" test program will be conducted. The SLS team completed a hotfire test series at Stennis to successfully demonstrate the ability of the RS-25 engine to operate under SLS environments and performance conditions. The team also test fired the second qualification five-segment solid rocket motor and cast the first six motor segments for the first SLS mission. The Interim Cryogenic Propulsion Stage (ICPS) test article was delivered to Marshall for structural tests, and work is nearly finished on the flight stage. Flight software testing completed at Marshall included power quality and command and data handling. In 2017, that work continues. SLS completed Preliminary Design Review (PDR) on the Exploration Upper Stage (EUS), a powerful, human-rated spacecraft that will propel explorers to cis-lunar space. In 2017, hardware will continue to be integrated at MAF for core stage structural test articles and the first two operational flights. RS-25 hotfire testing will continue to explore engine performance, as well as test flight-like software and four new Engine Controller Units (ECUs) for the first mission. Production of development components for a more affordable RS-25 design is underway. Core stage structural test articles have begun arriving at Marshall. While engineering challenges typical of a new development are possible, SLS is working toward launch readiness in late 2018. This paper will discuss these and other technical and programmatic successes and challenges over the past year and provide a preview of work ahead before first flight

Space Shuttle Main Engine: Advanced Health Monitoring System

NASA Technical Reports Server (NTRS)

Singer, Chirs

1999-01-01

The main gola of the Space Shuttle Main Engine (SSME) Advanced Health Management system is to improve flight safety. To this end the new SSME has robust new components to improve the operating margen and operability. The features of the current SSME health monitoring system, include automated checkouts, closed loop redundant control system, catastropic failure mitigation, fail operational/ fail-safe algorithms, and post flight data and inspection trend analysis. The features of the advanced health monitoring system include: a real time vibration monitor system, a linear engine model, and an optical plume anomaly detection system. Since vibration is a fundamental measure of SSME turbopump health, it stands to reason that monitoring the vibration, will give some idea of the health of the turbopumps. However, how is it possible to avoid shutdown, when it is not necessary. A sensor algorithm has been developed which has been exposed to over 400 test cases in order to evaluate the logic. The optical plume anomaly detection (OPAD) has been developed to be a sensitive monitor of engine wear, erosion, and breakage.

Model-Based Systems Engineering for Capturing Mission Architecture System Processes with an Application Case Study - Orion Flight Test 1

NASA Technical Reports Server (NTRS)

Bonanne, Kevin H.

2011-01-01

Model-based Systems Engineering (MBSE) is an emerging methodology that can be leveraged to enhance many system development processes. MBSE allows for the centralization of an architecture description that would otherwise be stored in various locations and formats, thus simplifying communication among the project stakeholders, inducing commonality in representation, and expediting report generation. This paper outlines the MBSE approach taken to capture the processes of two different, but related, architectures by employing the Systems Modeling Language (SysML) as a standard for architecture description and the modeling tool MagicDraw. The overarching goal of this study was to demonstrate the effectiveness of MBSE as a means of capturing and designing a mission systems architecture. The first portion of the project focused on capturing the necessary system engineering activities that occur when designing, developing, and deploying a mission systems architecture for a space mission. The second part applies activities from the first to an application problem - the system engineering of the Orion Flight Test 1 (OFT-1) End-to-End Information System (EEIS). By modeling the activities required to create a space mission architecture and then implementing those activities in an application problem, the utility of MBSE as an approach to systems engineering can be demonstrated.

Engineering evaluation of SSME dynamic data from engine tests and SSV flights

NASA Technical Reports Server (NTRS)

1986-01-01

An engineering evaluation of dynamic data from SSME hot firing tests and SSV flights is summarized. The basic objective of the study is to provide analyses of vibration, strain and dynamic pressure measurements in support of MSFC performance and reliability improvement programs. A brief description of the SSME test program is given and a typical test evaluation cycle reviewed. Data banks generated to characterize SSME component dynamic characteristics are described and statistical analyses performed on these data base measurements are discussed. Analytical models applied to define the dynamic behavior of SSME components (such as turbopump bearing elements and the flight accelerometer safety cut-off system) are also summarized. Appendices are included to illustrate some typical tasks performed under this study.

Perseus B Landing on Runway

NASA Technical Reports Server (NTRS)

1999-01-01

The Perseus B high-altitude, remotely piloted research vehicle touches down on the runway at Edwards AFB, adjacent to NASA's Dryden Flight Research Center, after a test flight in September 1999. The Perseus B was the third version of the Perseus design developed by Aurora Flight Sciences under the Dryden-managed Environmental Research Aircraft and Sensor Technology (ERAST) program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Aurora Flight Sciences' Perseus B Remotely Piloted Aircraft in Flight

NASA Technical Reports Server (NTRS)

1998-01-01

A long, slender wing and a pusher propeller at the rear characterize the Perseus B remotely piloted research aircraft, seen here during a test flight in June 1998. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus in Flight

NASA Technical Reports Server (NTRS)

1991-01-01

The Perseus proof-of-concept vehicle in flight at the Dryden Flight Research Center, Edwards, California in 1991. Perseus is one of several remotely-piloted aircraft designed for high-altitude, long-endurance scientific sampling missions being evaluated under the ERAST program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B Heads for Landing on Edwards AFB Runway

NASA Technical Reports Server (NTRS)

1998-01-01

The Perseus B remotely piloted aircraft approaches the runway at Edwards Air Force Base, Calif. at the conclusion of a development flight at NASA's Dryden flight Research Center in April 1998. The Perseus B is the latest of three versions of the Perseus design developed by Aurora Flight Sciences under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Perseus B Heads for Landing on Edwards AFB Runway

NASA Technical Reports Server (NTRS)

1997-01-01

The Perseus B remotely piloted aircraft nears touchdown at Edwards Air Force Base, Calif. at the conclusion of a development flight at NASA's Dryden Flight Research Center. The Perseus B is the latest of three versions of the Perseus design developed by Aurora Flight Sciences under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) program. Perseus B is a remotely piloted aircraft developed as a design-performance testbed under NASA's Environmental Research Aircraft and Sensor Technology (ERAST) project. Perseus is one of several flight vehicles involved in the ERAST project. A piston engine, propeller-powered aircraft, Perseus was designed and built by Aurora Flight Sciences Corporation, Manassas, Virginia. The objectives of Perseus B's ERAST flight tests have been to reach and maintain horizontal flight above altitudes of 60,000 feet and demonstrate the capability to fly missions lasting from 8 to 24 hours, depending on payload and altitude requirements. The Perseus B aircraft established an unofficial altitude record for a single-engine, propeller-driven, remotely piloted aircraft on June 27, 1998. It reached an altitude of 60,280 feet. In 1999, several modifications were made to the Perseus aircraft including engine, avionics, and flight-control-system improvements. These improvements were evaluated in a series of operational readiness and test missions at the Dryden Flight Research Center, Edwards, California. Perseus is a high-wing monoplane with a conventional tail design. Its narrow, straight, high-aspect-ratio wing is mounted atop the fuselage. The aircraft is pusher-designed with the propeller mounted in the rear. This design allows for interchangeable scientific-instrument payloads to be placed in the forward fuselage. The design also allows for unobstructed airflow to the sensors and other devices mounted in the payload compartment. The Perseus B that underwent test and development in 1999 was the third generation of the Perseus design, which began with the Perseus Proof-Of-Concept aircraft. Perseus was initially developed as part of NASA's Small High-Altitude Science Aircraft (SHASA) program, which later evolved into the ERAST project. The Perseus Proof-Of-Concept aircraft first flew in November 1991 and made three low-altitude flights within a month to validate the Perseus aerodynamic model and flight control systems. Next came the redesigned Perseus A, which incorporated a closed-cycle combustion system that mixed oxygen carried aboard the aircraft with engine exhaust to compensate for the thin air at high altitudes. The Perseus A was towed into the air by a ground vehicle and its engine started after it became airborne. Prior to landing, the engine was stopped, the propeller locked in horizontal position, and the Perseus A glided to a landing on its unique bicycle-type landing gear. Two Perseus A aircraft were built and made 21 flights in 1993-1994. One of the Perseus A aircraft reached over 50,000 feet in altitude on its third test flight. Although one of the Perseus A aircraft was destroyed in a crash after a vertical gyroscope failed in flight, the other aircraft completed its test program and remains on display at Aurora's facility in Manassas. Perseus B first flew Oct. 7, 1994, and made two flights in 1996 before being damaged in a hard landing on the dry lakebed after a propeller shaft failure. After a number of improvements and upgrades-including extending the original 58.5-foot wingspan to 71.5 feet to enhance high-altitude performance--the Perseus B returned to Dryden in the spring of 1998 for a series of four flights. Thereafter, a series of modifications were made including external fuel pods on the wing that more than doubled the fuel capacity to 100 gallons. Engine power was increased by more than 20 percent by boosting the turbocharger output. Fuel consumption was reduced with fuel control modifications and a leaner fuel-air mixture that did not compromise power. The aircraft again crashed on Oct. 1, 1999, near Barstow, California, suffering moderate damage to the aircraft but no property damage, fire, or injuries in the area of the crash. Perseus B is flown remotely by a pilot from a mobile flight control station on the ground. A Global Positioning System (GPS) unit provides navigation data for continuous and precise location during flight. The ground control station features dual independent consoles for aircraft control and systems monitoring. A flight termination system, required for all remotely piloted aircraft being flown in military-restricted airspace, includes a parachute system deployed on command plus a C-Band radar beacon and a Mode-C transponder to aid in location. Dryden has provided hanger and office space for the Perseus B aircraft and for the flight test development team when on site for flight or ground testing. NASA's ERAST project is developing aeronautical technologies for a new generation of remotely piloted and autonomous aircraft for a variety of upper-atmospheric science missions and commercial applications. Dryden is the lead center in NASA for ERAST management and operations. Perseus B is approximately 25 feet long, has a wingspan of 71.5 feet, and stands 12 feet high. Perseus B is powered by a Rotax 914, four-cylinder piston engine mounted in the mid-fuselage area and integrated with an Aurora-designed three-stage turbocharger, connected to a lightweight two-blade propeller.

Model-Based Systems Engineering Approach to Managing Mass Margin

NASA Technical Reports Server (NTRS)

Chung, Seung H.; Bayer, Todd J.; Cole, Bjorn; Cooke, Brian; Dekens, Frank; Delp, Christopher; Lam, Doris

2012-01-01

When designing a flight system from concept through implementation, one of the fundamental systems engineering tasks ismanaging the mass margin and a mass equipment list (MEL) of the flight system. While generating a MEL and computing a mass margin is conceptually a trivial task, maintaining consistent and correct MELs and mass margins can be challenging due to the current practices of maintaining duplicate information in various forms, such as diagrams and tables, and in various media, such as files and emails. We have overcome this challenge through a model-based systems engineering (MBSE) approach within which we allow only a single-source-of-truth. In this paper we describe the modeling patternsused to capture the single-source-of-truth and the views that have been developed for the Europa Habitability Mission (EHM) project, a mission concept study, at the Jet Propulsion Laboratory (JPL).

Pulse Detonation Engines for High Speed Flight

NASA Technical Reports Server (NTRS)

Povinelli, Louis A.

2002-01-01

Revolutionary concepts in propulsion are required in order to achieve high-speed cruise capability in the atmosphere and for low cost reliable systems for earth to orbit missions. One of the advanced concepts under study is the air-breathing pulse detonation engine. Additional work remains in order to establish the role and performance of a PDE in flight applications, either as a stand-alone device or as part of a combined cycle system. In this paper, we shall offer a few remarks on some of these remaining issues, i.e., combined cycle systems, nozzles and exhaust systems and thrust per unit frontal area limitations. Currently, an intensive experimental and numerical effort is underway in order to quantify the propulsion performance characteristics of this device. In this paper, we shall highlight our recent efforts to elucidate the propulsion potential of pulse detonation engines and their possible application to high-speed or hypersonic systems.

International Space Station Sustaining Engineering: A Ground-Based Test Bed for Evaluating Integrated Environmental Control and Life Support System and Internal Thermal Control System Flight Performance

NASA Technical Reports Server (NTRS)

Ray, Charles D.; Perry, Jay L.; Callahan, David M.

2000-01-01

As the International Space Station's (ISS) various habitable modules are placed in service on orbit, the need to provide for sustaining engineering becomes increasingly important to ensure the proper function of critical onboard systems. Chief among these are the Environmental Control and Life Support System (ECLSS) and the Internal Thermal Control System (ITCS). Without either, life onboard the ISS would prove difficult or nearly impossible. For this reason, a ground-based ECLSS/ITCS hardware performance simulation capability has been developed at NASA's Marshall Space Flight Center. The ECLSS/ITCS Sustaining Engineering Test Bed will be used to assist the ISS Program in resolving hardware anomalies and performing periodic performance assessments. The ISS flight configuration being simulated by the test bed is described as well as ongoing activities related to its preparation for supporting ISS Mission 5A. Growth options for the test facility are presented whereby the current facility may be upgraded to enhance its capability for supporting future station operation well beyond Mission 5A. Test bed capabilities for demonstrating technology improvements of ECLSS hardware are also described.

Test and evaluation of the HIDEC engine uptrim algorithm. [Highly Integrated Digital Electronic Control for aircraft

NASA Technical Reports Server (NTRS)

Ray, R. J.; Myers, L. P.

1986-01-01

The highly integrated digital electronic control (HIDEC) program will demonstrate and evaluate the improvements in performance and mission effectiveness that result from integrated engine-airframe control systems. Performance improvements will result from an adaptive engine stall margin mode, a highly integrated mode that uses the airplane flight conditions and the resulting inlet distortion to continuously compute engine stall margin. When there is excessive stall margin, the engine is uptrimmed for more thrust by increasing engine pressure ratio (EPR). The EPR uptrim logic has been evaluated and implemente into computer simulations. Thrust improvements over 10 percent are predicted for subsonic flight conditions. The EPR uptrim was successfully demonstrated during engine ground tests. Test results verify model predictions at the conditions tested.

CASIS Fact Sheet: Hardware and Facilities

NASA Technical Reports Server (NTRS)

Solomon, Michael R.; Romero, Vergel

2016-01-01

Vencore is a proven information solutions, engineering, and analytics company that helps our customers solve their most complex challenges. For more than 40 years, we have designed, developed and delivered mission-critical solutions as our customers' trusted partner. The Engineering Services Contract, or ESC, provides engineering and design services to the NASA organizations engaged in development of new technologies at the Kennedy Space Center. Vencore is the ESC prime contractor, with teammates that include Stinger Ghaffarian Technologies, Sierra Lobo, Nelson Engineering, EASi, and Craig Technologies. The Vencore team designs and develops systems and equipment to be used for the processing of space launch vehicles, spacecraft, and payloads. We perform flight systems engineering for spaceflight hardware and software; develop technologies that serve NASA's mission requirements and operations needs for the future. Our Flight Payload Support (FPS) team at Kennedy Space Center (KSC) provides engineering, development, and certification services as well as payload integration and management services to NASA and commercial customers. Our main objective is to assist principal investigators (PIs) integrate their science experiments into payload hardware for research aboard the International Space Station (ISS), commercial spacecraft, suborbital vehicles, parabolic flight aircrafts, and ground-based studies. Vencore's FPS team is AS9100 certified and a recognized implementation partner for the Center for Advancement of Science in Space (CASIS