Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “trajectory constrained scheduling”

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.

28 records · Page 2
All sourcesNASA NTRSDOE OSTI
NASA NTRS1996

Effects of modeling errors on trajectory predictions in air traffic control automation

Air traffic control automation synthesizes aircraft trajectories for the generation of advisories. Trajectory computation employs models of aircraft performances and weather conditions. In contrast, actual trajectories are flown in real aircraft under actual conditions. Since synthetic trajectories are used in landing scheduling and conflict probing, it is very important to understand the differences between computed trajectories and actual trajectories. This paper examines the effects of aircraft modeling errors on the accuracy of trajectory predictions in air traffic control automation. Three-dimensional point-mass aircraft equations of motion are assumed to be able to generate actual aircraft flight paths. Modeling errors are described as uncertain parameters or uncertain input functions. Pilot or autopilot feedback actions are expressed as equality constraints to satisfy control objectives. A typical trajectory is defined by a series of flight segments with different control objectives for each flight segment and conditions that define segment transitions. A constrained linearization approach is used to analyze trajectory differences caused by various modeling errors by developing a linear time varying system that describes the trajectory errors, with expressions to transfer the trajectory errors across moving segment transitions. A numerical example is presented for a complete commercial aircraft descent trajectory consisting of several flight segments.

Jackson, Michael R. C.↗
NASA NTRS2017

Integrated Demand Management: Minimizing Unanticipated Excessive Departure Delay while Ensuring Fairness from a Traffic Management Initiative

This paper introduces NASA's Integrated Demand Management (IDM) concept and presents the results from an early proof-of-concept evaluation and an exploratory experiment. An initial development of the concept was focused on integrating two systems - i.e. the FAA's newly deployed Traffic Flow Management System (TFMS) tool called the Collaborative Trajectory Options Program (CTOP) and the Time-Based Flow Management (TBFM) system with Extended Metering (XM) capabilities to manage projected heavy traffic demand into a capacity-constrained airport. A human-in-the-loop (HITL) simulation experiment was conducted to demonstrate the feasibility of the initial development of the concept by adapting it to an arrival traffic problem at Newark Liberty International Airport (EWR) during clear weather conditions. In this study, the CTOP was utilized to strategically plan the arrival traffic demand by controlling take-off times of both short- and long-haul flights (long-hauls specify aircraft outside TBFM regions and short-hauls specify aircraft within TBFM regions) in a way that results in equitable delays among the groups. Such strategic planning allows less airborne delay to occur within TBFM by feeding manageable long-haul traffic demand while reserving sufficient slots in the overhead streams for the short-haul departures. The manageable traffic demand indicates the TBFM scheduler assigns no more airborne delay than its assigned airspace is capable of absorbing. TBFM then uses its time-based metering capabilities to deliver the desirable throughput by tactically rescheduling the TBFM entered long-haul flights and short-haul departures. Additional research was also performed to explore use of Required Time of Arrival (RTA) capabilities as a potential control mechanism for the airborne flights to improve arrival traffic delivery accuracy of scheduled long-haul traffic demand. The study results show that both short- and long-haul flights received similar ground delays. In addition, there was a noticeable reduction in the total amount of excessive unanticipated last-minute ground delays, i.e. delays that are frequently imposed on the short-haul flight in current day operations due to saturation in the overhead stream, commonly referred to as 'double penalty'. Furthermore, the concept achieved the target throughput while minimizing the expected cost associated with overall delays in arrival traffic. Assessment of the RTA capabilities showed that there was indeed improvement of the scheduled entry times into TBFM regions by using RTA capabilities. However, with respect to reduction in delays incurred within TBFM, there was no observable benefit of improving the precision of long-haul flights entry times.

Collaborative Trajectory Options Program (CTOP)↗
NASA NTRS2016

Wind Information Uplink to Aircraft Performing Interval Management Operations

Interval Management (IM) is an ADS-B-enabled suite of applications that use ground and flight deck capabilities and procedures designed to support the relative spacing of aircraft (Barmore et al., 2004, Murdoch et al. 2009, Barmore 2009, Swieringa et al. 2011; Weitz et al. 2012). Relative spacing refers to managing the position of one aircraft to a time or distance relative to another aircraft, as opposed to a static reference point such as a point over the ground or clock time. This results in improved inter-aircraft spacing precision and is expected to allow aircraft to be spaced closer to the applicable separation standard than current operations. Consequently, if the reduced spacing is used in scheduling, IM can reduce the time interval between the first and last aircraft in an overall arrival flow, resulting in increased throughput. Because IM relies on speed changes to achieve precise spacing, it can reduce costly, low-altitude, vectoring, which increases both efficiency and throughput in capacity-constrained airspace without negatively impacting controller workload and task complexity. This is expected to increase overall system efficiency. The Flight Deck Interval Management (FIM) equipment provides speeds to the flight crew that will deliver them to the achieve-by point at the controller-specified time, i.e., assigned spacing goal, after the target aircraft crosses the achieve-by point (Figure 1.1). Since the IM and target aircraft may not be on the same arrival procedure, the FIM equipment predicts the estimated times of arrival (ETA) for both the IM and target aircraft to the achieve-by point. This involves generating an approximate four-dimensional trajectory for each aircraft. The accuracy of the wind data used to generate those trajectories is critical to the success of the IM operation. There are two main forms of uncertainty in the wind information used by the FIM equipment. The first is the accuracy of the forecast modeling done by the weather provider. This is generally a global environmental prediction obtained from a weather model such as the Rapid Refresh (RAP) from the National Centers for Environmental Prediction (NCEP). The weather forecast data will have errors relative to the actual, or truth, winds that the aircraft will encounter. The second source of uncertainty is that only a small subset of the forecast data can be uplinked to the aircraft for use by the FIM equipment. This results in loss of additional information. The Federal Aviation Administration (FAA) and RTCA are currently developing standards for the communication of wind and atmospheric data to the aircraft for use in NextGen operations. This study examines the impact of various wind forecast sampling methods on IM performance metrics to inform the standards development.

Ahmad, Nashat N.↗
NASA NTRS2000

Sliding Mode Control of the X-33 with an Engine Failure

Ascent flight control of the X-3 is performed using two XRS-2200 linear aerospike engines. in addition to aerosurfaces. The baseline control algorithms are PID with gain scheduling. Flight control using an innovative method. Sliding Mode Control. is presented for nominal and engine failed modes of flight. An easy to implement, robust controller. requiring no reconfiguration or gain scheduling is demonstrated through high fidelity flight simulations. The proposed sliding mode controller utilizes a two-loop structure and provides robust. de-coupled tracking of both orientation angle command profiles and angular rate command profiles in the presence of engine failure, bounded external disturbances (wind gusts) and uncertain matrix of inertia. Sliding mode control causes the angular rate and orientation angle tracking error dynamics to be constrained to linear, de-coupled, homogeneous, and vector valued differential equations with desired eigenvalues. Conditions that restrict engine failures to robustness domain of the sliding mode controller are derived. Overall stability of a two-loop flight control system is assessed. Simulation results show that the designed controller provides robust, accurate, de-coupled tracking of the orientation angle command profiles in the presence of external disturbances and vehicle inertia uncertainties, as well as the single engine failed case. The designed robust controller will significantly reduce the time and cost associated with flying new trajectory profiles or orbits, with new payloads, and with modified vehicles

Shtessel, Yuri B.↗
NASA NTRS2018

Using an Automated Air Traffic Simulation Capability for a Parametric Study in Traffic Flow Management

Flight delays occur when demand for capacity-constrained airspace or airports exceeds predicted capacity. Demand for capacity-constrained airspace or airports can be controlled by a series of Traffic Management Initiatives (TMIs), which use departure and airborne delays, as well as pre-departure and airborne reroutes, to manage access to the constrained resources. Two systems exist in current and planned future operations to address imbalances between demand and capacity. The Collaborative Trajectory Options Program (CTOP) reduces demand to constrained resources by assigning strategic departure delay and pre-departure reroutes. Reroutes are selected from Trajectory Options Sets (TOSs) submitted by airlines. As flights approach the constrained resource, the Time-Based Flow Management System (TBFM) is used to assign tactical delay to satisfy constraints. This paper describes experiments performed to study the impact of varying levels of airline participation in CTOP via submission of TOSs on ground delay and flight time, and the impact of departure uncertainty on TBFM delays. Results suggest that as CTOP participation increases, average ground delays decrease for all airlines, but to the greatest extent for airlines participating in CTOP. A threshold in CTOP participation, which varies with the constraint capacity, is identified beyond which there is relatively little further reduction in average ground delays. Similarly, given the likely level of CTOP participation, the capacity reduction for which CTOP would be an appropriate TMI is also identified. Results also suggest that high average departure errors and high variability in departure error can make the prioritization of TBFM internal departures in TBFM metering and scheduling infeasible. Departure errors at current levels are, however, acceptable.

CTOP↗
NASA NTRS2018

Using an Automated Air Traffic Simulation Capability for a Parametric Study in Traffic Flow Management

Flight delays occur when demand for capacity-constrained airspace or airports exceeds predicted capacity. Demand for capacity-constrained airspace or airports can be controlled by a series of Traffic Management Initiatives (TMIs), which use departure and airborne delays, as well as pre-departure and airborne reroutes, to manage access to the constrained resources. Two systems exist in current and planned future operations to address imbalances between demand and capacity. The Collaborative Trajectory Options Program (CTOP) reduces demand to constrained resources by assigning strategic departure delay and pre-departure reroutes. Reroutes are selected from Trajectory Options Sets (TOSs) submitted by airlines. As flights approach the constrained resource, the Time-Based Flow Management System (TBFM) is used to assign tactical delay to satisfy constraints. This paper describes experiments performed to study the impact of varying levels of airline participation in CTOP via submission of TOSs on ground delay and flight time, and the impact of departure uncertainty on TBFM delays. Results suggest that as CTOP participation increases, average ground delays decrease for all airlines, but to the greatest extent for airlines participating in CTOP. A threshold in CTOP participation, which varies with the constraint capacity, is identified beyond which there is relatively little further reduction in average ground delays. Similarly, given the likely level of CTOP participation, the capacity reduction for which CTOP would be an appropriate TMI is also identified. Results also suggest that high average departure errors and high variability in departure error can make the prioritization of TBFM internal departures in TBFM metering and scheduling infeasible. Departure errors at current levels are, however, acceptable.

integrated demand management↗
NASA NTRSDate not supplied

Validation of an Automated System for Arrival Traffic Management

The fuel-efficiencies of arrival flights that were managed by an automated system were compared to the fuel-efficiencies of arrival flights that were managed by air traffic controllers. It was infeasible to have the automated system control arrivals in real operations, so the comparison was accomplished by setting up a fast-time simulation where the automated system could manage arrivals with the same initial conditions and flight plans as those that operated in real operations during a selected comparison period and in the same background traffic. For this study, Newark Liberty International Airport was selected as the arrival airport because its high traffic load and constrained arrival procedures were expected to highlight fuel-efficiency benefits of an automated system. In the simulation, the automated system managed Newark arrivals, and the other flights (arrivals to other airports, departures, and overflights) composed the background traffic. To match the simulation and the real operations background traffic, the other flights flew in simulation the same trajectory that they flew in real operations during the comparison period. Fuel-efficiency was measured by calculating fuel burns of the arrival trajectories. The fuel-efficiencies of arrival trajectories produced in the simulation were compared with the estimated fuel-efficiencies of arrival trajectories recorded from real operations during the comparison period. Results showed that automation managed arrivals burned 346 lbs less fuel per flight on average than controller managed arrivals.

air traffic control↗
NASA NTRSDate not supplied

Validation of an Automated System for Arrival Traffic Management

The fuel-efficiencies of arrival flights that were managed by an automated system were compared to the fuel-efficiencies of arrival flights that were managed by air traffic controllers. It was infeasible to have the automated system control arrivals in real operations, so the comparison was accomplished by setting up a fast-time simulation where the automated system could manage arrivals with the same initial conditions and flight plans as those that operated in real operations during a selected comparison period and in the same background traffic. For this study, Newark Liberty International Airport was selected as the arrival airport because its high traffic load and constrained arrival procedures were expected to highlight fuel-efficiency benefits of an automated system. In the simulation, the automated system managed Newark arrivals, and the other flights (arrivals to other airports, departures, and overflights) composed the background traffic. To match the simulation and the real operations background traffic, the other flights flew in simulation the same trajectory that they flew in real operations during the comparison period. Fuel-efficiency was measured by calculating fuel burns of the arrival trajectories. The fuel-efficiencies of arrival trajectories produced in the simulation were compared with the estimated fuel-efficiencies of arrival trajectories recorded from real operations during the comparison period. Results showed that automation managed arrivals burned 346 lbs less fuel per flight on average than controller managed arrivals.

air traffic control↗
NASA NTRS2015

Attitude Design for the LADEE Mission

The Lunar Atmosphere and Dust Environment Explorer (LADEE) satellite successfully completed its 148-day science investigation in a low-altitude, near-equatorial lunar orbit on April 18, 2014. The LADEE spacecraft was built, managed and operated by NASA's Ames Research Center (ARC). The Mission Operations Center (MOC) was located at Ames and was responsible for activity planning, command sequencing, trajectory and attitude design, orbit determination, and spacecraft operations. The Science Operations Center (SOC) was located at Goddard Space Flight Center and was responsible for science planning, data archiving and distribution. This paper details attitude design and operations support for the LADEE mission. LADEE's attitude design was shaped by a wide range of instrument pointing requirements that necessitated regular excursions from the baseline one revolution per orbit "Ram" attitude. Such attitude excursions were constrained by a number of flight rules levied to protect instruments from the Sun, avoid geometries that would result in simultaneous occlusion of LADEE's two star tracker heads, and maintain the spacecraft within its thermal and power operating limits. To satisfy LADEE's many attitude requirements and constraints, a set of rules and conventions was adopted to manage the complexity of this design challenge and facilitate the automation of ground software that generated pointing commands spanning multiple days of operations at a time. The resulting LADEE Flight Dynamics System (FDS) that was developed used Visual Basic scripts that generated instructions to AGI's Satellite Tool Kit (STK) in order to derive quaternion commands at regular intervals that satisfied LADEE's pointing requirements. These scripts relied heavily on the powerful "align and constrain" capability of STK's attitude module to construct LADEE's attitude profiles and the slews to get there. A description of the scripts and the attitude modeling they embodied is provided. One particular challenge analysts faced was in the design of LADEE maneuver attitudes. A flight rule requiring pre-maneuver verification of in-flight maneuver conditions by ground operators prior to burn execution resulted in the need to accommodate long periods in the maneuver attitude. This in turn complicated efforts to satisfy star tracker interference and communication constraints in lunar orbit. In response to this challenge, a graphical method was developed and used to survey candidate rotation angles about the thrust vector. This survey method is described and an example of its use on a particular LADEE maneuver is discussed. Finally, the software and methodology used to satisfy LADEE's attitude requirements are also discussed in the context of LADEE's overall activity planning effort. In particular, the way in which strategic schedules of instrument and engineering activities were translated into actual attitude profiles at the tactical level, then converted into precise quaternion commands to achieve those pointing goals is explained. In order to reduce the risk of time-consuming re-planning efforts, this process included the generation of long-term projections of constraint violation predictions for individual attitude profiles that could be used to establish keep-out time-frames for particular attitude profiles. The challenges experienced and overall efficacy of both the overall LADEE ground system and the attitude components of the Flight Dynamics System in meeting LADEE's varied pointing requirements are discussed.

LADEE↗
NASA NTRS2013

Evaluation of the Terminal Area Precision Scheduling and Spacing System for Performance-Based Navigation Arrivals

The growth of global demand for air transportation has put increasing strain on the nation's air traffic management system. To relieve this strain, the International Civil Aviation Organization has urged all nations to adopt Performance-Based Navigation (PBN), which can help to reduce air traffic congestion, decrease aviation fuel consumption, and protect the environment. NASA has developed a Terminal Area Precision Scheduling and Spacing (TAPSS) system that can support increased use of PBN during periods of high traffic, while supporting fuel-efficient, continuous descent approaches. In the original development of this system, arrival aircraft are assigned fuel-efficient Area Navigation (RNAV) Standard Terminal Arrival Routes before their initial descent from cruise, with routing defined to a specific runway. The system also determines precise schedules for these aircraft that facilitate continuous descent through the assigned routes. To meet these schedules, controllers are given a set of advisory tools to precisely control aircraft. The TAPSS system has been evaluated in a series of human-in-the-loop (HITL) air traffic simulations during 2010 and 2011. Results indicated increased airport arrival throughput up to 10 over current operations, and maintained fuel-efficient aircraft decent profiles from the initial descent to landing with reduced controller workload. This paper focuses on results from a joint NASA and FAA HITL simulation conducted in 2012. Due to the FAA rollout of the advance terminal area PBN procedures at mid-sized airports first, the TAPSS system was modified to manage arrival aircraft as they entered Terminal Radar Approach Control (TRACON). Dallas-Love Field airport (DAL) was selected by the FAA as a representative mid-sized airport within a constrained TRACON airspace due to the close proximity of a major airport, in this case Dallas-Ft Worth International Airport, one of the busiest in the world. To address this constraint, RNAV routes and Required Navigation Performance with the particular capability known as Radius-to-Fix (RNP-RF) approaches to a short final were used. The purpose of this simulation was to get feedback on how current operations could benefit with the TAPSS system and also to evaluate the efficacy of the advisory tools to support the broader use of PBN in the US National Airspace System. For this NASA-FAA joint experiment, an Air Traffic Control laboratory at NASA Ames was arranged to simulate arrivals into DAL in Instrument Meteorological Conditions utilizing parallel dependent approaches, with two feeder positions that handed off traffic to one final position. Four FAA controllers participated, alternately covering these three positions. All participants were Full-Performance Level terminal controllers and members of the National Air Traffic Controllers Association. During the simulation, PBN arrival operations were compared and contrasted in three conditions. They were the Baseline, where none of the TAPSS systems TRACON controller decision support advisories were provided, the Limited Advisories, reflecting the existing but dormant capabilities of the current terminal automation equipment with providing a subset of the TAPSS systems advisories; numerical delay, landing sequence, and runway assignment information, and the Full Advisories, with providing the following in addition to the ones in the Limited condition; trajectory slot markers, timelines of estimated times of arrivals and sched

Performance based navigation↗