Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “licenses”

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.

At least 1,279 records · Page 71

Pre-Demonstration Development of Controlled-Release Corrosion Inhibitors and Healing Agents as Alternatives to Hexavalent Chromium

This Limited Scope Study was directed to achieve the following objectives: (1) Scale-up of materials that can meet MIL-PRF-23377 (solvent-based primer). (2) Provide evidence of resistance to aircraft alkaline cleaners and deicing fluids. (3) Provide formulation for initial ecological and toxicity screening. (4) Submit an interim report that will provide the basis for a future ESTCP demonstration effort. The encapsulation procedure for two corrosion inhibitors was scaled up from lab scale to 2.0 kg. This scale will accommodate high volume production of coatings with encapsulated corrosion inhibitors for large surface areas during a follow on ESTCP demonstration effort. Test results provided evidence of resistance to alkaline cleaners and aircraft deicing fluids and compliance with MIL-PRF-23377. All the MIL-PRF-23377 requirements were met with the exception of the adhesion requirement, in top coated panels, and the flexibility requirement. Work on solving these two problems will be done prior to validation and demonstration of the technology. An initial ecological and toxicity screening identified several factors that were not critical to the acceptance of the encapsulated corrosion inhibitor. This new technology will lead to environmentally friendly alternatives to hexavalent chromium that will enable DoD to protect its assets. Field demonstration, licensing, qualification, and commercialization will allow its real world utilization.

Alternatives to Hexavalent Chromium↗

Pre-Demonstration Development of Controlled-Release Corrosion Inhibitors and Healing Agents as Alternatives to Hexavalent Chromium

This Limited Scope Study was directed to achieve the following objectives: (1) Scale-up of materials that can meet MIL-PRF-23377 (solvent-based primer). (2) Provide evidence of resistance to aircraft alkaline cleaners and deicing fluids. (3) Provide formulation for initial ecological and toxicity screening. (4) Submit an interim report that will provide the basis for a future ESTCP demonstration effort. The encapsulation procedure for two corrosion inhibitors was scaled up from lab scale to 2.0 kg. This scale will accommodate high volume production of coatings with encapsulated corrosion inhibitors for large surface areas during a follow on ESTCP demonstration effort. Test results provided evidence of resistance to alkaline cleaners and aircraft deicing fluids and compliance with MIL-PRF-23377. All the MIL-PRF-23377 requirements were met with the exception of the adhesion requirement, in top coated panels, and the flexibility requirement. Work on solving these two problems will be done prior to validation and demonstration of the technology. An initial ecological and toxicity screening identified several factors that were not critical to the acceptance of the encapsulated corrosion inhibitor. This new technology will lead to environmentally friendly alternatives to hexavalent chromium that will enable DoD to protect its assets. Field demonstration, licensing, qualification, and commercialization will allow its real world utilization.

Alternatives to Hexavalent Chromium, Controlled Re↗

Mechanically Strong Polyimide Aerogels (MSPA) As Multifunctional Acoustic Insulation

Aerogel Technologies has an exclusive license from NASA to commercialize polyimide aerogels developed at NASA GRC. They combine low density, low thermal conductivity, high specific strength, and soundproofing properties in a single material envelope. Aerogel Technologies and NASA GRC are working together to optimize the properties for lightweight, structural material for vibro-acoustic mitigation for launch vehicles, with the goal of achieving TRL 6 by the conclusion of the project.

polyimide aerogel↗

Cloud Software Enables Collaborative, Real-Time Procedures for NASA and Others

TRACLabs’ PRIDE software was the first collaborative and highly-customizable tool designed to allow astronauts to document and mark progress on procedures in real-time, display system data, and issue commands—all from a single application. The versatility of the software caught the eye of a major oil field service company, who bought licenses and support from TRACLabs for $3.3M

William Douglas Goodman↗

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗

Best Practices Identified Through the Completion of UAS Flight Demonstrations

After several years of research into Detect and Avoid (DAA) and Command and Control (C2) systems for Unmanned Aircraft Systems (UAS), the National Aeronautics and Space Administration’s (NASA) UAS Integration into the National Airspace System project initiated a focused two-year effort along with the Federal Aviation Administration (FAA) and three industry partners to investigate remaining issues in the specification, test, certification and airspace integration to allow UAS operations in non-segregated airspace. The approach taken had the industry partners propose a flight demonstration approximating a commercial operation, while NASA helped, as needed, the partners through design and test phases and NASA observed interactions with the FAA. During this effort NASA collected best practices intended to be of value to similar UAS endeavors. These best practices can be divided into different sets, including practices that describe the relationship between business considerations to UAS design or describe several UAS development challenges. Another set includes best practices focused on navigating the UAS design and type certification processes. A third set includes best practices that relate to the design of the DAA system. Deploying DAA systems in this timeframe posed unique challenges. Commercial off-the-shelf DAA systems do not exist, necessitating custom development and, for two of the partners, the use of low-size, -weight, and -power (SWaP) sensors not completely specified for DAA. A fourth set of best practices relates to lost-link contingency planning. The final set of best practices relates to the design and testing of C2 systems and obtaining spectrum licenses. The UAS demonstrations were piloted remotely, and for all aspects of flight safety, a C2 system was required to communicate DAA and other UAS subsystem data to the remote pilot and to allow the pilot to issue commands to the vehicle. Throughout the course of this effort, the partners integrated prototype DAA and C2 systems into unmanned aircraft, tested those systems, and laid the groundwork for type certification programs that are expected to continue.

NASA↗

NASA Class A Certification of Core Flight Software (cFS)

NASA Gateway program has named cFS as the software architecture for the vehicle. The core CFS team (GSFC+JSC) is tasked to develop a certifiable release of the cFS bundle, by components, as class A, safety-critical flight software. It is to be available to all Gateway software developers, including our element vendors and international partners. Its availability & usage will be as stated by the Gateway User Agreement license. In this presentation, we will describe our general certification process, and more importantly, our certification artifacts that can be re-run to certify cFS on different platforms. Our goal is to also make available these certifiable packages to the open source community, specifically for cFE, OSAL and certain cFS applications and libraries that are currently hosted on NASA github (https://github.com/nasa).

Tam M Ngo↗

The InSAR Scientific Computing Environment 3.0: A Flexible Framework for NISAR Operational and User-Led Science Processing

The InSAR Scientific Computing Environment (ISCE) was first developed under the NASA Advanced Information Systems Technology as a flexible, extensible object-oriented framework for Interferometric Synthetic Aperture Radar (InSAR) processing. The ISCE framework uses Python 3 at the workflow level, controlling modules of compiled code for functional processing, and managing inputs, outputs, and other flow control services. The currently released version, called ISCE 2.1, is distributed to the research community through the Western North America InSAR Consortium under a research license. The ISCE team is working on the next generation of the code in order to prepare for the NASAISRO SAR (NISAR) mission operational processing. Innovations in this code include augmentation or conversion of the custom Python framework elements in ISCE with the Pyre framework, new workflows for interferometric and polarimetric stack processing, a more intuitive and graphically based user interface, and flow control for hybrid computing environments including CPU/GPU clusters, logging and error tracking facilities, and new more efficient computational modules that exploit graphical processor units (GPUs) when available. The ISCE 3.0 framework is designed to work in an operational environment as well as on a single user’s laptop or compute cluster, with services to discover capabilities and scale computations accordingly.

Buckley, Sean M.↗

Computing observation geometry for small satellites

Most solar system science missions need a variety of observation geometry–quantities such as position and velocity, range and altitude, viewing latitude and longitude, and lighting angles– to support mission engineering, science planning, and science data analysis activities. NASA's "SPICE" system offers one popular, multi-mission means for doing just that. SPICE comprises both data files, called kernels, and a SPICE software Toolkit that is available in many popular languages. A mission operations center produces the SPICE kernel files. Scientists and engineers write their own applications programs to address some need, and they include a few SPICE subroutines within that code to do the needed geometry computations. The SPICE system has been in use throughout NASA’s planetary science mission domain since 1991, and it has slowly spread to most major space agencies around the globe since then. The SPICE software is available in most popular languages, and for most popular platforms. The code is thoroughly tested before being released, and new versions of the Toolkit are always backwards compatible. The SPICE components are freely offered to everyone, and have no export, licensing or similar restrictions. Maybe using SPICE would work for your CubeSat or SmallSat mission?

Acton, Charles H.↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service.Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations.The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-to-station handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an in-orbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

On-demand Command and Control of ASTERIA with Cloud-based Ground Station Services

ASTERIA (Arcsecond Space Telescope Enabling Research in Astrophysics) was a 6-unit CubeSat technology demonstration mission that deployed from the International Space Station on November 20th, 2017. After successfully completing its 90-day primary mission that demonstrated arcsecond-level line-of-sight pointing and focal plane thermal stability for exoplanet detection, it entered an extended mission performing onboard software demonstrations to mature technology both in space and on the ground. One of the technologies was a completely cloud-based ground system leveraging Amazon Web Services (AWS) Ground Station service. Announced in December 2018 and launched in May 2019, AWS Ground Station is a fully managed ground station service that aims to reduce the overhead associated with developing and maintaining ground system infrastructure throughout the mission lifecycle. AWS Ground Station makes available the suite of features required for any ground system in support of low-Earth orbit (LEO) and medium-Earth Orbit (MEO) satellite operations on-demand and without setting up or maintaining long-term contracts. Charges are incurred on a per-minute basis for antenna usage during scheduled tracks. Support is available for S-band uplink and downlink, along with X-band narrowband and wideband downlink. Missions that use the service may reserve tracks with any licensed AWS Ground Station antennas located across each service region and have direct access to any AWS services in support of mission operations. The cloud-based architecture built around the AWS Ground Station service greatly enhanced ASTERIA mission operations by enabling end-to-end pass automation, on-demand contact scheduling and contingency planning, along with more efficient data downlink through station availability and station-tostation handovers. It incorporated open-source software, particularly NASA's AMMOS Instrument Toolkit (AIT) and Open Mission Control Technologies (OpenMCT), along with the AWS application programming interfaces (API) to the Ground Station, Elastic Compute Cloud (EC2) and Simple Storage Service (S3) services. After showcasing operability in August 2019, the team continued using and improving this novel ground system architecture until the end of mission in December 2019. This paper describes the cloud-based ground system, how it was designed, tested, and evaluated with an inorbit spacecraft, the operational capabilities that it enabled, along with lessons learned and recommendations for future missions.

Fesq, Lorraine↗

High-Propellant Throughput Sub-kW Electric Propulsion System for Deep Space Science and Exploration

The National Aeronautics and Space Administration (NASA) is maturing high-propellant throughput sub-kilowatt electric propulsion technologies to enable small spacecraft deep space science and exploration missions with high delta-v requirements. The pathfinder model (PM) propulsion system consists of the H71M-PM Hall-effect thruster, a breadboard 1-kW power processing unit (PPU), and a propellant flow control system. The propulsion system requirements balance the needs of various high delta-v NASA and commercial industry mission concepts to achieve a design that both enables a variety of NASA small spacecraft deep space missions, while remaining viable for select commercial applications. The H71M-PM thruster has completed performance characterization and three 500-h short duration wear tests (SDWT). The propulsion system provides stable thrust generation over a wide range of operating conditions from 200 W to 1 kW, and 200 V to 400 V. The thruster has demonstrated a thrust as high as 68 mN at 300 V and 1 kW. The thruster has similarly demonstrated a specific impulse of 1850 s at 400 V and 1 kW. Key surfaces were machined between each SDWT to simulate accelerated discharge channel and pole cover erosion. Profilometry scans across masked pole cover surfaces were conducted to determine erosion rates. SDWT results support that a target thruster lifetime of 14 kh with 50% margin is achievable. Component testing has demonstrated propellant azimuthal flow uniformity better than ± 2 percent of the nominal value, azimuthal magnetic field uniformity better than ± 0.5 percent of the nominal value, and cathode heater cycle testing to greater than 30,000 cycles. Propulsion system integrated system testing is planned to use the H71M-PM and a breadboard 1-kW PPU. Pathfinder model test results are now supporting the design of the H71M-EM engineering model thruster. A second-generation breadboard PPU has been fabricated and is currently under test. NASA has made these technologies available to U.S. industry through a no cost, nonexclusive license agreement.

Hall↗

Henrich Focke —Inventor of the First Successful Helicopter

In 1924, Henrich Focke, Georg Wulf and Dr. Werner Naumann started Focke-Wulf Flugzeugbau GmbH (Focke-Wulf Aircraft Manufacturing Ltd.). Focke-Wulf constructed Juan de la Cierva’s C.19 and C.30 Autogiros under license from 1930 until 1937. This led Focke to design the first successful and fully controllable helicopter, the Fw-61. Model tests in his wind tunnel supported the configuration and in 1932 Focke proposed a helicopter project to the ministry with drawings and calculations, which was granted in that same year. Impressed with the success of the Fw-61, the German Air Ministry suggested that Focke establish a new company dedicated to helicopter development and issued him a requirement for an improved design, capable of carrying a 700 kg (1,500 lbs) payload. Focke and Gerd Achgelis (a test pilot) partnered to establish the Focke–Achgelis company in 1938. The Fw-61 became the Fa-61. Historically, Henrich Focke and his Focke-Achgelis company must surely be considered as the developer of the world’s first successful helicopter. They began development of the Focke Wulf company’s Model Fw-61 helicopter, which had a side-by-side rotor system, in 1932. First flight was achieved on June 26, 1936 with test pilot Ewald Rohlfs at the controls. With the Fw-61’s flight demonstrated success, Professor Focke went on to present three early papers: 1. Das Trag- und Hubschrauberproblem (Autogyro and Helicopter Problems), November 1937 2. Forschung und Entwicklung der Drehflügelflugzeuge (Research and Development of Rotating Wing Aircraft), April 1942 3. Fortschritte des Hubschraubers (Progress of the Helicopter), October 1943 The first paper was also published by the German Museum (Munich) in 1938 and it was translated into English on the order of the Ministry of Aircraft Production by J. Helledoren as R.T.P No. 2128 at the end of 1937. The other two reports, however, appear not to have been translated during or after World War II and thus are made public here – probably for the first time. Translations of the three Focke papers are provided in this report. A careful translation from German to English of the papers has been made. Many of original photos have been recovered from the German Museum (Munich). In several cases, the original graphs have been redrawn to enhance each paper’s technical value. The editors have added footnotes where appropriate. The editors consider Focke’s papers to be of such immense technical and historical value that they deserve wide distribution to the rotorcraft industry. Finally, the editors believe that readers of the many technical points Henrich Focke makes about his development program will see that Focke’s program anticipated even today’s best rotorcraft industry efforts.

Inventor↗

SEE Test Results for SAMA5D3

ARM processors power a class of high-performance, lower power system on a chip devices. In the absence of radiation effects, these devices are highly desirable for space use. The processor core architecture for ARM devices is licensed to provide computing on multiple hardware platforms. The A5 processor is in a unique pioneering space for providing detailed radiation response data to explore the baseline performance of these devices. These data can help set options for ARM processors and possibly impact design choices for the next generation of ARM fault tolerance capabilities. The SAMA5D3 was tested to establish general SEE performance for a relatively simple implementation of the ARM A5 core. This testing observed SRAM sensitivity starting at an LET of about 3 MeV-cm2/mg, with a saturated cross section of about 2x10-8cm2/bit, and this was determined by both active write and read of the caches, in addition to the use of a debugger to provide test results. Crash/SEFI data was collected using both Linux and bare metal C-code. The onset LET for crashes was about LET 1.5 MeV-cm2/mg, with saturated cross sections of about 2x10-5 cm2 for bare metal (low utilization), and 2x10-4cm2 for Linux (high utilization) tests.

Daniel, Andrew C.↗

Effects of Communication Modality on Pilot-Controller Coordination during a Simulated m:N Operation

The last decade or so has seen growing interest in new control paradigms and concepts of operation for uncrewed aircraft systems (UAS) in which multiple aircraft are piloted remotely by a single or relatively small number of people. Referred to as “one-to-many” and “many-to- many” (alternatively, “multi-operator, multi-vehicle”)—and frequently expressed as the corresponding ratios, 1:N and m:N—such novel configurations of aircraft and the people who manage them are seen as critical to the path to future operations involving UAS. Examples of industry domains interested in these control paradigms are small package delivery services utilizing small UAS and passenger-carrying, short-range “Urban Air Mobility” (UAM) operations. Stakeholders in such operations have identified communication and coordination of flight activity with air traffic controllers (ATC) as a barrier to operations. In contrast to present-day flight operations, in which a pilot communicates with one ATC on one radio frequency for one aircraft, multi-vehicle operations potentially entail a significant increase in pilot task load for management of comms. New concepts, such as UAS Service Suppliers (USSs) and Providers of Services to UAM (PSUs), have been proposed to address the known bottleneck for Air Traffic Management (ATM) presented by multi-vehicle operations. While progress has been steadily made over years developing USSs and PSUs, it is generally expected that initial UAM operations will rely on traditional voice-over-radio communication with ATC for purposes of ATM. The current study was a human-in-the-loop simulation that had participants, each possessing a Private Pilot License, act as the ground-based pilot-in- command for multiple vehicles in a hypothetical UAM service in the San Francisco Bay Area. The experiment utilized a 2-by-3, within-subjects design in which the pilot’s Vehicle Load (4 vs. 12) and Comm System (Voice, Datalink, and a Hybrid) were manipulated. The task given to pilots was to use the Comm System to coordinate flight activity for all aircraft with appropriate controllers, having to obtain departure and arrival clearances at “vertiport” facilities and transition clearances for any intermediate airspaces along the route. Pilots were additionally responsible for compliance with vectoring instructions issued by ATC. Subjective workload questionnaires (NASA-TLX) were administered following each experimental trial. Screen recordings of the pilot’s Ground Control Station (GCS) and audio recordings of trials were subsequently coded to obtain performance metrics: response times and error rates. Presented in this paper are results related to pilot responses to vectoring instructions issued by ATC. Workload was found to be significantly higher in the 12-Vehicle condition compared to the 4-Vehicle condition, nearly maxing out the NASA-TLX overall workload scale. There was no significant difference made by the Comm System on workload ratings. Pilots’ response times to communications were fastest in the Voice condition, although overall “service time” for compliance was shorter in Datalink and Hybrid conditions in most cases. Errors by pilots were frequent in both Vehicle Load conditions, most perniciously when using the Voice system. The results of this study suggest tradeoffs in advantages and disadvantages of the three comm systems. Recommendations for communication system design are provided taking the tradeoffs into account.

Garrett G Sadler↗

Effects of Communication Modality on Pilot-Controller Coordination during a Simulated m:N Operation

The last decade or so has seen growing interest in new control paradigms and concepts of operation for uncrewed aircraft systems (UAS) in which multiple aircraft are piloted remotely by a single or relatively small number of people. Referred to as “one-to-many” and “many-to- many” (alternatively, “multi-operator, multi-vehicle”)—and frequently expressed as the corresponding ratios, 1:N and m:N—such novel configurations of aircraft and the people who manage them are seen as critical to the path to future operations involving UAS. Examples of industry domains interested in these control paradigms are small package delivery services utilizing small UAS and passenger-carrying, short-range “Urban Air Mobility” (UAM) operations. Stakeholders in such operations have identified communication and coordination of flight activity with air traffic controllers (ATC) as a barrier to operations. In contrast to present-day flight operations, in which a pilot communicates with one ATC on one radio frequency for one aircraft, multi-vehicle operations potentially entail a significant increase in pilot task load for management of comms. New concepts, such as UAS Service Suppliers (USSs) and Providers of Services to UAM (PSUs), have been proposed to address the known bottleneck for Air Traffic Management (ATM) presented by multi-vehicle operations. While progress has been steadily made over years developing USSs and PSUs, it is generally expected that initial UAM operations will rely on traditional voice-over-radio communication with ATC for purposes of ATM. The current study was a human-in-the-loop simulation that had participants, each possessing a Private Pilot License, act as the ground-based pilot-in- command for multiple vehicles in a hypothetical UAM service in the San Francisco Bay Area. The experiment utilized a 2-by-3, within-subjects design in which the pilot’s Vehicle Load (4 vs. 12) and Comm System (Voice, Datalink, and a Hybrid) were manipulated. The task given to pilots was to use the Comm System to coordinate flight activity for all aircraft with appropriate controllers, having to obtain departure and arrival clearances at “vertiport” facilities and transition clearances for any intermediate airspaces along the route. Pilots were additionally responsible for compliance with vectoring instructions issued by ATC. Subjective workload questionnaires (NASA-TLX) were administered following each experimental trial. Screen recordings of the pilot’s Ground Control Station (GCS) and audio recordings of trials were subsequently coded to obtain performance metrics: response times and error rates. Presented in this paper are results related to pilot responses to vectoring instructions issued by ATC. Workload was found to be significantly higher in the 12-Vehicle condition compared to the 4-Vehicle condition, nearly maxing out the NASA-TLX overall workload scale. There was no significant difference made by the Comm System on workload ratings. Pilots’ response times to communications were fastest in the Voice condition, although overall “service time” for compliance was shorter in Datalink and Hybrid conditions in most cases. Errors by pilots were frequent in both Vehicle Load conditions, most perniciously when using the Voice system. The results of this study suggest tradeoffs in advantages and disadvantages of the three comm systems. Recommendations for communication system design are provided taking the tradeoffs into account.

urban air mobility↗

The Community Radiative Transfer Model (CRTM): Community-Focused Collaborative Model Development Accelerating Research to Operations

The Joint Center for Satellite Data Assimilation (JCSDA) Community Radiative Transfer Model (CRTM) is a fast, 1-D radiative transfer model used in numerical weather prediction, calibration/validation, etc. across multiple federal agencies and universities. The key benefit of the CRTM is that it is a satellite simulator. It provides a highly accurate representation of satellite radiances by using the specific sensor response functions convolved with a line-by-line radiative transfer model (LBLRTM). CRTM covers the spectral ranges consistent with all present operational and most research satellites, from visible to microwave. The capability to simulate ultraviolet radiances and support space-based radar sensors is being added over the next two years in CRTM Version 3.0. In addition to simulated radiances, the CRTM also provides Jacobian outputs needed to interpret satellite observations for numerical weather prediction. The Jacobian estimates how changes in geophysical parameters affect simulated measurements from satellite sensors. Using the Jacobian in modeling and weather prediction improves the accuracy and efficiency of data analysis, leading to better weather predictions. The CRTM model's success and growth depend on community contributions and evaluation. To facilitate this, we have made the CRTM highly accessible through modular programming, clear documentation and tutorials, public domain licensing, unfettered public access via Github, and a clear path to operational implementation for innovative research. We encourage and welcome contributions from the community to help us continue to improve the CRTM.

Benjamin T Johnson↗

Information and Best Practices Related to NASA Nuclear Flight Safety for Space Flights Involving Space Nuclear Systems

The purpose of this handbook is to facilitate a repeatable and robust process that promotes clear and effective interfaces between activities and stakeholders focused on meeting nuclear flight safety requirements for missions utilizing space nuclear systems (SNS), within the context of NASA’s broader nuclear-related activities and interfaces. NPR 8715.26, Nuclear Flight Safety, requires that the NASA project manager “incorporate nuclear flight safety considerations starting with program or project formulation through the point at which the SNS or other radioactive material no longer has the potential to affect Earth’s biosphere.” NASA’s use of SNS inherently involves partnering with other stakeholders to conduct a range of related activities that interface with nuclear flight safety. From a categorical perspective these include: (i) meeting the authorities and licensing requirements for possession and use of nuclear material, as governed by other Federal authorities; (ii) conducting National Environmental Policy Act (NEPA) activities for nuclear-enabled missions; (iii) meeting Federal nuclear launch authorization requirements; (iv) conducting radiological contingency planning activities, including those associated with international commitments; (v) performing risk communication and public outreach activities; and (vi) ensuring decommissioning and disposal strategies reflect National policies and interests. It is the intent of this handbook to promote an effective interface between nuclear flight safety and these interrelated categorical activities. In addition to activities undertaken with partnering agencies, there are individual nuclear-related activities and programs that have a nexus to nuclear flight safety, and these include: (i) applicable NASA Standing Review Boards; (ii) the US Department of Energy nuclear safety activities conducted in partnership with NASA under Memoranda of Understanding; (iii) the Department of Defense’s Range Safety activities; (iv) NASA’s general involvement in interagency and international dialogues regarding nuclear safety; (v) the NASA-administered Interagency Nuclear Safety Review Board; (vi) NASA’s program and project governance activities and nuclear-specific Technical Discipline Team activities under the Office of the Chief Engineer; and others. It is the intent of this handbook to promote effective leveraging of these additional interrelated organizational activities, as appropriate.

Donald Helton↗