Search NASA⌕ Search

SEARCH · Search NASA

Results for “ENGINES - PERFORMANCE”

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

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

At least 595 records · Page 33

Aerojet - Attitude Control Engines

All the engines were both qualification and acceptance tested at Marquardt s facilities. After we won the Apollo Program contract, we went off and built two vacuum test facilities, which simulated altitude continuous firing for as long as we wanted to run an engine. They would run days and days with the same capability we had on steam ejection. We did all of the testing in both for the qualification and the acceptance test. One of them was a large ball, which was an eighteen-foot diameter sphere, evacuated again with a big steam ejector system that could be used for system testing; that s where we did the Lunar Excursion Module testing. We put the whole cluster in there and tested the entire cluster at the simulated altitude conditions. The lowest altitude we tested at - typically an acceptance test - was 105,000 feet simulated altitude. The big ball - because people were interested in what they called goop formation, which is an unburned hydrazine product migrating to cold surfaces on different parts of spacecraft - was built to address those kinds of issues. We ran long-life tests in a simulated space environment with the entire inside of the test cell around the test article, liquid nitrogen cooled, so it could act as getter for any of the exhaust products. That particular facility could pull down to about 350,000 feet (atmosphere) equivalent altitude, which was pushing pretty close to the thermodynamic triple point of the MMH. It was a good test facility. Those facilities are no longer there. When the guys at Marquardt sold the company to what eventually became part of Aerojet, all those test facilities were cut off at the roots. I think they have a movie studio there at this point. That part of it is truly not recoverable, but it did some excellent high-altitude, space-equivalent testing at the time. Surprisingly, we had very few problems while testing in the San Fernando Valley. In the early 1960s, nobody had ever seen dinitrogen tetroxide (N2O4), so that wasn't too big a deal. We really did only make small, red clouds. In all the hundreds of thousands of tests and probably well over one million firings that I was around that place for, in all that thirty-something years, we had a total of one serious injury associated with rocket engine testing and propellants. Because we were trying to figure out what propellants would really be good, we tried all of the fun stuff like the carbon tetrafluoride, chlorine pentafluoride, and pure fluorine. The materials knowledge wasn't all that great at the time. On one test, the fluorine we had didn't react well with the copper they were using for tubing, and it managed to cause another unscheduled disassembly of the facility. It was very serious. It's like one of those Korean War stories. The technician happened to be walking past the test facility when it decided to blow itself up. A piece of copper tubing pierced one cheek and came out the other. That was the only serious accident in all of the engines handled in all those years. Now, we did have a problem with the EPA later because they figured out what the brown clouds were about. We built a whole bunch of exhaust mitigation scrubbers to take care of engine testing in the daytime. In general, we operated the big shuttle (RCS) engine, the 870- pounder at nominal conditions; they scrubbed the effluents pretty well. If you operated that same 870-pound force engine at a level where you get a lot of excess oxidizer, yeah, there s a brown cloud. But, you know, it doesn't show up well in the dark. They did do some of that. But, that s gone; it was addressed one way or another. RELEASED -

Pfeifer, Gerald R.↗

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

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.

Cutright, Amanda↗

Turbofan gas turbine engine with variable fan outlet guide vanes

A turbofan gas turbine engine includes a forward fan section with a row of fan rotor blades, a core engine, and a fan bypass duct downstream of the forward fan section and radially outwardly of the core engine. The forward fan section has only a single stage of variable fan guide vanes which are variable fan outlet guide vanes downstream of the forward fan rotor blades. An exemplary embodiment of the engine includes an afterburner downstream of the fan bypass duct between the core engine and an exhaust nozzle. The variable fan outlet guide vanes are operable to pivot from a nominal OGV position at take-off to an open OGV position at a high flight Mach Number which may be in a range of between about 2.5-4+. Struts extend radially across a radially inwardly curved portion of a flowpath of the engine between the forward fan section and the core engine.

Wood, Peter John↗

Status of the Combined Cycle Engine Rig

Status for the past year is provided of the turbine-based Combined-Cycle Engine (CCE) Rig for the hypersonic project. As part of the first stage propulsion of a two-stage-to-orbit vehicle concept, this engine rig is designed with a common inlet that supplies flow to a turbine engine and a dual-mode ramjet / scramjet engine in an over/under configuration. At Mach 4 the inlet has variable geometry to switch the airflow from the turbine to the ramjet / scramjet engine. This process is known as inlet mode-transition. In addition to investigating inlet aspects of mode transition, the rig will allow testing of turbine and scramjet systems later in the test series. Fully closing the splitter cowl "cocoons" the turbine engine and increases airflow to the scramjet duct. The CCE Rig will be a testbed to investigate integrated propulsion system and controls technology objectives. Four phases of testing are planned to 1) characterize the dual inlet database, 2) collect inlet dynamics using system identification techniques, 3) implement an inlet control to demonstrate mode-transition scenarios and 4) demonstrate integrated inlet/turbine engine operation through mode-transition. Status of the test planning and preparation activities is summarized with background on the inlet design and small-scale testing, analytical CFD predictions and some details of the large-scale hardware. The final stages of fabrication are underway.

Saunders, Dave↗

NASA Applications and Lessons Learned in Reliability Engineering

Since the Shuttle Challenger accident in 1986, communities across NASA have been developing and extensively using quantitative reliability and risk assessment methods in their decision making process. This paper discusses several reliability engineering applications that NASA has used over the year to support the design, development, and operation of critical space flight hardware. Specifically, the paper discusses several reliability engineering applications used by NASA in areas such as risk management, inspection policies, components upgrades, reliability growth, integrated failure analysis, and physics based probabilistic engineering analysis. In each of these areas, the paper provides a brief discussion of a case study to demonstrate the value added and the criticality of reliability engineering in supporting NASA project and program decisions to fly safely. Examples of these case studies discussed are reliability based life limit extension of Shuttle Space Main Engine (SSME) hardware, Reliability based inspection policies for Auxiliary Power Unit (APU) turbine disc, probabilistic structural engineering analysis for reliability prediction of the SSME alternate turbo-pump development, impact of ET foam reliability on the Space Shuttle System risk, and reliability based Space Shuttle upgrade for safety. Special attention is given in this paper to the physics based probabilistic engineering analysis applications and their critical role in evaluating the reliability of NASA development hardware including their potential use in a research and technology development environment.

Safie, Fayssal M.↗

Embedded Acoustic Sensor Array for Engine Fan Noise Source Diagnostic Test: Feasibility of Noise Telemetry via Wireless Smart Sensors

Aircraft engines have evolved into a highly complex system to meet ever-increasing demands. The evolution of engine technologies has primarily been driven by fuel efficiency, reliability, as well as engine noise concerns. One of the sources of engine noise is pressure fluctuations that are induced on the stator vanes. These local pressure fluctuations, once produced, propagate and coalesce with the pressure waves originating elsewhere on the stator to form a spinning pressure pattern. Depending on the duct geometry, air flow, and frequency of fluctuations, these spinning pressure patterns are self-sustaining and result in noise which eventually radiate to the far-field from engine. To investigate the nature of vane pressure fluctuations and the resulting engine noise, unsteady pressure signatures from an array of embedded acoustic sensors are recorded as a part of vane noise source diagnostics. Output time signatures from these sensors are routed to a control and data processing station adding complexity to the system and cable loss to the measured signal. "Smart" wireless sensors have data processing capability at the sensor locations which further increases the potential of wireless sensors. Smart sensors can process measured data locally and transmit only the important information through wireless communication. The aim of this wireless noise telemetry task was to demonstrate a single acoustic sensor wireless link for unsteady pressure measurement, and thus, establish the feasibility of distributed smart sensors scheme for aircraft engine vane surface unsteady pressure data transmission and characterization.

Zaman, Afroz↗

NESTA: NASA Engineering Shuttle Telemetry Agent

The Spaceport Processing Systems Branch at NASA Kennedy Space Center has developed and deployed an agent based tool to monitor the Space Shuttle's ground processing telemetry stream. The application, the NASA Engineering Shuttle Telemetry Agent, increases situational awareness for system and hardware engineers during ground processing of the Shuttle's subsystems. The agent provides autonomous monitoring of the telemetry stream and automatically alerts system engineers when predefined criteria have been met. Efficiency and safety are improved through increased automation. Sandia National Labs' Java Expert System Shell is employed as the rule engine. The shell's predicate logic lends itself well to capturing the heuristics and specifying the engineering rules of this spaceport domain. The declarative paradigm of the rule-based agent yields a highly modular and scalable design spanning multiple subsystems of the Shuttle. Several hundred monitoring rules have been written thus far with corresponding notifications sent to Shuttle engineers. This paper discusses the rule-based telemetry agent used for Space Shuttle ground processing and explains the problem domain, development of the agent software, benefits of AT technology, and deployment and sustaining engineering of the product.

Semmel, Glenn S.↗

Applying Model Based Systems Engineering to NASA's Space Communications Networks

System engineering practices for complex systems and networks now require that requirement, architecture, and concept of operations product development teams, simultaneously harmonize their activities to provide timely, useful and cost-effective products. When dealing with complex systems of systems, traditional systems engineering methodology quickly falls short of achieving project objectives. This approach is encumbered by the use of a number of disparate hardware and software tools, spreadsheets and documents to grasp the concept of the network design and operation. In case of NASA's space communication networks, since the networks are geographically distributed, and so are its subject matter experts, the team is challenged to create a common language and tools to produce its products. Using Model Based Systems Engineering methods and tools allows for a unified representation of the system in a model that enables a highly related level of detail. To date, Program System Engineering (PSE) team has been able to model each network from their top-level operational activities and system functions down to the atomic level through relational modeling decomposition. These models allow for a better understanding of the relationships between NASA's stakeholders, internal organizations, and impacts to all related entities due to integration and sustainment of existing systems. Understanding the existing systems is essential to accurate and detailed study of integration options being considered. In this paper, we identify the challenges the PSE team faced in its quest to unify complex legacy space communications networks and their operational processes. We describe the initial approaches undertaken and the evolution toward model based system engineering applied to produce Space Communication and Navigation (SCaN) PSE products. We will demonstrate the practice of Model Based System Engineering applied to integrating space communication networks and the summary of its results and impact. We will highlight the insights gained by applying the Model Based System Engineering and provide recommendations for its applications and improvements.

Bhasin, Kul↗

Status on the Verification of Combustion Stability for the J-2X Engine Thrust Chamber Assembly

Development is underway of the J -2X engine, a liquid oxygen/liquid hydrogen rocket engine for use on the Space Launch System. The Engine E10001 began hot fire testing in June 2011 and testing will continue with subsequent engines. The J -2X engine main combustion chamber contains both acoustic cavities and baffles. These stability aids are intended to dampen the acoustics in the main combustion chamber. Verification of the engine thrust chamber stability is determined primarily by examining experimental data using a dynamic stability rating technique; however, additional requirements were included to guard against any spontaneous instability or rough combustion. Startup and shutdown chug oscillations are also characterized for this engine. This paper details the stability requirements and verification including low and high frequency dynamics, a discussion on sensor selection and sensor port dynamics, and the process developed to assess combustion stability. A status on the stability results is also provided and discussed.

Casiano, Matthew↗

Enhancing Systems Engineering Education Through Case Study Writing

Developing and refining methods for teaching systems engineering is part of Systems Engineering grand challenges and agenda for research in the SE research community. Retention of systems engineering knowledge is a growing concern in the United States as the baby boom generation continues to retire and the faster pace of technology development does not allow for younger generations to gain experiential knowledge through years of practice. Government agencies, including the National Aeronautics and Space Administration (NASA), develop their own curricula and SE leadership development programs to "grow their own" systems engineers. Marshall Space Flight Center (MSFC) conducts its own Center-focused Marshall Systems Engineering Leadership Development Program (MSELDP), a competitive program consisting of coursework, a guest lecture series, and a rotational assignment into an unfamiliar organization engaged in systems engineering. Independently, MSFC developed two courses to address knowledge retention and sharing concerns: Real World Marshall Mission Success course and its Case Study Writers Workshop and Writers Experience. Teaching case study writing and leading students through a hands-on experience at writing a case study on an SE topic can enhance SE training and has the potential to accelerate the transfer of experiential knowledge. This paper is an overview of the pilot experiences with teaching case study writing, its application in case study-based learning, and identifies potential areas of research and application for case study writing in systems engineering education.

Stevens, Jennifer Stenger↗

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

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.

Ballard, Richard O.↗

Using Model-Based Systems Engineering to Provide Artifacts for NASA Project Life-cycle and Technical Reviews

This paper is for the AIAA Space Conference. The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.

MBSE↗

Using Model-Based Systems Engineering To Provide Artifacts for NASA Project Life-Cycle and Technical Reviews

The ability of systems engineers to use model-based systems engineering (MBSE) to generate self-consistent, up-to-date systems engineering products for project life-cycle and technical reviews is an important aspect for the continued and accelerated acceptance of MBSE. Currently, many review products are generated using labor-intensive, error-prone approaches based on documents, spreadsheets, and chart sets; a promised benefit of MBSE is that users will experience reductions in inconsistencies and errors. This work examines features of SysML that can be used to generate systems engineering products. Model elements, relationships, tables, and diagrams are identified for a large number of the typical systems engineering artifacts. A SysML system model can contain and generate most systems engineering products to a significant extent and this paper provides a guide on how to use MBSE to generate products for project life-cycle and technical reviews. The use of MBSE can reduce the schedule impact usually experienced for review preparation, as in many cases the review products can be auto-generated directly from the system model. These approaches are useful to systems engineers, project managers, review board members, and other key project stakeholders.

SE Product↗

Principles of Sociology in Systems Engineering

Systems engineering involves both the integration of the system and the integration of the disciplines which develop and operate the system. Integrating the disciplines is a sociological effort to bring together different groups, often with different terminology, to achieve a common goal, the system. The focus for the systems engineer is information flow through the organization, between the disciplines, to ensure the system is developed and operated with all relevant information informing system decisions. Robert K. Merton studied the sociological principles of the sciences and the sociological principles he developed apply to systems engineering. Concepts such as specification of ignorance, common terminology, opportunity structures, role-sets, and the reclama (reconsideration) process are all important sociological approaches that should be employed by the systems engineer. In bringing the disciplines together, the systems engineer must also be wary of social ambivalence, social anomie, social dysfunction, insider-outsider behavior, unintended consequences, and the self-fulfilling prophecy. These sociological principles provide the systems engineer with key approaches to manage the information flow through the organization as the disciplines are integrated and share their information. This also helps identify key sociological barriers to information flow through the organization. This paper will discuss this theoretical basis for the application of sociological principles to systems engineering.

Watson, Michael D.↗

Angled Core Gas Turbine Engine Mounting

A propulsion system for an aircraft includes first and second turbine engines mounted within a fuselage of the aircraft. The first turbine engine includes a first engine core that drives a first propulsor disposed about a first propulsor axis. The second turbine engine includes a second engine core and a second propulsor disposed about a second propulsor axis parallel to the first propulsor axis. The first engine core and the second engine core are mounted at an angle relative to corresponding ones of the first and second propulsor axes.

Suciu, Gabriel L.↗

Diverter fittings for cooling systems of an engine

A passive diverter fitting for a cooling system of an engine includes a base defining an interior cavity, an inlet opening extending through the base that is in fluid communication with the interior cavity, an outlet opening that is in fluid communication with the interior cavity, and a bypass opening that is in fluid communication with the interior cavity. The base is configured to be removably disposed in a cavity of an engine block. The inlet opening is positioned to receive coolant when the passive diverter fitting is disposed in the cavity of the engine block. The outlet opening is in fluid communication with the area exterior to the engine block when the passive diverter fitting is disposed in the cavity of the engine block. The bypass opening is in fluid communication with an interior coolant passage of the engine block when the passive diverter fitting is disposed in the cavity of the engine block.

Chen, Allen Yao↗

A detailed experimental and modeling comparison of molecular radiative heat loss in a spark-ignition engine

Radiative heat transfer has been chiefly considered negligible in internal combustion engines, except for Diesel engines where soot radiation was recognized as a significant radiative transfer source. Only more recently, detailed simulations have shown that molecular radiation can be substantial as well. In extension to this, molecular radiative heat transfer can reach detectable levels of about 5–10% of the total heat transfer in spark-ignited engines. The broadband radiative nature of the significant emitting molecules, carbon dioxide and water, makes it necessary to address whether radiative trapping plays a substantial role in either total heat loss or energy redistribution within the cylinder. An experimental setup that allows measurements of the infrared emissions at a 2-crank-angle-degree resolution was developed to determine the importance of radiative trapping by carbon dioxide and water. Measurements were conducted in the well-characterized and documented TCC-III engine at the University of Michigan. The engine operated on a stoichiometric propane/air mixture at a speed of 1,300 RPM. Large Eddy Simulations with added line-by-line photon Monte-Carlo simulations of the molecular radiation were an integral part of this study to plan and devise the measurements. Post-processing of the simulation data included an accurate representation of the experimental volume from where infrared signals are collected. Additionally, the experimental data were used for validation of the photon Monte-Carlo simulations. Joint analysis of experimental and simulated spectra allowed quantifying the significance of radiative trapping. Results show the significant role of radiative trapping when predicting radiative heat transfer in the TCC-III engine.

42 ENGINEERING↗

Investigation of the end-gas autoignition process in natural gas engines and evaluation of the methane number index

Engine knock and misfire are barriers to pathways leading to high-efficiency Spark-Ignited (SI) Natural Gas (NG) engines. The general tendency to knock is highly dependent on engine operating conditions and the fuel reactivity. The problem is further complicated by the wide range of chemical reactivity in pipeline quality NG, represented by the Methane Number (MN) (65< MN<95). Understanding the underlying phenomena responsible for engine knock can support the development of predictive tools capable of identifying knock onset/intensity as well as a fuel’s propensity to knock, allowing engine manufacturers to expand the knock envelope and design more efficient/robust SI NG engines. Additionally, there is an opportunity for increased efficiency by controlling levels of end-gas autoignition if this can be predicted and controlled. This work focuses on the development of a novel methodology to understand/predict a fuel’s propensity to knock. This methodology is based on the charge fraction undergoing autoignition, namely fractional end-gas autoignition (F-EGAI), and was developed based on first order laminar flame speeds and ignition delay analysis combined with a 0-D homogeneous batch reactor model. This methodology proved to be suitable to predict a fuel’s propensity to knock, even under conditions when light knock was observed. The simple modeling approach was used to explain the results from a series of MN tests with multiple NG compositions exhibiting a wide range of reactivity compositions and providing insight on why fuels of very different chemical compositions can have the same MN. Finally, a CFD model was developed was used to confirm the methodology capability and provide further insights in the physical and chemical phenomena behind end gas autoignition.

42 ENGINEERING↗