Search NASA⌕ Search

SEARCH · Search NASA

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

248 records · Page 14
All sourcesNASA NTRSDOE OSTI
NASA NTRS2020

Benefit Assessment of the Integrated Demand Management Concept for Multiple New York Metroplex Airports

Benefits of the Integrated Demand Management (IDM) concept were assessed utilizing a newly developed automated simulation capability called ‘Traffic Management Initiative Automated Simulation (TMIAutoSim).’ The IDM concept focuses on improving traffic flow management (TFM) by coordinating the FAA’s strategic Traffic Flow Management System (TFMS) with its more tactical Time-Based Flow Management (TBFM) system. The IDM concept leverages a new TFMS capability called Collaborative Trajectory Options Program (CTOP) to strategically pre-condition traffic demand flowing into a TBFM-managed arrival environment, where TBFM is responsible for tactically managing traffic by generating precise arrival schedules. The IDM concept was developed over a multi-year effort, focusing on solving New York metroplex airport arrival problems. TMIAutoSim closely mimics NASA’s high-fidelity simulation capabilities while enabling more data to be collected at higher speed. Using this new capability, the IDM concept was evaluated using realistic traffic across various weather scenarios. Six representative weather days were selected after clustering three months of historical data. For those selected six days, Newark Liberty International Airport (EWR) and LaGuardia Airport (LGA) arrival traffic scenarios were developed. For each selected day, the historical data were analyzed to accurately simulate actual operations and the weather impact of the day. The current day operations and the IDM concept operations were simulated for the same weather scenarios and the results were compared. The selected six days were categorized into two groups: ‘clear weather’ for days without Ground Delay Programs (GDP) and ‘convective weather’ for days with GDP and significant weather around New York metroplex airports. For the clear weather scenarios, IDM operations reduced last minute, unanticipated departure delays for short-haul flights within TBFM control boundaries with minimal to no impact on throughput and total delay. For the convective weather scenarios, IDM significantly reduced delays and increased throughput to the destination airports.

Traffic Management Initiative Automated Simulation↗
NASA NTRS1999

Aerospace Safety Advisory Panel

This report covers the activities of the Aerospace Safety Advisory Panel (ASAP) for calendar year 1998-a year of sharp contrasts and significant successes at NASA. The year opened with the announcement of large workforce cutbacks. The slip in the schedule for launching the International Space Station (ISS) created a 5-month hiatus in Space Shuttle launches. This slack period ended with the successful and highly publicized launch of the STS-95 mission. As the year closed, ISS assembly began with the successful orbiting and joining of the Functional Cargo Block (FGB), Zarya, from Russia and the Unity Node from the United States. Throughout the year, the Panel maintained its scrutiny of NASAs safety processes. Of particular interest were the potential effects on safety of workforce reductions and the continued transition of functions to the Space Flight Operations Contractor. Attention was also given to the risk management plans of the Aero-Space Technology programs, including the X-33, X-34, and X-38. Overall, the Panel concluded that safety is well served for the present. The picture is not as clear for the future. Cutbacks have limited the depth of talent available. In many cases, technical specialties are "one deep." The extended hiring freeze has resulted in an older workforce that will inevitably suffer significant departures from retirements in the near future. The resulting "brain drain" could represent a future safety risk unless appropriate succession planning is started expeditiously. This and other topics are covered in the section addressing workforce. In the case of the Space Shuttle, beneficial and mandatory safety and operational upgrades are being delayed because of a lack of sufficient present funding. Likewise, the ISS has little flexibility to begin long lead-time items for upgrades or contingency planning.

Source record↗
NASA NTRS2008

Constellation Training Facility Support

The National Aeronautics and Space Administration is developing the next set of vehicles that will take men back to the moon under the Constellation Program. The Constellation Training Facility (CxTF) is a project in development that will be used to train astronauts, instructors, and flight controllers on the operation of Constellation Program vehicles. It will also be used for procedure verification and validation of flight software and console tools. The CxTF will have simulations for the Crew Exploration Vehicle (CEV), Crew Module (CM), CEV Service Module (SM), Launch Abort System (LAS), Spacecraft Adapter (SA), Crew Launch Vehicle (CLV), Pressurized Cargo Variant CM, Pressurized Cargo Variant SM, Cargo Launch Vehicle, Earth Departure Stage (EDS), and the Lunar Surface Access Module (LSAM). The Facility will consist of part-task and full-task trainers, each with a specific set of mission training capabilities. Part task trainers will be used for focused training on a single vehicle system or set of related systems. Full task trainers will be used for training on complete vehicles and all of its subsystems. Support was provided in both software development and project planning areas of the CxTF project. Simulation software was developed for the hydraulic system of the Thrust Vector Control (TVC) of the ARES I launch vehicle. The TVC system is in charge of the actuation of the nozzle gimbals for navigation control of the upper stage of the ARES I rocket. Also, software was developed using C standards to send and receive data to and from hand controllers to be used in CxTF cockpit simulations. The hand controllers provided movement in all six rotational and translational axes. Under Project Planning & Control, support was provided to the development and maintenance of integrated schedules for both the Constellation Training Facility and Missions Operations Facilities Division. These schedules maintain communication between projects in different levels. The CxTF support provided is one that requires continuous maintenance since the project is still on initial development phases.

Flores, Jose M.↗
NASA NTRS1999

STS-96 Mission Highlights

In this second part of a three-part video mission-highlights set, on-orbit spacecrew activities performed on the STS-96 Space Shuttle Orbiter Discovery and the International Space Station are reviewed. The flight crew consists of Kent V. Rominger, Commander; Rick D. Husband, Pilot; and Mission Specialists Ellen Ochoa, Tamara E. Jernigan, Daniel T. Barry, Julie Payette (Canadian), and Valery Ivanovich Tokarev (Russian). The primary goals of this mission were to work on logistics and resupply the International Space Station. This second part in the mission series features video from Flight Day 4-7 (FD 4-7). FD 4 of STS-96 presents astronauts Tammy Jernigan and Dan Barry completing the second longest space walk in shuttle history. Footage includes Jernigan and Barry transferring and installing two cranes from the shuttle's payload bay to locations on the outside of the station. The astronauts enter the International Space Station delivering supplies and prepare the outpost to receive its first resident crew, scheduled to arrive in early 2000 on FD 5. The video also captures the crew involved in logistics transfer activities within the Discovery/ISS orbiting complex. FD 6 includes footage of Valery Tokarev and Canadian astronaut Julie Payette charging out the final six battery recharge controller units for two of Zarya's power-producing batteries and all crew members' involvement in logistics transfer activities from the SPACEHAB module to designated locations in the International Space Station. With the transfer work of FD 6 all but complete, the astronauts conduct some additional work, installing parts of a wireless strain gauge system that will help engineers track the effects of adding modules to the station throughout its assembly. Moving the few remaining items from Discovery to the ISS, then closing a series of hatches within the station's modules leading back to the shuttle are the primary activities contained in FD 7. Final coverage features Discovery's astronauts finishing their work inside the International Space Station, closing all of the hatches and readying the shuttle's small thrusters to be fired to raise the entire complex's orbit in preparation for the undocking and departure set for FD 8.

Source record↗
NASA NTRS2011

The J-2X Fuel Turbopump - Design, Development, and Test

Pratt and Whitney Rocketdyne (PWR), a NASA subcontractor, is executing the design, development, test, and evaluation (DDT&E) of a liquid oxygen, liquid hydrogen two hundred ninety four thousand pound thrust rocket engine initially intended for the Upper Stage (US) and Earth Departure Stage (EDS) of the Constellation Program Ares-I Crew Launch Vehicle (CLV). A key element of the design approach was to base the new J-2X engine on the heritage J-2S engine with the intent of uprating the engine and incorporating SSME and RS-68 lessons learned. The J-2S engine was a design upgrade of the flight proven J-2 configuration used to put American astronauts on the moon. The J-2S Fuel Turbopump (FTP) was the first Rocketdyne-designed liquid hydrogen centrifugal pump and provided many of the early lessons learned for the Space Shuttle Main Engine High Pressure Fuel Turbopumps. This paper will discuss the design trades and analyses performed for the current J-2X FTP to increase turbine life; increase structural margins, facilitate component fabrication; expedite turbopump assembly; and increase rotordynamic stability margins. Risk mitigation tests including inducer water tests, whirligig turbine blade tests, turbine air rig tests, and workhorse gas generator tests characterized operating environments, drove design modifications, or identified performance impact. Engineering design, fabrication, analysis, and assembly activities support FTP readiness for the first J-2X engine test scheduled for July 2011.

Tellier, James G.↗
NASA NTRS2010

Altitude Testing of Large Liquid Propellant Engines

The National Aeronautics and Space Administration entered a new age on January 14, 2004 with President Bush s announcement of the creation the Vision for Space Exploration that will take mankind back to the Moon and on beyond to Mars. In January, 2006, after two years of hard, dedicated labor, engineers within NASA and its contractor workforce decided that the J2X rocket, based on the heritage of the Apollo J2 engine, would be the new engine for the NASA Constellation Ares upper stage vehicle. This engine and vehicle combination would provide assured access to the International Space Station to replace that role played by the Space Shuttle and additionally, would serve as the Earth Departure Stage, to push the Crew Excursion Vehicle out of Earth Orbit and head it on a path for rendezvous with the Moon. Test as you fly, fly as you test was chosen to be the guiding philosophy and a pre-requisite for the engine design, development, test and evaluation program. An exhaustive survey of national test facility assets proved the required capability to test the J2X engine at high altitude for long durations did not exist so therefore, a high altitude/near space environment testing capability would have to be developed. After several agency concepts the A3 High Altitude Testing Facility proposal was selected by the J2X engine program on March 2, 2007 and later confirmed by a broad panel of NASA senior leadership in May 2007. This facility is to be built at NASA s John C. Stennis Space Center located near Gulfport, Mississippi. 30 plus years of Space Shuttle Main Engine development and flight certification testing makes Stennis uniquely suited to support the Vision For Space Exploration Return to the Moon. Propellant handling infrastructure, engine assembly facilities, a trained and dedicated workforce and a broad and varied technical support base will all ensure that the A3 facility will be built on time to support the schedule needs of the J2X engine and the ultimate flight of the first Ares I vehicle. The A3 facility will be able to simulate pre-ignition altitude from sea-level to 100,000 feet and maintain it up to 650 seconds. Additionally the facility will be able to accommodate initial ignition, shutdown and then restart test profiles. A3 will produce up to 5000 lbm/sec of superheated steam utilizing a Chemical Steam generation system. Two separate inline steam ejectors will be used to produce a test cell vacuum to simulate the 100,000 ft required altitude. Operational capability will ensure that the facility can start up and shutdown without producing adverse pressure gradients across the J2X nozzle. The facility will have a modern thrust measurement system for accurate determination of engine performance. The latest advances in data acquisition and control will be incorporated to measure performance parameters during hotfire testing. Provisions are being made in the initial design of the new altitude facility to allow for testing of other, larger engines and potential upper stage launch vehicles that might require vacuum start testing of the engines. The new facility at Stennis Space Center will be complete and ready for hotfire operations in late 2010.

Maynard, Bryon T.↗
NASA NTRS2010

Testing to Transition the J-2X from Paper to Hardware

The J-2X Upper Stage Engine (USE) will be the first new human-rated upper stage engine since the Apollo program of the 1960s. It is designed to carry the Ares I and Ares V into orbit and send the Ares V to the Moon as part of NASA's Constellation Program. This paper will provide an overview of progress on the design, testing, and manufacturing of this new engine in 2009 and 2010. The J-2X embodies the program goals of basing the design on proven technology and experience and seeking commonality between the Ares vehicles as a way to minimize risk, shorten development times, and live within current budget constraints. It is based on the proven J-2 engine used on the Saturn IB and Saturn V launch vehicles. The prime contractor for the J-2X is Pratt & Whitney Rocketdyne (PWR), which is under a design, development, test, and engineering (DDT&E) contract covering the period from June 2006 through September 2014. For Ares I, the J-2X will provide engine start at approximately 190,000 feet, operate roughly 500 seconds, and shut down. For Ares V, the J-2X will start at roughly 190,000 feet to place the Earth departure stage (EDS) in orbit, shut down and loiter for up to five days, re-start on command and operate for roughly 300 seconds at its secondary power level to perform trans lunar injection (TLI), followed by final engine shutdown. The J-2X development effort focuses on four key areas: early risk mitigation, design risk mitigation, component and subassembly testing, and engine system testing. Following that plan, the J-2X successfully completed its critical design review (CDR) in 2008, and it has made significant progress in 2009 and 2010 in moving from the drawing board to the machine shop and test stand. Post-CDR manufacturing is well under way, including PWR in-house and vendor hardware. In addition, a wide range of component and sub-component tests have been completed, and more component tests are planned. Testing includes heritage powerpack, turbopump inducer water flow, turbine air flow, turbopump seal testing, main injector and gas generator, injector testing, augmented spark igniter testing, nozzle side loads cold flow testing, nozzle extension film cooling flow testing, control system testing with hardware in the loop, and nozzle extension emissivity coating tests. In parallel with hardware manufacturing, work is progressing on the new A-3 test stand to support full duration altitude testing. The Stennis A-2 test stand is scheduled to be turned over to the Constellation Program in September 2010 to be modified for J-2X testing also. As the structural steel was rising on the A-3 stand, work was under way in the nearby E complex on the chemical steam generator and subscale diffuser concepts to be used to evacuate the A-3 test cell and simulate altitude conditions.

Byrd, Tom↗
NASA NTRS2016

In-Flight Operation of the Dawn Ion Propulsion System Through the Low Altitude Mapping Orbit at Ceres

The Dawn mission, part of NASA’s Discovery Program, has as its goal the scientific exploration of the two most massive main-belt objects, Vesta and Ceres. The Dawn spacecraft was launched from the Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H- 9.5 (Delta-II Heavy) rocket that placed the 1218-kg spacecraft onto an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory for the heliocentric transfer to Vesta, orbit capture at Vesta, transfer between Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, transfer between Ceres science orbits, and orbit maintenance maneuvers. Full-power thrusting from December 2007 through October 2008 was used to successfully target a Mars gravity assist flyby in February 2009 that provided an additional ΔV of 2.6 km/s. Deterministic thrusting for the heliocentric transfer to Vesta resumed in June 2009 and concluded with orbit capture at Vesta on July 16, 2011. From July 2011 through September 2012 the IPS was used to transfer to all the different science orbits at Vesta and to escape from Vesta orbit. Cruise for a rendezvous with Ceres began in August 2012 and completed in late December 2014. From December 2014 through June 2016 the IPS was used for transiting the spacecraft to the Approach phase, survey orbit, the high altitude mapping orbit (HAMO), and the low altitude mapping orbit (LAMO) with arrival to LAMO on December 13, 2015, almost eight years after the start of deterministic thrusting to Vesta. The LAMO orbit, at a mean altitude above Ceres of approximately 385 km, is the spacecraft’s final destination and there are no plans to move the spacecraft from LAMO once science operations there are completed. Since arrival at LAMO Dawn’s IPS has been used for occasional orbit maintenance maneuvers while the spacecraft performs scientific investigations. Dawn has successfully completed its science goals and Dawn’s primary mission is scheduled to end June 30, 2016. To date the IPS has been operated for approximately 48,458 hours, consumed approximately 401 kg of xenon, and provided a delta-V of over 11.0 km/s, a record for an on-board propulsion system. The IPS performance characteristics are close to the expected performance based on analysis and testing performed pre-launch. Dawn’s IPS continues to be fully operational as of June 2016. This paper provides an overview of Dawn’s mission objectives and the results of Dawn IPS mission operations from Survey orbit through the completion of Dawn’s primary mission.

Garner, Charles E.↗
NASA NTRS2016

In-flight Operation of the Dawn Ion Propulsion System Through the Low Altitude Mapping Orbit at Ceres

The Dawn mission, part of NASA’s Discovery Program, has as its goal the scientific exploration of the two most massive main-belt objects, Vesta and Ceres. The Dawn spacecraft was launched from the Cape Canaveral Air Force Station on September 27, 2007 on a Delta-II 7925H- 9.5 (Delta-II Heavy) rocket that placed the 1218-kg spacecraft onto an Earth-escape trajectory. On-board the spacecraft is an ion propulsion system (IPS) developed at the Jet Propulsion Laboratory for the heliocentric transfer to Vesta, orbit capture at Vesta, transfer between Vesta science orbits, departure and escape from Vesta, heliocentric transfer to Ceres, orbit capture at Ceres, transfer between Ceres science orbits, and orbit maintenance maneuvers. Full-power thrusting from December 2007 through October 2008 was used to successfully target a Mars gravity assist flyby in February 2009 that provided an additional ΔV of 2.6 km/s. Deterministic thrusting for the heliocentric transfer to Vesta resumed in June 2009 and concluded with orbit capture at Vesta on July 16, 2011. From July 2011 through September 2012 the IPS was used to transfer to all the different science orbits at Vesta and to escape from Vesta orbit. Cruise for a rendezvous with Ceres began in August 2012 and completed in late December 2014. From December 2014 through June 2016 the IPS was used for transiting the spacecraft to the Approach phase, survey orbit, the high altitude mapping orbit (HAMO), and the low altitude mapping orbit )LAMO) with arrival to LAMO on December 13, 2015, almost eight years after the start of deterministic thrusting to Vesta. The LAMO orbit, at a mean altitude above Ceres of approximately 385 km, is the spacecraft’s final destination and there are no plans to move the spacecraft from LAMO once science operations there are completed. Since arrival at LAMO Dawn’s IPS has been used for occasional orbit maintenance maneuvers while the spacecraft performs scientific investigations. Dawn has successfully completed its science goals and Dawn’s primary mission is scheduled to end in the summer of 2016. To date the IPS has been operated for over 48,454 hours, consumed approximately 401 kg of xenon, and provided a delta-V of over 11.0 km/s, a record for an on-board propulsion system. The IPS performance characteristics are close to the expected performance based on analysis and testing performed pre-launch. Dawn’s IPS continues to be fully operational as of June 2016. This paper provides an overview of Dawn’s mission objectives and the results of Dawn IPS mission operations from Survey orbit through June 2016.

Garner, Charles E.↗
NASA NTRS2017

ATD-2 Surface Scheduling and Metering Concept

This presentation describes the concept of ATD-2 tactical surface scheduling and metering. The concept is composed of several elements, including data exchange and integration; surface modeling; surface scheduling; and surface metering. The presentation explains each of the elements. Surface metering is implemented to balance demand and capacity• When surface metering is on, target times from surface scheduler areconverted to advisories for throttling demand• Through the scheduling process, flights with CTOTs will not get addedmetering delay (avoids potential for ‘double delay’)• Carriers can designate certain flights as exempt from metering holds• Demand throttle in Phase 1 at CLT is through advisories sent to rampcontrollers for pushback instructions to the flight deck– Push now– Hold for an advised period of time (in minutes)• Principles of surface metering can be more generally applied to otherairports in the NAS to throttle demand via spot-release times (TMATs Strong focus on optimal use of airport resources• Flexibility enables stakeholders to vary the amount of delay theywould like transferred to gate• Addresses practical aspects of executing surface metering in aturbulent real world environment• Algorithms designed for both short term demand/capacityimbalances (banks) or sustained metering situations• Leverage automation to enable surface metering capability withoutrequiring additional positions• Represents first step in Tactical/Strategic fusion• Provides longer look-ahead calculations to enable analysis ofstrategic surface metering potential usage

Departure↗
NASA NTRS2004

Improved Estimate of Phobos Secular Acceleration from MOLA Observations

We report on new observations of the orbital position of Phobos, and use them to obtain a new and improved estimate of the rate of secular acceleration in longitude due to tidal dissipation within Mars. Phobos is the inner-most natural satellite of Mars, and one of the few natural satellites in the solar system with orbital period shorter than the rotation period of its primary. As a result, any departure from a perfect elastic response by Mars in the tides raised on it by Phobos will cause a transfer of angular momentum from the orbit of Phobos to the spin of Mars. Since its discovery in 1877, Phobos has completed over 145,500 orbits, and has one of the best studied orbits in the solar system, with over 6000 earth-based astrometric observations, and over 300 spacecraft observations. As early as 1945, Sharpless noted that there is a secular acceleration in mean longitude, with rate (1.88 + 0.25) 10(exp -3) degrees per square year. In preparation for the 1989 Russian spacecraft mission to Phobos, considerable work was done compiling past observations, and refining the orbital model. All of the published estimates from that era are in good agreement. A typical solution (Jacobson et al., 1989) yields (1.249 + 0.018) 10(exp -3) degrees per square year. The MOLA instrument on MGS is a laser altimeter, and was designed to measure the topography of Mars. However, it has also been used to make observations of the position of Phobos. In 1998, a direct range measurement was made, which indicated that Phobos was slightly ahead of the predicted position. The MOLA detector views the surface of Mars in a narrow field of view, at 1064 nanometer wavelength, and can detect shadows cast by Phobos on the surface of Mars. We have found 15 such serendipitous shadow transit events over the interval from xx to xx, and all of them show Phobos to be ahead of schedule, and getting progressively farther ahead of the predicted position. In contrast, the cross-track positions are quite close to the predicted values. Assuming that the along-track discrepancy is small enough that we can linearize the corrections, we model the mean orbital longitude as a quadratic function of time, and solve for corrections to the constant, linear, and quadratic terms. The time span of the recent observations is insufficient to properly resolve this issue alone, but when the 127 years of prior observations are added, we find a solution which reduces misfit to the new observations considerably, and makes no significant change to the fit to earlier observations. Our estimate for the secular acceleration term is (1.367 + 0.006) degrees per square year. The corresponding rate of energy dissipation is 3.34 MW. From a geophysical perspective, a more interesting parameter than the secular acceleration itself is the tidal lag angle, or tidal quality factor Q, for Mars. Unfortunately, the limiting error source in that determination is remaining uncertainty in the tidal Love numbers at harmonic degrees 2,3, and even 4. Until those parameters are better constrained, improvement in the orbital model of Phobos will not provide corresponding benefits for understanding the interior of Mars.

Bills, Bruce↗
NASA NTRS2016

An Integrated Gate Turnaround Management Concept Leveraging Big Data Analytics for NAS Performance Improvements

"Gate Turnaround" plays a key role in the National Air Space (NAS) gate-to-gate performance by receiving aircraft when they reach their destination airport, and delivering aircraft into the NAS upon departing from the gate and subsequent takeoff. The time spent at the gate in meeting the planned departure time is influenced by many factors and often with considerable uncertainties. Uncertainties such as weather, early or late arrivals, disembarking and boarding passengers, unloading/reloading cargo, aircraft logistics/maintenance services and ground handling, traffic in ramp and movement areas for taxi-in and taxi-out, and departure queue management for takeoff are likely encountered on the daily basis. The Integrated Gate Turnaround Management (IGTM) concept is leveraging relevant historical data to support optimization of the gate operations, which include arrival, at the gate, departure based on constraints (e.g., available gates at the arrival, ground crew and equipment for the gate turnaround, and over capacity demand upon departure), and collaborative decision-making. The IGTM concept provides effective information services and decision tools to the stakeholders, such as airline dispatchers, gate agents, airport operators, ramp controllers, and air traffic control (ATC) traffic managers and ground controllers to mitigate uncertainties arising from both nominal and off-nominal airport gate operations. IGTM will provide NAS stakeholders customized decision making tools through a User Interface (UI) by leveraging historical data (Big Data), net-enabled Air Traffic Management (ATM) live data, and analytics according to dependencies among NAS parameters for the stakeholders to manage and optimize the NAS performance in the gate turnaround domain. The application will give stakeholders predictable results based on the past and current NAS performance according to selected decision trees through the UI. The predictable results are generated based on analysis of the unique airport attributes (e.g., runway, taxiway, terminal, and gate configurations and tenants), and combined statistics from past data and live data based on a specific set of ATM concept-of-operations (ConOps) and operational parameters via systems analysis using an analytic network learning model. The IGTM tool will then bound the uncertainties that arise from nominal and off-nominal operational conditions with direct assessment of the gate turnaround status and the impact of a certain operational decision on the NAS performance, and provide a set of recommended actions to optimize the NAS performance by allowing stakeholders to take mitigation actions to reduce uncertainty and time deviation of planned operational events. An IGTM prototype was developed at NASA Ames Simulation Laboratories (SimLabs) to demonstrate the benefits and applicability of the concept. A data network, using the System Wide Information Management (SWIM)-like messaging application using the ActiveMQ message service, was connected to the simulated data warehouse, scheduled flight plans, a fast-time airport simulator, and a graphic UI. A fast-time simulation was integrated with the data warehouse or Big Data/Analytics (BAI), scheduled flight plans from Aeronautical Operational Control AOC, IGTM Controller, and a UI via a SWIM-like data messaging network using the ActiveMQ message service, illustrated in Figure 1, to demonstrate selected use-cases showing the benefits of the IGTM concept on the NAS performance.

Efficent ATM systems↗
NASA NTRS2017

Subject Matter Expert Evaluation of Multi-Flight Common Route Advisories

Traffic flow management seeks to balance the demand for National Airspace System (NAS) flight resources, such as airspace and airports, with the available supply. When forecasted weather blocks nominal air traffic routes, traffic managers must re-route affected flights for weather avoidance. Depending on the nature and scope of the weather, traffic managers may use pre-coordinated re-routes such as Playbook Routes or Coded Departure Routes, or may design ad hoc local re-routes. The routes of affected flights are modified accordingly. These weather avoidance routes will, of course, be less efficient than the nominal routes due to increased flight time and fuel burn. In current traffic management operations, the transition into a weather avoidance re-routing initiative is typically implemented more aggressively than the transition out of that initiative after the weather has dissipated or moved away. For example, strategic large-scale Playbook re-routes are sometimes left in place (as initially implemented) for many hours before being lifted entirely when the weather dissipates. There is an opportunity to periodically modify the re-routing plan as weather evolves, thereby attenuating its adverse impact on flight time and fuel consumption; this is called delay recovery. Multi-Flight Common Routes (MFCR) is a NASA-developed operational concept and associated decision support tool for delay recovery, designed to assist traffic managers to efficiently update weather avoidance traffic routes after the original re-routes have become stale due to subsequent evolution of the convective weather system. MFCR groups multiple flights to reduce the number of advisories that the traffic manager needs to evaluate, and also merges these flights on a common route segment to provide an orderly flow of re-routed traffic. The advisory is presented to the appropriate traffic manager who evaluates it and has the option to modify it using MFCRs graphical user interface. If the traffic manager finds the advisory to be operationally appropriate, he or she would coordinate with the Area Supervisor(s) of the sectors that currently control the flights in the advisory. When the traffic manager accepts the MFCR advisory via the user interface, the corresponding flight plan amendments would be sent to the displays of the appropriate sector controllers, using the Airborne Re-Routing (ABRR) capability which is scheduled for nationwide operation in 2017. The sector controllers would then offer this time-saving route modification to the pilots of the affected flights via datalink (or voice), and implement the corresponding flight plan amendment if the pilots accept it. MFCR is implemented as an application in the software environment of the Future Air traffic management Concepts Evaluation Tool (FACET). This paper focuses on an initial subject matter expert (SME) evaluation of MFCR. The evaluation covers MFCRs operational concept, algorithm, and user interface.

Human-in-the-loop Evaluation↗
NASA NTRS2017

Subject Matter Expert Evaluation of Multi-Flight Common Route Advisories

Traffic flow management seeks to balance the demand for National Airspace System (NAS) flight resources, such as airspace and airports, with the available supply. When forecasted weather blocks nominal air traffic routes, traffic managers must re-route affected flights for weather avoidance. Depending on the nature and scope of the weather, traffic managers may use pre-coordinated re-routes such as Playbook Routes or Coded Departure Routes, or may design ad hoc local re-routes. The routes of affected flights are modified accordingly. These weather avoidance routes will, of course, be less efficient than the nominal routes due to increased flight time and fuel burn. In current traffic management operations, the transition into a weather avoidance re-routing initiative is typically implemented more aggressively than the transition out of that initiative after the weather has dissipated or moved away. For example, strategic large-scale Playbook re-routes are sometimes left in place (as initially implemented) for many hours before being lifted entirely when the weather dissipates. There is an opportunity to periodically modify the re-routing plan as weather evolves, thereby attenuating its adverse impact on flight time and fuel consumption; this is called delay recovery. Multi-Flight Common Routes (MFCR) is a NASA-developed operational concept and associated decision support tool for delay recovery, designed to assist traffic managers to efficiently update weather avoidance traffic routes after the original re-routes have become stale due to subsequent evolution of the convective weather system. MFCR groups multiple flights to reduce the number of advisories that the traffic manager needs to evaluate, and also merges these flights on a common route segment to provide an orderly flow of re-routed traffic. The advisory is presented to the appropriate traffic manager who evaluates it and has the option to modify it using MFCRs graphical user interface. If the traffic manager finds the advisory to be operationally appropriate, he or she would coordinate with the Area Supervisor(s) of the sectors that currently control the flights in the advisory. When the traffic manager accepts the MFCR advisory via the user interface, the corresponding flight plan amendments would be sent to the displays of the appropriate sector controllers, using the Airborne Re-Routing (ABRR) capability which is scheduled for nationwide operation in 2017. The sector controllers would then offer this time-saving route modification to the pilots of the affected flights via datalink (or voice), and implement the corresponding flight plan amendment if the pilots accept it. MFCR is implemented as an application in the software environment of the Future Air traffic management Concepts Evaluation Tool (FACET). This paper focuses on an initial subject matter expert (SME) evaluation of MFCR. The evaluation covers MFCRs operational concept, algorithm, and user interface.

Traffic flow management↗