9 research outputs found
Air Traffic Management Technology Demonstration - 3 (ATD-3) Multi-Flight Common Route (MFCR) Concept of Operations Version 1.0
NASA's Multi Flight Common Route (MFCR) automation represents one element of those technologies focusing primarily on delay recovery in the en route phase of flight. Delay recovery is an attenuation of flight-time delay, accomplished by periodically revising weather-avoidance routing as the convective weather system evolves. MFCR is intended for use by Traffic Management Coordinators (TMCs) in Air Route Traffic Control Centers (ARTCCs, or Centers) and traffic management specialists (TMSs) in the Air Traffic Control System Command Center (ATCSCC). MFCR leverages existing weather, airspace, and traffic data, as well as improvements in navigation, surveillance, communication, and digital information technologies, to build on existing ATM automation and address some of the shortcomings associated with strategic traffic flow management initiatives and weather forecasting uncertainties. These capabilities provide significant potential benefits in the form of time, fuel, and cost savings. The concept of operations described in this document describes MFCR functionality as delivered by NASA to the FAA in December 2017, including a list of potential enhancements that may be realized when the system is fielded
Air Traffic Management Technology Demonstration - 3 (ATD-3): Operational Concept for the Integration of ATD-3 Capabilities Version 1.0
ATD-3 has developed four capabilities to address its goal and objectives. The four ATD-3 capabilities include: Dynamic Weather Routes (DWR), Multi-Flight Common Routes (MFCR), Traffic Aware Strategic Aircrew Requests (TASAR), and Dynamic Routes for Arrivals in Weather (DRAW). This document describes the long-term, mature vision for the use and incorporation of the ATD-3 capabilities into the National Airspace System (NAS). This vision describes their complementary interaction and the benefit capture that accrues from use. Recognizing that all capabilities are unlikely to be implemented in unison, each of the capabilities is designed and able to be implemented independently. As discrete portions of the integrated capabilities are planned, additional integration efforts should be undertaken to validate the complementary interactions and benefit pool are realized from the selected subset