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.
The Urban Air Mobility (UAM) Market Study is an in-depth study for ODM market leveraging identified key technical barriers to understand community interests and market conditions from all aspects such as regulations, economics, public acceptance, airspace operations and safety.
The Urban Air Mobility (UAM) Market Study is an in-depth study for ODM market leveraging identified key technicalbarriers to understand community interests and market conditions from all aspects such as regulations, economics,public acceptance, airspace operations and safety.
RadLab, a new component of the NASA Open Science Data Repository (OSDR), is a platform built upon a database of radiation data relevant to space biology. RadLab provides visual and programmatic interfaces for interrogation of its database, as well as a submission process for inclusion of data from investigators. The RadLab application programming interface (API) implements a request syntax enabling users to retrieve data filtered by various combinations of parameters (detector type, location, direction, timespan, etc), which are delivered in machine-readable text formats, ready to be ingested by downstream analysis pipelines; while the graphical user interface (GUI) provides easy means to iteratively modify query parameters and incorporates a number of standard analyses and visualizations (time series plots, geospatial visualizations, detector comparison). Investigators from many countries, including US, Russia, Japan, Canada, the Czech Republic, Germany, Hungary, and Italy, have committed to provide data from their instruments located on the ISS; RadLab will also include data from other spacecraft in LEO (e.g., the Space Shuttle, the Mir space station), BLEO (e. g. BioSentinel, Mars Orbiter, among others), and on other celestial bodies (e. g. Chang’e 4, Curiosity). The first release of RadLab has been made available to the public. Once fully operational, RadLab will provide a comprehensive and ever-growing compendium of space radiation data, facilitating straightforward access to multiple types of readings and enabling space biology researchers to perform intercomparisons of detectors and to determine the radiation environment of research missions, both via programmatic retrieval of these data and via the graphical analysis toolkit; as well as a user-friendly submission portal for ingesting data from space agencies and research institutions. Radiation scientists will be able to use RadLab to gain a deeper understanding of the space radiation environment for future human space exploration. The RadLab Working Group has been formed to foster close collaborations among data contributors and users, to identify data sources, to put in place standards for data normalization, to guide the development of features of the analysis toolkit, to establish the use of RadLab in space radiation biology research, and eventually to provide a forum for discussing relevant research issues that can take advantage of RadLab's capabilities.
The buildings industry is currently striving to adopt green solutions to make infrastructure more energy-efficient in order to meet the 2050 net-zero climate goals. This planning requires reliable environmental datasets that are crucial in designing, building, and maintaining our world’s-built environment, as well as other energy-related processes and investments. This webinar for the National Institute of Building Sciences provides an overview of NASA’s Prediction Of Worldwide Energy Resources (POWER) Project that informs decision-making and development for sustainable building design and operations by enabling public open discovery, efficient access, and convenient distribution of NASA’s Earth Observations and global atmospheric model datasets. POWER’s datastore is comprised of solar radiation and surface meteorology parameters, spanning nearly 40 years of hourly data, that are easily accessible via several access methods and tools to support three focus areas: 1) renewable energy deployment and management, 2) sustainable infrastructure, and 3) agroclimatology applications. POWER and NASA Earth Science both plan future data parameters, updated tools, and improved observations that could directly support U.S. and international sustainable development goals, climate strategies, and building information modeling. To this end, solar data from several NASA projects and meteorological data from NASA assimilation models have already been reformatted and disseminated to the public via a user-friendly web GIS-enabled based data portal through the POWER Project. POWER data is analysis-ready and accessible through an Application Programming Interface (API), ArcGIS Image Services, and the project’s Data Access Viewer enhanced (DAVe), an interactive online tool. The POWER DAVe also features data consistent with ASHRAE Climate Design Conditions and has developed web image services showing Building Climate Zones and their variability. Through those tools, the data can be downloaded into multiple formats that support the infrastructure community, including CSV and Energy Plus Weather (EPW). POWER’s entire data product catalog is available through Amazon Web Services (AWS) Open Data Registry (ODR) via a free and publicly accessible Simple Storage Service (S3). This webinar provides a full overview of the NASA POWER Project's data and services developed in collaboration with the sustainable infrastructure community. Examples of how the renewable energy and building communities have utilized POWER data products to make decisions and a preview of future data product expansion, including climate projections, and web services will also be provided. Additionally, use case stories from our broad community of users will be presented.
Jessica Rye from NASA Public Affairs is the narrator for the tanking operations for the launch of the Space Shuttle Discovery. She presents a video of the arrival and processing of the new external tank at the Kennedy Space Center. The external tank is also shown entering the Vehicle Assembly Building (VAB). The external tank underwent new processing resulting from its redesign including inspection of the bipod heater and the external separation camera. The changes to the external tank include: 1) Electric heaters to protect from icing; and 2) Liquid Oxygen feed line bellows to carry fuel from the external tank to the Orbiter. Footage of the external tank processing facility at NASA's Michoud Assembly Facility in New Orleans, La. prior to its arrival at Kennedy Space Center is shown and a video of the three key modifications to the external tank including the bipod, flange and bellows are shown.
The interrelationship of urban helicopter operations, helicopter noise, and the establishment of urban public-use heliports is discussed. Public resistance to urban helicopter operations due to concern for safety and noise is shown to negatively impact the establishment of public-use heliports in urban centers. It is indicated that increased government and industry effort to reduce helicopter noise is needed to ensure continued growth in the helicopter industry.
Need, facility requirements, operational problems, and biomedical and physiological aspects associated with certification of simulated space environmental chambers for human occupancy
This publication reports on developments in programs managed by JPL's office of Telecommunications and Data Acquisition (TDA). In space communications, radio navigation, radio science, and ground based radio astronomy, it reports on activities of the Deep Space Network (DSN) and its associated Ground Communications Facility (GCF) in planning, in supporting research and technology, in implementation and in operations. In geodynamics, the publication reports on the application of radio interferometry at microwave frequencies for geodynamic measurements. This publication also reports on implementation and operations for searching the microwave spectrum.
With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.
With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.
With a voice command or a few taps on the console, the spacecraft pivots on a dime at high velocity and gently docks to an orbiting space platform. This is the image most people have of the complex software computations and integrated hardware performance necessary for a spacecraft to successfully perform an automated launch, rendezvous, and docking. Today’s reality is that while computer operations are advancing rapidly, science fiction over-simplifies and over-sells current capabilities. This paper discusses the integration of spacecraft computer automation into the operation of one of the United States’ new Commercial Crew vehicles - the Boeing CST-100 Starliner. Lessons learned by the Boeing Mission Operations team, a private-public partnership with NASA, from conceptual design through real-time operation of the first test flight will be discussed. Focus will center on how operations has learned to use the automated software to their advantage while also knowing how to adjust the automation in response to spacecraft or mission anomalies. One goal of advanced spacecraft automation is the ability to reduce both the crew workload and the ground control footprint while at the same time increasing spacecraft and mission flexibility. Historically, crewed spacecraft required a large number of operators on the ground to use a plethora of tools to compute nominal and contingency mission trajectories. Moving those sophisticated software tools to being onboard the vehicle can reduce the need for such complex ground support. Given that today’s spacecraft software is not yet as capable or as flexible in all circumstances as the computers depicted in movies, there is usually a trade-off between software automation cost and the flexibility of that software resulting in a trade-off between what is performed on the spacecraft and what is left to onboard crew or ground control. For missions that go beyond the Moon, software that autonomously controls nearly every aspect of a crewed mission will become a necessity given the long time delays between the spacecraft and Earth’s ground control teams. The lessons learned by Boeing and its Mission Operations team, through the design and implementation of Starliner’s hardware and software automation, will be able to inform future public and private spacecraft design. As the technologies and capabilities evolve, incorporating lessons learned in successful low Earth orbit commercial crew vehicle missions, spacecraft designs will continue to improve and be able to better enable safe execution of human missions to the Moon and beyond.
Developments in programs in telecommunication and data acquisition in space communications, radio navigation, radio science, and ground based radio astronomy are reported. Activities of the deep space network (DSN) and its associated ground communication facility (GCF) in planning, supporting research and technology, implementation, and in operations are outlined. The publication of reports on the application of radio interferometry at microwave frequencies for geodynamic measurements are presented. Implementation and operation for searching the microwave spectrum is reported.
Standard operating procedures, utilizing remote sensing, are outlined for public health assistance during natural disaster relief operations. A manual to aid decision making for public health authorities is included. Flow charts which show the procedures that need to be implemented during a natural disaster are also included. Emphasis is placed on a preventive approach to the effects of disasters, and specifically to post-disaster problems that relate to public health concerns during the emergency phase of relief.
Presentation to inform the non-NASA general public of ground systems development and operations activities at Kennedy Space Center, particularly on what GSDO is and does, in a high level overview.
Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.
Ares I-X was the first test flight of NASA's Constellation Program's Ares I Crew Launch Vehicle designed to provide manned access to low Earth orbit. As a one-time test flight, the Air Force's 45th Space Wing required a series of Range Safety analysis data products to be developed for the specified launch date and mission trajectory prior to granting flight approval on the Eastern Range. The range safety data package is required to ensure that the public, launch area, and launch complex personnel and resources are provided with an acceptable level of safety and that all aspects of prelaunch and launch operations adhere to applicable public laws. The analysis data products, defined in the Air Force Space Command Manual 91-710, Volume 2, consisted of a nominal trajectory, three sigma trajectory envelopes, stage impact footprints, acoustic intensity contours, trajectory turn angles resulting from potential vehicle malfunctions (including flight software failures), characterization of potential debris, and debris impact footprints. These data products were developed under the auspices of the Constellation's Program Launch Constellation Range Safety Panel and its Range Safety Trajectory Working Group with the intent of beginning the framework for the operational vehicle data products and providing programmatic review and oversight. A multi-center NASA team in conjunction with the 45th Space Wing, collaborated within the Trajectory Working Group forum to define the data product development processes, performed the analyses necessary to generate the data products, and performed independent verification and validation of the data products. This paper outlines the Range Safety data requirements and provides an overview of the processes established to develop both the data products and the individual analyses used to develop the data products, and it summarizes the results of the analyses required for the Ares I-X launch.
This report examines the transformative impact of Artificial Intelligence (AI) and Machine Learning (ML) on operations research, private industry, and government sectors, highlighting their applications in automating processes, enhancing decision-making, and optimizing complex systems. AI/ML technologies have revolutionized industries through predictive maintenance, supply chain optimization, and autonomous systems, while also advancing public safety and defense operations. However, challenges such as data integrity, model transparency, and the need for human oversight persist, particularly in high-consequence environments. The report emphasizes the critical role of explainable AI (XAI) and human-computer interaction models like Human-in-the-Loop (HITL) and Human-on-the-Loop (HOTL) in fostering trust and accountability. Balancing automation with ethical responsibility and transparency is essential for the continued successful integration of AI/ML into operational and strategic decision-making frameworks.
Carbon, natural gas, and hydrogen gas storage is an emerging solution to safeguard us against pollution, support goals of negative carbon emission, and protect sources of renewable energy. Properly constructed storage wells provide a virtually impervious barrier to any unintended subsurface transmission. The ability to ensure the long-term integrity of such wells is vital to the success of any storage operation and be successful in the public eyes. Therefore, robust monitoring of any gas migration into the subsurface is highly sought. A fiber-optic distributed chemical sensor (DCS) enables monitoring of long-term well integrity along its depth, ensuring the success of any storage operation and bolsters public acceptance of the safety of the reservoir via leak early detection. The same technique can be applied to gas monitoring in pipeline networks and nuclear stockpile monitoring applications. Fiber based Raman spectroscopy enables DCS, as optical fibers can be deployed in virtually any environment and relay spectroscopic information over long distances back to the user. Hollow core fibers (HCF) make excellent DCSs as the air core of the fiber allows gas from the environment to diffuse into the core, which interacts with the laser signal that is carried in the air core. This work builds upon the previous LDRD project, Fiber Optic System for Direct Detection of Carbon Dioxide Leakage in Carbon Storage Wells (21-FS-003), in which the feasibility of Raman spectroscopy detection of Carbon Dioxide (CO2) in HCF detection was demonstrated. We mitigated the risk of this DCS technology by establishing and completing five objectives. The first objective was to model and optically characterize HCF uptake of CO2, establishing the relationship between HCF length, gas diffusion time, detectable gas concentration, and measured Raman intensity. In objective two, we developed a fiber core drilling recipe to enable additional diffusion ports in the fiber core and established a method for maintaining fiber strength and integrity post drilling. Objective three characterized the drilled fibers against the undrilled fibers, establishing the differences in the gas mechanics and optical properties and provided parameters to iterate the drilling process. In objective four, a fusion splicing technique was developed to join the HCF to conventional single-mode fibers, localizing the gas detection point at the drilled HCF hole, emulating a DCS. Lastly, objective five was the testing of the sensor in Edgar Mines at Colorado School of Mines on a CO2 pipeline with a simulated leak, to showcase the ability to detect CO2 leaks. This capstone result showed CO2 leak detection in < 10 minutes, raising the technology readiness level of HCF segments as deployable DCS.