SEARCH · Engineering Papers
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.
Technology development; project management; employment patterns; research productivity; legal status of support services; functions of senior executives; the role of the sponsoring agency; research diversification; obstacles to technical innovation; organizational structures; and personnel management are addressed.
The retrospective presentation provides technical disciplinary focus in the following technical areas: (1) integrated avionics; (2) guidance, navigation, and control; (3) aerodynamics; (4) structures; (5) life support, environmental control, and crew station; (6) ground operations; (7) propulsion and power; (8) communications and tracking; (9) mechanics and mechanical systems; and (10) thermal and contamination environments and protection systems.
This paper presents the technical background for including environmental effects in the design of helicopter composite structures. This effort was supported by test results of components and panels having up to four years of field exposure. The preceeding was part of an eight year program to evaluate in-service environmental factors for comparison with laboratory test results. Full scale static and fatigue tests were conducted on composite components removed from S-76 helicopters used in commercial operations in the Gulf Coast region of Louisiana. Small scale tests were conducted using coupons removed from panels exposed to the outdoor environment in Stratford, Connecticut and West Palm Beach, Florida. Panel configurations were representative of S-76 components. Moisture analysis and strength tests on components and panels are reported after two, three and four years of exposure. Moisture levels were compared with predicted values. Mechanical test results were compared to initial certification tests for component strength, and to baseline laboratory coupon testing.
At the 1979 World Administrative Conference, two new bands were allocated for deep space telecommunications: 31.8 to 32.3 GHz, space-to-Earth, and 34.2 to 34.7 GHz, Earth-to-space. These bands provide opportunity for further development of the Deep Space Network and its support of deep space research. The history of the process by which JPL/NASA developed the rationale, technical background, and statement of requirement for the bands are discussed. Based on this work, United States proposals to the conference included the bands, and subsequent U.S. and NASA participation in the conference led to successful allocations for deep space telecommunications in the 30 GHz region of the spectrum. A detailed description of the allocations is included.
Viewgraphs are presented on the Pathfinder program. Information is given on human exploration of the solar system, technical requirements interfaces, program objectives, space suits, human performance, man-machine systems, space habitats, life support systems, and artificial gravity
Traditional practice of systems engineering management assumes requirements can be precisely determined and unambiguously defined prior to system design and implementation; practice further assumes requirements are held static during implementation. Human-computer decision support systems for service planning and scheduling applications do not conform well to these assumptions. Adaptation to the traditional practice of systems engineering management are required. Basic technology exists to support these adaptations. Additional innovations must be encouraged and nutured. Continued partnership between the programmatic and technical perspective assures proper balance of the impossible with the possible. Past problems have the following origins: not recognizing the unusual and perverse nature of the requirements for planning and scheduling; not recognizing the best starting point assumptions for the design; not understanding the type of system that being built; and not understanding the design consequences of the operations concept selected.
This bibliography lists 205 reports, articles, and other documents introduced into the NASA Scientific and Technical Information System during Aug. 1992. Subject coverage includes the following: aerospace medicine and physiology, life support systems and man/system technology, protective clothing, exobiology and extraterrestrial life, planetary biology, and flight crew behavior and performance.
In this session, we address four fundamental questions related to environmental fields with emphasis on education. These are: What are the goals, objectives, and practical opportunities for coordinating our projects? How can we improve awareness of, interest in, access to, and support the products of our work? How can we build relationships between projects for scientific, educational, technical, and programmatic benefit? How can we evaluate the effectiveness of coordination efforts. In this working session, we produced answers to these questions and proposed a structure for future collaboration.
The NASA Glenn Research Center is developing technologies that utilize solar energy for various space applications including electrical power conversion, thermal propulsion, and furnaces. Common to all of these applications is the need for highly efficient, solar concentration systems. An effort is underway to develop the innovative single crystal refractive secondary concentrator, which uses refraction and total internal reflection to efficiently concentrate and direct solar energy. The refractive secondary offers very high throughput efficiencies (greater than 90%), and when used in combination with advanced primary concentrators, enables very high concentration ratios (10,0(X) to 1) and very high temperatures (greater than 2000 K). Presented is an overview of the refractive secondary concentrator development effort at the NASA Glenn Research Center, including optical design and analysis techniques, thermal modeling capabilities, crystal materials characterization testing, optical coatings evaluation, and component testing. Also presented is a discussion of potential future activity and technical issues yet to be resolved. Much of the work performed to date has been in support of the NASA Marshall Space Flight Center's Solar Thermal Propulsion Program. The many benefits of a refractive secondary concentrator that enable efficient, high temperature thermal propulsion system designs, apply equally well to other solar applications including furnaces and power generation systems such as solar dynamics, concentrated thermal photovoltaics, and thermionics.
This is Volume Four of a set of six reports produced by NASA and other organizations which were provided to the Columbia Accident Investigation Board (CAIB) in support of its inquiry into the February 1, 2003 destruction of the Space Shuttle Columbia. The Technical Documents included in this volume are: Appendix F.1 Water Absorption by Foam; Appendix F.2 Follow the TPS; Appendix F.3 MADS Sensor Data; Appendix F.4 ET Cryoinsulation; Appendix F.5 Space Shuttle STS-107 Columbia Accident Investigation, and External Tank Working Group Final Report - Volume 1.
Under this Cooperative Agreement, the objective was to investigate several emerging sealing technologies of interest to the Mechanical Components Branch of National Aeronautics and Space Administration Glenn Research Center at Lewis Field (NASA GRC). The majority of the work conducted was to support the development of Solid Oxide Fuel Cells for application to aeronautic auxiliary power units, though technical investigations of interest to other groups and projects were also conducted. In general, accomplishments and results were periodically reported to the NASA Technical Monitor, the NASA GRC Seal Team staff, and NASA GRC project management. Several technical reports, journal articles, and presentations were given internally to NASA GRC and to the external public.
The free-piston Stirling power convertor is being considered as an advanced power conversion technology to be used for future NASA deep space missions requiring long life radioisotope power systems. This technology has a conversion efficiency of over 25%, which is significantly higher than the efficiency of the Radioisotope Thermal-electric Generators (RTG) now in use. The NASA Glenn Research Center has long been recognized as a leader in Stirling technology and is responsible for the development of advanced technologies that are intended to significantly improve key characteristics of the Stirling convertor. The advanced technologies identified for development also consider the requirements of potential future missions and the new capabilities that have become available in the associated technical areas. One of the key areas identified for technology development is the engine controller. To support this activity, an advanced controller is being developed for the Stirling power convertor. This controller utilizes active power factor correction electronics and microcontroller-based controls. The object of this paper is to present an overview of the advanced controller concept with modeling, simulation and hardware test data.
Paul Hill, STS-114 Lead Shuttle Flight Director; Mark Ferring, Lead ISS Flight Director; Cindy Begley, STS-114 Lead EVA Officer were present. Paul reported on the general accomplishments of the mission for the day: the transfer to two stations are complete, transfers back from station into logistics module into the mid-deck are about 75 % complete and definitely in schedule to finish the next day, everything with the external video cam and the RGMC return are complete. He noted that all crews are doing great by all means. Paul also gave a detailed explanation with supporting video clips regarding concern for Eileen's side of window. Mark and Cindy both gave technical details on Mission Specialists Steven Robinson and Souichi Noguchi's extravehicular activities (EVA). News media focused most of their questions on extravehicular activities.
The Certification of Propulsion Systems is costly and complex, involving development and qualification testing. The desire of the certification process is to assure all requirements can be demonstrated to be compliant. The purpose of this paper is to address the technical design concerns of certifying a propulsion system for flight. Presented are Pressurization, Tankage, Feed System and Combustion Instability concerns. Propulsion System Engineers are challenged with the dilemma for testing new systems to specific levels to reduce risk yet maintain budgetary targets. A methodical approach is presented to define the types of test suitable to address the technical issues for qualifying systems for retiring the risk levels. Experience of the lessons learned from supporting the Shuttle Program for Main Propulsion and On Orbit Propulsions Systems as well as previous collaborations on design concerns for certifying propulsion systems are utilized to address design concerns and verification approaches.
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the development documents from the GCS project. Volume 2 contains three appendices: A. Guidance and Control Software Development Specification; B. Design Description for the Pluto Implementation of the Guidance and Control Software; and C. Source Code for the Pluto Implementation of the Guidance and Control Software
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the planning documents from the GCS project. Volume 1 contains five appendices: A. Plan for Software Aspects of Certification for the Guidance and Control Software Project; B. Software Development Standards for the Guidance and Control Software Project; C. Software Verification Plan for the Guidance and Control Software Project; D. Software Configuration Management Plan for the Guidance and Control Software Project; and E. Software Quality Assurance Activities.
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes the verification documents from the GCS project. Volume 3 contains four appendices: A. Software Verification Cases and Procedures for the Guidance and Control Software Project; B. Software Verification Results for the Pluto Implementation of the Guidance and Control Software; C. Review Records for the Pluto Implementation of the Guidance and Control Software; and D. Test Results Logs for the Pluto Implementation of the Guidance and Control Software.
The Guidance and Control Software (GCS) project was the last in a series of software reliability studies conducted at Langley Research Center between 1977 and 1994. The technical results of the GCS project were recorded after the experiment was completed. Some of the support documentation produced as part of the experiment, however, is serving an unexpected role far beyond its original project context. Some of the software used as part of the GCS project was developed to conform to the RTCA/DO-178B software standard, "Software Considerations in Airborne Systems and Equipment Certification," used in the civil aviation industry. That standard requires extensive documentation throughout the software development life cycle, including plans, software requirements, design and source code, verification cases and results, and configuration management and quality control data. The project documentation that includes this information is open for public scrutiny without the legal or safety implications associated with comparable data from an avionics manufacturer. This public availability has afforded an opportunity to use the GCS project documents for DO-178B training. This report provides a brief overview of the GCS project, describes the 4-volume set of documents and the role they are playing in training, and includes configuration management and quality assurance documents from the GCS project. Volume 4 contains six appendices: A. Software Accomplishment Summary for the Guidance and Control Software Project; B. Software Configuration Index for the Guidance and Control Software Project; C. Configuration Management Records for the Guidance and Control Software Project; D. Software Quality Assurance Records for the Guidance and Control Software Project; E. Problem Report for the Pluto Implementation of the Guidance and Control Software Project; and F. Support Documentation Change Reports for the Guidance and Control Software Project.