Publications
Tagged As
An analysis of the impacts of wake vortex restrictions at LGA
September 16, 2002
Project Report
Published in:
Project Report ATC-305, MIT Lincoln Laboratory
Summary
Wake vortex restrictions at New York's La Guardia airport cause a significant reduction in capacity when aircraft land on runway 22 and depart on runway 31. This report presents an analysis of the annual delay cost at LGA associated with the wake vortex restrictions. We find that the delay due to these restrictions exceeds 4000 hours annually, and that these restrictions cause a significant workload increase to controllers at both La Guardia and the New York TRACON. If traffic levels were to increase 10% from their February 2001 levels, the corresponding increase in delay due to the wake vortex restrictions would rise from 30 hours a day to over 400 hours a day in this runway configuration. It is also found that for a meaningful increase in passenger capacity in this runway configuration to be as demand grows, restrictions must be reduced from their current levels. If the percentage of heavy/757's doubled at LGA, there would be no increase in passenger capacity while daily delays in this runway configuration due to current wake vortex separation standards would increase by 250 hours.
Summary
Wake vortex restrictions at New York's La Guardia airport cause a significant reduction in capacity when aircraft land on runway 22 and depart on runway 31. This report presents an analysis of the annual delay cost at LGA associated with the wake vortex restrictions. We find that the delay due...
READ MORE
An analysis of the impacts of wake vortex restrictions at LGA
September 16, 2002
Project Report
Published in:
MIT Lincoln Laboratory Report ATC-305
Summary
Wake vortex restrictions at New York's La Guardia airport cause a significant reduction in capacity when aircraft land on runway 22 and depart on runway 31. This report presents an analysis of the annual delay cost at LGA associated with the wake vortex restrictions. We find that the delay due to these restrictions exceeds 4000 hours annually, and that these restrictions cause a significant workload increase to controllers at both La Guardia and the New York TRACON. If traffic levels were to increase 10% from their February 2001 levels, the corresponding increase in delay due to the wake vortex restrictions would rise from 30 hours a day to over 400 hours a day in this runway configuration. It is also found that for a meaningful increase in passenger capacity in this runway configuration to be as demand grows, restrictions must be reduced from their current levels. If the percentage of heavy/757's doubled at LGA, there would be no increase in passenger capacity while daily delays in this runway configuration due to current wake vortex separation standards would increase by 250 hours.
Summary
Wake vortex restrictions at New York's La Guardia airport cause a significant reduction in capacity when aircraft land on runway 22 and depart on runway 31. This report presents an analysis of the annual delay cost at LGA associated with the wake vortex restrictions. We find that the delay due...
READ MORE
Potential benefits of reducing wake-related aircraft spacing at the Dallas/Fort Worth International Airport
July 12, 2002
Project Report
Published in:
MIT Lincoln Laboratory Report ATC-304
Summary
Measurements and modeling of wake vortices reveal that the Federal Aviation Administration's (FAA) minimum separation requirements for departing aircraft are often overly conservative. If the separation times following heavy aircraft can be safely reduced, considerable savings will be realized. The Dallas/Fort Worth International Airport (DFW) experiences departure delays daily. Banks of departing aircraft often create a significant queue at the end of the runway, with aircraft waiting between 10-20 minutes to depart. Additional delays occur during weather recovery operations after the terminal airspace has been impacted by thunderstorms. This report produces projected delay and cost benefits of implementing reduced wake spacing for departing aircraft at DFW. The benefits are calculated by simulating aircraft departures during both clear weather and weather recovery operations, using current and possible reduced spacings. The difference in delay values using different separation standards is used to calculate a cost savings to the airlines. The benefits for a single day are extended to a yearly approximation based on the estimated number of days that the separation criteria could be safely reduced. Departure information from February 19, 2001 is analyzed for clear weather operations. The simulation reveals a savings of $4.7 million/yr when the separation criteria is reduced from the current practice of 110 seconds to 90 seconds. A further reduction in the separation criteria to 60 seconds pushes the maximum savings to almost $10 million/yr. The daily savings for a weather recovery operation is $19,600 for weather impacts between 15-60 minutes and a reduction in spacing fiom the current 110 seconds to 90 seconds. The average increases to $36,200 when the spacing is reduced to 60 seconds. Significant thunderstorm events impacted the DFW terminal airspace 59 times during 2001 leading to projected yearly savings of greater than $2.1 million for a 60 second separation criteria following heavies.
Summary
Measurements and modeling of wake vortices reveal that the Federal Aviation Administration's (FAA) minimum separation requirements for departing aircraft are often overly conservative. If the separation times following heavy aircraft can be safely reduced, considerable savings will be realized. The Dallas/Fort Worth International Airport (DFW) experiences departure delays daily. Banks...
READ MORE
Aircraft encounters with thunderstorms in enroute vs. terminal airspace above Memphis, Tennesssee
May 13, 2002
Conference Paper
Published in:
Proc. 10th Conf. on Aviation, Range and Aerospace Meteorology, 13-16 May 2002, pp. 162-165.
Summary
To date, very little attention has been given to quantifying the effects of thunderstorms on air traffic in enroute airspace. What types of storms cause pilots to deviate from their nominal flight routes? What types of storms do pilots fly through? Around? Over? When thunderstorms are forecast to affect a particular region, how many planes will need to be rerouted? Which ones? Which aspects of the storm need to be accurately forecast in order to answer those questions? How does the forecast accuracy affect the quality of airspace capacity predictions? Quantitative answers to these questions would contribute to the design of useful decision support tools. Federal Aviation Administration decision support tools are being equipped with the ability for air traffic managers to define dynamic "flow constrained areas" (FCAs). Each FCA will be a polygon in latitude/longitude space with ceiling and floor altitudes and a motion vector. One primary use for FCAs will be to define regions that do, or probably will, contain convective thunderstorm activity. These tools will help air traffic managers decide which planes to re-route around the weather and which planes have a reasonable chance of flying through, between, or over the storms. Although it will be helpful to have the ability to manually define FCAs in the traffic managers' tools, the efficiency of the solutions that will be worked out with those tools would be greatly enhanced by answers to the questions posed above. In our prior work we have attempted to quantify the behavior of pilots who encounter thunderstorms in terminal airspace during the final 60 nautical miles of flight. In this study we compare the storm avoidance behavior of pilots in enroute airspace with that of pilots who encountered the very same storms at lower altitudes, in terminal airspace. The study is preliminary, but it complements the terminal work, affords some insight into pilot behavior, and raises questions that should be addressed in a larger study.
Summary
To date, very little attention has been given to quantifying the effects of thunderstorms on air traffic in enroute airspace. What types of storms cause pilots to deviate from their nominal flight routes? What types of storms do pilots fly through? Around? Over? When thunderstorms are forecast to affect a...
READ MORE
Forecasting convective weather using multi-scale detectors and weather Classification - enhancements to the MIT Lincoln Laboratory Terminal Weather Forecast
May 13, 2002
Conference Paper
Published in:
10th Conf. on Aviation, Range, and Aerospace Meteorology, 13-16 May 2002, pp. 132-135.
Summary
Over the past decade the United States has seen drastic increases in air traffic delays resulting in enormous economic loses. Analysis shows that more then 50% of air traffic delays are due to convective weather. In response the FAA has assembled scientific and engineering teams from MIT Lincoln Laboratory, NCAR. NSSL, FSL and several universities to develop convective weather forecast systems to aid air traffic managers in delay reduction. A user-needs study conducted by Lincoln Laboratory identified that a major source of air traffic delay was due to line thunderstorms (Forman et al., 1999). Recognizing that the line storm envelope motion was distinct from the local cell motion was the impetus for developing the Growth and Decay Storm Tracker' (Wolfson et al., 1999). The algorithm produces forecasts by extracting large-scale features from two dimensional precipitation images. These images are tracked, using either correlation techniques (Terminal Convective Weather Forecast or TCWF) or centroid techniques (National Convective Weather Forecast or NCWF). In TCWF, the track vector field is used to advect the current precipitation images formed to produce a series of forecasts into minute increments up to 60 minutes. The TCWF forecasts are highly skilled for large scale persistent line storms. However, detailed performance analysis of the algorithm has shown that in cases dominated by airmass storms, the algorithm occasionally performed poorly (Theriault et al., 2001). In this paper we describe the sources of error discovered in the TCWF algorithm during the Memphis 2000 performance evaluation, and describe recent enhancements designed to address these problems.
Summary
Over the past decade the United States has seen drastic increases in air traffic delays resulting in enormous economic loses. Analysis shows that more then 50% of air traffic delays are due to convective weather. In response the FAA has assembled scientific and engineering teams from MIT Lincoln Laboratory, NCAR...
READ MORE
Operational Experience with TDWR/LLWAS-NE Integration at the Dallas, TX International Airport (DFW)
May 13, 2002
Conference Paper
Published in:
10th Conf. on Aviation, Range and Aerospace Meteorology, 13-16 May 2002, pp. 391-394.
Summary
At nine major airports, both the Terminal Doppler Weather Radar (TDWR) and Network Extension of the Low-Level Wind shear Advisory System (LLWAS-NE) data will be used to detect and warn Air Traffic Control (ATC) of dangerous wind shear conditions. The integration of wind shear alerts from the two systems is currently being carried out by the TDWR software and will be accomplished by Integrated Terminal Weather System (ITWS) software when the ITWS is installed at these airports. Previous studies of the performance of the TDWR/LLWAS-NE integrated system were carried out at Denver, CO, Dallas, and Orlando, FL. Additionally, there have been recent concerns about false alarms with the LLWAS-NE. In this study, we examine the performance of the integrated system at Dallas-Ft. Worth International Airport (DFW) over a 6-month period in 2000 with particular emphasis on integrated wind shear alerts produced during a number of cases where the TDWR had difficulty making detections due to: 1. radially aligned gust fronts over DFW, 2. radially aligned divergent features, divergence behind gust fronts and divergence embedded within gravity waves, and/or 3. TDWR radome attenuation or excessively aggressive clutter residue editing. DFW is a particularly good airport for such a study because there is an additional TDWR [for Dallas Love airport (DAL)] located in close proximity to DFW and situated in such a way that it provides a very good viewing angle for wind shear events that may not be well characterized by the DFW TDWR radial velocity data. DFW is also an ITWS demonstration system test site with trained meteorologists who review the wind shear detection performance after all convective weather events at DFW.
Summary
At nine major airports, both the Terminal Doppler Weather Radar (TDWR) and Network Extension of the Low-Level Wind shear Advisory System (LLWAS-NE) data will be used to detect and warn Air Traffic Control (ATC) of dangerous wind shear conditions. The integration of wind shear alerts from the two systems is...
READ MORE
Using ORPG to enhance NEXRAD products to support FAA critical systems
May 13, 2002
Conference Paper
Published in:
10th Conf. on Aviation, Range, and Aerospace Meteorology, 13-16 May 2002, pp. 77-80.
Summary
The initial release of a new operational open architecture is currently being phased into the national WSR-88D (NEXRAD) radar network. This new Common Operations and Development Environment (CODE) includes the Open Radar Product Generator (ORPG) that replaces the existing NEXRAD Radar Product Generator. The new ORPG includes all the algorithms of the RPG it replaces. Future algorithms designed for use within NEXRAD also will be processed by the ORPG. CODE can also be used in a research capacity to significantly enhance the process of ORPG meteorological algorithm development. When used independently of a NEXRAD installation, CODE/ORPG provides multiple playback options for accessing real-time base data streams. This allows development and testing of new algorithms under the same environment an algorithm would encounter in an operational setting. This establishes a flow relationship from algorithm development through operational implementation within the common environment of CODE/ORPG. A six-month Build cycle for future CODE/ORPG releases has been established. An algorithm developed in a research CODE/ORPG capacity has an opportunity, at six-month intervals, to garner agency approval and undergo final preparation for operational release. The NEXRAD Radar Operations Center (ROC) needs about eight months preparation time from algorithm submission until release of the next CODE/ORPG version. For instance. Build 2 is to be released September 30. 2002. Algorithms for Build 2 inclusion had to be submitted by January 31, 2002. It will take about three months after the release for the entire NEXRAD network to be updated. The deadline for Build 3 submission is in July 2002 with a release date set in March 2003. Multiple Federal Aviation Administration (FAA) critical systems rely on products from NEXRAD algorithms. These projects include ITWS (Integrated Airport Weather System), WARP (Weather and Radar Processing), and ClWS (Corridor Integrated Weather System). Some of the NEXRAD products used include severe storm information, composite reflectivity factor depictions, and velocity data. In this paper, we discuss new algorithms and modifications to existing algorithms earmarked for the first few releases of the CODE/ORPG that produce products of importance to these FAA systems. They include modifications to the existing Anomalous Propagation Edited Composite Reflectivity algorithm released during Build 1 upgrades, a new high resolution, digital VIL (Vertically Integrated Liquid) algorithm slated for Build 2, and a Data Quality Assurance algorithm anticipated for Build 3.
Summary
The initial release of a new operational open architecture is currently being phased into the national WSR-88D (NEXRAD) radar network. This new Common Operations and Development Environment (CODE) includes the Open Radar Product Generator (ORPG) that replaces the existing NEXRAD Radar Product Generator. The new ORPG includes all the algorithms...
READ MORE
Contributions to the AIAA Guidance, Navigation & Control Conference
January 23, 2002
Project Report
Published in:
MIT Lincoln Laboratory Report NASA-A-5
Summary
This report contains six papers presented by the Lincoln Laboratory Air Traffic Control Systems Group at the American Institute of Aeronautics & Astronautics (AIAA) Guidance, Navigation and Control (GNC) conference on 6-9 August 2001 in Montreal, Canada. The work reported was sponsored by the NASA Advanced Air Transportation Technologies (AATT) program and the FAA Free Flight Phase 1 (FFPl) program. The papers are based on studies completed at Lincoln Laboratory in collaboration with staff at NASA Ames Research Center. These papers were presented in the Air Traffic Automation Session of the conference and fall into three major areas: Traffic Analysis & Benefits Studies, Weather/Automation Integration, and Surface Surveillance. In the first area, a paper by Andrews & Robinson presents an analysis of the efficiency of runway operations at Dallas/l%. Worth using a tool called PARO, and a paper by Welch, Andrews, & Robinson presents delay benefit results for the Final Approach Spacing Tool (FAST). In the second area, a paper by Campbell, et al. describes a new weather distribution system for the Center/TRACON Automation System (CTAS) that allows ingestion of multiple weather sources, and a paper by van de Venne, Lloyd, & Hogaboom describes the use of the NOAA Eta model as a backup wind data source for CTAS. Also in this area, a paper by Murphy & Campbell presents initial steps towards integrating weather-impacted routes into FAST. In the third area, a paper by Welch, Bussolari, and Atkins presents an initial operational concept for using surface surveillance to reduce taxi delays.
Summary
This report contains six papers presented by the Lincoln Laboratory Air Traffic Control Systems Group at the American Institute of Aeronautics & Astronautics (AIAA) Guidance, Navigation and Control (GNC) conference on 6-9 August 2001 in Montreal, Canada. The work reported was sponsored by the NASA Advanced Air Transportation Technologies (AATT)...
READ MORE
Surveillance performance requirements for runway incursion prevention systems
September 26, 2001
Project Report
Published in:
MIT Lincoln Laboratory Report ATC-301
Summary
In response to concerns over the number of runway incursions and runway conflicts at U.S. airports, the FAA is sponsoring research and development of safety systems for the airport surface. Two types of safety systems are being actively pursued, a tower cab alerting system and a runway status light system. The tower cab alerting system, called the Airport Movement Area Safety System (AMASS) is currently undergoing initial operational evaluation at several major airports. It provides aural and visual alerts to the tower cab to warn the controllers of potential traffic conflicts. The runway status light system is currently in the development phase, with initial operational suitability demonstrations planned at Dallas/Fort Worth International Airport during FY2003. Intended to offer protection in time-critical conflict scenarios where there is not enough time to warn the aircrews indirectly via the tower cab, the runway status light system provides visual indication of runway status directly to the cockpit; runway entrance lights warn pilots not to enter a runway on which there is approaching high-speed traffic; takeoff-hold lights warn pilots not to start takeoff if a conflict could occur. Both systems operate automatically, requiring no controller inputs. Activation commands for alerts and lights are generated by the systems' safety logic, which in turn receives airport traffic inputs from a surface surveillance and target tracking system. Accurate traffic representation is essential to meet system requirements, which include high conflict detection rate, prompt and accurate alerting and light activation, low nuisance and false alarm rates, and negligible interference with normal operations. This report analyzes the effect of the two fundamental surveillance performance parameters-position accuracy and surveillance update rate - on the performance of three different surface safety systems. The first two are the above-mentioned tower cab alerting and runway status light systems. The third system is a hypothetical cockpit alerting system that delivers alerts directly to the cockpit rather than to the tower cab. The surveillance accuracy and update rate requirements of these three systems are analyzed for three of the most common runway conflict scenarios, using realistic parameter values for aircraft motion. The scenarios are 1) a runway incursion by a taxiing aircraft in front of a departure or arrival, 2) a departure on an occupied runway, and 3) an arrival on an occupied runway. Runway status lights are especially effective at preventing incursions and accidents between takeoff or arrival aircraft and intersection taxi aircraft. Tower cab alerts are effective at alerting controllers to aircraft crossing or on a runway during an arrival. Runway status information provided directly to the cockpit will be required for the case where a previous arrival or a taxi aircraft fails to exit the runway as anticipated shortly before the arrival crossed the threshold. (not complete)
Summary
In response to concerns over the number of runway incursions and runway conflicts at U.S. airports, the FAA is sponsoring research and development of safety systems for the airport surface. Two types of safety systems are being actively pursued, a tower cab alerting system and a runway status light system...
READ MORE
Assessing delay benefits of the Final Approach Spacing Tool (FAST)
August 6, 2001
Conference Paper
Published in:
AIAA Guidance, Navigation and control Conf., Vol. 3, 6-9 August 2001, pp. 1851-1859.
Topic:
R&D area:
Summary
Air traffic delay grows each year. NASA is developing the Final Approach Spacing Tool (FAST) to help reduce airport arrival delays. FAST is intended to increase throughput and reduce delays. Analysis and field trials have suggested that FAST can help controllers increase arrival throughput on busy runways by several aircraft per hour. Published simulation studies have predicted that delay reductions from such throughput increases would save several hundred million dollars annually. However, these predictions disagree on delay savings for some airports and omit other airports of interest. Their predicted delay savings for some airports are higher than actual reported delays for those airports. They do not consider hazardous weather disruptions to arrival routes, and they do not address downstream delays caused by schedule disruption. This paper focuses on simple statistical and analytical measures of delay to resolve these problems. It develops a rule for ranking benefits and compares delay reduction predictions against actual reported delays. It relates delay to ceiling and visibility and thunderstorms. It examines the correlation of delay between airports and estimates the impact of downstream delay on FAST benefits.
Summary
Air traffic delay grows each year. NASA is developing the Final Approach Spacing Tool (FAST) to help reduce airport arrival delays. FAST is intended to increase throughput and reduce delays. Analysis and field trials have suggested that FAST can help controllers increase arrival throughput on busy runways by several aircraft...
READ MORE