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.
Hank Rotter, NASA Technical Fellow for Environmental Control and Life Support System, will provide the causes and lessons learned for the two Space Shuttle Orbiter water dump icicles that formed on the side of the Orbiter. He will present the root causes and the criticality of these icicles, along with the redesign of the water dump nozzles and lessons learned during the redesign phase.
National research, development, test, and evaluation ground testing capabilities in the United States are at risk. There is a lack of vision and consensus on what is and will be needed, contributing to a significant threat that ground test capabilities may not be able to meet the national security and industrial needs of the future. To support future decisions, the AIAA Ground Testing Technical Committee’s (GTTC) “Future of Ground Test” (FoGT) Working Group selected and reviewed 20 “seminal” documents related to the application and direction of ground testing. Each document was reviewed, with the content main points collected and organized into sections in the form of a gap analysis – current state, future state, major challenges/gaps, and recommendations. This paper includes key findings and selected commentary by an editing team.
It has been over 50 years since the first launch of the Saturn V launch vehicle, Apollo 4, on November 9th,1967. Developed at NASA’s Marshall Space Flight Center (MSFC) in Huntsville, Alabama, the Saturn V was a massive multistage liquid-fuel expendable rocket used by NASA’s Apollo and Skylab programs. It safely flew 24 American astronauts to the Moon, blazing the trail for all American heavy-lift launch vehicles to follow. The Saturn V remains the only launch vehicle to carry humans beyond low Earth orbit. Nearly fifty years after the final May 1973 flight of the Saturn V, an enduring technical legacy of launch vehicle technologies still supports the United States space launch capabilities, particularly with respect to flight dynamics and control. The structured refinement of GN&C technologies during the Saturn program, leveraging the incremental advancements of the Jupiter, Redstone, and Saturn I/IB, systematically reduced risk and resulted in the most advanced and reliable launch vehicle flight control systems to have been developed before the advent of the Space Shuttle.
The purpose of this technical report is to provide current documentation of the Sensor Intercomparison and Merger for Biological and Interdisciplinary Oceanic Studies (SIMBIOS) Project activities, satellite data processing, and data product validation. This documentation is necessary to ensure that critical information is related to the scientific community and NASA management. This critical information includes the technical difficulties and challenges of validating and combining ocean color data from an array of independent satellite systems to form consistent and accurate global bio-optical time series products. This technical report focuses on the SIMBIOS Project s efforts in support of the Moderate-Resolution Imaging Spectroradiometer (MODIS) on the Earth Observing System (EOS) Terra platform (similar evaluations of MODIS/Aqua are underway). This technical report is not meant as a substitute for scientific literature. Instead, it will provide a ready and responsive vehicle for the multitude of technical reports issued by an operational project.
Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community.
This project developed tools to support the future use of Plankton, Aerosol, Cloud, ocean Ecosystem (PACE) hyperspectral imagery in water resource monitoring and research by NASA DEVELOP teams and members of the PACE applications community. We sought to address a need for support in processing and visualizing hyperspectral PACE Ocean Color Instrument (OCI) data among researchers and decision-makers working in coastal water quality management and harmful algal bloom (HAB) monitoring. To supplement the day of simulated PACE imagery available, we used Aqua MODIS earth observations with Level 3 processing from March 2022 to build a Python graphical user interface (GUI) for visualizing ocean biogeochemical parameters relevant to the early detection and monitoring of HABs. We used simulated PACE OCI Level 2 data derived from the Python Top of Atmosphere Simulation Tool (PyTOAST) to build Jupyter Notebooks for band subset and selection. The Level 3 PACE Viewer components support users with quick visualizations as well as the creation of geoTIFFs and time-series. The Level 2 Jupyter Notebooks address users’ concerns over the volume and complexity of hyperspectral imagery. The PACE Viewer is useful for visual inspection and netCDF data processing but should not be used for geospatial analysis. Once PACE launches, this tool will alleviate the technical burdens of working with hyperspectral data and support the early detection and monitoring of HABs using PACE satellite imagery.
In 2000 and 2001 studies were conducted at the NASA Marshall Space Flight Center on the technical requirements and commercial potential for propellant production depots in low Earth orbit (LEO) to support future commercial, NASA, and other Agency missions. Results indicate that propellant production depots appear to be technically feasible given continued technology development, and there is a substantial growing market that depots could support. Systems studies showed that the most expensive part of transferring payloads to geosynchronous orbit (GEO) is the fuel. A cryogenic propellant production and storage depot stationed in LEO could lower the cost of missions to GEO and beyond. Propellant production separates water into hydrogen and oxygen through electrolysis. This process utilizes large amounts of power, therefore a depot derived from advanced space solar power technology was defined. Results indicate that in the coming decades there could be a significant demand for water-based propellants from Earth, moon, or asteroid resources if in-space transfer vehicles (upper stages) transitioned to reusable systems using water based propellants. This type of strategic planning move could create a substantial commercial market for space resources development, and ultimately lead toward significant commercial infrastructure development within the Earth-Moon system.
The Mir Cooperative Solar Array (MCSA) project was a joint US/Russian effort to build a photovoltaic (PV) solar array and deliver it to the Russian space station Mir. The MCSA is currently being used to increase the electrical power on Mir and provide PV array performance data in support of Phase 1 of the International Space Station (ISS), which will use arrays based on the same solar cells used in the MCSA. The US supplied the photovoltaic power modules (PPMs) and provided technical and programmatic oversight while Russia provided the array support structures and deployment mechanism and built and tested the array. In order to ensure that there would be no problems with the interface between US and Russian hardware, an accelerated thermal life cycle test was performed at NASA Lewis Research Center on two representative samples of the MCSA. Over an eight-month period (August 1994 - March 1995), two 15-cell MCSA solar array 'mini' panel test articles were simultaneously put through 24,000 thermal cycles (+80 C to -100 C), equivalent to four years on-orbit. The test objectives, facility, procedure and results are described in this paper. Post-test inspection and evaluation revealed no significant degradation in the structural integrity of the test articles and no electrical degradation, not including one cell damaged early as an artifact of the test and removed from consideration. The interesting nature of the performance degradation caused by this one cell, which only occurred at elevated temperatures, is discussed. As a result of this test, changes were made to improve some aspects of the solar cell coupon-to-support frame interface on the flight unit. It was concluded from the results that the integration of the US solar cell modules with the Russian support structure would be able to withstand at least 24,000 thermal cycles (4 years on-orbit).
Manual assistance of therapists to help movement of legs of spinal cord injured (SCI) subjects during stepping on a treadmill for locomotion rehabilitation has severe economic and technical limitations. Scientists at the Department of Physiological Science at the University of California Los Angeles (UCLA) and roboticists at the Jet Propulsion Laboratory (JPL) initiated a joint effort to develop a robotic mechanism capable of performing controlled motions equivalent to the arm and hand motions of therapists assisting the stepping of locomotion impaired subjects on a treadmill, while the subjects' body weight is partially supported by an overhead harness. A first necessary technical step towards this development is to measure and understand the kinematics and dynamics of the therapists' arm and hand motions as they are reflected on the subjects' leg movement. This paper describes an initial measurement system developed for this purpose together with the related measurement results, and outlines the planned future technical work.
Concerns over accuracy, availability, integrity, and continuity have limited the integration of Global Positioning System (GPS) and Global Navigation Satellite System (GLONASS) for safety-critical applications. More recent augmentation systems, such as the European Geostationary Navigation Overlay Service (EGNOS) and the North American Wide Area Augmentation System (WAAS) have begun to address these concerns. Augmentation architectures build on the existing GPS/GLONASS infrastructures to support location based services in Safety of Life (SoL) applications. Much of the technical development has been directed by air traffic management requirements, in anticipation of the more extensive support to be offered by GPS III and Galileo. WAAS has already been approved to provide vertical guidance for aviation applications. During the next twelve months, the full certification of EGNOS for SoL applications is expected. This paper discusses similarities and differences between the safety assessment techniques used in Europe and North America.
NASA continues to operate all sizes of UAS in all classes of airspace both domestically and internationally. Missions range from highly complex operations in coordination with piloted aircraft, ground, and space systems in support of science objectives to single aircraft operations in support of aeronautics research. One such example is a scaled commercial transport aircraft being used to study recovery techniques due to large upsets. NASA's efforts to support routine UAS operations continued on several fronts last year. At the national level in the United States (U.S.), NASA continued its support of the UAS Executive Committee (ExCom) comprised of the Federal Aviation Administration (FAA), Department of Defense (DoD), Department of Homeland Security (DHS), and NASA. The committee was formed in recognition of the need of UAS operated by these agencies to access to the National Airspace System (NAS) to support operational, training, development and research requirements. Recommendations were received on how to operate both manned and unmanned aircraft in class D airspace and plans are being developed to validate and implement those recommendations. In addition the UAS ExCom has begun developing recommendations for how to achieve routine operations in remote areas as well as for small UAS operations in class G airspace. As well as supporting the UAS ExCom, NASA is a participant in the recently formed Aviation Rule Making Committee for UAS. This committee, established by the FAA, is intended to propose regulatory guidance which would enable routine civil UAS operations. As that effort matures NASA stands ready to supply the necessary technical expertise to help that committee achieve its objectives. By supporting both the UAS ExCom and UAS ARC, NASA is positioned to provide its technical expertise across the full spectrum of UAS airspace access related topic areas. The UAS NAS Access Project got underway this past year under the leadership of NASA s Aeronautics Research Mission Directorate. This project is focused on advancing the state of the art and providing research and analysis results in the areas of Separation Assurance, Communications (non-governmental spectrum allocation for UAS), Certification, and Human System Integration (ground control station design/pilot interfaces). The project is working in close coordination with the FAA and industry standards organizations (e.g. RTCA SC 203). More details on this project are provided in a separate article in this year's yearbook
Engineering metrics are useful in space life support technology selection, but they must be carefully used. Metrics are only part of a complete system trade-off. Metrics do harm if they cause neglect of other important technical, organizational, or intuitive decision factors. Two metrics have damaged space life support, closure and Equivalent Systems Mass (ESM). Closure measures the fraction of the required system inputs that are produced by recycling system outputs. Increasing closure produces diminishing returns and becomes increasingly expensive. Increasing closure does not directly contribute to providing better life support. ESM measures the total launch mass required to provide life support. ESM includes the mass of the system hardware and of its power, cooling, pressurized volume, spares, and logistics. ESM predicts launch costs, but recently launch costs have been reduced by a factor of 20 or more. System development cost for space hardware is often much greater than launch cost. The past nearly exclusive use of ESM has led to the neglect of Life Cycle Cost (LCC), reliability, cost, and the other engineering factors. Closure and ESM have misguided space life support technology selection for more than twenty years and have adversely affected the expenditure of 100’s of millions of dollars. Metrics can be effectively used three ways in space life support technology selection: 1. A small set of key engineering metrics for preliminary screening. 2. A full set of engineering to guide technical selection. 3. Combining engineering metrics with organizational, political, and intuitive decision factors to understand technology selection. The past emphasis on closure and ESM served to support recycling life support over resupply and built on the intuitive appeal of a human ecosystem in space.
Engineering metrics are useful in space life support technology selection, but they must be carefully used. Metrics are only part of a complete system trade-off. Metrics do harm if they cause neglect of other important technical, organizational, or intuitive decision factors. Two metrics have damaged space life support, closure and Equivalent Systems Mass (ESM). Closure measures the fraction of the required system inputs that are produced by recycling system outputs. Increasing closure produces diminishing returns and becomes increasingly expensive. Increasing closure does not directly contribute to providing better life support. ESM measures the total launch mass required to provide life support. ESM includes the mass of the system hardware and of its power, cooling, pressurized volume, spares, and logistics. ESM predicts launch costs, but recently launch costs have been reduced by a factor of 20 or more. System development cost for space hardware is often much greater than launch cost. The past nearly exclusive use of ESM has led to the neglect of Life Cycle Cost (LCC), reliability, cost, and the other engineering factors. Closure and ESM have misguided space life support technology selection for more than twenty years and have adversely affected the expenditure of 100’s of millions of dollars. Metrics can be effectively used three ways in space life support technology selection: 1. A small set of key engineering metrics for preliminary screening. 2. A full set of engineering to guide technical selection. 3. Combining engineering metrics with organizational, political, and intuitive decision factors to understand technology selection. The past emphasis on closure and ESM served to support recycling life support over resupply and built on the intuitive appeal of a human ecosystem in space.
eddy is a collection of tools - nonlinear solvers, meshing, post-processing, visualization, optimization, etc. - for performing scale-resolving simulations of multi-physics applications. The framework is designed to enable advanced R&D on a variety of topics by leveraging a mature capability for scale resolving simulations, and simultaneously be an appropriate tool for application analysis and support. Currently, eddy is at a relatively low technical readiness level (TRL), and users and developers should maintain appropriate expectations. The technical details behind eddy are outlined in several publications which can be consulted for more information [1–10]. The solvers are built around an unstructured high-order capability, and heavily utilize the tensor product sum-factorization approach for efficiency. The unsteady formulation utilizes a fully implicit space-time approach with a matrix-free Newton- Krylov method. A primitive steady-state solver is available for testing purposes, but is not expected to converge for all but simple verification cases. The Navier-Stokes fluid solvers do not support either RANS or hybrid-RANS capability, only LES and wall-modeled LES approaches. All of the solvers within eddy support three modes of operation: a primal solve of the full nonlinear problem, and two linearization approaches of the primal solve - the ad joint and the tangent solution. Details on how to select and use these three modes are outlined in Sec. 3.
To effectively manage a project, the project manager must have a plan, understand the current conditions, and be able to take action to correct the course when challenges arise. Research and design projects face technical, schedule, and budget challenges that make it difficult to utilize project management tools developed for projects based on previously demonstrated technologies. Projects developing new technologies by their inherent nature are trying something new and thus have little to no data to support estimates for schedule and cost, let alone the technical outcome. Projects with a vision for the outcome but little confidence in the exact tasks to accomplish in order to achieve the vision incur cost and schedule penalties when conceptual solutions require unexpected iterations or even a reinvention of the plan. This presentation will share the project management methodology and tools developed through trial and error for a NASA research and design project combining industry, academia, and NASA inhouse work in which Earned Value Management principles were employed but adapted for the reality of the government financial system and the reality of challenging technology development. The priorities of the presented methodology are flexibility, accountability, and simplicity to give the manager tools to help deliver to the customer while not using up valuable time and resources on extensive planning and analysis. This presentation will share the methodology, tools, and work through failed and successful examples from the three years of process evolution.
Reports on the design process, support of the design process, IPAD System design catalog of IPAD technical program elements, IPAD System development and operation, and IPAD benefits and impact are concisely reviewed. The approach used to define the design is described. Major activities performed during the product development cycle are identified. The computer system requirements necessary to support the design process are given as computational requirements of the host system, technical program elements and system features. The IPAD computer system design is presented as concepts, a functional description and an organizational diagram of its major components. The cost and schedules and a three phase plan for IPAD implementation are presented. The benefits and impact of IPAD technology are discussed.
Computer supported or machine aided indexing (MAI) can be categorized in multiple ways. The system used by the National Aeronautics and Space Administration's (NASA's) Center for AeroSpace Information (CASI) is described as semantic and computational. It's based on the co-occurrence of domain-specific terminology in parts of a sentence, and the probability that an indexer will assign a particular index term when a given word or phrase is encountered in text. The NASA CASI system is run on demand by the indexer and responds in 3 to 9 seconds with a list of suggested, authorized terms. The system was originally based on a syntactic system used in the late 1970's by the Defense Technical Information Center (DTIC). The NASA mainframe-supported system consists of three components: two programs and a knowledge base (KB). The evolution of the system is described and flow charts illustrate the MAI procedures. Tests used to evaluate NASA's MAI system were limited to those that would not slow production. A very early test indicated that MAI saved about 3 minutes and provided several additional terms for each document indexed. It also was determined that time and other resources spent in careful construction of the KB pay off with high-quality output and indexer acceptance of MAI results.
The Constellation program pressure garment subsystem (PGS) team has created a technical roadmap that communicates major technical questions and how and when the questions are being answered in support of major project milestones. The roadmap is a living document that guides the team priorities. The roadmap also communicates technical reactions to changes in project priorities and funding. This paper presents the roadmap and discusses specific roadmap elements in detail as representative examples to provide insight into the meaning and use of the roadmap.