Search NASA⌕ Search

SEARCH · Search NASA

Results for “trajectory planning”

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 433 records · Page 24

Earth return maneuver strategies for Genesis and Stardust

As part of NASA's Discovery Program, Genesis and Stardust will be the first missions since the Apollo Program to return samples collected in deep space. To constrain costs of recovery, entry requirements must be much tighter than those imposed on Apollo. Spacecraft designs were also greatly simplified to limit costs, giving rise to a variety of operational limitations and constraints. In light of these considerations, approach to Earth presents a challenge in terms of both mission planning and navigation. This paper discusses strategies for trajectory correction during the Earth return phases of both missions.

Williams, Kenneth E.↗

Uncertainty Optimization Applied to the Monte Carlo Analysis of Planetary Entry Trajectories

Recently, strong evidence of liquid water under the surface of Mars and a meteorite that might contain ancient microbes have renewed interest in Mars exploration. With this renewed interest, NASA plans to send spacecraft to Mars approx. every 26 months. These future spacecraft will return higher-resolution images, make precision landings, engage in longer-ranging surface maneuvers, and even return Martian soil and rock samples to Earth. Future robotic missions and any human missions to Mars will require precise entries to ensure safe landings near science objective and pre-employed assets. Potential sources of water and other interesting geographic features are often located near hazards, such as within craters or along canyon walls. In order for more accurate landings to be made, spacecraft entering the Martian atmosphere need to use lift to actively control the entry. This active guidance results in much smaller landing footprints. Planning for these missions will depend heavily on Monte Carlo analysis. Monte Carlo trajectory simulations have been used with a high degree of success in recent planetary exploration missions. These analyses ascertain the impact of off-nominal conditions during a flight and account for uncertainty. Uncertainties generally stem from limitations in manufacturing tolerances, measurement capabilities, analysis accuracies, and environmental unknowns. Thousands of off-nominal trajectories are simulated by randomly dispersing uncertainty variables and collecting statistics on forecast variables. The dependability of Monte Carlo forecasts, however, is limited by the accuracy and completeness of the assumed uncertainties. This is because Monte Carlo analysis is a forward driven problem; beginning with the input uncertainties and proceeding to the forecasts outputs. It lacks a mechanism to affect or alter the uncertainties based on the forecast results. If the results are unacceptable, the current practice is to use an iterative, trial-and-error approach to reconcile discrepancies. Therefore, an improvement to the Monte Carlo analysis is needed that will allow the problem to be worked in reverse. In this way, the largest allowable dispersions that achieve the required mission objectives can be determined quantitatively.

Olds, John↗

Overview and Software Architecture of the Copernicus Trajectory Design and Optimization System

The Copernicus Trajectory Design and Optimization System represents an innovative and comprehensive approach to on-orbit mission design, trajectory analysis and optimization. Copernicus integrates state of the art algorithms in optimization, interactive visualization, spacecraft state propagation, and data input-output interfaces, allowing the analyst to design spacecraft missions to all possible Solar System destinations. All of these features are incorporated within a single architecture that can be used interactively via a comprehensive GUI interface, or passively via external interfaces that execute batch processes. This paper describes the Copernicus software architecture together with the challenges associated with its implementation. Additionally, future development and planned new capabilities are discussed. Key words: Copernicus, Spacecraft Trajectory Optimization Software.

Williams, Jacob↗

Trajectory Orientation: A Technology-Enabled Concept Requiring a Shift in Controller Roles and Responsibilities

The development of a decision support tool (DST) for the en-route domain with accurate conflict prediction time horizons of 20 minutes has introduced an interesting problem. A 20 minute time horizon for conflict prediction often results in the predicted conflict occurring one or more sectors downstream from the sector controller who "owns" (i-e., is responsible for the safe separation of aircraft) one or both of the aircraft in the conflict pair. Based on current roles and responsibilities of today's en route controllers, the upstream controller would not resolve this conflict. In most cases, the downstream controller would wait until the conflicting aircraft entered higher sector before resolving the conflict. This results in a delay of several minutes from the time when the conflict was initially predicted. This delay is inefficient from both a controller workload and user's cost of operations perspective. Trajectory orientation, a new concept for facilitating an efficient, conflict-free flight path across several sectors while conforming to metering or miles-in-trail spacing, is proposed as an alternative to today's sector-oriented method. This concept necessitates a fundamental shift in thinking about inter-sector coordination. Instead of operating independently, with the main focus on protecting their internal airspace, controllers would work cooperatively, depending on each other for well-planned, conflict-free flow of aircraft. To support the trajectory orientation concept, a long time horizon (15 to 20 minutes) for conflict prediction and resolution would most likely be a primary requirement. In addition, new tools, such as controller-pilot data link will be identified to determine their necessity and applicability for trajectory orientation. Finally, with significant controller participation from selected Air Route Traffic Control Centers, potential shifts in R-side/D-side roles and responsibilities as well as the creation of a new controller position for multi-sector planning will be examined to determine the most viable solutions.

Leiden, Ken↗

The Cassini Grand Finale Mission: Planning for a New Mission Environment

The Cassini F-Ring & Proximal Orbits (FRPO) is a new and unique mission; to ensure the highest priority science gets implemented, the POST (Proximal Orbit Science Team) was created to pre-allocate the time around periapse for all 22 proximal orbits. The F-ring orbits, and proximal time outside of POST, were handled similar to Cassini’s Solstice Mission using the Pre-Integrated Event (PIE) process. The new and unique properties of the spacecraft’s trajectory required much forethought to be flown safely while still planning for the most and best science return possible. Some ring-plane crossings (RPX) will be protected against dust impacts by turning the high gain antenna (HGA) to the dust RAM direction (HGA2RAM). If on the first proximal RPX higher than expected dust readings are seen then the Project Office may choose to require more (all) subsequent RPX to be HGA2RAM, implemented via a real-time command overlay for uplinked sequences. The pointing uncertainties will be larger than usual after the final targeted flyby; some of the process changes to address this include adding extra orbit trim maneuvers (OTMs) (fuel permitting) to resync to the reference trajectory and reduce pointing uncertainties; and movable blocks of commands to be used for some periapses where atmospheric drag may cause large timing shifts Changes made for FRPO to address perceptions that these sequences will be hard to implement include requiring early pointing designs (during integration) for certain types of observations, requiring teams to check early on that they can turn to and from their observation attitude, and that their attitude is safe, and adjusting the Implementation process to give more time for science observation designers. This paper will discuss these process changes and lessons learned so far.

Ray, Trina↗

An interactive tool for design and support of lunar, gravity assist, and libration point trajectories

The 'Swingby' interactive tool for design, analysis, and support of maneuver planning for missions that involve transfers to the moon, the lunar orbits, multiple-gravity assists, and the libration-point orbits, runs on a PC and uses pull-down and pop-up menus to allow users to change physical constants and select perturbations for inclusion. Swingby can also target by ascertain parameters, or allow the computer to generate goals on the basis of mission requirements. Rapid mission analyses, operational maneuvers, and contingency plans are thereby obtainable.

Carrico, J.↗

Trajectory-Oriented Approach to Managing Traffic Complexity: Trajectory Flexibility Metrics and Algorithms and Preliminary Complexity Impact Assessment

This document describes exploratory research on a distributed, trajectory oriented approach for traffic complexity management. The approach is to manage traffic complexity based on preserving trajectory flexibility and minimizing constraints. In particular, the document presents metrics for trajectory flexibility; a method for estimating these metrics based on discrete time and degree of freedom assumptions; a planning algorithm using these metrics to preserve flexibility; and preliminary experiments testing the impact of preserving trajectory flexibility on traffic complexity. The document also describes an early demonstration capability of the trajectory flexibility preservation function in the NASA Autonomous Operations Planner (AOP) platform.

Idris, Husni↗

A Sampling Based Approach to Spacecraft Autonomous Maneuvering with Safety Specifications

This paper presents a methods for safe spacecraft autonomous maneuvering that leverages robotic motion-planning techniques to spacecraft control. Specifically the scenario we consider is an in-plan rendezvous of a chaser spacecraft in proximity to a target spacecraft at the origin of the Clohessy Wiltshire Hill frame. The trajectory for the chaser spacecraft is generated in a receding horizon fashion by executing a sampling based robotic motion planning algorithm name Fast Marching Trees (FMT) which efficiently grows a tree of trajectories over a set of probabillistically drawn samples in the state space. To enforce safety the tree is only grown over actively safe samples for which there exists a one-burn collision avoidance maneuver that circularizes the spacecraft orbit along a collision-free coasting arc and that can be executed under potential thrusters failures. The overall approach establishes a provably correct framework for the systematic encoding of safety specifications into the spacecraft trajectory generations process and appears amenable to real time implementation on orbit. Simulation results are presented for a two-fault tolerant spacecraft during autonomous approach to a single client in Low Earth Orbit.

Spacecraft↗

OSIRIS-REx Screening Experience & Lessons Learned

On September 24, 2023, the NASA OSIRIS-REx spacecraft returned a sample of asteroid Bennu, approaching on a hyperbolic impact trajectory relative to Earth. At approximately 108,000 km altitude and four hours prior to hitting the top of the atmosphere, the Sample Return Capsule (SRC) separated from the spacecraft bus, targeting the Utah Test and Training Range. Twenty minutes later, the bus performed a large divert maneuver to fly by at a perigee altitude of ~780 km. Given the immense scientific value of the sample, substantial efforts were undertaken by NASA CARA and the OSIRIS-REx mission to ensure safe passage of the objects from GEO through LEO. This presentation provides an overview of collision avoidance maneuver (CAM) options, results of screenings, coordination with DoD for contingency observations, and lessons learned for screening future Earth flyby and entry trajectories. Two particular challenges included screening two objects using a much larger than normal 250 km spherical monitor volume and decision planning for a single CAM while the SRC was still attached that would alter both trajectories. The larger, non-standard screening volume resulted in custom procedures that CARA personnel had to run manually for each screening, and the initial long propagation times while the objects were more than a week out required significant computing resources. With a single CAM opportunity at 13 hours out, the decision to execute a maneuver had to consider the risk to both objects, where one could imagine a situation where the maneuver would clear a high-risk conjunction for one object and introduce one for the other – begging the question of relative risk posture between the SRC and bus. These among other unique aspects of Earth flyby and entry missions led to novel planning and implementation procedures to support future missions of this type.

Dolan E. Highsmith↗

Steps Towards the Integration of Conflict Resolution with Metering and Scheduling

NASA Ames Research Center is developing decision support tool technology for air traffic controllers to improve the efficiency and capacity of National Airspace System. The goal is to provide technology, tools and procedures that result in the highest possible level of user preferred trajectories whenever possible with safe and efficient traffic management when necessary. The work is being conducted under the NASA Advanced Air Transportation Technology Program in cooperation with the FAA through the Inter-Agency Integrated Product Team. The objective is to develop technology and procedures that lead towards a seamless integration of conflict resolution with metering and scheduling for arrival aircraft and en route aircraft that are under metering restrictions. A requirement is that the integration incorporate user preferred trajectories. The ultimate goal is the implementation and validation of the Descent Advisor (DA) concept which provides clearance advisories to a sector controller that simultaneously meet metering constraints, are conflict free, incorporate a user preferred (e.g., minimum fuel) descent profile, and generally require no further corrective clearance as the aircraft transitions from en route cruise into the TRACON. The DA concept may also be applied to en route aircraft under metering constraints, e.g., miles-in-trail. To achieve the DA concept a stepwise development and field evaluation is anticipated. This paper addresses the initial steps towards implementation of the DA. The Traffic Management Advisor (TMA) computes arrival time sequence and required delay information for display to the sector controller during periods when arrivals must be metered due to landing rate restrictions at the airport. The Initial Conflict Probe (ICP) compares trajectory predictions for all aircraft and alerts the controller when any two aircraft are predicted to violate separation standards (5 mi. and 2000 ft. in en route airspace). ICP also includes a trial planning function allowing the controller to develop and check a separate "what if" trajectory for conflict resolution. TMA and ICP currently operate independent of one another and have separate controller displays. The TMA meter list is on the radar controller's plan view display. The ICP is still under development, but the current concept calls for a list of predicted conflicts at the data controller position. The research described herein address two steps towards the implementation of DA. The first is to develop a concept for integrated display of conflict and metering information on a controller's display. The objective is to provide the controller with situational awareness of one problem while he develops a solution to the other. The next step is to expand the concept for display of automated clearance advisories for one problem (e.g., metering) which take into account the other problems (e.g., conflicts). Information to be communicated between TMA and ICP to facilitate' manual or automated advisories is being identified as the concept matures. In order to study the ICP/TMA integration concept the CTAS conflict probe capability has been adapted to Ft. Worth Center. The system is being validated in the laboratory with all-track data and for non -interference with TMA, TMA is already running as a daily use prototype at Ft. Worth Center. A laboratory prototype system has been developed under the CTAS baseline which combines conflict and metering information on a common user interface. Elements of the user interface are shown in Figure 1. In this simple illustration the user sees the simultaneous effect of a trial plan on meter fix delay and conflict status. Delay information is shown in the aircraft flight data block, the meter list, and the TMA timeline. Experience during Descent Advisor development and observations at Ft. Worth Center high and low attitude arrival sectors during metering suggests that manual trial planning will be unworkable during rush periods due to high controller workload.

McNally, B. David↗

An Efficient Method to Design Premature End-of-Life Trajectories: A Hypothetical Alternate Fate for Cassini

What would happen if, hypothetically, the highly successful Cassini mission were to end prematurely due to lack of propellant or sudden subsystem failure? A solid plan to quickly produce a solution for any given scenario, regardless of where the spacecraft is along its reference path, must be in place to safely dispose of the spacecraft and meet all planetary protection requirements. As a contingency plan for this hypothetical situation, a method to design viable high-fidelity terminating trajectories based on a hybrid approach that exploits two-body and three-body flyby transfers combined with a numerical optimization scheme is detailed in this paper.

end-of-mission↗

Descent guidance and mission planning for space shuttle

The Space Shuttle descent mission planning, mission design, deorbit targeting, and entry guidance have necessarily become interrelated because of the nature of the Orbiter's design and mission requirements. The desired descent trajectory has been formulated in a drag acceleration/relative velocity state space since nearly all of the vehicle's highly constraining flight limitations can be uniquely represented in this plane. Constraints and flight requirements that affect the descent are described. The guidance logic which allows the Orbiter to follow the designed trajectory, the impacts of contingency aborts and flightcrew interaction are discussed. The mission planning and guidance techniques remain essentially unchanged through the Shuttle flight test program and subsequent operational flights.

Joosten, B. K.↗

Dawn Orbit Determination Team: Trajectory and Gravity Prediction Performance During Vesta Science Phases

The Dawn spacecraft was launched on September 27th, 2007. Its mission is to consecutively rendezvous with and observe the two largest bodies in the asteroid belt, Vesta and Ceres. It has already completed over a year's worth of direct observations of Vesta (spanning from early 2011 through late 2012) and is currently on a cruise trajectory to Ceres, where it will begin scientific observations in mid-2015. Achieving this data collection required careful planning and execution from all spacecraft teams. Dawn's Orbit Determination (OD) team was tasked with accurately predicting the trajectory of the Dawn spacecraft during the Vesta science phases, and also determining the parameters of Vesta to support future science orbit design. The future orbits included the upcoming science phase orbits as well as the transfer orbits between science phases. In all, five science phases were executed at Vesta, and this paper will describe some of the OD team contributions to the planning and execution of those phases.

gravity gradient torque↗

Air Traffic Complexity Measurement Environment (ACME): Software User's Guide

A user's guide for the Air Traffic Complexity Measurement Environment (ACME) software is presented. The ACME consists of two major components, a complexity analysis tool and user interface. The Complexity Analysis Tool (CAT) analyzes complexity off-line, producing data files which may be examined interactively via the Complexity Data Analysis Tool (CDAT). The Complexity Analysis Tool is composed of three independently executing processes that communicate via PVM (Parallel Virtual Machine) and Unix sockets. The Runtime Data Management and Control process (RUNDMC) extracts flight plan and track information from a SAR input file, and sends the information to GARP (Generate Aircraft Routes Process) and CAT (Complexity Analysis Task). GARP in turn generates aircraft trajectories, which are utilized by CAT to calculate sector complexity. CAT writes flight plan, track and complexity data to an output file, which can be examined interactively. The Complexity Data Analysis Tool (CDAT) provides an interactive graphic environment for examining the complexity data produced by the Complexity Analysis Tool (CAT). CDAT can also play back track data extracted from System Analysis Recording (SAR) tapes. The CDAT user interface consists of a primary window, a controls window, and miscellaneous pop-ups. Aircraft track and position data is displayed in the main viewing area of the primary window. The controls window contains miscellaneous control and display items. Complexity data is displayed in pop-up windows. CDAT plays back sector complexity and aircraft track and position data as a function of time. Controls are provided to start and stop playback, adjust the playback rate, and reposition the display to a specified time.

Source record↗

Space Flight Handbooks. Volume 3, Planetary Flight Handbook: Mars Stopover Missions Using Venus Swingbys - Part 6

This volume of the NASA Planetary Flight Handbook contains trajectory data to aid the mission analyst in the planning of stopover missions to Mars that employ the Venus swingby mode. Compared to other mission modes, the Venus swingbys yield substantial reductions in propulsive velocity and Earth entry speed requirements when employed as part of a round trip stopover mission. Conversely, the swingbys are at best, of marginal utility for one-way missions. Consequently, this Handbook has been tailored expressly for use in the planning of round trip missions. The relevant charts, graphs, and tabular data are presented for the totality of such missions, i.e., in terms of total round trip mission duration and stopover time at Mars. Recognizing, however, that within the context of round trip missions the single-leg data can be of importance in certain phases of the mission analyses, all such data has been preserved on a master magnetic tape. Copies of this tape will be made available to interested organizations.

Source record↗

Launch mission summary: INTELSAT 5(F1) ATLAS/CENTAUR-56

The technology and capability of the INTELSAT 5 series satellites and the Atlas-Centaur launch vehicle are described. Data relative to launch windows, flight plans, radar, and telemetry are included along with selected trajectory information and a sequence of flight events.

Source record↗

Halo-orbit and lunar-swingby missions of the 1990's

A significant number of spacecraft are planning to use halo orbits and lunar-swingby trajectories in the next decade. Four spacecraft will be placed into halo orbits around the earth's sunward libration point, while two others will be stationed near the sun-earth L2 libration point in the distant geomagnetic tail. Six spacecraft, including two of the aforementioned halo orbiters, will make use of lunar-swingby maneuvers to fulfill their mission objectives. Thus, a total of ten spacecraft, five from the Soviet Union, two from Japan, two from the United States, and one from the European Space Agency, will employ halo orbits and/or lunar-swingby trajectories in the 1990's. Pertinent facts are presented for each of these missions.

Farquhar, Robert W.↗

Technologies for automating rotorcraft nap-of-the-earth flight

This paper discusses the technologies required for automating rotorcraft nap-of-the-earth flight, where the use of natural obstacles for masking from the enemy is intentional and the danger of undesirable obstacles such as enemy traps is real. Specifically, the automatic guidance structure is modeled by three decision-making levels: the far-field mission planning and the mid-field terrain-masking trajectory shaping are both driven by prestored terrain data, whereas the nearfield obstacle detection/avoidance is driven by real-time on-board sensor data. This paper summarizes the far-field and mid-field accomplishments, and reports on the status of the more-recent efforts in obstacle detection and avoidance development. Obstacle detection is based primarily on passive imaging sensors for the desirable properties of covertness and wide field of view, although active sensors are included in the structure to provide the much needed high resolution for thin-wire detection.

Cheng, Victor H. L.↗