Search NASA⌕ Search

SEARCH · Search NASA

Results for “trajectory based operations”

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 667 records · Page 37
All sourcesNASA NTRSDOE OSTI
NASA NTRS2011

In-Flight Operation of the Dawn Ion Propulsion System Through Orbit Capture at Vesta

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, Vesta and Ceres. The Dawn spacecraft was launched from Cape Canaveral Air Force Station on September 27, 2007 on a Delta -II 7925H-9.5 (Delta-II Heavy) rocket that placed the 1218 kg spacecraft into an Earth-escape trajectory. Onboard the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory which will provide most of the ?V needed for heliocentric transfer to Vesta, orbit capture at Vesta, transfer among Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, and transfer among Ceres science orbits. The first 80 days after launch were dedicated to the initial checkout of the spacecraft which was followed by about ten months of full-power thrusting leading to a Mars gravity assist in February 2009 that provided 1 km/s of heliocentric energy increase and is the only part of the mission following launch in which a needed velocity change is not accomplished by the IPS. Deterministic thrusting for heliocentric transfer to Vesta resumed in June 2009 and was concluded with orbit capture at Vesta in July 2011. IPS was operated for approximately 23,400 hours, consumed approximately 250 kg of xenon, and provided a delta-V of approximately 6.7 km/s to achieve orbit capture at Vesta. IPS performance characteristics are very close to the expected performance characteristics based on analysis performed pre-launch. The only significant problem to have occurred over the almost four years of IPS operations in flight was the temporary failure of a valve driver board in DCIU-1, resulting in a loss of thrust of approximately 29 hours. Thrusting operations resumed after switching to DCIU-2, and power cycling conducted after orbit capture indicates DCIU-1 is completely operational. After about three weeks of survey operations IPS will be used to maneuver the spacecraft as needed for science operations including orbit transfers. After approximately one year of science operations IPS will then be used for escape from Vesta and begin thrusting for cruise to Ceres with a planned arrival date at Ceres in February 2015. This paper provides an overview of Dawn's mission objectives and the results of Dawn IPS mission operations through orbit capture and the start of science operations at Vesta.

Garner, Charles E.↗
NASA NTRS2022

Low-Earth Orbit Trajectory Optimization in the Presence of Atmospheric Uncertainty

The previous 20 to 25 years have seen a tremendous increase in space exploration, and with that an increase in the level of logistics planning needed to ensure mission success. For spacecraft that are designed to be periodically re-supplied, a key logistics consumable is propellant, as it constitutes the greatest up-mass on re-supply vehicles. A trajectory design strategy is therefore desired that minimizes propellant usage in order to ease the demand for propellant re-supply missions. This thesis develops such a strategy in three stages, and uses the International Space Station (ISS) as its testbed, as no other LEO spacecraft is more challenging from a space logistics standpoint. First, the ISS trajectory planning problem is formulated as a constrained burn optimization problem assuming a deterministic atmosphere. The cost function is total ∆v, with constraints imposed on longitude of ascending viii node (LAN) and semi-major axis (SMA) altitude. Analytic derivatives are constructed for both the cost and constraints, which are necessary given the 6-week to 2-year time frames being considered. A gradient-based optimizer is then utilized to find locally-optimal solutions to real-world ISS trajectory planning problems. Second, atmospheric uncertainty is addressed by constructing a probabilistic model of space weather data using Gaussian Processes (GPs). Bayesian inference is performed using the GP model to generate mean and covariance estimates for space weather predictions, whose pedigree is assessed against test data. The predictions are then mapped into atmospheric density via the analytic Jacchia-Roberts density model, and the effect of space weather uncertainty on orbital lifetime is examined. Third, an ISS burn execution uncertainty model is developed. This model, along with the space weather uncertainty model, are deployed in a linear covariance analysis to ascertain their combined effect on LAN and SMA altitude dispersions. The deterministic constraints from the original problem are re-formulated as stochastic constraints, where now the constraint uncertainty interval is required to fall within specified bounds. An updated optimization framework is constructed using the original ∆v cost function along with the stochastic constraints to solve the trajectory optimization problem under atmospheric uncertainty. Finally, the complete architecture is summarized for deployment in an operational setting.

Trajectory Optimization↗
NASA NTRS2007

Space Weather Nowcasting of Atmospheric Ionizing Radiation for Aviation Safety

There is a growing concern for the health and safety of commercial aircrew and passengers due to their exposure to ionizing radiation with high linear energy transfer (LET), particularly at high latitudes. The International Commission of Radiobiological Protection (ICRP), the EPA, and the FAA consider the crews of commercial aircraft as radiation workers. During solar energetic particle (SEP) events, radiation exposure can exceed annual limits, and the number of serious health effects is expected to be quite high if precautions are not taken. There is a need for a capability to monitor the real-time, global background radiations levels, from galactic cosmic rays (GCR), at commercial airline altitudes and to provide analytical input for airline operations decisions for altering flight paths and altitudes for the mitigation and reduction of radiation exposure levels during a SEP event. The Nowcast of Atmospheric Ionizing Radiation for Aviation Safety (NAIRAS) model is new initiative to provide a global, real-time radiation dosimetry package for archiving and assessing the biologically harmful radiation exposure levels at commercial airline altitudes. The NAIRAS model brings to bear the best available suite of Sun-Earth observations and models for simulating the atmospheric ionizing radiation environment. Observations are utilized from ground (neutron monitors), from the atmosphere (the METO analysis), and from space (NASA/ACE and NOAA/GOES). Atmospheric observations provide the overhead shielding information and the ground- and space-based observations provide boundary conditions on the GCR and SEP energy flux distributions for transport and dosimetry simulations. Dose rates are calculated using the parametric AIR (Atmospheric Ionizing Radiation) model and the physics-based HZETRN (High Charge and Energy Transport) code. Empirical models of the near-Earth radiation environment (GCR/SEP energy flux distributions and geomagnetic cut-off rigidity) are benchmarked against the physics-based CMIT (Coupled Magnetosphere- Ionosphere-Thermosphere) and SEP-trajectory models.

Mertens, Christopher J.↗
NASA NTRS2006

Software for Simulating Air Traffic

Future Air Traffic Management Concepts Evaluation Tool (FACET) is a system of software for performing computational simulations for evaluating advanced concepts of advanced air-traffic management. FACET includes a program that generates a graphical user interface plus programs and databases that implement computational models of weather, airspace, airports, navigation aids, aircraft performance, and aircraft trajectories. Examples of concepts studied by use of FACET include aircraft self-separation for free flight; prediction of air-traffic-controller workload; decision support for direct routing; integration of spacecraft-launch operations into the U.S. national airspace system; and traffic- flow-management using rerouting, metering, and ground delays. Aircraft can be modeled as flying along either flight-plan routes or great-circle routes as they climb, cruise, and descend according to their individual performance models. The FACET software is modular and is written in the Java and C programming languages. The architecture of FACET strikes a balance between flexibility and fidelity; as a consequence, FACET can be used to model systemwide airspace operations over the contiguous U.S., involving as many as 10,000 aircraft, all on a single desktop or laptop computer running any of a variety of operating systems. Two notable applications of FACET include: (1) reroute conformance monitoring algorithms that have been implemented in one of the Federal Aviation Administration s nationally deployed, real-time, operational systems; and (2) the licensing and integration of FACET with the commercially available Flight Explorer, which is an Internet- based, real-time flight-tracking system.

Sridhar, Banavar↗
NASA NTRS2013

In-flight Operation of the Dawn Ion Propulsion System Through Year One of Cruise to Ceres

The Dawn mission, part of NASA's Discovery Program, has as its goal the scientific exploration of the two most massive main-belt asteroids, 4 Vesta, and the dwarf planet 1 Ceres. The Dawn spacecraft was launched from the Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H-9.5 rocket that placed the 1218-kg spacecraft into an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory which will provide an additional delta- V of approximately 11 km/s for the heliocentric transfers to each body and for all orbit transfers including orbit capture/escape and transition to the various science orbits. Deterministic thrusting to Vesta began in December 2007 and concluded with orbit capture at Vesta in July 2011. The transfer to Vesta included a Mars gravity assist flyby in February 2009 that provided an additional delta-V of 2.6 km/s and was the only postlaunch mission delta-V not provided by IPS. During the mission at Vesta the IPS was used for all orbit transfers which included six different near-polar science mapping orbits. Thrusting for departure from Vesta and the start of cruise to Ceres began on July 25, 2012 with escape from Vesta occurring on September 5, 2012. To date the IPS has been operated for approximately 31,000 hours, consumed approximately 300 kg of xenon, and provided a delta-V of approximately 8.3 km/s. IPS performance characteristics are very close to the expected performance based on analysis and testing performed prelaunch. Thrusting for cruise to Ceres will continue until the spring of 2015, with a planned arrival date at Ceres in April 2015. This paper provides an overview of Dawn's mission objectives and the results of Dawn IPS mission operations from Vesta departure through the first year of cruise to Ceres.

Hayabusa spacecraft↗
NASA NTRSDate not supplied

A Distributed Simulation-to-Flight Framework to Support Investigating Trust/Trustworthiness in Multi-Agent Systems

As autonomous systems continue to grow both in use and complexity, the necessity for robust and extensible simulation-to-flight frameworks is paramount for establishing an effective architecture for autonomous systems. Hardware test flights are time-consuming and cost prohibitive during early system design and development. Simulation environments can be useful tools to accelerate algorithm development and testing. However, transitions from simulation to flight (sim-to-flight) can be challenging, unless systems are designed with this transition in mind and with the necessary capabilities built into the architecture and framework. One of the objectives of Autonomy Teaming and TRAjectories for Complex Trusted Operational Reliability (ATTRACTOR) was to design and develop a distributed mixed-reality simulation environment to begin establishing a basis for certification of autonomous systems via research into trust and trustworthiness. ATTRACTOR’s objective was to construct computational concepts of trustworthiness and justifiable trust in multi-agent autonomous teams, to inform future certification of safety-critical and time-critical autonomous systems in aviation. In this paper, we present an autonomous systems architecture and development framework paired with a persistent distributed modeling and simulation (ModSim) environment for test and evaluation of autonomous systems. They were designed under ATTRACTOR in order to measure and establish trustworthiness and trust in single-and multi-agent human-machine systems whether these machines are fixed-wing general aviation, rotary-wing Unmanned Aerial Vehicles (UAVs), ground rovers, or even spacecraft. The Autonomous Entity Operational Network (AEON) framework enables autonomous system development with an easily extensible collection of libraries and plug-n-play nodes facilitated by the Data Distribution Service (DDS) communication protocol standard. The Baseline Environment for Autonomous Modeling (BEAM) simulation environment is a distributed mixed-reality Unity™-based environment built around the same DDS communication paradigm allowing for easy integration with AEON-based autonomous applications, enabling sim-to-flight with minimal configuration changes. Using AEON and BEAM, source code that runs in simulation ports directly to hardware and has successfully flown in the National Airspace System (NAS) at NASA LaRC many times over the lifetime of ATTRACTOR.

Benjamin N Kelley↗
NASA NTRS1993

Profile negotiation: An air/ground automation integration concept for managing arrival traffic

NASA Ames Research Center and NASA Langley Research Center conducted a joint simulation study to evaluate a profile negotiation process (PNP) between a time-based air traffic control ATC system and an airplane equipped with a four dimensional flight management system (4D FMS). Prototype procedures were developed to support the functional implementation of this process. The PNP was designed to provide an arrival trajectory solution that satisfies the separation requirements of ATC while remaining as close as possible to the airplane's preferred trajectory. The Transport Systems Research Vehicle cockpit simulator was linked in real-time to the Center/TRACON Automation System (CTAS) for the experiment. Approximately 30 hours of simulation testing were conducted over a three week period. Active airline pilot crews and active Center controller teams participated as test subjects. Results from the experiment indicate the potential for successful incorporation of airplane preferred arrival trajectories in the CTAS automation environment. Controllers were able to consistently and effectively negotiate nominally conflict-free trajectories with pilots flying a 4D-FMS-equipped airplane. The negotiated trajectories were substantially closer to the airplane's preference than would have otherwise been possible without the PNP. Airplane fuel savings relative to baseline CTAS were achieved in the test scenarios. The datalink procedures and clearances developed for this experiment, while providing the necessary functionality, were found to be operationally unacceptable to the pilots. Additional pilot control and understanding of the proposed airplane-preferred trajectory and a simplified clearance procedure were cited as necessary for operational implementation of the concept. From the controllers' perspective, the main concerns were the ability of the 4D airplane to accurately track the negotiated trajectory and the workload required to support the PNP as implemented in this study.

Williams, David H.↗
NASA NTRS2009

A First Look at Carbon and Oxygen Stable Isotope Measurements of Martian Atmospheric C02 by the Phoenix Lander

Precise stable isotope measurements of the CO2 in the martian atmosphere have the potential to provide important constraints for our understanding of the history of volatiles, the carbon cycle, current atmospheric processes, and the degree of water/rock interaction on Mars. The isotopic composition of the martian atmosphere has been measured using a number of different methods (Table 1), however a precise value (<1%) has yet to be achieved. Given the elevated 13C values measured in carbonates in martian meteorites it has been supposed that the martian atmosphere was enriched in delta(sup 13)C. This was supported by measurements of trapped CO2 gas in EETA 79001[2] which showed elevated delta(sup 13)C values (Table 1). More recently, Earth-based spectroscopic measurements of the martian atmosphere have measured the martian CO2 to be depleted in delta(sup 13)C relative to CO2 in the terrestrial atmosphere. The spectroscopic measurements performed by Krasnopolsky et al. were reported with approx.2% uncertainties which are much smaller than the Viking measurements, but still remain very large in comparison to the magnitude of carbon and oxygen isotope fractionations under martian surface conditions. The Thermal Evolved Gas Analyzer (TEGA) instrument on the Mars Phoenix Lander included a magnetic sector mass spectrometer (EGA) which had the goal of measuring the isotopic composition of martian atmospheric CO2 to within 0.5%. The mass spectrometer is a miniature magnetic sector instrument intended to measure both the martian atmosphere as well as gases evolved from heating martian soils. Ions produced in the ion source are drawn out by a high voltage and focused by a magnetic field onto a set of collector slits. Four specific trajectories are selected to cover the mass ranges, 0.7 - 4, 7 - 35, 14 - 70, and 28 - 140 Da. Using four channels reduces the magnitude of the mass scan and provides simultaneous coverage of the mass ranges. Channel electron multiplier (CEM) detectors that operate in the pulse counting mode detect the ion beams.

Niles, P.B.↗
NASA NTRS2008

Evolution and Reengineering of NASA's Flight Dynamics Facility (FDF)

The NASA Goddard Space Flight Center's Flight Dynamics Facility (FDF) is a multimission support facility that performs ground navigation and spacecraft trajectory design services for a wide range of scientific satellites. The FDF also supports the NASA Space Network by providing orbit determination and tracking data evaluation services for the Tracking Data Relay Satellite System (TDRSS). The FDF traces its history to early NASA missions in the 1960's, including navigation support to the Apollo lunar missions. Over its 40 year history, the FDF has undergone many changes in its architecture, services offered, missions supported, management approach, and business operation. As a fully reimbursable facility (users now pay 100% of all costs for FDF operations and sustaining engineering activities), the FDF has faced significant challenges in recent years in providing mission critical products and services at minimal cost while defining and implementing upgrades necessary to meet future mission demands. This paper traces the history of the FDF and discusses significant events in the past that impacted the FDF infrastructure and/or business model, and the events today that are shaping the plans for the FDF in the next decade. Today's drivers for change include new mission requirements, the availability of new technology for spacecraft navigation, and continued pressures for cost reduction from FDF users. Recently, the FDF completed an architecture study based on these drivers that defines significant changes planned for the facility. This paper discusses the results of this study and a proposed implementation plan. As a case study in how flight dynamics operations have evolved and will continue to evolve, this paper focuses on two periods of time (1992 and the present) in order to contrast the dramatic changes that have taken place in the FDF. This paper offers observations and plans for the evolution of the FDF over the next ten years. Finally, this paper defines the mission model of the future for the FDF based on NASA's current mission list and planning for the Constellation Program. As part of this discussion the following are addressed: the relevance and benefits of a multi-mission facility for NASA's navigation operations in the future; anticipated technologies affecting ground orbit determination; continued incorporation of Commercial Off-the-shelf (COTS) software into the FDF; challenges of a business model that relies entirely on user fees to fund facility upgrades; anticipated changes in flight dynamics services required; and considerations for defining architecture upgrades given a set of cost drivers.

Stengle, Thomas↗
NASA NTRSDate not supplied

Aerial Vehicle Routing and Scheduling for UAS Traffic Management: A Monte Carlo Tree Search Approach

Numerous unmanned aircraft systems operating at low altitudes to deliver goods and services may one day become ubiquitous in our cities. In the Unmanned Aircraft Systems (UAS) Traffic Management (UTM) framework, such a concept is envisioned, where aerial vehicles operate beyond visual line of sight (BVLOS) within specifically reserved and time stamped “corridors” in the airspace. For example, these corridors or operational intent volumes can connect an aerial vehicle’s origin site to its destination site for package delivery operations. There may also be more than one corridor available for an aerial vehicle to choose from and often different corridors may intersect with one another. Thus, it is imperative to ensure flight trajectories belonging to different aerial vehicles are not in conflict. Per the UTM CONOPs, we assume that a vehicle almost always stays inside its corridor or operational volume. This work provides a framework for strategic deconfliction of UTM or package delivery drones, where we schedule the departure time of all vehicles subject to various temporal constraints (including the corridor deconfliction at the intersections). We present the “multi-route weighted package delivery problem” which serves as an exemplifying model for strategic deconfliction in UTM. In the multi-route weighted package delivery problem, a graph network is given which consists of a set of depots (source) and drop-off (destination) nodes, with multiple routes (defined as a sequence of waypoints) connecting the depots to drop-off nodes. In addition, routes are weighted by the associated ground risk and total travel distance for package delivery. The goal is for a known set of aerial vehicles to depart from the depots, choose a route and take off time, while avoiding conflicts with other aerial vehicles, and minimizing both risk and distance traveled. We provide a mixed integer linear programming (MILP) formulation of the problem, as well as a heuristic solution based on Monte Carlo Tree Search (MCTS) – a method used in game theory and artificial intelligence – to overcome limitations inherent to optimal solvers. Computational results show the advantages of using MCTS over the MILP formulation; the former can provide a sub-optimal solution quickly, and may sometimes even reach an optimal solution, whereas the latter may not even produce a solution in reasonable time. Furthermore, results from both the MILP formulation and MCTS methods were validated using a preliminary agent-based simulator implementing the UTM concept of operations. Thus, the MCTS method can be seen as a scalable solution to the complex multi-route weighted package delivery problem and may possibly be extended to similar complex optimization problems.

Kenny Chour↗
NASA NTRS2019

Fusion-Enabled Pluto Orbiter and Lander

Direct Fusion Drive (DFD) is a unique fusion engine concept based on the Princeton Field-Reversed Configuration (PFRC) fusion reactor conceived by Dr. Sam Cohen of the Princeton Plasma Physics Laboratory. DFD would enable the Pluto orbiter and lander context mission and more broadly enable true "rapid transit" to outer-planet and near interstellar space. The truly game-changing levels of thrust and power in a modestly sized package could integrate with our current launch infrastructure while radically expanding the science capability of these missions. Our Phase I was our first funded work on the DFD, with previous work at PSS occurring only under internal R&D. We established the feasibility of our Pluto mission trajectories using straight-line and planar models, including a departure spiral from Earth and insertion at Pluto. We developed our first thrust and specific impulse model using the results of the UEDGE multi-fluid code. Our specific power model was improved. During this Phase II effort, we continued our efforts to increase the fidelity of the designs for the RF, magnet, and shielding subsystems. Dedicated thrust augmentation experiments were run on the PFRC experiment, using a supersonic gas puffing valve. For the first time, we analyzed the design of a closed-loop operation mode and estimated the hardware that would be required for a dual-mode engine. In an exciting new development, we have invented a new thermophotovoltaic thermal conversion method that has the potential to have efficiencies of a Brayton or Stirling system. Our report presents details of these analyses. Our roadmap to bringing DFD to flight predicts that with sufficient support, a first flight unit could be built by 2040. We anticipate that three machine generations are required before this point: a ~1 T PFRC-3 machine hitting new plasma temperature and density levels, a ~5 T PFRC-4 machine with first demonstration of D-3He fusion, and a flight. (The current experiment, PFRC-2, is limited to about 0.1 T). In order to achieve a flight in 2035-2040, the TRL of the supporting systems must be increased in parallel, including low mass radiators, cryogenic propellant storage, and large (>100 kW) thermal conversion systems. Fortunately, many of these systems are dual-use and are required for other technologies including fission systems, so DFD would contribute to and benefit from those programs. This NIAC support and the results of our work have led to multiple follow-on contracts. We won two NASA STTRs focused on DFD subsystems, one on the RF system and one on the superconducting magnets, and our magnet STTR is now midway through a Phase II. We will be receiving a superconducting test magnet for experiments at PPPL this summer. In addition, we won an ARPA-E OPEN grant; this is the first time that OPEN has included fusion technologies, and we are part of a cohort of three alternative fusion companies now supported directly by DOE. We are very optimistic that if we are able to meet our experimental milestones in the next 12-18 months, we will be competitive for additional DOE grants to build PFRC-3.

Propulsion↗
NASA NTRS2016

Deploying a Route Optimization EFB Application for Commercial Airline Operational Trials

The Traffic Aware Planner (TAP), developed for NASA Langley Research Center to support the Traffic Aware Strategic Aircrew Requests (TASAR) project, is a flight-efficiency software application developed for an Electronic Flight Bag (EFB). Tested in two flight trials and planned for operational testing by two commercial airlines, TAP is a real-time trajectory optimization application that leverages connectivity with onboard avionics and broadband Internet sources to compute and recommend route modifications to flight crews to improve fuel and time performance. The application utilizes a wide range of data, including Automatic Dependent Surveillance Broadcast (ADS-B) traffic, Flight Management System (FMS) guidance and intent, on-board sensors, published winds and weather, and Special Use Airspace (SUA) schedules. This paper discusses the challenges of developing and deploying TAP to various EFB platforms, our solutions to some of these challenges, and lessons learned, to assist commercial software developers and hardware manufacturers in their efforts to implement and extend TAP functionality in their environments. EFB applications (such as TAP) typically access avionics data via an ARINC 834 Simple Text Avionics Protocol (STAP) server hosted by an Aircraft Interface Device (AID) or other installed hardware. While the protocol is standardized, the data sources, content, and transmission rates can vary from aircraft to aircraft. Additionally, the method of communicating with the AID may vary depending on EFB hardware and/or the availability of onboard networking services, such as Ethernet, WIFI, Bluetooth, or other mechanisms. EFBs with portable and installed components can be implemented using a variety of operating systems, and cockpits are increasingly incorporating tablet-based technologies, further expanding the number of platforms the application may need to support. Supporting multiple EFB platforms, AIDs, avionics datasets, and user interfaces presents a challenge for software developers and the management of their code baselines. Maintaining multiple baselines to support all deployment targets can be extremely cumbersome and expensive. Certification also needs to be considered when developing the application. Regardless of whether the software is itself destined to be certified, data requirements in support of the application and user interface elements may introduce certification requirements for EFB manufacturers and the airlines. The example of TAP, the challenges faced, solutions implemented, and lessons learned will give EFB application and hardware developers insight into future potential requirements in deploying TAP or similar flight-deck EFB applications.

Roscoe, David A.↗
NASA NTRS2023

NAIRAS Ionizing Radiation Model: Extension from Atmosphere to Space

The Nowcast of Aerospace Ionizing RAdiation System (NAIRAS) model is a real-time, global, physics-based model originally developed to predict exposure from cosmic radiation to air travelers from both galactic and solar sources. A prototype operational NAIRAS model has provided tabular and graphical data products via its public web site for about ten years. A new version of the NAIRAS model has been developed that incorporates an extension of the model domain from the atmospheric ionizing radiation environment to the space radiation environment, with the addition of the trapped inner belt proton source and altitude-dependent and rigidity-dependent geomagnetic shielding of the galactic cosmic rays (GCR) and solar energetic particle (SEP) protons. New output products of differential and integral particle flux have been developed for the characterization of single-event effects (SEE), expanding the application of NAIRAS from human radiation exposure assessment to allowing end-users to quantify radiation environment risks to aviation and spacecraft microelectronic systems. The NAIRAS model has transitioned to prototype operations at the Community Coordinated Modeling Center (CCMC) where the model now operates in two modes: (1) real-time global predictions of the atmospheric radiation environment and (2) a run-on-request (RoR) service allowing the user to select a specific time period for the global dosimetric calculations, or to upload an aircraft, balloon, or spaceflight trajectory file to provide predictions of the dosimetric and particle flux quantities along the flight path. The new features of NAIRAS version 3.0 are described in this paper and example results of the new output products for low-Earth orbit (LEO), medium-Earth orbit (MEO), and free-space radiation environments are presented

Christopher J. Mertens↗
NASA NTRS2007

Multi-Sensor Testing for Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Laboratory

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as AR&D). The crewed missions may also perform rendezvous and docking operations and may require different levels of automation and/or autonomy, and must provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success of the Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor proposed relative navigation sensor suite will meet the requirements. The relatively low technology readiness level of AR&D relative navigation sensors has been carried as one of the CEV Project's top risks. The AR&D Sensor Technology Project seeks to reduce the risk by the testing and analysis of selected relative navigation sensor technologies through hardware-in-the-loop testing and simulation. These activities will provide the CEV Project information to assess the relative navigation sensors maturity as well as demonstrate test methods and capabilities. The first year of this project focused on a series of"pathfinder" testing tasks to develop the test plans, test facility requirements, trajectories, math model architecture, simulation platform, and processes that will be used to evaluate the Contractor-proposed sensors. Four candidate sensors were used in the first phase of the testing. The second phase of testing used four sensors simultaneously: two Marshall Space Flight Center (MSFC) Advanced Video Guidance Sensors (AVGS), a laser-based video sensor that uses retroreflectors attached to the target vehicle, and two commercial laser range finders. The multi-sensor testing was conducted at MSFC's Flight Robotics Laboratory (FRL) using the FRL's 6-DOF gantry system, called the Dynamic Overhead Target System (DOTS). The target vehicle for "docking" in the laboratory was a mockup that was representative of the proposed CEV docking system, with added retroreflectors for the AVGS. The multi-sensor test configuration used 35 open-loop test trajectories covering three major objectives: (1) sensor characterization trajectories designed to test a wide range of performance parameters; (2) CEV-specific trajectories designed to test performance during CEV-like approach and departure profiles; and (3) sensor characterization tests designed for evaluating sensor performance under more extreme conditions as might be induced during a spacecraft failure or during contingency situations. This paper describes the test development, test facility, test preparations, test execution, and test results of the multi-sensor series of trajectories.

Brewster, L.↗
NASA NTRS2008

Multi-Sensor Testing for Automated Rendezvous and Docking Sensor Testing at the Flight Robotics Lab

The Exploration Systems Architecture defines missions that require rendezvous, proximity operations, and docking (RPOD) of two spacecraft both in Low Earth Orbit (LEO) and in Low Lunar Orbit (LLO). Uncrewed spacecraft must perform automated and/or autonomous rendezvous, proximity operations and docking operations (commonly known as AR&D). The crewed missions may also perform rendezvous and docking operations and may require different levels of automation and/or autonomy, and must provide the crew with relative navigation information for manual piloting. The capabilities of the RPOD sensors are critical to the success ofthe Exploration Program. NASA has the responsibility to determine whether the Crew Exploration Vehicle (CEV) contractor-proposed relative navigation sensor suite will meet the requirements. The relatively low technology readiness level of AR&D relative navigation sensors has been carried as one of the CEV Project's top risks. The AR&D Sensor Technology Project seeks to reduce the risk by the testing and analysis of selected relative navigation sensor technologies through hardware-in-the-Ioop testing and simulation. These activities will provide the CEV Project information to assess the relative navigation sensors maturity as well as demonstrate test methods and capabilities. The first year of this project focused on a series of "pathfinder" testing tasks to develop the test plans, test facility requirements, trajectories, math model architecture, simulation platform, and processes that will be used to evaluate the Contractor-proposed sensors. Four candidate sensors were used in the first phase of the testing. The second phase of testing used four sensors simultaneously: two Marshall Space Flight Center (MSFC) Advanced Video Guidance Sensors (AVGS), a laser-based video sensor that uses retroreflectors attached to the target vehicle, and two commercial laser range finders. The multi-sensor testing was conducted at MSFC's Flight Robotics Laboratory (FRL) using the FRL's 6-DOF gantry system, called the Dynamic Overhead Target System (DOTS). The target vehicle for "docking" in the laboratory was a mockup that was representative of the proposed CEV docking system, with added retroreflectors for the AVGS.' The multi-sensor test configuration used 35 open-loop test trajectories covering three major objectives: (l) sensor characterization trajectories designed to test a wide range of performance parameters; (2) CEV-specific trajectories designed to test performance during CEV-like approach and departure profiles; and (3) sensor characterization tests designed for evaluating sensor performance under more extreme conditions as might be induced during a spacecraft failure or during contingency situations. This paper describes the test development, test facility, test preparations, test execution, and test results of the multisensor series oftrajectories

Brewster, Linda L.↗
NASA NTRS2010

SPOT Program

A Spacecraft Position Optimal Tracking (SPOT) program was developed to process Global Positioning System (GPS) data, sent via telemetry from a spacecraft, to generate accurate navigation estimates of the vehicle position and velocity (state vector) using a Kalman filter. This program uses the GPS onboard receiver measurements to sequentially calculate the vehicle state vectors and provide this information to ground flight controllers. It is the first real-time ground-based shuttle navigation application using onboard sensors. The program is compact, portable, self-contained, and can run on a variety of UNIX or Linux computers. The program has a modular objec-toriented design that supports application-specific plugins such as data corruption remediation pre-processing and remote graphics display. The Kalman filter is extensible to additional sensor types or force models. The Kalman filter design is also strong against data dropouts because it uses physical models from state and covariance propagation in the absence of data. The design of this program separates the functionalities of SPOT into six different executable processes. This allows for the individual processes to be connected in an a la carte manner, making the feature set and executable complexity of SPOT adaptable to the needs of the user. Also, these processes need not be executed on the same workstation. This allows for communications between SPOT processes executing on the same Local Area Network (LAN). Thus, SPOT can be executed in a distributed sense with the capability for a team of flight controllers to efficiently share the same trajectory information currently being computed by the program. SPOT is used in the Mission Control Center (MCC) for Space Shuttle Program (SSP) and International Space Station Program (ISSP) operations, and can also be used as a post -flight analysis tool. It is primarily used for situational awareness, and for contingency situations.

Smith, Jason T.↗
NASA NTRSDate not supplied

Strategy for Developing Technologies for Megawatt-class Nuclear Electric Propulsion Systems

In late fiscal year 2020, the Space Nuclear Propulsion (SNP) project began the process of formulating an investment strategy to support development of the technologies required for a high-power (megawatt-class) nuclear electric propulsion (NEP) system capable of performing human-scale missions. This activity was initiated concurrent with several high-level studies and assessments were either under way or had just concluded. Studies of human-scale Mars missions have been performed several times over the past two decades. One of the most recent studies examined opposition-class human Mars missions to occur in the late 2030s timeframe [1,2]. The mission architecture assumed a hybrid NEP/chem-propelled vehicle that used a high specific impulse (Isp) NEP-system and a liquid oxygen (LOx)-liquid methane high thrust chemical stage (two 110 kN (25 klbf) thrust, 365 s Isp engines) for maneuvers performed to enter and exit gravity wells. Trajectory analyses performed in this study showed that such a mission could be performed with 2-4 MWe directed into the electric propulsion system (operating for 20,000+ hours), with the large range representing different opposition-class Mars mission opportunities and permutations on the trajectory design, concept of operations, and technology choices. In 2020, the NASA Engineering and Safety Center (NESC) performed a study to evaluate the maturity of the different technologies required for nuclear propulsion systems [3]. The executive summary of this report provided the following top-level conclusions: • “The majority of critical technologies for… NEP/Chem… systems are relatively immature” • “TRLs [technology readiness levels] in the literature are often overestimated” • “The majority of critical technologies… for NEP/Chem… systems are at a relatively high level of advancement degree of difficulty (AD2 > 4) for maturation, requiring a dual development approach” • “The proper assessment of baseline TRL and AD2 values and the estimation of requirements and resources required for advancement have been consistent issues for NEP,” • “Non-advocate reviews should occur at the start of a technology program and at all key milestones.” In 2021, the National Academies of Science, Engineering, and Medicine (NASEM) issued a separate report [4] identifying the “primary technical and programmatic challenges, merits, and risks for maturing space nuclear propulsion technologies of interest to a future human Mars exploration mission.” That work contained several important findings, including: • “Developing a MWe-class NEP system for the baseline mission would require increasing power by orders of magnitude relative to NEP system flight- or ground-based technology demonstrations completed to date.” • “Subscale in-space flight testing of NEP systems cannot address many of the risks and potential failure modes associated with the baseline mission NEP system. With sufficient M&S [modeling & simulation] and ground testing, including modular subsystem tests at full scale and power, flight qualification requirements can be met by the cargo missions that will precede the first crewed mission to Mars. Fully integrated ground testing may not be required.” • “As a result of low and intermittent investment over the past several decades, it is unclear if even an aggressive program would be able to develop an NEP system capable of executing the baseline mission in 2039.” These efforts motivated the SNP project to investigate the technologies available for a megawatt-class high power nuclear electric propulsion system. That system is illustrated schematically in Figure 1 and is comprised of five separate top-level critical technology elements (CTEs). 1. Nuclear Reactor – Thermal power source for the system, utilizing high-assay low enriched uranium (HALEU) as the nuclear fuel. Reactor radiation shielding is also included in this CTE. 2. Power Conversion – Operates as a thermodynamic cycle, accepting nuclear reactor thermal power as an input and converting it to mechanical power. 3. Power Management and Distribution (PMAD) – Accepts as an input mechanical power from the power conversion system, which is used to generate electrical power. The PMAD system also distributes the generated electrical power to all other parts of the spacecraft, including the high-power EP system. The PMAD system may also perform duties such as isolation, fault detection, and power transformation/rectification for different spacecraft systems, including the thrusters. 4. Electric Propulsion (EP) – Accepts as an input electrical power, which is used to accelerate a propellant to high speeds to produce thrust. This system includes the power processing unit (PPU), which converts the power it receives to the correct current and voltage required by the thrusters, and the propellant storage and feed systems, which contain and meter the flow of propellant to the thrusters. 5. Thermal Management (Radiators/Heat Rejection) – The cold side of the thermodynamic power conversion cycle, accepts thermal power from the power conversion system and radiatively rejects that heat to space. In this paper, we describe the SNP project formulation and investment strategy that aims to accomplish the research and development required to advance the technology readiness for each CTE. The strategy relies heavily upon experimental testing supported by modeling and simulation to yield realistic assessments of the technologies, which in turn will be used to inform future NEP system-level design decisions and any potential technology downselects.

Kurt A Polzin↗
NASA NTRS2016

A Numerical Approach to Estimate the Ballistic Coefficient of Space Debris from TLE Orbital Data

Low Earth Orbit (LEO) is full of space debris, which consist of spent rocket stages, old satellites and fragments from explosions and collisions. As of 2009, more than 21,000 orbital debris larger than 10 cm are known to exist], and while it is hard to track anything smaller than that, the estimated population of particles between 1 and 10 cm in diameter is approximately 500,000, whereas small as 1 cm exceeds 100 million. These objects orbit Earth with huge kinetic energies speeds usually exceed 7 kms. The shape of their orbit varies from almost circular to highly elliptical and covers all LEO, a region in space between 160 and 2,000 km above sea level. Unfortunately, LEO is also the place where most of our active satellites are situated, as well as, International Space Station (ISS) and Hubble Space Telescope, whose orbits are around 400 and 550 km above sea level, respectively.This poses a real threat as debris can collide with satellites and deal substantial damage or even destroy them.Collisions between two or more debris create clouds of smaller debris, which are harder to track and increase overall object density and collision probability. At some point, the debris density couldthen reach a critical value, which would start a chain reaction and the number of space debris would grow exponentially. This phenomenon was first described by Kessler in 1978 and he concluded that it would lead to creation of debris belt, which would vastly complicate satellite operations in LEO. The debris density is already relatively high, as seen from several necessary debris avoidance maneuvers done by Shuttle, before it was discontinued, and ISS. But not all satellites have a propulsion system to avoid collision, hence different methods need to be applied. One of the proposed collision avoidance concepts is called LightForce and it suggests using photon pressure to induce small orbital corrections to deflect debris from colliding. This method is very efficient as seen from theoretical simulations, even few continuous mode 10 kW ground-based lasers, focused by 1.5 m telescopes with adaptive optics, were enough to prevent significant amount of the debris collisions. Simulations were done by propagating all space objects in LEO by 1 year into the future and checking whether the probability of collision was high. For those space objects different ground-based lasers were used to divert them, afterwards collision probabilities were reevaluated. However, the actual accuracy of the LightForce software, which has been developed at NASA AmesResearch Center, depends on the veracity of the input parameters, one of which is the objects ballistic coefficient. It is a measure of bodys ability to overcome air resistance, which has a significant impact on the debris in LEO, and thus it is responsible for the shape of the trajectory of the debris. Having the exact values of the ballistic coefficient would make significantly better collision predictions, unfortunately, we do not know what are the values for most of the objects.In this research, we were working with part of LightForce code, which estimates the ballistic coefficient from ephemerides. Previously used method gave highly inaccurate values, when compared to known objects, and it needed to be changed. The goal of this work was to try out a different method of estimating the ballistic coefficient and to check whether or not it gives noticeable improvements.

Collisions↗