SEARCH · Search NASA
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.
Propulsion system performance is computed during engine sizing and whenver aircraft performance is computed. The propulsion model user's and programmer's manual is presented. Routines are provided for jet and propeller driven aircraft.
The desire to integrate newly available, graphically-oriented Computed Aided Software Engineering (CASE) tools with existing software design approaches is changing the way Program Design Language (PDL) or Process Description Language is used for large system development. In the approach documented here, Software Engineers use graphics tools to model the problem and to describe high level software design in diagrams. An Ada-based PDL is used to document low level design. Some results are provided along with an analysis for each of three smaller General Electric (GE) Ada development projects that utilized variations on this approach. Finally some considerations are identified for larger scale implementation.
The design, development, and implementation of a prototype expert system which could aid designers and system engineers in the placement of racks aboard modules on the Space Station Freedom are described. This type of problem is relevant to any program with multiple constraints and requirements demanding solutions which minimize usage of limited resources. This process is generally performed by a single, highly experienced engineer who integrates all the diverse mission requirements and limitations, and develops an overall technical solution which meets program and system requirements with minimal cost, weight, volume, power, etc. This system architect performs an intellectual integration process in which the underlying design rationale is often not fully documented. This is a situation which lends itself to an expert system solution for enhanced consistency, thoroughness, documentation, and change assessment capabilities.
This NASA Aerospace Flight Battery Systems Working Group was chartered within the NASA Engineering and Safety Center (NESC). The Battery Working Group was tasked to complete tasks and to propose proactive work to address battery related, agency-wide issues on an annual basis. In its first year of operation, this proactive program addressed various aspects of the validation and verification of aerospace battery systems for NASA missions. Studies were performed, issues were discussed and in many cases, test programs were executed to generate recommendations and guidelines to reduce risk associated with various aspects of implementing battery technology in the aerospace industry. This document contains Part 2 - Volume I: Recommendations for Technical Requirements for Inclusion in Aerospace Battery Procurements of the program's operations.
This NASA Aerospace Flight Battery Systems Working Group was chartered within the NASA Engineering and Safety Center (NESC). The Battery Working Group was tasked to complete tasks and to propose proactive work to address battery related, agency-wide issues on an annual basis. In its first year of operation, this proactive program addressed various aspects of the validation and verification of aerospace battery systems for NASA missions. Studies were performed, issues were discussed and in many cases, test programs were executed to generate recommendations and guidelines to reduce risk associated with various aspects of implementing battery technology in the aerospace industry. This document contains Part 3 - Volume I: Wet Life of Nickel-Hydrogen (Ni-H2) Batteries of the program's operations.
This NASA Aerospace Flight Battery Systems Working Group was chartered within the NASA Engineering and Safety Center (NESC). The Battery Working Group was tasked to complete tasks and to propose proactive work to address battery related, agency-wide issues on an annual basis. In its first year of operation, this proactive program addressed various aspects of the validation and verification of aerospace battery systems for NASA missions. Studies were performed, issues were discussed and in many cases, test programs were executed to generate recommendations and guidelines to reduce risk associated with various aspects of implementing battery technology in the aerospace industry. This document contains Part 2 - Volume II Appendix A to Part 2 - Volume I.
As Ada solidified in its development, it became evident that it offered advantages for avionics systems because of it support for modern software engineering principles and real time applications. An Ada programming support environment was developed for two major avionics subsystems in the Beech Starship. The two subsystems include electronic flight instrument displays and the flight management computer system. Both of these systems use multiple Intel 80186 microprocessors. The flight management computer provides flight planning, navigation displays, primary flight display of checklists and other pilot advisory information. Together these systems represent nearly 80,000 lines of Ada source code and to date approximately 30 man years of effort. The Beech Starship avionics systems are in flight testing.
This paper documents the effort conducted to collect hot-tire dynamic and acoustics environments data during 50,000-lb thrust lox-ethanol hot-fire rocket testing at NASA Marshall Space Flight Center (MSFC) in November-December 2003. This test program was conducted during development testing of the Boeing Rocketdyne RS-88 development engine thrust chamber assembly (TCA) in support of the Orbital Space Plane (OSP) Crew Escape System Propulsion (CESP) Program Pad Abort Demonstrator (PAD). In addition to numerous internal TCA and nozzle measurements, induced acoustics environments data were also collected. Provided here is an overview of test parameters, a discussion of the measurements, test facility systems and test operations, and a quality assessment of the data collected during this test program.
Over the years, computer modeling has been used extensively in many disciplines to solve engineering problems. A set of computer program tools is proposed to assist the engineer in the various phases of the Space Station program from technology selection through flight operations. The development and application of emulation and simulation transient performance modeling tools for life support systems are examined. The results of the development and the demonstration of the utility of three computer models are presented. The first model is a detailed computer model (emulation) of a solid amine water desorbed (SAWD) CO2 removal subsystem combined with much less detailed models (simulations) of a cabin, crew, and heat exchangers. This model was used in parallel with the hardware design and test of this CO2 removal subsystem. The second model is a simulation of an air revitalization system combined with a wastewater processing system to demonstrate the capabilities to study subsystem integration. The third model is that of a Space Station total air revitalization system. The station configuration consists of a habitat module, a lab module, two crews, and four connecting nodes.
Very early in the Space Launch Initiative program, a small team of engineers at MSFC proposed a process for performing system-level assessments of a launch vehicle. Aimed primarily at providing insight and making NASA a smart buyer, the Vehicle Integrated Performance Analysis (VIPA) team was created. The difference between the VIPA effort and previous integration attempts is that VIPA a process using experienced people from various disciplines, which focuses them on a technically integrated assessment. The foundations of VIPA s process are described. The VIPA team also recognized the need to target early detailed analysis toward identifying significant systems issues. This process is driven by the T-model for technical integration. VIPA s approach to performing system-level technical integration is discussed in detail. The VIPA process significantly enhances the development and monitoring of realizable project requirements. VIPA s assessment validates the concept s stated performance, identifies significant issues either with the concept or the requirements, and then reintegrates these issues to determine impacts. This process is discussed along with a description of how it may be integrated into a program s insight and review process. The VIPA process has gained favor with both engineering and project organizations for being responsive and insightful
The main contribution of the effort in the last two years is the introduction of the MOPPS system. After doing extensive literature search, we introduced the system which is described next. MOPPS employs a new solution to the problem of managing programs which solve scientific and engineering applications on a distributed processing environment. Autonomous computers cooperate efficiently in solving large scientific problems with this solution. MOPPS has the advantage of not assuming the presence of any particular network topology or configuration, computer architecture, or operating system. It imposes little overhead on network and processor resources while efficiently managing programs concurrently. The core of MOPPS is an intelligent program manager that builds a knowledge base of the execution performance of the parallel programs it is managing under various conditions. The manager applies this knowledge to improve the performance of future runs. The program manager learns from experience.
The purpose of the STME Main Injector Program was to enhance the technology base for the large-scale main injector-combustor system of oxygen-hydrogen booster engines in the areas of combustion efficiency, chamber heating rates, and combustion stability. The initial task of the Main Injector Program, focused on analysis and theoretical predictions using existing models, was complemented by the design, fabrication, and test at MSFC of a subscale calorimetric, 40,000-pound thrust class, axisymmetric thrust chamber operating at approximately 2,250 psi and a 7:1 expansion ratio. Test results were used to further define combustion stability bounds, combustion efficiency, and heating rates using a large injector scale similar to the Pratt & Whitney (P&W) STME main injector design configuration including the tangential entry swirl coaxial injection elements. The subscale combustion data was used to verify and refine analytical modeling simulation and extend the database range to guide the design of the large-scale system main injector. The subscale injector design incorporated fuel and oxidizer flow area control features which could be varied; this allowed testing of several design points so that the STME conditions could be bracketed. The subscale injector design also incorporated high-reliability and low-cost fabrication techniques such as a one-piece electrical discharged machined (EDMed) interpropellant plate. Both subscale and large-scale injectors incorporated outer row injector elements with scarfed tip features to allow evaluation of reduced heating rates to the combustion chamber.
A description of the CELCAP cogeneration analysis program is presented. A detailed description of the methodology used by the Naval Civil Engineering Laboratory in developing the CELCAP code and the procedures for analyzing cogeneration systems for a given user are given. The four engines modeled in CELCAP are: gas turbine with exhaust heat boiler, diesel engine with waste heat boiler, single automatic-extraction steam turbine, and back-pressure steam turbine. Both the design point and part-load performances are taken into account in the engine models. The load model describes how the hourly electric and steam demand of the user is represented by 24 hourly profiles. The economic model describes how the annual and life-cycle operating costs that include the costs of fuel, purchased electricity, and operation and maintenance of engines and boilers are calculated. The CELCAP code structure and principal functions of the code are described to how the various components of the code are related to each other. Three examples of the application of the CELCAP code are given to illustrate the versatility of the code. The examples shown represent cases of system selection, system modification, and system optimization.
The NASA Engineering and Safety Center (NESC) is an independent engineering analysis and test organization providing support across the range of NASA programs. In 2007 NASA was developing the launch escape system for the Orion spacecraft that was evolved from the traditional tower-configuration escape systems used for the historic Mercury and Apollo spacecraft. The NESC was tasked, as a programmatic risk-reduction effort to develop and flight test an alternative to the Orion baseline escape system concept. This project became known as the Max Launch Abort System (MLAS), named in honor of Maxime Faget, the developer of the original Mercury escape system. Over the course of approximately two years the NESC performed conceptual and tradeoff analyses, designed and built full-scale flight test hardware, and conducted a flight test demonstration in July 2009. Since the flight test, the NESC has continued to further develop and refine the MLAS concept.
The fusion energy conversion design approach, the Field Reversed Configuration (FRC) - when burning deuterium and helium-3, offers a new method and concept for space transportation with high energy demanding programs, like the Manned Mars Mission and planetary science outpost missions require. FRC's will increase safety, reduce costs, and enable new missions by providing a high specific power propulsion system from a high performance fusion engine system that can be optimally designed. By using spacecraft powered by FRC's the space program can fulfill High Energy Space Missions (HESM) in a manner not otherwise possible. FRC's can potentially enable the attainment of high payload mass fractions while doing so within shorter flight times.
This report documents the study of the Radioisotope Thermoelectric Generator Transport System (RTGTS) chillers capability to transport a Radioisotope Power System (RPS) with low heat loads in the cask. Tests of the RTGTS chillers included setting the glycol/water (coolant) temperature to a control set point of 40° and 60°F while applying heat loads ranging from 2500 to 0 W heat load. The tests performed showed that the chiller systems could handle the entire range of heat loads. However, a noise/vibration started to occur when the set point was 60°F with low heat loads. Three recommended changes to the RTGTS chillers are recommended with varying implementation windows. The first is an operational change that can be implemented immediately. The RTGTS chillers should have a set point of 40°F when transporting an RPS less than 1500 W. The second is a short-term change (within the next two years) augmenting RPS heat by utilizing one RTGTS onboard heater (2500 W) while transporting an RPS with less than 1500 W which will also require a change to the Instrument and Data Acquisition System (IDAS) to allow monitoring and possible control of power to the onboard heaters. However, if the heater does fail during transport, no emergency actions or immediate repairs will be required due to the chillers’ ability to handle low heat loads. Running a 2500 W heater when transporting low heat loads aids in prolonging the life of the chillers. The remaining recommended long-term change is to replace the current chillers with a new portable or permanently installed chiller system in the next five to ten years. This time frame takes advantage of the proven reliability and durability of the current chillers while the new chillers are phased in and proven to the RPS program.
Until recently, the design of jet engines for quiet operation was limited by engineers' ability to predict the jet noise generated by a nozzle exhaust system. More importantly, the 'intermediate steps' between nozzle design and noise had not been understood, limiting the design process to small variations around existing solutions. In recent years NASA's Quiet Aircraft Technology (QAT) Program has advanced the understanding and modeling of jet noise to give engineers the tools they need to design quiet nozzle systems for subsonic exhaust systems. The presentation discusses the approach followed for QAT and argues that a similar effort aimed at supersonic jet exhaust systems will be needed to allow designs of quiet military aircraft in the future.
NASA leads the world in space research and provides other government agencies, educational institutions, and companies opportunities to explore, launch, and conduct research in and around space. NASA has 11 formal locations based around the United States, and each has different goals and objectives to help NASA meet its overall mission. 2004, President George Bush announced a new vision for the Space Exploration program. During his grand announcement, he discussed that the Space Shuttles would retire due to the 2003 Space Shuttle Columbia accident, where the crew and the space vehicle were lost. The Kennedy Space Center (KSC) would no longer manage the day-to-day operations of maintaining the US Space Shuttle fleet. Our NASA teams would continue working to finish the Space Shuttle program's mission to build the International Space Station. Afterward, NASA would transition to develop and test a new spacecraft, the Crew Exploration Vehicle. The third goal was to return to the moon by 2020 as the launching point for missions beyond, to get humans from lower Earth orbit to the moon and Mars. (Secretary, 2004) The KSC engineering workforce had to prepare to transition from Operational support of the Space Shuttle program to the design and development of over 50 subsystems for the future SLS and Orion Launch Systems at the Kennedy Space Center. These subsystems developed at the Kennedy Space Center Engineering Directorate followed a comprehensive design process that required several different product deliverables during various phases for each subsystem. (Schafer et al., 2013) What allowed these systems to be successful? What enabled NASA KSC to complete over 130 Artemis 1 Design Certification and System Acceptance Reviews, closing over 21,656 Requirements to deem the Artemis 1 rocket ready for launch? Little is known about the NASA engineering workforce agility characteristics that enabled the organization to transition from the Space Shuttle program that ended in 2011 and launch the Artemis Program's SLS rocket on November 16, 2022.