Search NASA⌕ Search

SEARCH · Search NASA

Results for “precision arrival 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.

50 records · Page 3

A Concept of Operations for Far-Term Surface Trajectory-Based Operations (STBO)

The goal of this far-term STBO (Surface Trajectory-Based Operations) ConOps (Concept of Operations) is to increase the efficiency and predictability of airport surface operations, and reduce the environmental impact, by incorporating a time-based component to surface operations. In the far-term NextGen timeframe, airport surface operations will transition from current-day first-come, first-served operations, to strategically scheduled operations in which pilots are recruited as active participants in meeting the precise time-based goals of NextGen surface operations. The far-term STBO concept includes two-phases. Phase 1 introduces time-based traffic flow constraint points, which divide the taxi route into segments with an assigned Required Time of Arrival (RTA). This Phase 1 approach provides temporal certainty only near the traffic flow constraint points, but not in between. Minimal augmentations to the flight deck are required to support required time of arrival (RTA) management. Phase 2 further increases precision and efficiency by introducing full four-dimensional (4D) trajectories, with an x-y location for all times t. This phase assumes adoption of advanced flight deck equipage enabling higher temporal precision sufficient to support aircraft conformance to 4D trajectories. This allows more precision and less temporal uncertainty at all times along the route.

Surface Trajectory-Based Operations (STBO)↗

Reducing Departure Delays for Adjacent Center Airports using Time-Based Flow Management Scheduler: Checkbox On or Off?

The Federal Aviation Administration (FAA) has enhanced the Time-Based Flow Management (TBFM) scheduling tool with a "Checkbox ON" vs. "OFF" function which allows Traffic Management Coordinators (TMCs) to make room in a crowded arrival stream for a departure. When scheduling a departure, having the checkbox ON can delay the Scheduled Times of Arrivals (STAs) of the airborne flights upstream of the TBFM freeze horizons and can compress these flights to their minimum required spacing, thereby creating a slot for a departure. Hence, having the checkbox ON can reduce the frequent ground delays of aircraft departing near high volume airports but can increase delays for airborne arrivals. A Human-in-the-Loop (HITL) simulation compared arrival and departure delays to Newark Airport (EWR) with the checkbox ON vs. OFF as the default position. Three other conditions in this HITL involved various National Airspace System (NAS)-wide approaches for timely delivery of aircraft to the TBFM region. These conditions were: Baseline, using current Mile-in-Trail (MIT) spacing restrictions; Integrated Demand Management (IDM), where all aircraft were given departure times (Expect Departure Clearance Times, or EDCTs), ultimately based on the EWR Airport Arrival Rate; and IDM plus Required Time of Arrival (RTA), a flight deck tool which allowed some aircraft to meet a controlled time of arrival to the TBFM area more precisely. Results showed that the checkbox tool was powerful: with the checkbox ON, departure delays decreased and airborne delays increased, as predicted. However, assuming that the cost ratio of a minute of airborne delay to a minute of departure delay is in the range of 1.2 to 3, as commonly indicated by the literature, checkbox ON and checkbox OFF conditions showed approximately equal total delay costs, i.e., the cost of delays in the air balanced the cost of the delay on the ground. The three scheduling conditions also had approximately equal total delay costs, although a simulation artifact may have reduced the delays in the Baseline condition. In the debrief following the simulation, the TMCs concluded that the checkbox should be used flexibly depending on the current delay situation, and suggested modifications to the checkbox tool which would help them use it in this way, along with enhanced training. The relatively similar total cost of both checkbox default options in this simulation indicates that this might be a fruitful approach, and replace the necessity to have the checkbox rigidly set to either ON or OFF.

departure delay↗

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.↗

Interval Management Display Design Study

In 2012, the Federal Aviation Administration (FAA) estimated that U.S. commercial air carriers moved 736.7 million passengers over 822.3 billion revenue-passenger miles. The FAA also forecasts, in that same report, an average annual increase in passenger traffic of 2.2 percent per year for the next 20 years, which approximates to one-and-a-half times the number of today's aircraft operations and passengers by the year 2033. If airspace capacity and throughput remain unchanged, then flight delays will increase, particularly at those airports already operating near or at capacity. Therefore it is critical to create new and improved technologies, communications, and procedures to be used by air traffic controllers and pilots. National Aeronautics and Space Administration (NASA), the FAA, and the aviation industry are working together to improve the efficiency of the National Airspace System and the cost to operate in it in several ways, one of which is through the creation of the Next Generation Air Transportation System (NextGen). NextGen is intended to provide airspace users with more precise information about traffic, routing, and weather, as well as improve the control mechanisms within the air traffic system. NASA's Air Traffic Management Technology Demonstration-1 (ATD-1) Project is designed to contribute to the goals of NextGen, and accomplishes this by integrating three NASA technologies to enable fuel-efficient arrival operations into high-density airports. The three NASA technologies and procedures combined in the ATD-1 concept are advanced arrival scheduling, controller decision support tools, and aircraft avionics to enable multiple time deconflicted and fuel efficient arrival streams in high-density terminal airspace.

Baxley, Brian T.↗

Operational Impact of the Baseline Integrated Arrival, Departure, and Surface System Field Demonstration

To address the Integrated Arrival, Departure, and Surface (IADS) challenge, NASA is developing and demonstrating trajectory-based departure automation under a collaborative effort with the FAA and industry known as Airspace Technology Demonstration 2 (ATD-2). ATD-2 builds upon and integrates previous NASA research capabilities that include the Spot and Runway Departure Advisor (SARDA), the Precision Departure Release Capability (PDRC), and the Terminal Sequencing and Spacing (TSAS) capability. The ATD-2 field demonstration is organized into three phases. Phase I illustrates a Baseline IADS demonstration and includes all components of ATD-2 running in operational environments. Subsequent phases will fuse together strategic scheduling components as well as take into account metroplex considerations. This paper describes the baseline IADS system that was deployed at the end of 2017 and is continuing to run as part of the ATD-2 demonstration taking place at Charlotte-Douglas International Airport (CLT). The primary areas of deployment and system use are in the CLT Air Traffic Control Tower, CLT TRACON, CLT American Airlines ramp tower, Washington Center facility and American Airlines Integration Operations Center (IOC). In addition to describing the functions and capabilities that are part of the baseline IADS system, this paper also provides metrics regarding operational use as well as initial benefits metrics. Benefit metrics continue to be collected and aggregated across the areas of system delay, throughput, taxi time, fuel burn savings, and emissions savings. Furthermore, benefits as a result of common awareness of delays and the impact of takeoff and departure restrictions stemming from traffic flow management initiatives are described. The overall benefit of improved predictability and efficiency as a result of the baseline IADS system demonstration is also discussed.

operational system↗

Development of Closed-Loop Simulation Methods for a Next-Generation Terminal Area Automation System

A next-generation air traffic decision support tool, known as the Active Final Approach Spacing Tool (aFAST), will generate heading, speed and altitude commands to achieve more precise separation of aircraft in the terminal area. The techniques used to analyze the performance of earlier generation decision support tools are not adequate to analyze the performance of aFAST. This paper summarizes the development of a new and innovative fully closed-loop testing method for aFAST. This method, called trajectory feedback testing, closes each aircraft's control loop inside of the aFAST scheduling algorithm. Validation of trajectory feedback testing by examination of the variation of aircraft time-of-arrival predictions between schedule updates and the variation of aircraft excess separation distances between simulation runs is presented.

Robinson, John E., III↗

Tool-Enabled Changes in Terminal Air Traffic Controller Task and Workload Distribution

A human-in-the-loop simulation was conducted that examined an approach to adjusting airport arrivals in such a way as to enable higher departure throughput while maintaining arrival throughput. This approach, referred to as Departure-Sensitive Arrival Spacing (DSAS), leverages the capabilities of the Terminal Sequencing and Spacing (TSS) system with an additional Decision Support Tool (DST) to assign more precise arrival spacing interval. This presentation will focus on the changes observed in the task distribution and control strategies among three Terminal Radar Approach Control (TRACON) controller participants and the workload associated with those changes across three conditions: Baseline, TSS, and DSAS. Results showed that the application of the DSTs in the TSS condition and those in the DSAS condition enabled a progressive reduction in the number of clearances issued and for the clearances to be issued earlier, further away from the airport. In doing so, there was also a greater use of speed control versus vectoring and altitude for schedule conformance in the TSS and DSAS conditions respectively and relative to Baseline. Workload also shifted in conjunction with the clearance distribution with an overall reduction across conditions. The changes in task and workload distribution enabled a shift from tactical to strategic control, which allowed for a more predictable and efficient delivery of arrivals.

task↗

Operational Concept for Flight Crews to Participate in Merging and Spacing of Aircraft

The predicted tripling of air traffic within the next 15 years is expected to cause significant aircraft delays and create a major financial burden for the airline industry unless the capacity of the National Airspace System can be increased. One approach to improve throughput and reduce delay is to develop new ground tools, airborne tools, and procedures to reduce the variance of aircraft delivery to the airport, thereby providing an increase in runway throughput capacity and a reduction in arrival aircraft delay. The first phase of the Merging and Spacing Concept employs a ground based tool used by Air Traffic Control that creates an arrival time to the runway threshold based on the aircraft s current position and speed, then makes minor adjustments to that schedule to accommodate runway throughput constraints such as weather and wake vortex separation criteria. The Merging and Spacing Concept also employs arrival routing that begins at an en route metering fix at altitude and continues to the runway threshold with defined lateral, vertical, and velocity criteria. This allows the desired spacing interval between aircraft at the runway to be translated back in time and space to the metering fix. The tool then calculates a specific speed for each aircraft to fly while enroute to the metering fix based on the adjusted land timing for that aircraft. This speed is data-linked to the crew who fly this speed, causing the aircraft to arrive at the metering fix with the assigned spacing interval behind the previous aircraft in the landing sequence. The second phase of the Merging and Spacing Concept increases the timing precision of the aircraft delivery to the runway threshold by having flight crews using an airborne system make minor speed changes during enroute, descent, and arrival phases of flight. These speed changes are based on broadcast aircraft state data to determine the difference between the actual and assigned time interval between the aircraft pair. The airborne software then calculates a speed adjustment to null that difference over the remaining flight trajectory. Follow-on phases still under development will expand the concept to all types of aircraft, arriving from any direction, merging at different fixes and altitudes, and to any airport. This paper describes the implementation phases of the Merging and Spacing Concept, and provides high-level results of research conducted to date.

Baxley, Brian T.↗

Piloted simulation of a ground-based time-control concept for air traffic control

A concept for aiding air traffic controllers in efficiently spacing traffic and meeting scheduled arrival times at a metering fix was developed and tested in a real time simulation. The automation aid, referred to as the ground based 4-D descent advisor (DA), is based on accurate models of aircraft performance and weather conditions. The DA generates suggested clearances, including both top-of-descent-point and speed-profile data, for one or more aircraft in order to achieve specific time or distance separation objectives. The DA algorithm is used by the air traffic controller to resolve conflicts and issue advisories to arrival aircraft. A joint simulation was conducted using a piloted simulator and an advanced concept air traffic control simulation to study the acceptability and accuracy of the DA automation aid from both the pilot's and the air traffic controller's perspectives. The results of the piloted simulation are examined. In the piloted simulation, airline crews executed controller issued descent advisories along standard curved path arrival routes, and were able to achieve an arrival time precision of + or - 20 sec at the metering fix. An analysis of errors generated in turns resulted in further enhancements of the algorithm to improve the predictive accuracy. Evaluations by pilots indicate general support for the concept and provide specific recommendations for improvement.

Davis, Thomas J.↗

Evaluation of APREQCFR Coordination Procedures for Charlotte Douglas International Airport

NASA has been collaborating with the Federal Aviation Administration (FAA) and aviation industry partners to develop and demonstrate new concepts and technologies for the Integrated Arrival, Departure, and Surface (IADS) traffic management capabilities under the Airspace Technology Demonstration 2 (ATD-2) project. One of the goal of The IADS capabilities in the ATD-2 project is to increase predictability and increase throughput via improving TMI compliance. The IADS capabilities that will impact TMI compliance are built upon previous NASA research, the Precision Departure Release Capability (PDRC). The proposed paper will evaluate the APREQCFR process between ATC Tower and Center and information sharing between ATC Tower and the airline Ramp tower. Subjective measures collected from the HITL surveys (e.g., workload, situational awareness, acceptability, usability) and performance metrics such as TMI, TMAT, and pushback advisory compliance from APREQCFR flights and will be reported.

APREQ scheduling↗

Effect of Surface Traffic Count on Taxi Time at Dallas-Fort Worth (DFW) International Airport

As the amount of air traffic increases over the years, most airports simply do not have the means of expanding to handle the intensified traffic on the surface that will ensue. Precise surveillance equipment and automation concepts, as well as advanced surface traffic algorithms are being developed to improve airport efficiency. These surface algorithms require inputs unique to each airport to ensure maximum efficiency, and minimal taxi delay. This study analyzes surface traffic at Dallas-Fort Worth International Airport (DFW) to determine the effect of the number of aircraft on the surface and the amount of stop and go situations they experience to the amount of additional taxi time encountered. If the surface capacity of an airport is known, minimal delay can be accomplished by limiting the number of taxiing aircraft to that capacity. This concept is related to highways, where traffic flow drastically decreases as more cars occupy the road. An attempt to minimize this effect on highways is seen with the use of metering lights at freeway on-ramps. Since the surface traffic at airports is highly regulated, and aircraft are less mobile on the ground, limiting the surface count to a certain number can greatly reduce the amount of additional taxi time encountered, as well as reduce hazardous emissions. This study will also find the regions of an airport that encounter the most additional taxi time when the number of aircraft in that area is increased. This could help surface traffic algorithms avoid congesting that area, or re-route aircraft to different runways when that area reaches its capacity. The relationship between the amount of stop and go situations an aircraft encounters and their effect on the taxi time of that aircraft will also be investigated. This will help to determine the effect of holding an aircraft on the taxiway as opposed to re-routing it. The lesser of the two should be used when developing surface traffic algorithms to further minimize the delay encountered. The fields investigated in this study include taxi time, the number of aircraft on the surface, the number of stop and go situations, and the time stopped for each aircraft. Taxi time is defined as spot to runway for departures, and runway to spot for arrivals. It does not include ramp area taxi time because the ramp area is controlled differently, and surface traffic schedulers do not currently incorporate them. Taxi time is found by finding the difference between take-off time (OFF) and spot crossing time for departures, and spot crossing time and landing time (ON) for arrivals. All surface data was either found directly using the Surface Operations Data Analysis and Adaptation (SODAA), a tool to analyze the Surface Management System (SMS) generated log files, or indirectly from SODAA using Matlab to derive values from SODAA data. The number of aircraft on the surface is found by looping through the ON times, OFF times, and spot times for each aircraft during a particular day. For each departure aircraft, surface counts are taken at its spot crossing and OFF time. The average of these two is used as the surface count for that aircraft. For arrivals, surface counts are taken at its ON time and its spot crossing time. The average of these two is used.

Kistler, Matthew Stephen↗

A Notional Artemis Lunar Surface Exploration Package (ArLSEP) based on the Gandalf Staff Platform

Introduction: The Artemis program is planning to deliver crew and cargo to the lunar surface, but there is no current package for supporting lunar in-struments and experiments similar to the Apollo Lunar Surface Exploration Package (ALSEP). This abstract provides a possible concept for such a package using the Gandalf Staff Platform as a common core. Gandalf Staff: The Gandalf Staff is an early prototype system developed over FY’21/FY’22 using NASA Science Technology Mission Directorate (STMD) Center Information Fund (CIF) grants to de-sign, build and test “proof-of-concept” components. These components include a 24v battery powered monopole that powers a suite of subsystems, including a Graphical User Interface (GUI) for crew, surface voice and data communications, Lunar Search and Rescue (LunaSAR) navigation and communications, LiDAR, field site external lighting, 360-degree camera, and a geothermal instrument for measuring sub-surface temperature gradient. The staff can be carried independently by an Extra-Vehicular Activity (EVA) astronaut, or can be mounted into a tripod for “hands free” support at a surface site being investigated. The staff can be attached to an external solar array and power storage system for long-duration operations. [1,2] ALSEP: An ASLEP flew on each mission Apollo 12 to Apollo 17. For Apollo 11, a simplified packaged called the Early Apollo Scientific Experiments Pack-age (EASEP) was flown. Each package included a “Central Station” that provided the power and communications connected to a variety of instruments and sensors. The power was provided by a Radioisotope Thermoelectric Generator (RTG) fueled by Plutoni-um-238 generating 70 watts of power (initially, decayed over time) [3]. The communications system provide for direct to Earth data transfer from the lunar surface. Each pack-age was stowed externally in the Lunar Module (LM) Scientific Equipment (SEQ) bay with a mass up to 163 kg (Apollo 17). The crew unloaded the ALSEP from the LM and deployed the instruments on the lunar surface. Although designed to operate for only 1 year, many sites operated for up to 8 years successfully [4]. The Active Seismic Experiment (ASE) included 3 geophones for detecting seismic waves created by mortars and thumpers deployed by the crew. Other active experiments measured the lunar atmosphere, the heat flow in the subsurface, the lunar gravity and potential gravity waves, the lunar magnetic field, the solar wind and plasma interactions in cislunar space. Passive experiments included collectors for dust and cosmic rays, and retroreflectors for precise measurements of distance using a laser from Earth. The ALSEP program continues to generate insights into lunar formation and evolution. ArLSEP Concepts: The lunar surface science package for the Artemis program will hopefully exceed the capability of the ALSEP. There are multiple issues for discussion leading to the design of a new ArLSEP, needing requirements definition from the science community, NASA mission architecture, and NASA budget planners. 1. Delivery Mechanism Two possible projects currently provide capability to deliver scientific cargo to the lunar surface: 1) the Commercial Lunar Payload Services (CLPS) [5] and the Human Landing System (HLS) [6, 7]. Each project is controlled by a different organization within NASA and budgeted with different criteria although both support lunar exploration. The HLS system delivers crew (and potentially cargo) to human landing sites. If an ArLSEP is “predeployed” to such a site, the design must include power (either from the vehicle or independently) to keep the electronics functioning until deployed by the crew. If an ArLSEP is delivered on a vehicle after the crew is present on the lunar surface, safety protocols require adequate distance from the humans for impact from descent propelled sur-face regolith ejecta. This distance can not exceed the capability of the crew to walk (if no rover) to the vehicle for ArLSEP deployment. 2. Overall Guidelines The general design of ArLSEP will likely follow the ALSEP with a common system for communications and power; however, significant architecture differences between Apollo and Artemis exist. Power: The RTG will not be available for early Artemis missions nor likely follow-on Lunar Exploration Transportation Services (LETS) missions [8]. Thus, ArLSEP power must be supplied by solar arrays with sufficient battery capability to “keep alive” necessary electronics during any lunar surface eclipse period. Communication: The Artemis program is developing a series of communications satellites for lunar orbit to provide surface transmission of data and voice to Earth. Called “LunaNET”, this network is component useful for ArLSEP since south polar locations may not always have direct “line-of-sight” to Earth [9]. 3. Concept of Operations (ConOps) The general ConOps for ArLSEP is to deliver the package to lunar surface before the crew arrives, and then have the crew deploy the package after some period of time. This requires coordinated design (for power systems) and launch window (for schedule) on both the cargo and crew missions. Once the ArLSEP is deployed, it will operate autonomously for a number of years. It should be designed to be EVA compatible for crew maintenance and upgrade. 4. Notional Design (for discussion purpose only) The landing site near the South Pole is expected to have no eclipse cycle exceeding 5 days, so the “keep alive” power is 144 hours (6 days to include margin). A 12v ArLSEP will use rechargeable LiFePO4 cells, which are common in the Electric Vehicle (EV) industry. With a current of 5 amps and a 125 watt system, the mass is about 90kg. The comm. system and structure adds another 10kg, thus the “Central Station” is approximately 100kg. The solar power is collected on four arrays (each 2m above the surface), and the entire ArLSEP is designed to stow in a 2m x 1m x 1m volume. The experiment and instrument design will vary for each installation and add mass to the total (although they are expected to fit within the 2m3 volume). Seismic wave generation will likely not be provided with mortars, thus an electric “thumper” will be required. Active instruments such as imaging systems and sensing instruments will benefit from the additional power and communication capability provided by ArLSEP. Passive systems such as retroreflectors, witness plates, and cosmic dust collectors can be added to either the landing vehicle and/or the ArLSEP. With repeated HLS missions to the same human site, the ArLSEP can be expanded and easily maintained for long duration science collection on the lunar surface.

ALSEP↗

Nozomi Cis-Lunar Phase Orbit Determination

Japan's Institute of Space and Astronautical Science (ISAS) launched Nozomi, its first mission to the planet Mars using the newly developed M-V launch vehicle on July 3, 1998. Scientific objectives of the mission are to study the structure and dynamics of the Martian upper atmosphere and its interaction with the solar wind. Nozomi is a cooperative mission between ISAS and the National Aeronautics and Space Administration (NASA). The NASA contribution includes navigation and tracking services provided by the Jet Propulsion Laboratory (JPL). The spacecraft also serves as an engineering demonstration of basic technology for planetary exploration. One of the new technologies was a unique trajectory, developed by ISAS, which used solar gravitational perturbations at the weak stability boundary as an aid to achieve an Earth-Mars transfer orbit. This trajectory saves approximately 120 m/s of Delta V compared to direct hyperbolic insertion and is considered an enabling technology for the mission. Nozomi was the first spacecraft to employ this trajectory and provided on-orbit validation of the technique. The trajectory was achieved by initially placing the spacecraft in a highly elliptical cis-lunar phasing orbit. Six maneuvers were performed during this period to correct injection errors and target an outbound lunar swingby in September 1998. The gravity assist from the lunar swingby raised apogee to the vicinity of the weak stability boundary. After three more targeting maneuvers, Nozomi performed an inbound lunar swingby followed immediately by a powered Earth swingby in late December 1998. A 420 m/s Trans Mars Insertion (TMI) burn at the final Earth periapsis was intended to place the spacecraft on a heliocentric trajectory leading to Mars orbit insertion in October 1999. Orbit determination for Nozomi is performed in parallel by both ISAS and the Multi-Mission Navigation (MMNAV) group at JPL. This was an advantage for the mission because each group would generate solutions based on data collected from their respective tracking networks. Spacecraft events, such as sequence uplinks and maneuvers, were generally scheduled during passes at the Usuda tracking station in Japan. As a result, maneuver design and reconstruction was derived from MMNAV solutions based on JPL tracking data obtained immediately prior to or following maneuvers. Data was also exchanged between ISAS and MMNAV so orbit determination could be performed on joint data sets in support of critical targeting late in the cis-lunar phase. In this paper, information regarding the MMNAV orbit determination effort for the first six months of the mission is presented. The spacecraft trajectory is characterized first, followed by a discussion of the orbit determination estimation procedure and models. Results from selected orbit solutions are presented and compared against reconstructed trajectories. One area of emphasis in this paper is orbit determination in the vicinity of the weak stability boundary. Precise navigation was necessary to target the second lunar swingby and the powered Earth swingby. Delivery accuracy of 150 m was required for these critical encounters, but a number of factors contributed to the general degradation of orbit determination accuracy. This included the fact that the spacecraft was at apogee, at a range of 1.7 million km and moving at less than I km/sec perpendicular to the line of sight. Nozomi was also close to zero degrees declination where there are known limitations on orbit determination performance. Finally, S-band tracking data was acquired through the Nozomi backup low gain antenna. This antenna is offset from the axis of this spin stabilized spacecraft and superimposed large signatures in the Doppler and range data. These difficulties were overcome by combining long data arcs, spanning several maneuvers, with a high fidelity solar pressure model. The model included a physically accurate representation of the spacecraft structure and a high time resolution orientation model. Observation modeling included the removal of the spin induced Doppler bias, spin signature and per pass correction of range calibration errors applied for data leading up to critical events. As a result, all orbit determination goals were met. A second area of emphasis in this paper is the JPL tracking and orbit determination effort in support of the TMI maneuver. TMI occurred out of contact with ground stations and the JPL Goldstone tracking complex had the first pass following the bum. As a result, MMNAV had the responsibility to make a rapid assessment of the maneuver performance. MMNAV made the determination that a 100 m/s under bum had occurred and promptly informed ISAS via voice lines. ISAS immediately began preparations for a correction maneuver (TMIc), which had to be performed during the next Usuda pass. The near real time assessment by MMNAV provided accurate antenna frequency and pointing updates for the spacecraft acquisition at Usuda and the close coordination between the two agencies enabled the design and successful execution of the TMc maneuver. Propellant consumption during the correction burn dictated that the mission be redesigned. ISAS developed a new plan which adds 3 full solar orbits, two Earth swingbys and one lunar swingby with arrival at Mars in January 2004. The final Mars orbit will still enable the mission to achieve all of its science objectives.

Ryne, Mark↗

A Machine Learning Approach to Improve Air Traffic Management Initiatives

Collaborating closely with commercial air carriers and related organizations, the Federal Aviation Administration(FAA) regulates air traffic and ensures the safety and efficiency of air operations. Air traffic controllers make strategic decisions, such as delaying, rerouting, or canceling flights, partly based on guidance provided by the FAA’s Air TrafficControl System Command Center (ATCSCC). The guidance includes, among other things, control measures known asTraffic Management Initiatives (TMIs) designed to enhance safety and improve operational efficiency. TMIs play a crucial role in managing the demand and capacity within the U.S. National Airspace System (NAS). Two major TMIs that are routinely used (primarily to mitigate the adverse effects of bad weather) are Ground Delay Programs (GDPs) andGround Stops (GSs). In a GDP, flights destined for airports facing thunderstorm activity experience delays at their origin airports. This proactive approach minimizes the risk of routing aircraft through hazardous weather conditions and also replaces (fuel burning) airborne delays with ground delays. In a GS, a temporary restriction is imposed on the departure or arrival of aircraft at a specific airport or within a designated airspace. Although other TMIs (e.g., miles-in-trail) are also implemented as part of (air) traffic flow management in the NAS, the focus of this work is on GDPs and GSs. Since TMIs, by design, lead to flight delays or cancellations, it is crucial to put in place the right set of parameters(e.g., scope and duration of the GDP). For example, when the end time of a GDP extends beyond what is necessary, it imposes unnecessary delays on departing flights. This situation could occur as a result of inaccurate prediction of the(required) duration of the GDP based on the weather forecast. On the other hand, if a GDP ends prematurely before the underlying capacity constraints are resolved at the destination airport, it may result in airborne holding. The delicate balance lies in matching the termination of the GDP precisely with the resolution of capacity constraints, avoiding both the imposition of unnecessary ground delays and the need for airborne holding due to premature program termination.Failing to specify the right parameters for TMIs also leads to flight delays, creating a significant obstacle in managing the increasing traffic volumes causing increased work load for the controllers. To address this issue, we propose the integration of Machine Learning (ML) models in the traffic flow management(TFM) pipeline. In current operations, decisions are made by human experts based on extensive training, historical patterns, available traffic and weather data. Since we have an abundance of data from past events that tell us the likely impact of various TMIs, by ingesting historical data, properly trained ML models can offer valuable insights and aid human decision-making. With the FAA increasingly exploring advanced analytics, ML emerges as a focal point for enhancing TFM within the National Airspace System (NAS). As a first step, this study aims to provide traffic controllers with decision-making support for the issuance and adjustment of TMIs. Data analytics and machine learning have been previously employed to address some of the challenges associated with TMIs. Numerous studies have concentrated on various facets of TMI issuance, exploring factors influencing TMI parameters, including arrival rate, airport capacity, and delay prediction. For example, using weather forecasts, several statistical methods were used to produce probabilistic capacity profiles which in conjunction with deterministic models provided insights into the GDP planning process [1–4]. The downside of using deterministic models is that they rely on fixed inputs and predetermined rules, which lack the ability to account for the inherent uncertainty and variability present in real-world scenarios. In a separate series of studies, researchers aimed to predict the occurrences of GDPs and GSs. The majority of these studies utilized various supervised learning methods, including Decision Trees, Naive Bayes, Support VectorMachines, and Random Forests to analyze the influence of weather conditions and arrival demand on TMI incidents[5–8]. However, these studies primarily focused on predicting the incidence of TMIs without explicitly addressing the scope of TMIs, including their duration and their geographical coverage. Furthermore, the emphasis of these studies was largely on GDPs, given their higher frequency and longer duration when compared to GSs. A limited number of studies focused on predicting the parameters of TMIs, specifically addressing their duration and extent. In one such study focusing on optimizing the TMI parameters at San Francisco International Airport (SFO),the authors utilized a probabilistic forecast of fog [9]. They simulated various capacity scenarios based on the (fog)burn-off forecasts, selecting GDP parameters that minimized airborne and overall ground delays. However, this approach exclusively emphasizes stratus (fog) burn-off as the primary determinant of GDP and GS, neglecting other influential factors like severe weather events, runway closures, lower capacity than traffic demand, and other important variables. Given the complexity of predicting the TMI and determining its scope, we seek a more holistic approach. We aim to consider all significant factors that could impact TMIs and their parameters. What sets this research apart is the fusion of all data sources relevant to the issuance and adjustment of TMIs and it represents the first comprehensive attempt to optimize TMIs in this manner. Since this comprehensive solution involves various aspects, we break down the problem into smaller components and input all parameters into a unified model called the “TMI Adjuster”. Figure 1 shows the overall framework and the list of datasets used in each model. The objective of the TMI Adjuster module is to deliver reliable, consistent and expedited recommendations for the progression, adjustment, and termination of TMIs. The ML solution entails developing a pipeline capable of predicting the necessity of a TMI (e.g., GS or GDP) along with its various parameters. For example, in the case of a GS, this includes the scope of the GS either in terms of distance from the destination airport or based on pre-defined airspace sectors. Here, scope refers to those regions and departing airports that are subject to the GS. In this paper, we concentrate on the issuance of GSs in the three major airports in the New York area — LaGuardia(LGA), John F. Kennedy International (JFK), and Newark Liberty International (EWR). We fuse traffic, weather and other relevant aviation data from years 2017 to 2019 to train and validate the ML models. In particular, we use the following datasets: •Terminal Aerodrome Forecast (TAF): meteorological forecasts specific to each airport, issued four times a day, covering predefined time periods. •TMI data: includes all GSs and GDPs along with their respective parameters. •Aviation System Performance Metrics (ASPM): includes traffic related data such as aircraft delays, arrival, and departure rates. •Notices to Airmen (NOTAMs): utilized to extract runway closure data and manage interdependencies between terminals in close proximity. •Flight cancellation data •Airspace Flow Programs (AFP): includes information on flight airborne holdings caused by TMIs. The data preprocessing entails transforming ASPM, TMI, AFP, NOTAMs, and weather data into an hourly format and consolidating all datasets by merging them based on date and time as the primary key. The TMI Adjuster framework comprises two parallel models: one dedicated to GS and a second model focused on GDP. As previously mentioned, our specific focus is on the GS model as a multi-classification problem. In this framework, each data point of the GS model input summarizes ten hours of data. Specifically, the data loader for the GS model generates the input and output of the model as follows: at a given time step, the input includes the actual traffic, weather, and TMI data from the two-hour window before the time step, alongside the weather forecast and scheduled traffic for the next 8 hours starting from the time step. Based on this information, the output of the GS model for each time interval consists of three dimensions. The first dimension represents a binary decision on whether there should be a GS in place for the next hour or not. The second dimension is related to the scope of the GS in the United States, and the third dimension is related to the scope of the GS in Canada (i.e., to determine if the GS impacts airports in Canada).One of the challenges with TMI modeling is the sparsity of TMI events, particularly regarding its scope. To address this challenge in the scope of the GS model output, we implement grouping. The GS scope for the US region is defined based on a list of centers that should be included when the GS is in place. With 20 centers in the US, we utilized historical data to group them into 4 categories. In particular, we summarized our historical data in a graph format where nodes represent centers, and link weights are defined based on the co-occurrence of centers in the scope parameter ofTMIs. By identified strongly connected components in this graph, we were able to partition the centers into four groups. We consider two model structures for the GS Model. Firstly, a hierarchical classification model [10], where the human decision-making for a GS is of hierarchical nature. The decision-maker first decides whether there is a need fora GS, and if the answer is yes, determines the scope. A hierarchical classification model organizes the problem into a class hierarchy, typically a tree or a Directed Acyclic Graph (DAG) structure, and considers the dependency of the decision in the previous step to the next component [10]. Here, we employ the local classifier per level approach, which involves training one multi-class classifier for each level of the class hierarchy. The second structure is the independent structure. In this setting, as the name suggests, we do not consider the dependency of the decisions in the different dimensions of the output of the model. Instead, for each dimension, we train a multi-class classifier independently. Table 1 summarizes GS model statistics for training, validation and testing. The table documents the effect of limiting data to the time steps when there was actually a TMI in place or when a TMI had just terminated. This resulted in a more balanced distribution of the GS class(GS positive class)versus “No GS”(GS negative class), which might help the training process. While JFK and LGA follow very similar distributions, with 40% and 42% GS positive class respectively, EWR has proportionally fewer GS incidents at 28%. Our subsequent phase involves evaluating the performance of both hierarchical structure and independent structure using different state-of-the-art multi-class classifier models such as Random Forest, Decision Trees, K-nearest Neighbors, and Logistic Regression and forecast the duration and scope of the GSs.

Farzan Masrour Shalmani↗