SEARCH · Engineering Papers

Results for “Engineering”

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 1,585 records · Page 88

All sources NASA NTRS DOE OSTI

NASA NTRS2005

Introduction to Flight Test Engineering [Introduction Aux Techniques Des Essais En Vol]

Flight test is at the core of what organizations must do in order to validate the operation and systems on an aircraft. While the AGARDograph series 300 and 160 series deal with aspects of this testing, this volume pulls it all together as an introduction to the process required to do effective flight test engineering. This volume was originally published in 1995. Its utility has been proven in that many flight test organizations and universities have requested copies for their engineers and students. It was felt that re-issuing it in a new format designed for electronic publication would be valuable to the community. This second printing changes none of the text, but rather reformats it. All the original references to AGARD (instead of RTO) are left in place so that none of the flavor of the original publication is lost. This is the Introductory Volume to the Flight Test Techniques Series. It is a general introduction to the various activities and aspects of Flight Test Engineering that must be considered when planning, conducting, and reporting a flight test program. Its main intent is to provide a broad overview to the novice engineer or to other people who have a need to interface with specialists within the flight test community. The first two Sections provide some insight into the question of why flight test and give a short history of flight test engineering. Sections 3 through 10 deal with the preparation for flight testing. They provide guidance on the preliminary factors that must be considered; the composition of the test team; the logistic support requirements; the instrumentation and data processing requirements; the flight test plan; the associated preliminary ground tests; and last, but by no means least, discuss safety aspects. Sections 11 through 27 describe the various types of flight tests that are usually conducted during the development and certification of a new or modified aircraft type. Each Section offers a brief introduction to the topic under consideration, and the nature and the objectives of the tests to be conducted. It lists the test instrumentation (and, where appropriate, other test equipment and facilities) required, describes the test maneuvers to be executed, and indicates the way in which the test data is selected, analyzed, and presented. The various activities that should take place between test flights are presented next. Items that are covered are: who to debrief; what type of reports to send where: types of data analysis required for next flight; review of test data to make a comparison to predicted data and some courses of action if there is not good agreement; and comments on selecting the next test flight. The activities that must take place upon completion of the test program are presented. The types of reports and briefings that should take place and a discussion of some of the uses of the flight test data are covered. A brief forecast is presented of where present trends may be leading.

Test facilities↗

NASA NTRS2006

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

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.

systems engineering↗

NASA NTRS2014

A Model-Based Anomaly Detection Approach for Analyzing Streaming Aircraft Engine Measurement Data

This paper presents a model-based anomaly detection architecture designed for analyzing streaming transient aircraft engine measurement data. The technique calculates and monitors residuals between sensed engine outputs and model predicted outputs for anomaly detection purposes. Pivotal to the performance of this technique is the ability to construct a model that accurately reflects the nominal operating performance of the engine. The dynamic model applied in the architecture is a piecewise linear design comprising steady-state trim points and dynamic state space matrices. A simple curve-fitting technique for updating the model trim point information based on steadystate information extracted from available nominal engine measurement data is presented. Results from the application of the model-based approach for processing actual engine test data are shown. These include both nominal fault-free test case data and seeded fault test case data. The results indicate that the updates applied to improve the model trim point information also improve anomaly detection performance. Recommendations for follow-on enhancements to the technique are also presented and discussed.

Propulsion System Performance↗

NASA NTRS2015

A Model-Based Anomaly Detection Approach for Analyzing Streaming Aircraft Engine Measurement Data

Propulsion System Performance↗

NASA NTRS2008

Enabling Innovation and Collaboration Across Geography and Culture: A Case Study of NASA's Systems Engineering Community of Practice

In 2004, NASA faced major knowledge sharing challenges due to geographically isolated field centers that inhibited personnel from sharing experiences and ideas. Mission failures and new directions for the agency demanded better collaborative tools. In addition, with the push to send astronauts back to the moon and to Mars, NASA recognized that systems engineering would have to improve across the agency. Of the ten field centers, seven had not built a spacecraft in over 30 years, and had lost systems engineering expertise. The Systems Engineering Community of Practice came together to capture the knowledge of its members using the suite of collaborative tools provided by the NASA Engineering Network (NEN.) The NEN provided a secure collaboration space for over 60 practitioners across the agency to assemble and review a NASA systems engineering handbook. Once the handbook was complete, they used the open community area to disseminate it. This case study explores both the technology and the social networking that made the community possible, describes technological approaches that facilitated rapid setup and low maintenance, provides best practices that other organizations could adopt, and discusses the vision for how this community will continue to collaborate across the field centers to benefit the agency as it continues exploring the solar system.

NEN↗

NASA NTRS2012

Concept Assessment of a Fission Fragment Rocket Engine (FFRE) Propelled Spacecraft

The March, 2012 issue of Aerospace America stated that ―the near-to-medium prospects for applying advanced propulsion to create a new era of space exploration are not very good. In the current world, we operate to the Moon by climbing aboard a Carnival Cruise Lines vessel (Saturn 5), sail from the harbor (liftoff) shedding whole decks of the ship (staging) along the way and, having reached the return leg of the journey, sink the ship (burnout) and return home in a lifeboat (Apollo capsule). Clearly this is an illogical way to travel, but forced on Explorers by today's propulsion technology. However, the article neglected to consider the one propulsion technology, using today's physical principles that offer continuous, substantial thrust at a theoretical specific impulse of 1,000,000 sec. This engine unequivocally can create a new era of space exploration that changes the way spacecraft operate. Today's space Explorers could travel in Cruise Liner fashion using the technology not considered by Aerospace America, the novel Dusty Plasma Fission Fragment Rocket Engine (FFRE). This NIAC study addresses the FFRE as well as its impact on Exploration Spacecraft design and operation. It uses common physics of the relativistic speed of fission fragments to produce thrust. It radiatively cools the fissioning dusty core and magnetically controls the fragments direction to practically implement previously patented, but unworkable designs. The spacecraft hosting this engine is no more complex nor more massive than the International Space Station (ISS) and would employ the successful ISS technology for assembly and check-out. The elements can be lifted in "chunks" by a Heavy Lift Launcher. This Exploration Spacecraft would require the resupply of small amounts of nuclear fuel for each journey and would be an in-space asset for decades just as any Cruise Liner on Earth. This study has synthesized versions of the FFRE, integrated one concept onto a host spacecraft designed for manned travel to Jupiter's moon, Callisto, and assessed that round trip journey. This engine, although unoptimized, produced 10 pounds force of thrust at a delivered specific impulse of 527,000 seconds for the entire 15-year mission while providing enormous amounts of electrical power to the spacecraft. A payload of 60 metric tons, included in the 300 metric ton vehicle, was carried to Callisto and back; the propellant tanks holding the 4 metric tons of fuel were not jettisoned in the process. The study concluded that the engine and spacecraft are within today's technology, could be built, tested, launched on several SLS (Space Launch System) (or similar) launchers, integrated, checked out, moved to an in-space base such as at a Lagrange point and operated for decades.

Engine↗

NASA NTRS2016

Improving Free-Piston Stirling Engine Power Density

Analyses and experiments demonstrate the potential benefits of optimizing piston and displacer motion in a free piston Stirling Engine. Isothermal analysis shows the theoretical limits of power density improvement due to ideal motion in ideal Stirling engines. More realistic models based on nodal analysis show that ideal piston and displacer waveforms are not optimal, often producing less power than engines that use sinusoidal piston and displacer motion. Constrained optimization using nodal analysis predicts that Stirling engine power density can be increased by as much as 58% using optimized higher harmonic piston and displacer motion. An experiment is conducted in which an engine designed for sinusoidal motion is forced to operate with both second and third harmonics, resulting in a maximum piston power increase of 14%. Analytical predictions are compared to experimental data showing close agreement with indirect thermodynamic power calculations, but poor agreement with direct electrical power measurements.

Stirling engines↗

NASA NTRS2015

Simulation of Liquid Rocket Engine Failure Propagation Using Self-Evolving Scenarios

Traditional probabilistic risk assessment approaches often require failure scenarios to be explicitly defined through event sequences that are then quantified as part of the integrated analysis. This approach becomes difficult when failure propagation paths change as a function of the system operation. Additionally, if the propagation paths represent interactions among even a modest number of components, the scenario count becomes combinatorially intractable. This paper presents an alternate approach for quantifying the probability of failure propagation in such a case. Rather than explicitly defining scenario sequences, simple physical models are created for each of the components. In this way, only the physical states and rules of component interactions must be defined, rather than event sequences for each individual scenario. Initiating failures are introduced into the system, either randomly or as defined by relative likelihood, and the failures cascade through the system via the interaction rules. This process is repeated using Monte Carlo methods and, as a result, the most probable scenarios “self-evolve” in terms of both sequence path and frequency. This approach was applied to failures occurring in the engine compartment of a space launch vehicle with four liquid rocket engines and four high-pressure helium tanks. Each engine was modeled with key components, such as turbomachinery, combustion chamber, propellant lines, and additional support systems. Three test cases were conducted with different high-energy engine failures. End results of interest included an additional engine-out failure and tank burst, which represent the loss-of-mission (LOM) and loss-of-crew (LOC) failure environments, respectively. Observations show that almost every scenario outcome is unique and that many scenarios involve complex chain reactions that are difficult to predict. This validates the usefulness of the modeling approach in assessing the overall risks to the crew during a launch vehicle abort.

Rocket Engine↗

NASA NTRS2015

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

In FY11, NASA formulated a plan for Nuclear Thermal Propulsion (NTP) development that included Foundational Technology Development followed by system-level Technology Demonstrations. The ongoing NTP project, funded by NASA's Advanced Exploration Systems (AES) program, is focused on Foundational Technology Development and includes 5 key task activities: (1) Fuel element fabrication and non-nuclear validation testing of heritage fuel options; (2) Engine conceptual design; (3) Mission analysis and engine requirements definition; (4) Identification of affordable options for ground testing; and (5) Formulation of an affordable and sustainable NTP development program. Performance parameters for Point of Departure designs for a small criticality-limited and full size 25 klb (sub f) (kip, or 1000 pound-force)-class engine were developed during FYs 13-14 using heritage fuel element designs for both Rover NERVA (Nuclear Engine for Rocket Vehicle Applications) Graphite Composite (GC) and Ceramic Metal (Cermet) fuel forms. To focus the fuel development effort and maximize use of its resources, the AES program decided, in FY14, that a leader-follower down-selection between GC and cermet fuel was required. An Independent Review Panel (IRP) was convened by NASA and tasked with reviewing the available fuel data and making a recommendation to NASA. In February 2015, the IRP recommended and the AES program endorsed GC as the leader fuel In FY14, a preliminary development schedule DDTE (Design Development Test and Evaluation) plan was produced by GRC (Glenn Research Center), DOE (Department of Energy) and industry for the AES program. Assumptions, considerations and key task activities are presented here. At the direction of NASA HQ (32515), NASA and DOE are to work together to formulate a detailed development plan and schedule allowing the affordable development of a small (7.5-16.5 klbf) GC engine for possible flight technology demonstration (FTD) mission within a 10-year timeframe.

Lunar Flyby Mission↗

NASA NTRSDate not supplied

A Review Towards the Design Optimization of High-Performance Additively Manufactured Rotating Detonation Rocket Engine Injectors

Rotating Detonation Rocket Engines (RDRE) have been marketed primarily for their higher specific impulse potential over constant pressure (CP) liquid rocket engines. However, several other performance advantages exist such as heat transfer advantages for gas expander cycle, increased completeness of combustion at low chamber L*, compact engine design, reduced coolant channel pressure drop potential, and improved injector C* performance. NASA has paved the way for liquid engine system performance enhancement since the Apollo program and continues to do so with metal additive manufacturing (AM), new advanced materials, and advanced propulsion concepts. A team of propulsion development engineers at NASA are in the process of developing high-performance 7K lbf class RDRE hardware for their potential use in lander, upper stage, and even launch vehicle applications. Clear advantages have been demonstrated with AM including program cost and schedule reductions of up to 50%. It is well known that injector performance is integrally linked to the global performance of a combustion device. This is especially the case for RDREs since detonation stability is heavily dependent on the mixedness of propellants. A major goal of this work is to identify what has been done in the open experimental literature and what injectors design features are conducive to high performance in the detonation cycle. This paper reviews the available literature and reports the primary gaps in the knowledge base needed by the pressure gain combustion (PGC) community. Major conclusions are documented, and suggestions given towards the design of high-performance liquid RDRE injectors. In addition, the integration of metal AM into the design of liquid RDRE injector schemes is included.

rotating detonation rocket engine↗

NASA NTRSDate not supplied

System Safety Analysis of Complex NASA Systems with Model Based Engineering

The emergence of model-based engineering is transforming design and analysis methodologies [5]. A recognized benefit of model-based engineering is the existence of a “single source of truth” about the system that becomes the authoritative source of data and information for designers, analysts, and developers. This promotes consistency and efficiency as the design emerges and can be used to further optimize the design. Integrating System Safety Engineers to the “single source of truth” will ensure that the outputs of their assessments and analyses are relevant to the design as it evolves. Use of an integrated system model enables near immediate evaluation of a design change as well as development of operational processes for risk assessment and communication. Such models can enable efficient and timely analysis of system hazards (e.g., hazard fault tree analysis and procedure simulations) and produce complete, accurate, and more consistent products (e.g., hazard reports and safety requirement evaluations). Therefore, an agency-sponsored team at Goddard Space Flight Center (GSFC) recently completed a System Safety Study of modeling and testing capabilities as part of a Model-Based Safety and Mission Assurance Initiative (MBSMAI). Using an existing model developed for reliability analyses [1], GSFC modeling and system safety experts performed system safety analysis/modeling and produced safety products. The team evaluated model-based feasibility to support System Safety Engineering, developed safety analysis modeling processes, and identified tool capability advancement/development needs. These study results indicate model-based engineering is valid and useable for System

Model Based Engineering↗

NASA NTRSDate not supplied

ExMC Systems Engineering Status

The Exploration Medical Capability (ExMC) Element within the Human Research Program (HRP) applies systems engineering principles along with the use of Model-Based Systems Engineering (MBSE) tools to identify and communicate the requirements for medical and crew health and performance (CHP) systems. The MBSE approach to medical system design offers a paradigm shift toward greater integration between the vehicle and a human health and performance system. In addition, the MBSE tools provide a means in which systems engineers can develop different views of the relationships between and among requirements, standards, functions, and capabilities, to name a few, that is best suited for a user’s objectives. Applying these tools, ExMC Systems Engineering (SE) developed three MBSE models in support of multiple projects in fiscal year (FY) 2023. These included the Long-Duration Lunar Orbit and Lunar Surface (LDLOLS) Medical System Foundation, Earth-Independent Medical Operations (EIMO) medical system ConOps, and the 2023 Artemis CHP System model. This talk will provide a high-level overview of what the ExMC SE team has accomplished since the last Investigators’ Workshop, an introduction to upcoming SE talks, and the ongoing systems engineering work.

Systems engineering↗

NASA NTRSDate not supplied

ExMC Systems Engineering Status

Systems engineering↗

NASA NTRSDate not supplied

Systems Engineering Tutorial with Case Studies

Due to the ever-growing number of complex technical problems facing our world, a Systems Engineering approach is needed to assist in successful design, build and implementation of solutions. The interdisciplinary technical structure of current systems, technical processes representing System Design, Technical Management and Product Realization are instrumental in the development and integration of new technologies into mainstream applications. This tutorial will demonstrate the application of Systems Engineering tools to these types of problems. Learning objectives include, understanding how to develop and engineer a conceptual system; understand the importance of teams, communication, requirements definition, interface control, and focus on deliverables; useful tools and techniques for each aspect of the System Engineering process including Model Based Systems Engineering which will be touched upon lightly. Some hands-on problems will be pursued especially in requirements development which is always key to a successful project. Case studies will be presented to assist in the learning process.

Systems Engineering↗

NASA NTRSDate not supplied

X-57 Systems Engineering Lessons Learned

The X-57 Maxwell is an electric aircraft based on a 4-passenger, twin engine Tecnam P2006T General Aviation aircraft. The X-57 project originally envisioned a straightforward integration of commercial-off-the-shelf hardware components and software into a novel configuration to demonstrate the aerodynamic and performance benefits of Distributed Electric Propulsion (DEP). The project was initially started with a high-risk venture capitalist approach under NASA’s Convergent Aeronautics Solutions (CAS) project, which led to an initial philosophy of Project Management “light” (which was then interpreted as Systems Engineering (SE) “light”). As the project matured, it was forced to transition to one with increasing SE-rigor as the project scope changed, hardware and software deficiencies were found, and the team realized the magnitude of the technical and integration challenges. In hindsight, these technical challenges came in part from an overly optimistic technology readiness assessment (TRA) at the beginning of the project, which resulted in the project assuming that little to no subsystem development would be required. The project’s approach to systems engineering evolved throughout three separate informal phases of the project as it underwent two key transitions as a result of the team wrestling with the technical challenges and resultant changing project scope. This paper discusses the assumptions, approaches, and challenges encountered from a Systems Engineering standpoint in each of the three informal phases of the X-57 project. This paper also provides recommendations on how future projects can apply Systems Engineering best practices upfront along with a realistic TRA to aid projects that find themselves with similar challenges.

Systems Engineering↗

DOE OSTI2025

CIE Analysis Process for Engineered Systems

"CIE Analysis Process for Engineered Systems" outlines a comprehensive methodology for integrating Cyber-Informed Engineering (CIE) principles into both new and existing engineered systems. Sponsored by the U.S. Department of Energy’s Office of Cybersecurity, Energy Security, and Emergency Response (DOE CESER), the process aims to achieve cyber-informed decisions by producing functional security requirements for new systems and retrofitting existing systems to mitigate digital risks. The document details a step-by-step approach, including mission and function definition, digital asset awareness, consequence analysis, and mitigation analysis. It emphasizes the importance of documenting mechanical, electrical, programmable, and network components to protect system functions and provides examples and considerations for each step. The ultimate goal is to ensure that engineered systems remain resilient against cyber threats, maintaining safety, performance, and reliability.

42 - ENGINEERING↗

NASA NTRS1951

Combustion-chamber Performance Characteristics of a Python Turbine-propeller Engine Investigated in Altitude Wind Tunnel

Combustion-chamber performance characteristics of a Python turbine-propeller engine were determined from investigation of a complete engine over a range of engine speeds and shaft horsepowers at simulated altitudes. Results indicated the effect of engine operating conditions and altitude on combustion efficiency and combustion-chamber total pressure losses. Performance of this vaporizing type combustion chamber was also compared with several atomizing type combustion chambers. Over the range of test conditions investigated, combustion efficiency varied from approximately 0.95 to 0.99.

COMBUSTION - EFFECT OF ENGINE OPERATING CONDITIONS↗

NASA NTRS1993

Operating Characteristics of a 15-cm dia. Ion Engine for Small Planetary Spacecraft

A 15-cm diameter, scaled-down version of the NASA light-weight 30-cm ion engine has been developed for potential application to very small planetary spacecraft. Integration of the 15-cm ion source into 4x15-cm segmented engine configuration results in a 30-cm equivalent engine which can be throttled over a 7-to-1 input power variation with a constant beam current in each of the four segments. Throttling the segmented engine by turning off individual segments can result in a significant decrease in the required service life (and qualification requirements) of the ion source components.

grids segmented ion engine↗