Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “TRAJECTORIES”

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 379 records · Page 21

Performance of Trajectory Models with Wind Uncertainty

Typical aircraft trajectory predictors use wind forecasts but do not account for the forecast uncertainty. A method for generating estimates of wind prediction uncertainty is described and its effect on aircraft trajectory prediction uncertainty is investigated. The procedure for estimating the wind prediction uncertainty relies uses a time-lagged ensemble of weather model forecasts from the hourly updated Rapid Update Cycle (RUC) weather prediction system. Forecast uncertainty is estimated using measures of the spread amongst various RUC time-lagged ensemble forecasts. This proof of concept study illustrates the estimated uncertainty and the actual wind errors, and documents the validity of the assumed ensemble-forecast accuracy relationship. Aircraft trajectory predictions are made using RUC winds with provision for the estimated uncertainty. Results for a set of simulated flights indicate this simple approach effectively translates the wind uncertainty estimate into an aircraft trajectory uncertainty. A key strength of the method is the ability to relate uncertainty to specific weather phenomena (contained in the various ensemble members) allowing identification of regional variations in uncertainty.

Lee, Alan G.↗

Improving Separation Assurance Stability Through Trajectory Flexibility Preservation

New information and automation technologies are enabling the distribution of tasks and decisions from the service providers to the users of the air traffic system, with potential capacity and cost benefits. This distribution of tasks and decisions raises the concern that independent user actions will decrease the predictability and increase the complexity of the traffic system, hence inhibiting and possibly reversing any potential benefits. One such concern is the adverse impact of uncoordinated actions by individual aircraft on the stability of separation assurance. For example, individual aircraft performing self-separation may resolve predicted losses of separation or conflicts with some traffic, only to result in secondary conflicts with other traffic or with the same traffic later in time. In answer to this concern, this paper proposes metrics for preserving user trajectory flexibility to be used in self-separation along with other objectives. The hypothesis is that preserving trajectory flexibility will naturally reduce the creation of secondary conflicts by bringing about implicit coordination between aircraft. The impact of using these metrics on improving self-separation stability is investigated by measuring the impact on secondary conflicts. The scenarios analyzed include aircraft in en route airspace with each aircraft meeting a required time of arrival in a twenty minute time horizon while maintaining separation from the surrounding traffic and using trajectory flexibility metrics to mitigate the risk of secondary conflicts. Preliminary experiments showed promising results in that the trajectory flexibility preservation reduced the potential for secondary conflicts.

Idris, Husni↗

Definition and Demonstration of a Methodology for Validating Aircraft Trajectory Predictors

This paper presents a new methodology for validating an aircraft trajectory predictor, inspired by the lessons learned from a number of field trials, flight tests and simulation experiments for the development of trajectory-predictor-based automation. The methodology introduces new techniques and a new multi-staged approach to reduce the effort in identifying and resolving validation failures, avoiding the potentially large costs associated with failures during a single-stage, pass/fail approach. As a case study, the validation effort performed by the Federal Aviation Administration for its En Route Automation Modernization (ERAM) system is analyzed to illustrate the real-world applicability of this methodology. During this validation effort, ERAM initially failed to achieve six of its eight requirements associated with trajectory prediction and conflict probe. The ERAM validation issues have since been addressed, but to illustrate how the methodology could have benefited the FAA effort, additional techniques are presented that could have been used to resolve some of these issues. Using data from the ERAM validation effort, it is demonstrated that these new techniques could have identified trajectory prediction error sources that contributed to several of the unmet ERAM requirements.

Vivona, Robert A.↗

The Best Estimated Trajectory Analysis for Pad Abort One

I. Best Estimated Trajectory (BET) objective: a) Produce reconstructed trajectory of the PA-1 flight to understand vehicle dynamics and aid other post flight analyses. b) Leverage all measurement sources taken of vehicle during flight to produce the most accurate estimate of vehicle trajectory. c) Generate trajectory reconstructions of the Crew Module (CM), Launch Abort System (LAS), and Forward Bay Cover (FBC). II. BET analysis was started immediately following the PA-1 mission and was completed in September, 2010 a) Quick look version of BET released 5/25/2010: initial repackaging of SIGI data. b) Preliminary version of BET released 7/6/2010: first blended solution using available sources of external measurements. c) Final version of BET released 9/1/2010: final blended solution using all available sources of data.

Kutty, Prasad↗

Multi Sector Planning Tools for Trajectory-Based Operations

This paper discusses a suite of multi sector planning tools for trajectory-based operations that were developed and evaluated in the Airspace Operations Laboratory (AOL) at the NASA Ames Research Center. The toolset included tools for traffic load and complexity assessment as well as trajectory planning and coordination. The situation assessment tools included an integrated suite of interactive traffic displays, load tables, load graphs, and dynamic aircraft filters. The planning toolset allowed for single and multi aircraft trajectory planning and data communication-based coordination of trajectories between operators. Also newly introduced was a real-time computation of sector complexity into the toolset that operators could use in lieu of aircraft count to better estimate and manage sector workload, especially in situations with convective weather. The tools were used during a joint NASA/FAA multi sector planner simulation in the AOL in 2009 that had multiple objectives with the assessment of the effectiveness of the tools being one of them. Current air traffic control operators who were experienced as area supervisors and traffic management coordinators used the tools throughout the simulation and provided their usefulness and usability ratings in post simulation questionnaires. This paper presents these subjective assessments as well as the actual usage data that was collected during the simulation. The toolset was rated very useful and usable overall. Many elements received high scores by the operators and were used frequently and successfully. Other functions were not used at all, but various requests for new functions and capabilities were received that could be added to the toolset.

Prevot, Thomas↗

Hayabusa Re-Entry: Trajectory Analysis and Observation Mission Design

On June 13th, 2010, the Hayabusa sample return capsule successfully re-entered Earth s atmosphere over the Woomera Prohibited Area in southern Australia in its quest to return fragments from the asteroid 1998 SF36 Itokawa . The sample return capsule entered at a super-orbital velocity of 12.04 km/sec (inertial), making it the second fastest human-made object to traverse the atmosphere. The NASA DC-8 airborne observatory was utilized as an instrument platform to record the luminous portion of the sample return capsule re-entry (~60 sec) with a variety of on-board spectroscopic imaging instruments. The predicted sample return capsule s entry state information at ~200 km altitude was propagated through the atmosphere to generate aerothermodynamic and trajectory data used for initial observation flight path design and planning. The DC- 8 flight path was designed by considering safety, optimal sample return capsule viewing geometry and aircraft capabilities in concert with key aerothermodynamic events along the predicted trajectory. Subsequent entry state vector updates provided by the Deep Space Network team at NASA s Jet Propulsion Laboratory were analyzed after the planned trajectory correction maneuvers to further refine the DC-8 observation flight path. Primary and alternate observation flight paths were generated during the mission planning phase which required coordination with Australian authorities for pre-mission approval. The final observation flight path was chosen based upon trade-offs between optimal viewing requirements, ground based observer locations (to facilitate post-flight trajectory reconstruction), predicted weather in the Woomera Prohibited Area and constraints imposed by flight path filing deadlines. To facilitate sample return capsule tracking by the instrument operators, a series of two racetrack flight path patterns were performed prior to the observation leg so the instruments could be pointed towards the region in the star background where the sample return capsule was expected to become visible. An overview of the design methodologies and trade-offs used in the Hayabusa re-entry observation campaign are presented.

Cassell, Alan M.↗

Dynamic Weather Routes: A Weather Avoidance Concept for Trajectory-Based Operations

The integration of convective weather modeling with trajectory automation for conflict detection, trial planning, direct routing, and auto resolution has uncovered a concept that could help controllers, dispatchers, and pilots identify improved weather routes that result in significant savings in flying time and fuel burn. Trajectory automation continuously and automatically monitors aircraft in flight to find those that could potentially benefit from improved weather reroutes. Controllers, dispatchers, and pilots then evaluate reroute options to assess their suitability given current weather and traffic. In today's operations aircraft fly convective weather avoidance routes that were implemented often hours before aircraft approach the weather and automation does not exist to automatically monitor traffic to find improved weather routes that open up due to changing weather conditions. The automation concept runs in real-time and employs two keysteps. First, a direct routing algorithm automatically identifies flights with large dog legs in their routes and therefore potentially large savings in flying time. These are common - and usually necessary - during convective weather operations and analysis of Fort Worth Center traffic shows many aircraft with short cuts that indicate savings on the order of 10 flying minutes. The second and most critical step is to apply trajectory automation with weather modeling to determine what savings could be achieved by modifying the direct route such that it avoids weather and traffic and is acceptable to controllers and flight crews. Initial analysis of Fort Worth Center traffic suggests a savings of roughly 50% of the direct route savings could be achievable.The core concept is to apply trajectory automation with convective weather modeling in real time to identify a reroute that is free of weather and traffic conflicts and indicates enough time and fuel savings to be considered. The concept is interoperable with today's integrated FMS/datalink. Auxiliary(lat/long) waypoints define a minimum delay reroute between current position and a downstream capture fix beyond the weather. These auxiliary waypoints can be uplinked to equipped aircraft and auto-loaded into the FMS. Alternatively, for unequipped aircraft, auxiliary waypoints can be replaced by nearby named fixes, but this could reduce potential savings. The presentation includes an overview of the automation approach and focuses on several cases in terms of potential savings, reroute complexity, best auxiliary waypoint solution vs. named fix solution, and other metrics.

McNally, B. David↗

Patched Conic Trajectory Code

PatCon code was developed to help mission designers run trade studies on launch and arrival times for any given planet. Initially developed in Fortran, the required inputs included launch date, arrival date, and other orbital parameters of the launch planet and arrival planets at the given dates. These parameters include the position of the planets, the eccentricity, semi-major axes, argument of periapsis, ascending node, and inclination of the planets. With these inputs, a patched conic approximation is used to determine the trajectory. The patched conic approximation divides the planetary mission into three parts: (1) the departure phase, in which the two relevant bodies are Earth and the spacecraft, and where the trajectory is a departure hyperbola with Earth at the focus; (2) the cruise phase, in which the two bodies are the Sun and the spacecraft, and where the trajectory is a transfer ellipse with the Sun at the focus; and (3) the arrival phase, in which the two bodies are the target planet and the spacecraft, where the trajectory is an arrival hyperbola with the planet as the focus.

Park, Brooke Anderson↗

Mars Sample Return Using Commercial Capabilities: ERV Trajectory and Capture Requirements

Mars Sample Return was presented as the highest priority planetary science mission of the next decade [1]. Lemke et al. [2] present a Mars Sample Return mission concept in which the sample is returned directly from the surface of Mars to an Earth orbit. The sample is recovered in Earth Orbit instead of being transferred between spacecraft in Mars Orbit. This paper provides the details of this sample recovery in Earth orbit and presents as such a sub-element of the overall Mars sample return concept given in [2]. We start from the assumption that a Mars Ascent Vehicle (MAV), initially landed on Mars using a modified SpaceX Dragon capsule, has successfully delivered the sample, already contained within an Earth Return Vehicle (ERV), to a parking orbit around Mars. From the parking orbit, the ERV imparts sufficient Delta-V to inject itself into an earthbound trajectory and to be captured into an Earth orbit eventually. We take into account launch window and Delta-V considerations as well as the additional constraint of increased safety margins imposed by planetary protection regulations. We focus on how to overcome two distinct challenges of the sample return that are driven by the issues of planetary protection: (1) the design of an ERV trajectory meeting all the requirements including the need to avoid contamination of Earth's atmosphere; (2) the concept of operations for retrieving the Martian samples in Earth orbit in a safe way. We present an approach to retrieve the samples through a rendezvous between the ERV and a second SpaceX Dragon capsule. The ERV executes a trajectory that brings it from low Mars orbit (LMO) to a Moon-trailing Earth orbit at high inclination with respect to the Earth-Moon plane. After a first burn at Trans-Earth Injection (TEI), the trajectory uses a second burn at perigee during an Earth flyby maneuver to capture the ERV in Earth orbit. The ERV then uses a non-propulsive Moon flyby to come to a near-circular Moon-trailing orbit. To perform the Earth Orbit Rendezvous (EOR), a second Dragon capsule is then launched from Earth and a similar lunar flyby is performed to rendezvous with the ERV. The requirements for rendezvous, close proximity operations and capture of the sample canister are described. A concept of operations for sample retrieval is presented along with design specifications of the ERV, the required modifications to the Dragon capsule, as well as the hardware, software, sensors, actuators, and capture mechanisms used. In our concept, a container is mounted to the front hatch of Dragon, capable of accommodating the sample canister and sealing it from the rest of the capsule. The sample canister is captured using a robotic arm with a magnetic grappling mechanism. Dragon then performs a propulsive maneuver to return to Earth for a controlled re-entry while the ERV (sans sample container) is left in the Moon trailing orbit. Contingency cases and related mitigation strategies are also discussed, including the advantages and disadvantages of performing the ERV rendezvous with a crew.

Faber, Nicolas F.↗

Visiting Vehicle Ground Trajectory Tool

The International Space Station (ISS) Visiting Vehicle Group needed a targeting tool for vehicles that rendezvous with the ISS. The Visiting Vehicle Ground Trajectory targeting tool provides the ability to perform both realtime and planning operations for the Visiting Vehicle Group. This tool provides a highly reconfigurable base, which allows the Visiting Vehicle Group to perform their work. The application is composed of a telemetry processing function, a relative motion function, a targeting function, a vector view, and 2D/3D world map type graphics. The software tool provides the ability to plan a rendezvous trajectory for vehicles that visit the ISS. It models these relative trajectories using planned and realtime data from the vehicle. The tool monitors ongoing rendezvous trajectory relative motion, and ensures visiting vehicles stay within agreed corridors. The software provides the ability to update or re-plan a rendezvous to support contingency operations. Adding new parameters and incorporating them into the system was previously not available on-the-fly. If an unanticipated capability wasn't discovered until the vehicle was flying, there was no way to update things.

Hamm, Dustin↗

Pair-Wise Trajectory Management-Oceanic (PTM-O)

This document describes the Pair-wise Trajectory Management-Oceanic (PTM-O) Concept of Operations (ConOps). Pair-wise Trajectory Management (PTM) is a concept that includes airborne and ground-based capabilities designed to enable and to benefit from, airborne pair-wise distance-monitoring capability. PTM includes the capabilities needed for the controller to issue a PTM clearance that resolves a conflict for a specific pair of aircraft. PTM avionics include the capabilities needed for the flight crew to manage their trajectory relative to specific designated aircraft. Pair-wise Trajectory Management PTM-Oceanic (PTM-O) is a regional specific application of the PTM concept. PTM is sponsored by the National Aeronautics and Space Administration (NASA) Concept and Technology Development Project (part of NASA's Airspace Systems Program). The goal of PTM is to use enhanced and distributed communications and surveillance along with airborne tools to permit reduced separation standards for given aircraft pairs, thereby increasing the capacity and efficiency of aircraft operations at a given altitude or volume of airspace.

Jones, Kenneth M.↗

A Global Ozone Climatology from Ozone Soundings via Trajectory Mapping: A Stratospheric Perspective

This study explores a domain-filling trajectory approach to generate a global ozone climatology from sparse ozonesonde data. Global ozone soundings of 51,898 profiles at 116 stations over 44 years (1965-2008) are used, from which forward and backward trajectories are performed for 4 days, driven by a set of meteorological reanalysis data. Ozone mixing ratios of each sounding from the surface to 26 km altitude are assigned to the entire path along the trajectory. The resulting global ozone climatology is archived monthly for five decades from the 1960s to the 2000s with grids of 5 degree 5 degree 1 km (latitude, longitude, and altitude). It is also archived yearly from 1965 to 2008. This climatology is validated at 20 ozonesonde stations by comparing the actual ozone sounding profile with that found through the trajectories, using the ozone soundings at all the stations except one being tested. The two sets of profiles are in good agreement, both individually with correlation coefficients between 0.975 and 0.998 and root mean square (RMS) differences of 87 to 482 ppbv, and overall with a correlation coefficient of 0.991 and an RMS of 224 ppbv. The ozone climatology is also compared with two sets of satellite data, from the Satellite Aerosol and Gas Experiment (SAGE) and the Optical Spectrography and InfraRed Imager System (OSIRIS). Overall, the ozone climatology compares well with SAGE and OSIRIS data by both seasonal and zonal means. The mean difference is generally under 20 above 15 km. The comparison is better in the northern hemisphere, where there are more ozonesonde stations, than in the southern hemisphere; it is also better in the middle and high latitudes than in the tropics, where assimilated winds are imperfect in some regions. This ozone climatology can capture known features in the stratosphere, as well as seasonal and decadal variations of these features. Furthermore, it provides a wealth of detail about longitudinal variations in the stratosphere such as the spring ozone maximum over the Canadian Arctic. It also covers higher latitudes than current satellite data. The climatology shows clearly the depletion of ozone from the 1970s to the mid 1990s and ozone recovery in the 2000s. When this climatology is used as the upper boundary condition in an Environment Canada operational chemical forecast model, the forecast is improved in the vicinity of the upper tropospherelower stratosphere region. As this ozone climatology is neither dependent on a priori data or photochemical modeling, it provides independent information and insight that can supplement satellite data and model simulations and enhance our understanding of stratospheric ozone.

SAGE↗

Design of the VISITOR Tool: A Versatile ImpulSive Interplanetary Trajectory OptimizeR

The design of trajectories for interplanetary missions represents one of the most complex and important problems to solve during conceptual space mission design. To facilitate conceptual mission sizing activities, it is essential to obtain sufficiently accurate trajectories in a fast and repeatable manner. To this end, the VISITOR tool was developed. This tool modularly augments a patched conic MGA-1DSM model with a mass model, launch window analysis, and the ability to simulate more realistic arrival and departure operations. This was implemented in MATLAB, exploiting the built-in optimization tools and vector analysis routines. The chosen optimization strategy uses a grid search and pattern search, an iterative variable grid method. A genetic algorithm can be selectively used to improve search space pruning, at the cost of losing the repeatability of the results and increased computation time. The tool was validated against seven flown missions: the average total mission (Delta)V offset from the nominal trajectory was 9.1%, which was reduced to 7.3% when using the genetic algorithm at the cost of an increase in computation time by a factor 5.7. It was found that VISITOR was well-suited for the conceptual design of interplanetary trajectories, while also facilitating future improvements due to its modular structure.

Corpaccioli, Luca↗

An Evaluation of a Flight Deck Interval Management Algorithm Including Delayed Target Trajectories

NASA's first Air Traffic Management (ATM) Technology Demonstration (ATD-1) was created to facilitate the transition of mature air traffic management technologies from the laboratory to operational use. The technologies selected for demonstration are the Traffic Management Advisor with Terminal Metering (TMA-TM), which provides precise timebased scheduling in the terminal airspace; Controller Managed Spacing (CMS), which provides controllers with decision support tools enabling precise schedule conformance; and Interval Management (IM), which consists of flight deck automation that enables aircraft to achieve or maintain precise in-trail spacing. During high demand operations, TMA-TM may produce a schedule and corresponding aircraft trajectories that include delay to ensure that a particular aircraft will be properly spaced from other aircraft at each schedule waypoint. These delayed trajectories are not communicated to the automation onboard the aircraft, forcing the IM aircraft to use the published speeds to estimate the target aircraft's estimated time of arrival. As a result, the aircraft performing IM operations may follow an aircraft whose TMA-TM generated trajectories have substantial speed deviations from the speeds expected by the spacing algorithm. Previous spacing algorithms were not designed to handle this magnitude of uncertainty. A simulation was conducted to examine a modified spacing algorithm with the ability to follow aircraft flying delayed trajectories. The simulation investigated the use of the new spacing algorithm with various delayed speed profiles and wind conditions, as well as several other variables designed to simulate real-life variability. The results and conclusions of this study indicate that the new spacing algorithm generally exhibits good performance; however, some types of target aircraft speed profiles can cause the spacing algorithm to command less than optimal speed control behavior.

Swieringa, Kurt A.↗

Lunar Cube Transfer Trajectory Options

Contingent upon the modification of an initial condition of the injected or deployed orbit. Additionally, these designs can be restricted by the selection of the Cubesat subsystem design such as propulsion or communication. Nonetheless, many trajectory options can be designed with have a wide range of transfer durations, fuel requirements, and final destinations. Our investigation of potential trajectories highlights several design options including deployment into low Earth orbit (LEO), geostationary transfer orbits (GTO), and higher energy direct lunar transfer orbits. In addition to direct transfer options from these initial orbits, we also investigate the use of longer duration Earth-Moon dynamical systems. For missions with an intended lunar orbit, much of the design process is spent optimizing a ballistic capture while other science locations such as Sun-Earth libration or heliocentric orbits may simply require a reduced Delta-V imparted at a convenient location along the trajectory. In this article we examine several design options that meet the above limited deployment and subsystem drivers. We study ways that both impulsive and low-thrust Solar Electric Propulsion (SEP) engines can be used to place the Cubesat first into a highly eccentric Earth orbit, enter the Moon's Sphere of Influence, and finally achieve a highly eccentric lunar orbit. We show that such low-thrust transfers are feasible with a realistic micro-thruster model, assuming that the Cubesat can generate sufficient power for the SEP. Two examples are shown here: (1) A Cubestat injected by Exploration Mission 1 (EM-1) then employing low thrust; and (2) a CubSat deployed in a GTO, then employing impulsive maneuvers. For the EM-1 injected initial design, we increase the EM-1 targeted lunar flyby distance to reduce the energy of the lunar flyby to match that of a typical lMoon system heteroclinic manifold. Figure 1 presents an option that encompasses the similar dynamics as that of the ARTEMIS mission design. Low-thrust maneuvers are used along the manifold trajectory to raise perigee to that of a lunar orbit, adjust the timing with respect to the Moon, rotate the line of apsides, and target a ballistic lunar encounter. In this design a second flyby decreases the orbital energy with respect to the Moon, so that C3 -0.1 km2s2. Another design, shown in Figure 2 emanates from a GTO then uses impulsive maneuvers to phase onto a local Earth-Moon manifold, which then transfers the CubeSat to a lunar encounter.

Dynamical System↗

Broad Search Solar Electric Propulsion Trajectories to Saturn with Gravity Assists

Solar electric propulsion (SEP) trajectories to Saturn using multiple gravity assists are explored for the joint NASA and ESA Titan Saturn System Mission study. Results show that these new trajectories enable greater performance compared to chemical propulsion with similar gravity assists or SEP without gravity assists. This paper describes the method used in finding these interplanetary trajectories and examines variations in the performance for different SEP systems, flight times, and flyby sequences. The benefits of the SEP trajectories for a mission to Saturn are also discussed.

Titan↗

Trajectory Reconstruction of the ST-9 Sounding Rocket Experiment Using IMU and Landmark Data

This paper presents trajectory reconstruction of the ST-9 sounding rocket experiment using the onboard IMU data and descent imagery. The raw IMU accelerometer measurements are first converted into inertial acceleration and then used in trajectory integration. The descent images are pre-processed using a map-matching algorithm and unique landmarks for each image are created. Using the converted IMU data and descent images, the result from dead-reckoning and the kinematic-fix approaches are first compared with the GPS measurements. Then, both the IMU data and landmarks are processed together using a batch least-squares filter and the position, velocity, stochastic acceleration, and camera orientation of each image are estimated. The reconstructed trajectory is compared with the GPS data and the corresponding formal uncertainties are presented. The result shows that IMU data and descent images processed with a batch filter algorithm provide the trajectory accuracy required for pin-point landing.

Park, Ryan S.↗

Orion Exploration Flight Test 1 (EFT-1) Best Estimated Trajectory Development

The Orion Exploration Flight Test 1 (EFT-1) mission successfully flew on Dec 5, 2014 atop a Delta IV Heavy launch vehicle. The goal of Orions maiden flight was to stress the system by placing an uncrewed vehicle on a high-energy trajectory replicating conditions similar to those that would be experienced when returning from an asteroid or a lunar mission. The Orion navigation team combined all trajectory data from the mission into a Best Estimated Trajectory (BET) product. There were significant challenges in data reconstruction and many lessons were learned for future missions. The team used an estimation filter incorporating radar tracking, onboard sensors (Global Positioning System and Inertial Measurement Unit), and day-of-flight weather balloons to evaluate the true trajectory flown by Orion. Data was published for the entire Orion EFT-1 flight, plus objects jettisoned during entry such as the Forward Bay Cover. The BET customers include approximately 20 disciplines within Orion who will use the information for evaluating vehicle performance and influencing future design decisions.

Holt, Greg N.↗