Aviation Particle Emissions Reductions From Lean-Burn Engines Burning Sustainable Aviation Fuel
Explore the source record for details and available documents.
Richard H Moore↗
SEARCH · Search NASA
Results for “sustainable 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.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
Configuration development study of the X-24C hypersonic research airplane, phase 2
The X-24C Hypersonic Research Vehicle, configured with a heat-sink structure, a launch mass limit of 31.75 Mg and powered by an LR-105 Rocket Engine plus 12 LR-101 Sustainer Engines, was found to be the more cost effective of the candidate configurations. In addition, the configuration provides the maximum off design growth potential capability and subsequently, was selected as the candidate configuration to be subjected to the design refinement study in the remaining segment of the study. Selection of this configuration was based on the analytical study conducted on the performance growth capabilities of the candidate configurations selected from the Phase 1 Study.
Combs, H. G.↗
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.↗
Automation of Design Engineering Processes
A method, and a computer program that helps to implement the method, have been developed to automate and systematize the retention and retrieval of all the written records generated during the process of designing a complex engineering system. It cannot be emphasized strongly enough that all the written records as used here is meant to be taken literally: it signifies not only final drawings and final engineering calculations but also such ancillary documents as minutes of meetings, memoranda, requests for design changes, approval and review documents, and reports of tests. One important purpose served by the method is to make the records readily available to all involved users via their computer workstations from one computer archive while eliminating the need for voluminous paper files stored in different places. Another important purpose served by the method is to facilitate the work of engineers who are charged with sustaining the system and were not involved in the original design decisions. The method helps the sustaining engineers to retrieve information that enables them to retrace the reasoning that led to the original design decisions, thereby helping them to understand the system better and to make informed engineering choices pertaining to maintenance and/or modifications of the system. The software used to implement the method is written in Microsoft Access. All of the documents pertaining to the design of a given system are stored in one relational database in such a manner that they can be related to each other via a single tracking number.
Torrey, Glenn↗
Intrinsic self-stressing and low carbon Engineered Cementitious Composites (ECC) for improved sustainability
Highlights: • A self-stressing criterion for ECC was established and experimentally verified. • An intrinsic self-stressing ECC was developed by utilizing LC3 and CSA cement. • Initial maximum expansion and later expansion loss were successfully tailored. • Expansion mechanism was identified by XRD patterns. • Self-stressing ECC has 64% of the carbon footprint of conventional concrete. Engineered Cementitious Composites (ECC) is an emerging cementitious composite material with ultra-high ductility. However, its higher cement dosage limits its material greenness and leads to concerns with drying shrinkage. In this research, an ECC utilizing limestone calcined clay cement (LC3) and calcium sulphoaluminate cement (CSA) is investigated, focusing on minimizing the material's embodied carbon while enhancing its durability with intrinsic self-stressing functionality. A self-stressing criterion is theoretically established and experimentally verified. X-ray diffraction patterns reveal an ettringite quantity that modulates the initial expansion and later expansion-reversal of LC3-CSA-ECC to support a persistent self-stressing mechanism. LC3-CSA-ECC has a lower (64%) carbon footprint and similar embodied energy compared to conventional concrete. When combined with the durability advantage (tiny crack, high ductility of 5.5%, and self-stressing function), this low carbon self-stressing ECC holds promise as a sustainable repair material that lowers the embodied and operational carbon in civil infrastructure.
36 MATERIALS SCIENCE↗
Development Status of the J-2X
In June 2006, the NASA Marshall Space Flight Center (MSFC) and Pratt & Whitney Rocketdyne began development of an engine for use on the Ares I crew launch vehicle and the Ares V cargo launch vehicle. The development program will be completed in December 2012 at the end of a Design Certification Review and after certification testing of two flight configuration engines. A team of over 600 people within NASA and Pratt & Whitney Rocketdyne are currently working to prepare for the fall 2008 Critical Design Review (CDR), along with supporting an extensive risk mitigation test program. The J-2X will power the Ares I upper stage and the Ares V earth departure stage (EDS). The initial use will be in the Ares I, used to launch the Orion crew exploration vehicle. In this application, it will power the upper stage after being sent aloft on a Space Shuttle-derived. 5-segment solid rocket booster first stage. In this mission. the engine will ignite at altitude and provide the necessary acceleration force to allow the Orion to achieve orbital velocity. The Ares I upper stage, along with the J-2X. will then be expended. On the Ares V. first stage propulsion is provided by five RS-68B engines and two 5-segment boosters similar to the Ares I configuration. In the Ares V mission. the J-2X is first started to power the EDS and its payload. the Altair lunar lander. into earth orbit, then shut-down and get prepared for its next start. The EDS/Altair will remain in a parking orbit, awaiting rendezvous and docking with Orion. Once the two spacecraft are mated, the J-2X will be restarted to achieve earth departure velocity. After powering the Orion and Altair, the EDS will be expended. By using the J-2X Engine in both applications, a significant infrastructure cost savings is realized. Only one engine development is required, and the sustaining engineering and flight support infrastructures can be combined. There is also flexibility for changing, the production and flight manifest because a single production line can support both missions with minimal differences between each engine configuration kit.
Kynard, Mike↗
The History of Orbiter Corrosion Control (1981 - 2011)
After 135 missions and 30 years the Orbiter fleet was retired in 2011. Working with Orbiter project management and a world class engineering team the CCRB was successful in providing successful sustaining engineering support for approximately 20 years. Lessons learned from the Orbiter program have aided NASA and contractor engineers in the design and manufacture of new spacecraft so that exploration of space can continue. The Orbiters are proudly being displayed for all the public to see in New York City, Washington D.C., Los Angeles, and at the Kennedy Space Center in Florida.
Corrosion↗
A Return to Innovative Engineering Design, Critical Thinking and Systems Engineering
I believe we are facing a critical time where innovative engineering design is of paramount importance to the success of our aerospace industry. However, the very qualities and attributes necessary for enhancing, educating, and mentoring a creative spirit are in decline in important areas. The importance of creativity and innovation in this country was emphasized by a special edition of the Harvard Business Review OnPoint entitled: "The Creative Company" which compiled a series of past and present articles on the subject of creativity and innovation and stressed its importance to our national economy. There is also a recognition of a lack of engineering, critical thinking and problem-solving skills in our education systems and a trend toward trying to enhance those skills by developing K-12 educational programs such as Project Lead the Way, "Science for All Americans", Benchmarks 2061 , etc. In addition, with respect to spacecraft development, we have a growing need for young to mid-level engineers with appropriate experience and skills in spacecraft design, development, analysis, testing, and systems engineering. As the Director of Engineering at NASA's Johnson Space Center, I realized that sustaining engineering support of an operational human spacecraft such as the Space Shuttle is decidedly different than engineering design and development skills necessary for designing a new spacecraft such as the Crew Exploration Vehicle of the Constellation Program. We learned a very important lesson post Columbia in that the Space Shuttle is truly an experimental and not an operational vehicle and the strict adherence to developed rules and processes and chains of command of an inherently bureaucratic organizational structure will not protect us from a host of known unknowns let alone unknown unknowns. There are no strict rules, processes, or procedures for understanding anomalous results of an experiment, anomalies with an experimental spacecraft like Shuttle, or in the conceptual design of a spacecraft. Engineering design is as much an art as it is a science. The critical thinking skills necessary to uncover lurking problems in an experimental design and creatively develop solutions are some of the same skills necessary to design a new spacecraft. Thus, I believe engineers unfamiliar with or removed from design and development need time to transition and develop the required skill set to be effective spacecraft designers. I believe the creative process necessary in design can be enhanced and even taught as early as grades K-12 and should continue to be nurtured and developed at the university level and beyond. I am going to present a strategy for developing learning teams to address complex multidisciplinary problems and to creatively develop solutions to those problems rapidly at minimal cost. I will frame a real problem, the development of on-orbit thermal protection system repair of the Space Shuttle, and step through the series of skills necessary to enhance the creative process. The case study I will illustrate is based on a real project, the R&D Reinforced Carbon-Carbon (RCC) Repair Team's development of on-orbit repair concepts for damaged Space Shuttle RCC nose cap and/or leading edges.
Camarda, Charles J.↗
Parametric analysis of performance and design characteristics for advanced earth-to-orbit shuttles
Performance, trajectory, and design characteristics are presented for (1) a single-stage shuttle with a single advanced rocket engine, (2) a single-stage shuttle with an initial parallel chemical engine and advanced engine burn followed by an advanced engine sustainer burn, (3) a single-stage shuttle with an initial chemical engine burn followed by an advanced engine burn, and (4) a two-stage shuttle with a chemical propulsion booster stage and an advanced propulsion upper stage. The ascent trajectory profile includes a brief initial vertical rise; zero-lift flight through the sensible atmosphere; variational steering into an 83-kilometer by 185-kilometer intermediate orbit; and a fixed, 460-meter per second allowance for subsequent maneuvers. Results are given in terms of burnout mass fractions (including structure and payload), trajectory profiles, propellant loadings, and burn times. These results are generated with a trajectory analysis that includes a parametric variation of the specific impulse from 800 to 3000 seconds and the specific engine weight from 0 to 1.0.
Willis, E. A., Jr.↗
Delivering Contextual Knowledge and Critical Skills of Disruptive Technologies through Problem-Based Learning in Research Experiences for Undergraduates Setting
The recent development in transportation, such as energy-efficient and autonomous vehicles, defines a condition for the students in transportation engineering. Students in the field of transportation engineering should be ready upon their graduation with new knowledge and skills that are compatible with the need of the industry and sustainable engineering practices.During summers of 2018 and 2019, we developed and implemented an eight-week program to increase the knowledge and skills of students coming from multidisciplinary fields related to autonomous vehicles. Problem of “How much will platooning reduce fuel consumption and emissions per vehicle mile traveled?” was instrumentalized in subsequent activities to introduce the comprehensive knowledge structure of autonomous vehicles.The engineering concept of reducing the cost and sustainability was embedded in the leading research question that helped us to develop and implement activities on an overall knowledge structure in autonomous vehicles. The goal of using problem-based learning activities was not to encourage the students to focus on reaching the solution merely. We aimed to introduce the multidisciplinary knowledge and critical skills aspects of learning about disruptive technologies.In this paper, we will discuss how a multidisciplinary research approach was incorporated into a problem-based learning activity. The students were introduced the subjects related to math, physics, computer science, and biology as the integration of the knowledge structure of autonomous vehicles. We will also present the results on students’ use of critical skills such as machine learning and computer programming.
Comert, Gurcan↗
Use of Soft Computing Technologies for a Qualitative and Reliable Engine Control System for Propulsion Systems
The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to improve overall vehicle system safety, reliability, and rocket engine performance by development of a qualitative and reliable engine control system (QRECS). Specifically, this will be addressed by enhancing rocket engine control using SCT, innovative data mining tools, and sound software engineering practices used in Marshall's Flight Software Group (FSG). The principle goals for addressing the issue of quality are to improve software management, software development time, software maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control methodologies, but to provide alternative design choices for control, implementation, performance, and sustaining engineering, all relative to addressing the issue of reliability. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion (system level), software engineering for embedded flight software systems, and soft computing technologies (i.e., neural networks, fuzzy logic, data mining, and Bayesian belief networks); some of which are briefed in this paper. For this effort, the targeted demonstration rocket engine testbed is the MC-1 engine (formerly FASTRAC) which is simulated with hardware and software in the Marshall Avionics & Software Testbed (MAST) laboratory that currently resides at NASA's Marshall Space Flight Center, building 4476, and is managed by the Avionics Department. A brief plan of action for design, development, implementation, and testing a Phase One effort for QRECS is given, along with expected results. Phase One will focus on development of a Smart Start Engine Module and a Mainstage Engine Module for proper engine start and mainstage engine operations. The overall intent is to demonstrate that by employing soft computing technologies, the quality and reliability of the overall scheme to engine controller development is further improved and vehicle safety is further insured. The final product that this paper proposes is an approach to development of an alternative low cost engine controller that would be capable of performing in unique vision spacecraft vehicles requiring low cost advanced avionics architectures for autonomous operations from engine pre-start to engine shutdown.
Trevino, Luis↗
The sum is greater than the parts: exploiting microbial communities to achieve complex functions
We report multi-species microbial communities are ubiquitous in nature. The widespread prevalence of these communities is due to highly elaborated interactions among their members thereby accomplishing metabolic functions that are unattainable by individual members alone. Harnessing these communal capabilities is an emerging field in biotechnology. The rational intervention of microbial communities for the purpose of improved function has been facilitated in part by developments in multi-omics approaches, synthetic biology, and computational methods. Recent studies have demonstrated the benefits of rational interventions to human and animal health as well as agricultural productivity. Emergent technologies, such as in situ modification of complex microbial community and community metabolic modeling, represent an avenue to engineer sustainable microbial communities. In this opinion, we review relevant computational and experimental approaches to study and engineer microbial communities and discuss their potential for biotechnological applications.
59 BASIC BIOLOGICAL SCIENCES↗
Trajectory description
The Mariner 9 spacecraft was launched by an Atlas/Centaur launch vehicle (AC-23) on a direct-ascent trajectory from the Air Force Eastern Test Range (AFETR) launch complex 36B on May 30, 1971. Liftoff occurred at 22 h 23 min 04.5 s GMT, slightly more than 6 min after the opening of a 60-min launch window. The vehicle rose vertically for approximately 15 s, during which time, a programmed roll to a launch azimuth of 92.74 deg was performed. After the initial vertical rise, the vehicle, guided by the open-loop Atlas autopilot, began to pitch over into a zero-lift trajectory. The first of three main powered phases was terminated by booster engine cutoff (BECO) at 22 h 25 min 35.5 s. After the Atlas booster engine package was jettisoned 3 s later, the flight continued under the power of the Atlas sustainer engine and guided by the Centaur guidance system operating in a closed-loop mode.
Webb, W. A.↗
Use of Soft Computing Technologies For Rocket Engine Control
The problem to be addressed in this paper is to explore how the use of Soft Computing Technologies (SCT) could be employed to further improve overall engine system reliability and performance. Specifically, this will be presented by enhancing rocket engine control and engine health management (EHM) using SCT coupled with conventional control technologies, and sound software engineering practices used in Marshall s Flight Software Group. The principle goals are to improve software management, software development time and maintenance, processor execution, fault tolerance and mitigation, and nonlinear control in power level transitions. The intent is not to discuss any shortcomings of existing engine control and EHM methodologies, but to provide alternative design choices for control, EHM, implementation, performance, and sustaining engineering. The approaches outlined in this paper will require knowledge in the fields of rocket engine propulsion, software engineering for embedded systems, and soft computing technologies (i.e., neural networks, fuzzy logic, and Bayesian belief networks), much of which is presented in this paper. The first targeted demonstration rocket engine platform is the MC-1 (formerly FASTRAC Engine) which is simulated with hardware and software in the Marshall Avionics & Software Testbed laboratory that
Trevino, Luis C.↗
Marshall Space Flight Center Ground Systems Development and Integration
Ground Systems Development and Integration performs a variety of tasks in support of the Mission Operations Laboratory (MOL) and other Center and Agency projects. These tasks include various systems engineering processes such as performing system requirements development, system architecture design, integration, verification and validation, software development, and sustaining engineering of mission operations systems that has evolved the Huntsville Operations Support Center (HOSC) into a leader in remote operations for current and future NASA space projects. The group is also responsible for developing and managing telemetry and command configuration and calibration databases. Personnel are responsible for maintaining and enhancing their disciplinary skills in the areas of project management, software engineering, software development, software process improvement, telecommunications, networking, and systems management. Domain expertise in the ground systems area is also maintained and includes detailed proficiency in the areas of real-time telemetry systems, command systems, voice, video, data networks, and mission planning systems.
Wade, Gina↗
Integrating International Engineering Organizations For Successful ISS Operations
The International Space Station (ISS) is a multinational orbiting space laboratory that is built in cooperation with 16 nations. The design and sustaining engineering expertise is spread worldwide. As the number of Partners with orbiting elements on the ISS grows, the challenge NASA is facing as the ISS integrator is to ensure that engineering expertise and data are accessible in a timely fashion to ensure ongoing operations and mission success. Integrating international engineering teams requires definition and agreement on common processes and responsibilities, joint training and the emergence of a unique engineering team culture. ISS engineers face daunting logistical and political challenges regarding data sharing requirements. To assure systematic information sharing and anomaly resolution of integrated anomalies, the ISS Partners are developing multi-lateral engineering interface procedures. Data sharing and individual responsibility are key aspects of this plan. This paper describes several examples of successful multilateral anomaly resolution. These successes were used to form the framework of the Partner to Partner engineering interface procedures, and this paper describes those currently documented multilateral engineering processes. Furthermore, it addresses the challenges experienced to date, and the forward work expected in establishing a successful working relationship with Partners as their hardware is launched.
Blome, Elizabeth↗
NASA software documentation standard software engineering program
The NASA Software Documentation Standard (hereinafter referred to as Standard) can be applied to the documentation of all NASA software. This Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. This basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.
Source record↗
NASA Software Documentation Standard
The NASA Software Documentation Standard (hereinafter referred to as "Standard") is designed to support the documentation of all software developed for NASA; its goal is to provide a framework and model for recording the essential information needed throughout the development life cycle and maintenance of a software system. The NASA Software Documentation Standard can be applied to the documentation of all NASA software. The Standard is limited to documentation format and content requirements. It does not mandate specific management, engineering, or assurance standards or techniques. This Standard defines the format and content of documentation for software acquisition, development, and sustaining engineering. Format requirements address where information shall be recorded and content requirements address what information shall be recorded. This Standard provides a framework to allow consistency of documentation across NASA and visibility into the completeness of project documentation. The basic framework consists of four major sections (or volumes). The Management Plan contains all planning and business aspects of a software project, including engineering and assurance planning. The Product Specification contains all technical engineering information, including software requirements and design. The Assurance and Test Procedures contains all technical assurance information, including Test, Quality Assurance (QA), and Verification and Validation (V&V). The Management, Engineering, and Assurance Reports is the library and/or listing of all project reports.
Source record↗