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 1,135 records · Page 63
All sourcesNASA NTRSDOE OSTI
NASA NTRS2002

Mechanical stimulation improves tissue-engineered human skeletal muscle

Human bioartificial muscles (HBAMs) are tissue engineered by suspending muscle cells in collagen/MATRIGEL, casting in a silicone mold containing end attachment sites, and allowing the cells to differentiate for 8 to 16 days. The resulting HBAMs are representative of skeletal muscle in that they contain parallel arrays of postmitotic myofibers; however, they differ in many other morphological characteristics. To engineer improved HBAMs, i.e., more in vivo-like, we developed Mechanical Cell Stimulator (MCS) hardware to apply in vivo-like forces directly to the engineered tissue. A sensitive force transducer attached to the HBAM measured real-time, internally generated, as well as externally applied, forces. The muscle cells generated increasing internal forces during formation which were inhibitable with a cytoskeleton depolymerizer. Repetitive stretch/relaxation for 8 days increased the HBAM elasticity two- to threefold, mean myofiber diameter 12%, and myofiber area percent 40%. This system allows engineering of improved skeletal muscle analogs as well as a nondestructive method to determine passive force and viscoelastic properties of the resulting tissue.

Non-NASA Center↗
NASA NTRS2003

Information technology security system engineering methodology

A methodology is described for system engineering security into large information technology systems under development. The methodology is an integration of a risk management process and a generic system development life cycle process. The methodology is to be used by Security System Engineers to effectively engineer and integrate information technology security into a target system as it progresses through the development life cycle. The methodology can also be used to re-engineer security into a legacy system.

Security risk analysis system engineering↗
NASA NTRS2006

Fusing Quantitative Requirements Analysis with Model-based Systems Engineering

A vision is presented for fusing quantitative requirements analysis with model-based systems engineering. This vision draws upon and combines emergent themes in the engineering milieu. "Requirements engineering" provides means to explicitly represent requirements (both functional and non-functional) as constraints and preferences on acceptable solutions, and emphasizes early-lifecycle review, analysis and verification of design and development plans. "Design by shopping" emphasizes revealing the space of options available from which to choose (without presuming that all selection criteria have previously been elicited), and provides means to make understandable the range of choices and their ramifications. "Model-based engineering" emphasizes the goal of utilizing a formal representation of all aspects of system design, from development through operations, and provides powerful tool suites that support the practical application of these principles. A first step prototype towards this vision is described, embodying the key capabilities. Illustrations, implications, further challenges and opportunities are outlined.

optimization↗
NASA NTRS2014

Preliminary Study on Acoustic Detection of Faults Experienced by a High-Bypass Turbofan Engine

The vehicle integrated propulsion research (VIPR) effort conducted by NASA and several partners provided an unparalleled opportunity to test a relatively low TRL concept regarding the use of far field acoustics to identify faults occurring in a high bypass turbofan engine. Though VIPR Phase II ground based aircraft installed engine testing wherein a multitude of research sensors and methods were evaluated, an array of acoustic microphones was used to determine the viability of such an array to detect failures occurring in a commercially representative high bypass turbofan engine. The failures introduced during VIPR testing included commanding the engine's low pressure compressor (LPC) exit and high pressure compressor (HPC) 14th stage bleed values abruptly to their failsafe positions during steady state

acoustics↗
NASA NTRS2014

Improving Free-Piston Stirling Engine Specific Power

This work uses analytical methods to demonstrate the potential benefits of optimizing piston and/or displacer motion in a Stirling Engine. Isothermal analysis was used to show the potential benefits of ideal motion in ideal Stirling engines. Nodal analysis is used to show that ideal piston and displacer waveforms are not optimal in real Stirling engines. Constrained optimization was used to identify piston and displacer waveforms that increase Stirling engine specific power.

Stirling Engine↗
NASA NTRS2014

Possible Mechanisms for Turbofan Engine Ice Crystal Icing at High Altitude

A thermodynamic model is presented to describe possible mechanisms of ice formation on unheated surfaces inside a turbofan engine compression system from fully glaciated ice crystal clouds often formed at high altitude near deep convective weather systems. It is shown from the analysis that generally there could be two distinct types of ice formation: (1) when the "surface freezing fraction" is in the range of 0 to 1, dominated by the freezing of water melt from fully or partially melted ice crystals, the ice structure is formed from accretion with strong adhesion to the surface, and (2) when the "surface melting fraction" is the range of 0 to 1, dominated by the further melting of ice crystals, the ice structure is formed from accumulation of un-melted ice crystals with relatively weak bonding to the surface. The model captures important qualitative trends of the fundamental ice-crystal icing phenomenon reported earlier1,2 from the research collaboration work by NASA and the National Research Council (NRC) of Canada. Further, preliminary analysis of test data from the 2013 full scale turbofan engine ice crystal icing test3 conducted in the NASA Glenn Propulsion Systems Laboratory (PSL) has also suggested that (1) both types of ice formation occurred during the test, and (2) the model has captured some important qualitative trend of turning on (or off) the ice crystal ice formation process in the tested engine low pressure compressor (LPC) targeted area under different icing conditions that ultimately would lead to (or suppress) an engine core roll back (RB) event.

Crystal Icing↗
NASA NTRS2015

Advanced Stirling Radioisotope Generator Engineering Unit 2 (ASRG EU2) Final Assembly

NASA Glenn Research Center (GRC) has recently completed the assembly of a unique Stirling generator test article for laboratory experimentation. Under the Advanced Stirling Radioisotope Generator (ASRG) flight development contract, NASA GRC initiated a task to design and fabricate a flight-like generator for in-house testing. This test article was given the name ASRG Engineering Unit 2 (EU2) as it was effectively the second engineering unit to be built within the ASRG project. The intent of the test article was to duplicate Lockheed Martin's qualification unit ASRG design as much as possible to enable system-level tests not previously possible at GRC. After the cancellation of the ASRG flight development project, the decision was made to continue the EU2 build, and make use of a portion of the hardware from the flight development project. GRC and Lockheed Martin engineers collaborated to develop assembly procedures, leveraging the valuable knowledge gathered by Lockheed Martin during the ASRG development contract. The ASRG EU2 was then assembled per these procedures at GRC with Lockheed Martin engineers on site. The assembly was completed in August 2014. This paper details the components that were used for the assembly, and the assembly process itself.

Stirling Cycle↗
NASA NTRS2011

Aerospace Concurrent Engineering Design Teams: Current State, Next Steps and a Vision for the Future

Over the past sixteen years, government aerospace agencies and aerospace industry have developed and evolved operational concurrent design teams to create novel spaceflight mission concepts and designs. These capabilities and teams, however, have evolved largely independently. In today's environment of increasingly complex missions with limited budgets it is becoming readily apparent that both implementing organizations and today's concurrent engineering teams will need to interact more often than they have in the past. This will require significant changes in the current state of practice. This paper documents the findings from a concurrent engineering workshop held in August 2010 to identify the key near term improvement areas for concurrent engineering capabilities and challenges to the long-term advancement of concurrent engineering practice. The paper concludes with a discussion of a proposed vision for the evolution of these teams over the next decade.

concurrent engineering design↗
NASA NTRS2012

A Model-Based Approach to Engineering Behavior of Complex Aerospace Systems

One of the most challenging yet poorly defined aspects of engineering a complex aerospace system is behavior engineering, including definition, specification, design, implementation, and verification and validation of the system's behaviors. This is especially true for behaviors of highly autonomous and intelligent systems. Behavior engineering is more of an art than a science. As a process it is generally ad-hoc, poorly specified, and inconsistently applied from one project to the next. It uses largely informal representations, and results in system behavior being documented in a wide variety of disparate documents. To address this problem, JPL has undertaken a pilot project to apply its institutional capabilities in Model-Based Systems Engineering to the challenge of specifying complex spacecraft system behavior. This paper describes the results of the work in progress on this project. In particular, we discuss our approach to modeling spacecraft behavior including 1) requirements and design flowdown from system-level to subsystem-level, 2) patterns for behavior decomposition, 3) allocation of behaviors to physical elements in the system, and 4) patterns for capturing V&V activities associated with behavioral requirements. We provide examples of interesting behavior specification patterns, and discuss findings from the pilot project.

SysML↗
NASA NTRS2015

Affordable Development and Demonstration of a Small NTR engine and Stage: A Preliminary NASA, DOE, and Industry Assessment

In FY'11, Nuclear Thermal Propulsion (NTP) was identified as a key propulsion option under the Advanced In-Space Propulsion (AISP) component of NASA's Exploration Technology Development and Demonstration (ETDD) program A strategy was outlined by GRC and NASA HQ that included 2 key elements -"Foundational Technology Development" followed by specific "Technology Demonstration" projects. The "Technology Demonstration "element proposed ground technology demonstration (GTD) testing in the early 2020's, followed by a flight technology demonstration (FTD) mission by approx. 2025. In order to reduce development costs, the demonstration projects would focus on developing a small, low thrust (approx. 7.5 -16.5 klb(f)) engine that utilizes a "common" fuel element design scalable to the higher thrust (approx. 25 klb(f)) engines used in NASA's Mars DRA 5.0 study(NASA-SP-2009-566). Besides reducing development costs and allowing utilization of existing, flight proven engine hard-ware (e.g., hydrogen pumps and nozzles), small, lower thrust ground and flight demonstration engines can validate the technology and offer improved capability -increased payloads and decreased transit times -valued for robotic science missions identified in NASA's Decadal Study.

Spacecraft design↗
NASA NTRS2016

Possible Mechanisms for Turbofan Engine Ice Crystal Icing at High Altitude

A thermodynamic model is presented to describe possible mechanisms of ice formation on unheated surfaces inside a turbofan engine compression system from fully glaciated ice crystal clouds often formed at high altitude near deep convective weather systems. It is shown from the analysis that generally there could be two distinct types of ice formation: (1) when the "surface freezing fraction" is in the range of 0 to 1, dominated by the freezing of water melt from fully or partially melted ice crystals, the ice structure is formed from accretion with strong adhesion to the surface, and (2) when the "surface melting fraction" is the range of 0 to 1, dominated by the further melting of ice crystals, the ice structure is formed from accumulation of un-melted ice crystals with relatively weak bonding to the surface. The model captures important qualitative trends of the fundamental ice-crystal icing phenomenon reported earlier (Refs. 1 and 2) from the research collaboration work by NASA and the National Research Council (NRC) of Canada. Further, preliminary analysis of test data from the 2013 full scale turbofan engine ice crystal icing test (Ref. 3) conducted in the NASA Glenn Propulsion Systems Laboratory (PSL) has also suggested that (1) both types of ice formation occurred during the test, and (2) the model has captured some important qualitative trend of turning on (or off) the ice crystal ice formation process in the tested engine low pressure compressor (LPC) targeted area under different icing conditions that ultimately would lead to (or suppress) an engine core roll back (RB) event.

Crystal Icing↗
NASA NTRSDate not supplied

Space Launch System Engine Out Capabilities

NASA's Space Launch System (SLS) is being developed with the primary purpose of returning people to the Moon and eventually landing people on Mars. With these lofty goals, ensuring mission completion is paramount even in the event of an in-flight mishap. One possible mishap is the loss of an engine in flight. While SLS was not required to show full engine out capability, the program took an ``assess to'' approach to see when the launch vehicle could complete the mission after an engine failure versus when the launch vehicle targets required a down-mode to an alternate mission target to ensure at least some flight objectives were complete, or at a minimum ensure safe return of Orion and the Crew. While this paper will focus on Artemis I, an uncrewed mission, some comparisons will be made to how the engine out capability will change for the subsequent Crewed flights of SLS and Orion.

Engine Out↗
NASA NTRSDate not supplied

Space Launch System Engine Out Capabilities

NASA's SLS is being developed with the primary purpose of returning people to the Moon and eventually landing people on Mars. With these lofty goals, ensuring mission completion is paramount even in the event of an in-flight mishap. One possible mishap is the loss of an engine in flight. While SLS was not required to show full engine out capability, the program took an ``assess to'' approach to see when the launch vehicle could complete the mission after an engine failure versus when the launch vehicle targets required a down-mode to an alternate mission target to ensure at least some flight objectives were complete, or at a minimum ensure safe return of Orion and the Crew. While this paper will focus on Artemis I, an uncrewed mission, some comparisons will be made to how the engine out capability will change for the subsequent Crewed flights of SLS and Orion.

Space Launch System↗
NASA NTRS2020

Particle Size Measurements from the 2018 Honeywell Uncertified Research Engine Test in the NASA Propulsion Systems Laboratory

The particle size measurements from the Honeywell Uncertified Research Engine Icing Test in the NASA Propulsion Systems Laboratory conducted in 2018 are presented. This work focuses on describing the experimental arrangement, the processing and analysis methods, and final results for select cases acquired during ice crystal cloud conditions. The measurements presented will include data acquired by two High Speed Imaging instruments located both upstream and downstream of the fan, in the engine bypass section. Experimental results demonstrate the expected downward shift in the particle size distribution as the cloud passes through the engine fan and the ice particles break-up. This work also demonstrates the feasibility of acquiring particle size distributions in the environment of a running engine.

Engine icing↗
NASA NTRSDate not supplied

Numerical Investigation of Film Coefficient Engineering Methodology for Dissociated, Chemically Reacting Boundary Layers

Aerothermal analysis of spacecraft planetary entry is heavily dependent on heritage engineering models. The film coefficient heat transfer model examined in this paper estimates the convective heating to the vehicle for a laminar, dissociated, chemically reacting boundary layer for an Earth atmosphere. This model requires information about the vehicle and flow field for a given trajectory point and estimates a proportional relationship between enthalpy potential and convective heat flux. In practice it is the aerothermal engineer who must decide which assumptions are appropriate for their application. This work looks at numerous CFD simulations for an arbitrary, axisymmetric flight vehicle to analyze the relative importance of both the mass and energy constraints imposed at the wall boundary, as well as the effect of various diffusion models. The sensitivity of the engineering model is assessed based on the impact of the CFD assumptions as an effort to make it available to design engineers across industry.

numerical boundary layer↗
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer's Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRSDate not supplied

Lessons Learned With Risk Management: A Systems Engineer’s Perspective

Risk management is a communications device that, when executed as an essential task, enables systems engineering to effectively balance risk across the project. Developing and baselining risks is an essential continuous task to ensure top project concerns both from bottom up and top down are being mitigated. Risk management provides the opportunity to avoid the consequence of the risk when mitigation steps start early enough. Just discussing risk with all the project flight elements during development, even if no risks are open, provides an excellent communication opportunity between systems engineering and those elements, ensuring concerns and worries have a platform for discussion. A well-managed risk identification process will identify concerns that are serious but not being clearly communicated, and it will enable mitigation of those potential problems before they cause a failure. Effective risk management requires considerable time and effort, but that effort will save time and money across the development. Risk management must be frequent enough to be useful and in depth enough to bring out emerging issues. It also requires a trusting relationship between the lead systems engineer and element and/or subsystem leads. The discussions need to be with the right number of individuals (typically a handful) and the right duration in time (typically an hour a month). Outside of these risk working groups, there is a formal management process to input, status, and disposition risks, and a monthly Risk Management Board meeting where key project stakeholders are informed. This paper provides good guidance on effective risk management from a systems engineering perspective and provides project lessons learned from the NASA spaceflight missions NICER, Landsat 9, LRO, and OSIRIS-REx to demonstrate the effectiveness of risk management.

Lessons Learned↗
NASA NTRS2026

Assessment of Aircraft Electric Engine Regulatory Special Conditions

This report provides a regulatory gap assessment of the Federal Aviation Administration (FAA) and the European Union Aviation Safety Agency (EASA) Special Conditions (SC) for electric engines. This information is presented to support ongoing international harmonization efforts for electric engine certification, to establish a level of safety consistent across regulatory bodies and equivalent to that of existing combustion engines. HS Advanced Concepts LLC assembled a team of subject-matter experts to develop a comprehensive comparison of the regulatory text of EASA SC E-19 and the FAA special conditions for the certification of electric engines. The team included Mr. Chris Baczynski of BAC Aerospace Inc. and Mr. Zach Kaufman, formerly with magniX.

aircraft certification↗