Search NASA⌕ Search

SEARCH · Search NASA

Results for “Weather avoidance”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 37 records · Page 2

Evaluation of a Dispatcher's Route Optimization Decision Aid to Avoid Aviation Weather Hazards

This document describes the results and analysis of the formal evaluation plan for the Honeywell software tool developed under the NASA AWIN (Aviation Weather Information) 'Weather Avoidance using Route Optimization as a Decision Aid' project. The software tool aims to provide airline dispatchers with a decision aid for selecting optimal routes that avoid weather and other hazards. This evaluation compares and contrasts route selection performance with the AWIN tool to that of subjects using a more traditional dispatcher environment. The evaluation assesses gains in safety, in fuel efficiency of planned routes, and in time efficiency in the pre-flight dispatch process through the use of the AWIN decision aid. In addition, we are interested in how this AWIN tool affects constructs that can be related to performance. The construct of Situation Awareness (SA), workload, trust in an information system, and operator acceptance are assessed using established scales, where these exist, as well as through the evaluation of questionnaire responses and subject comments. The intention of the experiment is to set up a simulated operations area for the dispatchers to work in. They will be given scenarios in which they are presented with stored company routes for a particular city-pair and aircraft type. A diverse set of external weather information sources is represented by a stand-alone display (MOCK), containing the actual historical weather data typically used by dispatchers. There is also the possibility of presenting selected weather data on the route visualization tool. The company routes have not been modified to avoid the weather except in the case of one additional route generated by the Honeywell prototype flight planning system. The dispatcher will be required to choose the most appropriate and efficient flight plan route in the displayed weather conditions. The route may be modified manually or may be chosen from those automatically displayed.

Dorneich, Michael C.↗

Weather Avoidance Guidelines for NASA Global Hawk High-Altitude Unmanned Aircraft Systems (UAS)

The current Global Hawk flight rules would probably not have been effective in the single event of greatest concern (the Emily encounter). The cloud top had not reached 50,000 ft until minutes before the encounter. The TOT and lightning data would not have been available until near the overflight time since this was a rapidly growing cell. This case would have required a last‐minute diversion when lightning became frequent. Avoiding such a cell probably requires continual monitoring of the forward camera and storm scope, whether or not cloud tops have been exceeding specific limits. However, the current overflight rules as strictly interpreted would have prohibited significant fractions of the successful Global Hawk overpasses of Karl and Matthew that proved not to be hazardous. Many other high altitude aircraft (ER‐2 and Global Hawk) flights in NASA tropical cyclone field programs have successfully overflown deep convective clouds without incident.The convective cell that caused serious concern about the safety of the ER‐2 in Emily was especially strong for a tropical cyclone environment, probably as strong or stronger than any that was overflown by the ER‐2 in 20 previous flights over tropical cyclones. Specifically, what made that cell a safety concern was the magnitude of the vertical velocity of the updraft, at least 20 m/s (4000 ft/minute) at the time the ER‐2 overflew it. Such a strong updraft can generate strong gravity waves at and above the tropopause, posing a potential danger to aircraft far above the maximum altitude of the updraft itself or its associated cloud top. Indeed, the ER‐2 was probably at least 9000 ft above that cloud top. Cloud‐top height, by itself, is not an especially good indicator of the intensity of convection and the likelihood of turbulence. Nor is overflying high cloud tops (i.e. > 50,000 ft) of particular concern unless there is other evidence of very strong convective updrafts beneath those tops in the path of the aircraft. center dot Lightning, especially lightning with a high flash rate, is well correlated with convective intensity. Lightning with a minimal flash rate (say 1‐3 flashes per minute) is indicative of updraft speeds of about 10 m/s in the mixed phase region where charge is being separated, generally at altitudes about 20‐25 kft in a hurricane. That is still stronger than typical updrafts (more like 5 m/s). An unresolved issue is whether there is a high and instantaneous correlation between vertical velocity in the middle troposphere (necessary for lightning generation) and near cloud top (more direct concern for overflights).

Cecil, Daniel J.↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Weather Routes (DWR) Technology Transfer Document Summary Version 1.0

Airspace Technology Demonstration #3 (ATD-3) is part of NASA's Airspace Operations and Safety Program (AOSP) - specifically, its Airspace Technology Demonstrations (ATD) Project. ATD-3 is a multiyear research and development effort which proposes to develop and demonstrate automation technologies and operating concepts that enable air navigation service providers and airspace users to continuously assess weather, winds, traffic, and other information to identify, evaluate, and implement workable opportunities for flight plan route corrections that can result in significant flight time and fuel savings in en route airspace. In order to ensure that the products of this tech-transfer are relevant and useful, NASA has created strong partnerships with the FAA and key industry stakeholders. This summary document and accompanying technology artifacts satisfy the first of three Research Transition Products (RTPs) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan. This transfer consists of NASA's legacy Dynamic Weather Routes (DWR) work for efficient routing for en-route weather avoidance. DWR is a ground-based trajectory automation system that continuously and automatically analyzes active airborne aircraft in en route airspace to identify opportunities for simple corrections to flight plan routes that can save significant flying time, at least five minutes wind-corrected, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions. The key benefit of the DWR concept is to let automation continuously and automatically analyze active flights to find those where simple route corrections can save significant time and fuel. Operators are busy during weather events. It is more effective to let automation find the opportunities for high-value route corrections.

ATD-3↗

Step 1: Human System Integration Pilot-Technology Interface Requirements for Weather Management

This document involves definition of technology interface requirements for Hazardous Weather Avoidance. Technology concepts in use by the Access 5 Weather Management Work Package were considered. Beginning with the Human System Integration (HIS) high-level functional requirement for Hazardous Weather Avoidance, and Hazardous Weather Avoidance technology elements, HSI requirements for the interface to the pilot were identified. Results of the analysis describe (1) the information required by the pilot to have knowledge of hazardous weather, and (2) the control capability needed by the pilot to obtain hazardous weather information. Fundamentally, these requirements provide the candidate Hazardous Weather Avoidance technology concepts with the necessary human-related elements to make them compatible with human capabilities and limitations. The results of the analysis describe how Hazardous Weather Avoidance operations and functions should interface with the pilot to provide the necessary Weather Management functionality to the UA-pilot system. Requirements and guidelines for Hazardous Weather Avoidance are partitioned into four categories: (1) Planning En Route (2) Encountering Hazardous Weather En Route, (3) Planning to Destination, and (4) Diversion Planning Alternate Airport. Each requirement is stated and is supported with a rationale and associated reference(s).

Source record↗

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↗

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↗

Weather Guidance for UAS Urban Medical Transport Missions

Unmanned aircraft will revolutionize healthcare services by providing efficient and expeditious delivery of life-saving transplant organs and supplies to hospitals in urban environments, where road traffic and congestion can slow delivery times and endanger lives. Bell has developed the Autonomous Pod Transport (APT) vehicle to serve this market, with entry into service in mid-2020s. Adverse weather conditions can introduce risks and inefficiencies in urban environments leading to flight delays and cancellations. In 2018, National Aeronautics and Space Administration (NASA) and Bell entered into a cooperative agreement, under the Systems Integration and Operationalization (SIO) program to tackle key challenges to enable future commercial unmanned aircraft operations. The Center for Collaborative Adaptive Sensing of the Atmosphere (CASA) at the University of Massachusetts, Amherst, joined this team to demonstrate weather avoidance technologies for remotely piloted and autonomous vehicles. CASA has developed the ‘City Warn’ hazard alerting platform to gather weather information from various weather sensors and models, and based on user (or mission) preferences for alerting and on user (or unmanned aircraft) locations, the platform shares timely weather intelligence with users and the systems used by them for remote operations. This presentation discusses the weather avoidance solution developed during this project, leading up to the demonstration of the end-to-end system in Fall 2020. The presentation will cover the following topics: 1) goals related to weather avoidance 2) the design requirements process, including the results of pilot interviews, 3) weather observation and avoidance needs 4) selection of regional and national weather data sets 5) design of the weather graphical interface and 6) considerations for real-time weather alerting. The end-to-end system that was developed will be discussed, along with the results from the demonstration flight. The presentation will conclude with insights from the project team on lessons learned and best practices on weather avoidance technologies for the industry going ahead.

weather avoidance↗

Weather Guidance for UAS Urban Medical Transport Missions

Unmanned aircraft will revolutionize healthcare services by providing efficient and expeditious delivery of life-saving transplant organs and supplies to hospitals in urban environments, where road traffic and congestion can slow delivery times and endanger lives. Bell has developed the Autonomous Pod Transport (APT) vehicle to serve this market, with entry into service in mid-2020s. Adverse weather conditions can introduce risks and inefficiencies in urban environments leading to flight delays and cancellations. In 2018, National Aeronautics and Space Administration (NASA) and Bell entered into a cooperative agreement, under the Systems Integration and Operationalization (SIO) program to tackle key challenges to enable future commercial unmanned aircraft operations. The Center for Collaborative Adaptive Sensing of the Atmosphere (CASA) at the University of Massachusetts, Amherst, joined this team to demonstrate weather avoidance technologies for remotely piloted and autonomous vehicles. CASA has developed the ‘City Warn’ hazard alerting platform to gather weather information from various weather sensors and models, and based on user (or mission) preferences for alerting and on user (or unmanned aircraft) locations, the platform shares timely weather intelligence with users and the systems used by them for remote operations. This presentation discusses the weather avoidance solution developed during this project, leading up to the demonstration of the end-to-end system in Fall 2020. The presentation will cover the following topics: 1) goals related to weather avoidance 2) the design requirements process, including the results of pilot interviews, 3) weather observation and avoidance needs 4) selection of regional and national weather data sets 5) design of the weather graphical interface and 6) considerations for real-time weather alerting. The end-to-end system that was developed will be discussed, along with the results from the demonstration flight. The presentation will conclude with insights from the project team on lessons learned and best practices on weather avoidance technologies for the industry going ahead.

weather avoidance↗

Concept of Operations for the NASA Weather Accident Prevention (WxAP) Project

The Weather Accident Prevention Concept of Operations (CONOPS) serves as a decision-making framework for research and technology development planning. It is intended for use by the WxAP members and other related programs in NASA and the FAA that support aircraft accident reduction initiatives. The concept outlines the project overview for program level 3 elements-such as AWIN, WINCOMM, and TPAWS (Turbulence)-that develop the technologies and operating capabilities to form the building blocks for WxAP. Those building blocks include both retrofit of equipment and systems and development of new aircraft, training technologies, and operating infrastructure systems and capabilities. This Concept of operations document provides the basis for the WxAP project to develop requirements based on the operational needs ofthe system users. It provides the scenarios that the flight crews, airline operations centers (AOCs), air traffic control (ATC), and flight service stations (FSS) utilize to reduce weather related accidents. The provision to the flight crew of timely weather information provides awareness of weather situations that allows replanning to avoid weather hazards. The ability of the flight crew to locate and avoid weather hazards, such as turbulence and hail, contributes to safer flight practices.

Green, Walter S.↗

Integration of Dynamic Weather Routes Automation with Air/Ground Data Communications

The Dynamic Weather Routes (DWR) toolcontinuously and automatically analyzes airborne flights in en route airspace to identify flights where a route correction could save significant flight time and still avoid weather. A partnership between NASA, American Airlines (AA), and the FAA has enabled testing of DWR in real-world air traffic operations. En route Data Communications (Data Comm) could significantly reduce the controller and pilot workload needed to communicate DWR route changes under today’s voice-based operations and thereby enable more timely and frequent high-value corrections to weather avoidance routes. Sample data from the DWR trial at AA illustrate how Data Comm could improve DWR operations. Two operating concepts that integrate DWR with Data Comm are described:(1) route corrections are initiated by air traffic control and implemented using Airborne Reroutes and Data Comm, and (2) route corrections are initiated by the dispatcher and pilot and implemented via Data Comm. Both concepts align with Federal Aviation Administration (FAA) plans for implementation ofData Comm in en route airspace.

weather avoidance↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Routes for Arrivals in Weather (DRAW) Technology Transfer Document Summary Version 2.0

Airspace Technology Demonstration – 3 (ATD-3) is part of NASA’s Airspace Operations and Safety Program (AOSP) – specifically, its Airspace Technology Demonstrations (ATD) Project. ATD-3 is a multi-year research and development effort which proposes to develop and demonstrate automation technologies and operating concepts that enable air navigation service providers and airspace users to continuously assess weather, winds, traffic, and other information to identify, evaluate, and implement workable opportunities for flight plan route corrections that can result in significant flight time and fuel savings in en route airspace. In order to ensure that the products of this tech-transfer are relevant and useful, NASA has created strong partnerships with the FAA and key industry stakeholders. This summary document and accompanying technology artifacts satisfy the third Research Transition Product (RTP) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan, which is Dynamic Routes for Arrivals in Weather (DRAW). This technology transfer consists of artifacts for DRAW Arrival Metering (AM) Operations delivered in June 2018, DRAW AM updates, and DRAW Extended Metering (XM) Operations. Blue highlighting indicates the new or modified deliverables. Some of the artifacts in this technology transfer have distribution restrictions that need to be followed. Distribution information is noted in each section. DRAW is a trajectory-based system that combines the legacy Dynamic Weather Routes (DWR) weather avoidance technology with an arrival-specific rerouting algorithm and arrival scheduler to improve traffic flows on weather-impacted arrival routes into major airports. First, DRAW identifies flights that could be rerouted to more efficient Standard Terminal Arrival Routes (STARs) that may have previously been impacted by weather. Second, when weather is impacting the arrival routing, DRAW proposes simple arrival route corrections that enable aircraft to stay on their flight plan while avoiding weather. The DRAW system proposes reroutes early enough to allow Time Based Flow Management (TBFM) to make the necessary schedule adjustments. As a result, metering operations can be sustained longer and more consistently in the presence of weather because the arrival schedule accounts for the dynamic routing intent of arrival flights to deviate around weather. The first DRAW tech transfer in June 2018 focused on arrival metering operations with the DRAW algorithm implemented in the NASA Center TRACON Automation System (CTAS) automation software. This tech transfer delivery includes updates for DRAW implemented in FAA’s TBFM 4.7 automation software and preliminary research into DRAW for XM operations.

Isaacson, Douglas R.↗

Airspace Technology Demonstration 3 (ATD-3): Dynamic Weather Routes (DWR) Technology Transfer Document Summary Version 2.0

This summary document and accompanying technology artifacts satisfy the first of three Research Transition Products (RTPs) defined in the Applied Traffic Flow Management (ATFM) Research Transition Team (RTT) Plan. The original transfer, completed in September 2016, consisted of NASA's legacy Dynamic Weather Routes (DWR) work for efficient routing for en-route weather avoidance. This transfer updates the Concept of Operations document to a publicly-available NASA Technical Memorandum. Dynamic Weather Routes (DWR) is a ground-based trajectory automation system that continuously and automatically analyzes active in-flight aircraft in en route airspace to identify opportunities for simple corrections to flight plan routes that can save significant flying time, at least five minutes wind-corrected, while avoiding weather and considering traffic conflicts, airspace sector congestion, special use airspace, and FAA routing restrictions.

DWR↗

Analysis of Multi-Flight Common Routes for Traffic Flow Management

This paper presents an approach for creating common weather avoidance reroutes for multiple flights and the associated benefits analysis, which is an extension of the single flight advisories generated using the Dynamic Weather Routes (DWR) concept. These multiple flight advisories are implemented in the National Airspace System (NAS) Constraint Evaluation and Notification Tool (NASCENT), a nation-wide simulation environment to generate time- and fuel-saving alternate routes for flights during severe weather events. These single flight advisories are clustered together in the same Center by considering parameters such as a common return capture fix. The clustering helps propose routes called, Multi-Flight Common Routes (MFCR), that avoid weather and other airspace constraints, and save time and fuel. It is expected that these routes would also provide lower workload for traffic managers and controllers since a common route is found for several flights, and presumably the route clearances would be easier and faster. This study was based on 30-days in 2014 and 2015 each, which had most delays attributed to convective weather. The results indicate that many opportunities exist where individual flight routes can be clustered to fly along a common route to save a significant amount of time and fuel, and potentially reducing the amount of coordination needed.

weather uncertainty↗

Impact of Conflict Avoidance Responsibility Allocation on Pilot Workload in a Distributed Air Traffic Management System

Pilot workload was examined during simulated flights requiring flight deck-based merging and spacing while avoiding weather. Pilots used flight deck tools to avoid convective weather and space behind a lead aircraft during an arrival into Louisville International airport. Three conflict avoidance management concepts were studied: pilot, controller or automation primarily responsible. A modified Air Traffic Workload Input Technique (ATWIT) metric showed highest workload during the approach phase of flight and lowest during the en-route phase of flight (before deviating for weather). In general, the modified ATWIT was shown to be a valid and reliable workload measure, providing more detailed information than post-run subjective workload metrics. The trend across multiple workload metrics revealed lowest workload when pilots had both conflict alerting and responsibility of the three concepts, while all objective and subjective measures showed highest workload when pilots had no conflict alerting or responsibility. This suggests that pilot workload was not tied primarily to responsibility for resolving conflicts, but to gaining and/or maintaining situation awareness when conflict alerting is unavailable.

Ligda, Sarah V.↗

Multi-Flight Common Routes

Flights often experience large delays when they are routed around weather. Multi-flight common routes advisories provide delay recovery by suggesting time-saving re-routes for groups of flights whose current weather-avoidance routes have become outdated because the weather has dissipated and/or moved away. The multi-flight common routes tool provides time-saving route change advisories taking into account flight plans, wind fields, and the spatio-temporal evolution of predicted convective weather. A graphical user interface enables these advisories to be easily modified by a traffic manager for possible operational implementation.

ATD-3↗

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.

conops↗

Traffic Management Coordinator Evaluation of the Dynamic Weather Routes Concept and System

Dynamic Weather Routes (DWR) is a weather-avoidance system for airline dispatchers and FAA traffic managers that continually searches for and advises the user of more efficient routes around convective weather. NASA and American Airlines (AA) have been conducting an operational trial of DWR since July 17, 2012. The objective of this evaluation is to assess DWR from a traffic management coordinator (TMC) perspective, using recently retired TMCs and actual DWR reroutes advisories that were rated acceptable by AA during the operational trial. Results from the evaluation showed that the primary reasons for a TMC to modify or reject airline reroute requests were related to airspace configuration. Approximately 80 percent of the reroutes evaluated required some coordination before implementation. Analysis showed TMCs approved 62 percent of the requested DWR reroutes, resulting in 57 percent of the total requested DWR time savings.

weather avoidance↗

Dynamic Weather Routes: Two Years of Operational Testing at American Airlines

The Dynamic Weather Routes (DWR) tool continuously analyzes active flights in en-route airspace and finds simple route corrections to achieve more time- and fuel-efficient routes around convective weather. A strong partnership between NASA, American Airlines (AA), and the Federal Aviation Administration has enabled testing of DWR in real-world air traffic operations. NASA and AA have been conducting a trial of DWR at AA’s Integrated Operations Center in Fort Worth, Texas since July 2012. This paper describes test results based on AA’s use of DWR for their flights in and around Fort Worth Center (ZFW). Results indicate an actual savings of 3,290 flying minutes for 526 AA revenue flights from January 2013 through September 2014. Of these, 48 flights each indicate a savings of 15 minutes or more. Potential savings for all flights in ZFW airspace, corrected for savings flights achieve today through normal pilot requests and controller clearances, is about 100,000 flying minutes for 15,000 flights in 2013. Results indicate that AA flights with DWR in use realize about 20 percent more savings than non-AA flights. A weather forecast analysis examines the extent to which DWR routes rated acceptable by AA users remain clear of downstream weather. A sector congestion analysis indicates congestion could be reduced 19-38 percent if all flights fly DWR routes rather than nominal weather-avoidance routes.

Trajectory Automation↗