SEARCH · Search NASA

Results for “Engine Out”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

SourceResearch connectionFrom yearThrough year

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 469 records · Page 26

All sources NASA NTRS DOE OSTI

NASA NTRS1998

The Strutjet Rocket Based Combined Cycle Engine

The multi stage chemical rocket has been established over many years as the propulsion System for space transportation vehicles, while, at the same time, there is increasing concern about its continued affordability and rather involved reusability. Two broad approaches to addressing this overall launch cost problem consist in one, the further development of the rocket motor, and two, the use of airbreathing propulsion to the maximum extent possible as a complement to the limited use of a conventional rocket. In both cases, a single-stage-to-orbit (SSTO) vehicle is considered a desirable goal. However, neither the "all-rocket" nor the "all-airbreathing" approach seems realizable and workable in practice without appreciable advances in materials and manufacturing. An affordable system must be reusable with minimal refurbishing on-ground, and large mean time between overhauls, and thus with high margins in design. It has been suggested that one may use different engine cycles, some rocket and others airbreathing, in a combination over a flight trajectory, but this approach does not lead to a converged solution with thrust-to-mass, specific impulse, and other performance and operational characteristics that can be obtained in the different engines. The reason is this type of engine is simply a combination of different engines with no commonality of gas flowpath or components, and therefore tends to have the deficiencies of each of the combined engines. A further development in this approach is a truly combined cycle that incorporates a series of cycles for different modes of propulsion along a flight path with multiple use of a set of components and an essentially single gas flowpath through the engine. This integrated approach is based on realizing the benefits of both a rocket engine and airbreathing engine in various combinations by a systematic functional integration of components in an engine class usually referred to as a rocket-based combined cycle (RBCC) engine. RBCC engines exhibit a high potential for lowering the operating cost of launching payloads into orbit. Two sources of cost reductions can be identified. First, RBCC powered vehicles require only 20% takeoff thrust compared to conventional rockets, thereby lowering the thrust requirements and the replacement cost of the engines. Second, due to the higher structural and thermal margins achievable with RBCC engines coupled with a higher degree of subsystem redundance lower maintenance and operating cost are obtainable.

Siebenhaar, A.↗

NASA NTRS2002

Virtual Collaborative Environments for System of Systems Engineering and Applications for ISAT

This paper describes an system of systems or metasystems approach and models developed to help prepare engineering organizations for distributed engineering environments. These changes in engineering enterprises include competition in increasingly global environments; new partnering opportunities caused by advances in information and communication technologies, and virtual collaboration issues associated with dispersed teams. To help address challenges and needs in this environment, a framework is proposed that can be customized and adapted for NASA to assist in improved engineering activities conducted in distributed, enhanced engineering environments. The approach is designed to prepare engineers for such distributed collaborative environments by learning and applying e-engineering methods and tools to a real-world engineering development scenario. The approach consists of two phases: an e-engineering basics phase and e-engineering application phase. The e-engineering basics phase addresses skills required for e-engineering. The e-engineering application phase applies these skills in a distributed collaborative environment to system development projects.

Dryer, David A.↗

NASA NTRS2004

Autonomous Propulsion System Technology Being Developed to Optimize Engine Performance Throughout the Lifecycle

The goal of the Autonomous Propulsion System Technology (APST) project is to reduce pilot workload under both normal and anomalous conditions. Ongoing work under APST develops and leverages technologies that provide autonomous engine monitoring, diagnosing, and controller adaptation functions, resulting in an integrated suite of algorithms that maintain the propulsion system's performance and safety throughout its life. Engine-to-engine performance variation occurs among new engines because of manufacturing tolerances and assembly practices. As an engine wears, the performance changes as operability limits are reached. In addition to these normal phenomena, other unanticipated events such as sensor failures, bird ingestion, or component faults may occur, affecting pilot workload as well as compromising safety. APST will adapt the controller as necessary to achieve optimal performance for a normal aging engine, and the safety net of APST algorithms will examine and interpret data from a variety of onboard sources to detect, isolate, and if possible, accommodate faults. Situations that cannot be accommodated within the faulted engine itself will be referred to a higher level vehicle management system. This system will have the authority to redistribute the faulted engine's functionality among other engines, or to replan the mission based on this new engine health information. Work is currently underway in the areas of adaptive control to compensate for engine degradation due to aging, data fusion for diagnostics and prognostics of specific sensor and component faults, and foreign object ingestion detection. In addition, a framework is being defined for integrating all the components of APST into a unified system. A multivariable, adaptive, multimode control algorithm has been developed that accommodates degradation-induced thrust disturbances during throttle transients. The baseline controller of the engine model currently being investigated has multiple control modes that are selected according to some performance or operational criteria. As the engine degrades, parameters shift from their nominal values. Thus, when a new control mode is swapped in, a variable that is being brought under control might have an excessive initial error. The new adaptive algorithm adjusts the controller gains on the basis of the level of degradation to minimize the disruptive influence of the large error on other variables and to recover the desired thrust response.

Litt, Jonathan S.↗

NASA NTRS2008

Engine Validation of Noise and Emission Reduction Technology Phase I

This final report has been prepared by Honeywell Aerospace, Phoenix, Arizona, a unit of Honeywell International, Inc., documenting work performed during the period December 2004 through August 2007 for the NASA Glenn Research Center, Cleveland, Ohio, under the Revolutionary Aero-Space Engine Research (RASER) Program, Contract No. NAS3-01136, Task Order 8, Engine Validation of Noise and Emission Reduction Technology Phase I. The NASA Task Manager was Dr. Joe Grady of the NASA Glenn Research Center. The NASA Contract Officer was Mr. Albert Spence of the NASA Glenn Research Center. This report is for a test program in which NASA funded engine validations of integrated technologies that reduce aircraft engine noise. These technologies address the reduction of engine fan and jet noise, and noise associated with propulsion/airframe integration. The results of these tests will be used by NASA to identify the engineering tradeoffs associated with the technologies that are needed to enable advanced engine systems to meet stringent goals for the reduction of noise. The objectives of this program are to (1) conduct system engineering and integration efforts to define the engine test-bed configuration; (2) develop selected noise reduction technologies to a technical maturity sufficient to enable engine testing and validation of those technologies in the FY06-07 time frame; (3) conduct engine tests designed to gain insight into the sources, mechanisms and characteristics of noise in the engines; and (4) establish baseline engine noise measurements for subsequent use in the evaluation of noise reduction.

Weir, Don↗

NASA NTRS1947

Investigation of the I-40 Jet-Propulsion Engine in the Cleveland Altitude Wind Tunnel. V - Operational Characteristics: Operational Characteristics - 5

An investigation has been conducted in the Cleveland altitude wind tunnel to determine the operational characteristics of the I-40 jet-propulsion engine over a range of pressure altitudes from 10,000 to 50,000 feet and ram-pressure ratios from 1.00 to 1.76. Engine operational data were obtained with the engine in the standard configuration and with various modifications of the fuel system, the electrical system, and the combustion chambers. The effects of altitude and airspeed on operating speed range, starting, windmilli.ng, acceleration, speed regulation, cooling, and vibration of the standard and modified engines were determined, and damage to parts was noted. Maximum engine speed was obtainable at all altitudes and airspeeds wi th each fuel-control system investigated. The minimum idling speed was raised by increases in altitude and airspeed. The lowest minimum stable speeds were obtained with the standard configuration using 40-gallon nozzles with individual metering plugs. The engine was started normally at altitudes as high as 20,000 feet with all of the fuel systems and ignition combinations except one. Ignition at 70,000 feet was difficult and, although successful ignition occurred, acceleration was slow and usually characterized by excessive tail-pipe temperature. During windmilling investigations of the engine equipped with the standard fuel system, the engine could not be started at ram-pressure ratios of 1.1 to 1.7 at altitudes of 10,000, 20,000 and 30,000 feet. When equipped with the production barometric and Monarch 40-gallon nozzles, the engine accelerated in 12 seconds from an engine speed of 6000 rpm to 11,000 rpm at 20,000 feet and an average tail-pipe temperature of 11000 F. At the same altitude and temperature, all the engine configurations had approximately the same rate of acceleration. The Woodward governor produced the safest accelerations, inasmuch as it could be adjusted to automatically prevent acceleration blow out. The engine speed was held constant by the Woodward governor and the Edwards regulator during simulated dives and climbs at constant throttle position. The bearing cooling system was satisfactory at all altitudes and airspeeds. The engines operated without serious failure, although the exhaust cone, the tail pipe, and the airplane fuselage were damaged during altitude starts.

Golladay, Richard L.↗

NASA NTRS2010

Altitude Testing of Large Liquid Propellant Engines

The National Aeronautics and Space Administration entered a new age on January 14, 2004 with President Bush s announcement of the creation the Vision for Space Exploration that will take mankind back to the Moon and on beyond to Mars. In January, 2006, after two years of hard, dedicated labor, engineers within NASA and its contractor workforce decided that the J2X rocket, based on the heritage of the Apollo J2 engine, would be the new engine for the NASA Constellation Ares upper stage vehicle. This engine and vehicle combination would provide assured access to the International Space Station to replace that role played by the Space Shuttle and additionally, would serve as the Earth Departure Stage, to push the Crew Excursion Vehicle out of Earth Orbit and head it on a path for rendezvous with the Moon. Test as you fly, fly as you test was chosen to be the guiding philosophy and a pre-requisite for the engine design, development, test and evaluation program. An exhaustive survey of national test facility assets proved the required capability to test the J2X engine at high altitude for long durations did not exist so therefore, a high altitude/near space environment testing capability would have to be developed. After several agency concepts the A3 High Altitude Testing Facility proposal was selected by the J2X engine program on March 2, 2007 and later confirmed by a broad panel of NASA senior leadership in May 2007. This facility is to be built at NASA s John C. Stennis Space Center located near Gulfport, Mississippi. 30 plus years of Space Shuttle Main Engine development and flight certification testing makes Stennis uniquely suited to support the Vision For Space Exploration Return to the Moon. Propellant handling infrastructure, engine assembly facilities, a trained and dedicated workforce and a broad and varied technical support base will all ensure that the A3 facility will be built on time to support the schedule needs of the J2X engine and the ultimate flight of the first Ares I vehicle. The A3 facility will be able to simulate pre-ignition altitude from sea-level to 100,000 feet and maintain it up to 650 seconds. Additionally the facility will be able to accommodate initial ignition, shutdown and then restart test profiles. A3 will produce up to 5000 lbm/sec of superheated steam utilizing a Chemical Steam generation system. Two separate inline steam ejectors will be used to produce a test cell vacuum to simulate the 100,000 ft required altitude. Operational capability will ensure that the facility can start up and shutdown without producing adverse pressure gradients across the J2X nozzle. The facility will have a modern thrust measurement system for accurate determination of engine performance. The latest advances in data acquisition and control will be incorporated to measure performance parameters during hotfire testing. Provisions are being made in the initial design of the new altitude facility to allow for testing of other, larger engines and potential upper stage launch vehicles that might require vacuum start testing of the engines. The new facility at Stennis Space Center will be complete and ready for hotfire operations in late 2010.

Maynard, Bryon T.↗

NASA NTRS2010

An Integrated Architecture for On-Board Aircraft Engine Performance Trend Monitoring and Gas Path Fault Diagnostics

Aircraft engine performance trend monitoring and gas path fault diagnostics are closely related technologies that assist operators in managing the health of their gas turbine engine assets. Trend monitoring is the process of monitoring the gradual performance change that an aircraft engine will naturally incur over time due to turbomachinery deterioration, while gas path diagnostics is the process of detecting and isolating the occurrence of any faults impacting engine flow-path performance. Today, performance trend monitoring and gas path fault diagnostic functions are performed by a combination of on-board and off-board strategies. On-board engine control computers contain logic that monitors for anomalous engine operation in real-time. Off-board ground stations are used to conduct fleet-wide engine trend monitoring and fault diagnostics based on data collected from each engine each flight. Continuing advances in avionics are enabling the migration of portions of the ground-based functionality on-board, giving rise to more sophisticated on-board engine health management capabilities. This paper reviews the conventional engine performance trend monitoring and gas path fault diagnostic architecture commonly applied today, and presents a proposed enhanced on-board architecture for future applications. The enhanced architecture gains real-time access to an expanded quantity of engine parameters, and provides advanced on-board model-based estimation capabilities. The benefits of the enhanced architecture include the real-time continuous monitoring of engine health, the early diagnosis of fault conditions, and the estimation of unmeasured engine performance parameters. A future vision to advance the enhanced architecture is also presented and discussed

Simon, Donald L.↗

NASA NTRS2010

A Historical Systems Study of Liquid Rocket Engine Throttling Capabilities

This is a comprehensive systems study to examine and evaluate throttling capabilities of liquid rocket engines. The focus of this study is on engine components, and how the interactions of these components are considered for throttling applications. First, an assessment of space mission requirements is performed to determine what applications require engine throttling. A background on liquid rocket engine throttling is provided, along with the basic equations that are used to predict performance. Three engines are discussed that have successfully demonstrated throttling. Next, the engine system is broken down into components to discuss special considerations that need to be made for engine throttling. This study focuses on liquid rocket engines that have demonstrated operational capability on American space launch vehicles, starting with the Apollo vehicle engines and ending with current technology demonstrations. Both deep throttling and shallow throttling engines are discussed. Boost and sustainer engines have demonstrated throttling from 17% to 100% thrust, while upper stage and lunar lander engines have demonstrated throttling in excess of 10% to 100% thrust. The key difficulty in throttling liquid rocket engines is maintaining an adequate pressure drop across the injector, which is necessary to provide propellant atomization and mixing. For the combustion chamber, cooling can be an issue at low thrust levels. For turbomachinery, the primary considerations are to avoid cavitation, stall, surge, and to consider bearing leakage flows, rotordynamics, and structural dynamics. For valves, it is necessary to design valves and actuators that can achieve accurate flow control at all thrust levels. It is also important to assess the amount of nozzle flow separation that can be tolerated at low thrust levels for ground testing.

Betts, Erin M.↗

NASA NTRS1983

Study of LH2-fueled topping cycle engine for aircraft propulsion

An analytical investigation was made of a topping cycle aircraft engine system which uses a cryogenic fuel. This system consists of a main turboshaft engine which is mechanically coupled (by cross-shafting) to a topping loop which augments the shaft power output of the system. The thermodynamic performance of the topping cycle engine was analyzed and compared with that of a reference (conventional-type) turboshaft engine. For the cycle operating conditions selected, the performance of the topping cycle engine in terms of brake specific fuel consumption (bsfc) was determined to be about 12 percent better than that of the reference turboshaft engine. Engine weights were estimated for both the topping cycle engine and the reference turboshaft engine. These estimates were based on a common shaft power output for each engine. Results indicate that the weight of the topping cycle engine is comparable to that of the reference turboshaft engine.

Turney, G. E.↗

NASA NTRS1984

Analysis of a topping-cycle, aircraft, gas-turbine-engine system which uses cryogenic fuel

A topping-cycle aircraft engine system which uses a cryogenic fuel was investigated. This system consists of a main turboshaft engine that is mechanically coupled (by cross-shafting) to a topping loop, which augments the shaft power output of the system. The thermodynamic performance of the topping-cycle engine was analyzed and compared with that of a reference (conventional) turboshaft engine. For the cycle operating conditions selected, the performance of the topping-cycle engine in terms of brake specific fuel consumption (bsfc) was determined to be about 12 percent better than that of the reference turboshaft engine. Engine weights were estimated for both the topping-cycle engine and the reference turboshaft engine. These estimates were based on a common shaft power output for each engine. Results indicate that the weight of the topping-cycle engine is comparable with that of the reference turboshaft engine.

Turney, G. E.↗

NASA NTRS1983

Study of a LH2-fueled topping cycle engine for aircraft propulsion

Turney, G. E.↗

NASA NTRS1985

The STOL performance of a two-engine, USB powered-lift aircraft with cross-shafted fans

The short takeoff and landing capabilities that characterize the performance of powered-lift aircraft are dependent on engine thrust and are, therefore, severely affected by loss of an engine. This paper shows that the effects of engine loss on the short takeoff and landing performance of powered-lift aircraft can be effectively mitigated by cross-shafting the engine fans in a twin-engine configuration. Engine-out takeoff and landing performances are compared for three powered-lift aircraft configurations: one with four engines, one with two engines, and one with two engines in which the fans are cross-shafted. The results show that the engine-out takeoff and landing performance of the cross-shafted two-engine configuration is significantly better than that of the two-engine configuration without cross-shafting.

Stevens, V. C.↗

NASA NTRS1987

Measurement uncertainty for the Uniform Engine Testing Program conducted at NASA Lewis Research Center

An uncertainty analysis was conducted to determine the bias and precision errors and total uncertainty of measured turbojet engine performance parameters. The engine tests were conducted as part of the Uniform Engine Test Program which was sponsored by the Advisory Group for Aerospace Research and Development (AGARD). With the same engines, support hardware, and instrumentation, performance parameters were measured twice, once during tests conducted in test cell number 3 and again during tests conducted in test cell number 4 of the NASA Lewis Propulsion Systems Laboratory. The analysis covers 15 engine parameters, including engine inlet airflow, engine net thrust, and engine specific fuel consumption measured at high rotor speed of 8875 rpm. Measurements were taken at three flight conditions defined by the following engine inlet pressure, engine inlet total temperature, and engine ram ratio: (1) 82.7 kPa, 288 K, 1.0, (2) 82.7 kPa, 288 K, 1.3, and (3) 20.7 kPa, 288 K, 1.3. In terms of bias, precision, and uncertainty magnitudes, there were no differences between most measurements made in test cells number 3 and 4. The magnitude of the errors increased for both test cells as engine pressure level decreased. Also, the level of the bias error was two to three times larger than that of the precision error.

Abdelwahab, Mahmood↗

NASA NTRS1993

Space Shuttle Main Engine real time stability analysis

The Space Shuttle Main Engine (SSME) is a reusable, high performance, liquid rocket engine with variable thrust. The engine control system continuously monitors the engine parameters and issues propellant valve control signals in accordance with the thrust and mixture ratio commands. A real time engine simulation lab was installed at MSFC to verify flight software and to perform engine dynamic analysis. A real time engine model was developed on the AD100 computer system. This model provides sufficient fidelity on the dynamics of major engine components and yet simplified enough to be executed in real time. The hardware-in-the-loop type simulation and analysis becomes necessary as NASA is continuously improving the SSME technology, some with significant changes in the dynamics of the engine. The many issues of interfaces between new components and the engine can be better understood and be resolved prior to the firing of the engine. In this paper, the SSME real time simulation Lab at the MSFC, the SSME real time model, SSME engine and control system stability analysis, both in real time and non-real time is presented.

Kuo, F. Y.↗

NASA NTRS1993

STS-55 pad abort: Engine 2011 oxidizer preburner augmented spark igniter check valve leak

The STS-55 initial launch attempt of Columbia (OV102) was terminated on KSC launch pad A March 22, 1993 at 9:51 AM E.S.T. due to violation of an ME-3 (Engine 2011) Launch Commit Criteria (LCC) limit exceedance. The event description and timeline are summarized. Propellant loading was initiated on 22 March, 1993 at 1:15 AM EST. All SSME chill parameters and launch commit criteria (LCC) were nominal. At engine start plus 1.44 seconds, a Failure Identification (FID) was posted against Engine 2011 for exceeding the 50 psia Oxidizer Preburner (OPB) purge pressure redline. The engine was shut down at 1.50 seconds followed by Engines 2034 and 2030. All shut down sequences were nominal and the mission was safely aborted. The OPB purge pressure redline violation and the abort profile/overlay for all three engines are depicted. SSME Avionics hardware and software performed nominally during the incident. A review of vehicle data table (VDT) data and controller software logic revealed no failure indications other than the single FID 013-414, OPB purge pressure redline exceeded. Software logic was executed according to requirements and there was no anomalous controller software operation. Immediately following the abort, a Rocketdyne/NASA failure investigation team was assembled. The team successfully isolated the failure cause to the oxidizer preburner augmented spark igniter purge check valve not being fully closed due to contamination. The source of the contaminant was traced to a cut segment from a rubber O-ring which was used in a fine clean tool during valve production prior to 1992. The valve was apparently contaminated during its fabrication in 1985. The valve had performed acceptably on four previous flights of the engine, and SSME flight history shows 780 combined check valve flights without failure. The failure of an Engine 3 (SSME No. 2011) check valve to close was sensed by onboard engine instruments even though all other engine operations were normal. This resulted in an engine shutdown and safe sequential shutdown of all three engines prior to ignition of the solid boosters.

Source record↗

NASA NTRS1993

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

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

Source record↗

NASA NTRS2002

Modes 1 and 4 Testing of an Axisymmetric GTX RBCC Engine

Under sponsorship of the NASA Glenn Research Center (NASA GRC), the Johns Hopkins University Applied Physics Laboratory (JHU/APL) designed and built a five-inch diameter, Rocket-Based Combined Cycle (RBCC) engine to investigate mode 1 and mode 4 performance. This engine was designed so that engine area and length ratios were similar to the NASA GRC GTX engine. Unlike the GTX semi-circular engine design, the APL engine is completely axisymmetric. For this design, a traditional rocket thruster was installed inside of the scramjet flowpath, along the engine centerline. A three part test series is currently underway to determine mode 1 and mode 4 engine performance and compare those results to the rocket thruster operating by itself. All tests are to be conducted in APL's Cell 2 Freejet Engine Facility. Testing of the rocket thruster alone has been accomplished and its performance determined (average Isp efficiency = 90%). Mode 1 (air-augmented rocket) testing is to be conducted at various chamber pressure-to-ambient pressure ratios with the engine inlet fully open. Mode 4 (vacuum rocket) testing is to be conducted with chamber pressure-to-ambient pressure ratios greater than 600 with the inlet fully closed to simulate high-altitude flight conditions. The engine is currently installed in Cell 2 and awaiting testing. This paper discusses the engine design and details the results of the rocket-only testing. Comparisons to previous tests and projected mode 1 and mode 4 test conditions are also discussed.

Rice, Tharen↗

NASA NTRS2002

Liquid Engine Test Facilities Assessment

The John C. Stennis Space Center (SSC) requested The Aerospace Corporation to examine the current testing capability of all existing large liquid engine test facilities located in the United States. That information along with projected liquid rocket engine development was used to examine future liquid rocket engine testing facilities needs in the coming decade. Current domestic liquid engine test facilities capabilities, when examined against engine concepts for the coming decade, indicate there are ample facilities offering altitude simulation during test. In addition, it was observed that many contractor facilities have limited ambient test capability of larger thrust engines under current consideration. Finally, it was concluded that diminished contractor participation engine development testing will drive this activity to the government sector. Only three facilities are seen as key contributors to engine testing in the coming decade, namely John C. Stennis Space Center (SSC), Marshall Space Flight Center (MSFC), and Air Force Research Laboratory (AFRL). Past rocket engine test experience was evaluated as a possible resource for projecting future engine test needs. A database comprised of various engine models and the level of testing performed to flight qualify those systems for their first flight was constructed. For comparison purposes in this study, development and qualification efforts were totaled and treated as one test program. Based on experience with past Air Force programs, the time on the test stand accounts for typically 50% or more of the total program time. Historical data show that the time to design and develop new engines has increased over the last 40 years, most likely due to scarcer resources in today's funding environment.

Adams, Michael J.↗