Publications

Aviation weather refers to any type of weather that can affect the operation of an aircraft – anything from a brief delay in departure to a catastrophic accident during flight. Wind shear and events associated with convective weather were recognized as an aviation hazard long before Dr. Theodore Fujita began publishing his now-famous treatises. On July 28, 1943, American Airlines Flight 63 from Cleveland, Ohio, USA to Nashville, Tennessee crashed after the pilot lost control of the Douglas DC3. The pilots and numerous passengers were fatally injured. The aircraft was destroyed by impact and post crash fire. The weather report at the time included warnings for storms, heavy rain, lightning and severe turbulence. The Civil Aeronautics Board found that the probable cause was a loss of control of the aircraft due to unusually severe turbulence and violent downdraft caused by a thunderstorm. In the ten-year period from 1987 through 1996, 24% of all U.S. accidents were judged to be "weather related". For the twenty-year period 1976 to 1996 fully 43% of U.S. accidents were judged to have involved wind or wind shear, and 2.3 % thunderstorm, although the two data elements are not mutually exclusive. In the U.S., approximately 82% of accidents are general aviation; the rest are air carriers and commuters of various types. When general aviation accidents are negated, and only air carriers are considered, wind and wind shear issues account for 9.5% of accidents. The Weather Systems Processor (WSP) has been developed to reduce the impact of severe weather conditions on air traffic by providing information concerning weather conditions in the airport terminal environment. WSP provides warnings to air traffic controllers and supervisors of hazardous wind shear and microburst events in the terminal area, forecasts the arrival of gust fronts, and tracks thunderstorms, providing a complete picture of current and future terminal area hazardous weather conditions that may impact runway and airport usage. Common weather situation awareness allows Terminal Approach, Tower Controllers and other traffic management personnel to jointly plan with confidence and safely manage more arrivals and departures with less delay. Knowledge of the location, severity and movement of hazardous weather allows dynamic adjustments to be made in routing aircraft to runways, approach and departure corridors, terminal arrival and departure transition areas (i.e. gate-posts) and other air routes.

Operational experience with the Integrated Terminal Weather Systems (ITWS) and Airport Surveillance Radar, Model 9, (ASR-9) Weather System Processor (WSP) demonstration systems, studies of pilot weather avoidance decision making), and recent accidents have demonstrated the need to provide timely, accurate information on the location and movement of storms to air traffic controllers, pilots, and airline dispatch. At medium-intensity airports, generally those with too few flight operations to justify the presence of Doppler radar systems like the Terminal Doppler Weather Radar (TDWR) or the WSP, terminal air traffic surveillance is currently provided with the ASR-7 and ASR-8 radar systems. The ASR-7 and ASR-8 do not provide calibrated precipitation intensity products or any storm motion information. The Medium-Intensity Airport Weather System (MIAWS) program is intended to address these terminal weather information deficiencies. MIAWS-generated products would be displayed to tower and Terminal Radar Approach Control (TRACON) supervisors and delivered to aircraft cockpits and airline dispatchers to assist pilots during landings. Initially, the MIAWS will provide a real time display of storm positions and motion based on Next Generation Weather Radar (NEXRAD) product data using a product generation and display system derived from the WSP. Airport wind and wind shear information will be acquired from an FAA Low Level Wind Shear Alert System (LLWAS). A demonstration system will be installed and demonstrated at experimental sites in Memphis, TN and Jackson, MS in 2000 and potentially at a third site in 2001. This demonstration system will be used to assess technical and operational issues such as compensation for the relatively slow updates of the NEXRAD products and, Anomalous Propagation (AP) ground clutter. The ASR-11 is a replacement for the ASR-7/8 radars that feature a weather reflectivity processing channel. When it becomes available at MIAWS locations, the MIAWS processor will acquire and display precipitation and storm movement products derived from the ASR-11. Likewise, when an LLWAS Relocation/Sustainment (LLWAS-RS) (Nilsen, et al., 1999) becomes available at MIAWS locations, the MIAWS will acquire wind and wind shear information derived from the LLWAS-RS.

On December 6th, 1998, a fatal accident involving a twin engine Beech Baron occurred near the Max-Westheimer Airport at Norman Oklahoma (OUN). Although the National Transportation Safety Board (NTSB) conducted an extensive investigation into this accident, the probable cause for the accident has yet to be determined. Since the accident occurred outside of weather echoes that might be considered hazardous, it seems difficult to deduce a meteorological explanation for this accident. However, Doppler radar data suggested the presence of wave formations near the site of the accident. This report reflects examination of the data provided by the NTSB.

Air traffic delay due to convective weather reached historically high levels in 1999, as passengers blamed airlines and airlines blamed the FAA for the massive inconveniences. While coordination between the FAA's System Command Center and the regional centers and terminals can be expected to improve with the FAA's new initiatives, it is clear that air traffic management and planning during convective weather will ultimately require accurate convective weather forecasts. In addition to improving system capacity and reducing delay, convective forecasts can help provide safer flight routes as well. The crash of a commercial airliner at Little Rock, AR in June 1999 after a one-hour flight from Dallas/Ft. Worth illustrates the dangers and potential tactical advantage that could be gained with frequently updated one-hour forecasts of convective storms. The Terminal Convective Weather Forecast (TCWF) product has been developed by MIT Lincoln Laboratory as part of the FAA Aviation Weather' Research Convective Weather Product Development Team (PDT). Lincoln began by consulting with air traffic personnel and commercial airline dispatchers to determine the needs of aviation users (Forman, et. al., 1999). Users indicated that convective weather, particularly line storms, caused the most consistent problems for managing air traffic. The "Growth and Decay Storm Tracker" developed by Wolfson et al. (1999) allows the generation of up to 1-hour forecasts of large scale, organized precipitation features with operationally useful accuracy. This patented technology. represents a breakthrough in short-term forecasting capability, providing quantitative envelope tracking as opposed to the usual cell tracking. This tracking technology is now being utilized in NCAR's AutoNowcaster (Mueller, et al., 2000), the National Convective Weather Forecast running at the Aviation Weather Center (Megenhardt, et al., 2000) and by private sector meteorological data vendors. The TCWF has been tested in Dallas/Ft. Worth (DFW) since 1998, in Orlando (MCO) since 1999, and in New York (NYC) since fiscal year 2000 began. These have been informal demonstrations, with the FAA William J. Hughes Technical Center (WJHTC) assessing utility to the users, and with MIT LL modifying the system based on user feedback and performance analyses. TCWF has undergone major revisions, and the latest build has now been deployed at all sites. The TCWF is now in a formal assessment phase at the Memphis international Airport as a prerequisite to an FAA operational requirement. The FAA Technical Center will make a recommendation on whether TCWF is suitable for inclusion in the FAA's operational integrated Terminal Weather System (ITWS), which has an unmet requirement for 30+ minute forecasts of convective weather. Memphis was selected for the TCWF Assessment since it has not been exposed to the forecast product during prior demonstrations. Operations began on March 24, 2000 and operational feedback is being assessed by the FAA Technical Center (McGettigan, et al., 2000) and MCR Corporation is performing a quantitative benefits assessment (Sunderlin and Paull, 2000). This paper details the refined TCWF algorithm and display concept, gives examples of the operational impact of terminal forecasts, and analyzes the technical performance of the TCWF during the early stages of the Memphis Assessment.

Adverse terminal weather is a key factor in the safety and efficiency of airline operations. Weather has been directly related to many of the air carrier accidents with fatalities in the 1990's, and the cost to airlines per year for weather delays is estimated to exceed one billion dollars, with at least half of this arising from convective weather. This paper discusses the airline operations center (AOC) use of information from the Federal Aviation Administration (FAA) terminal weather systems to improve safety and operational efficiency (e.g., reduce delays and diversions, improve predictability, and airline schedule integrity) during severe or rapidly changing conditions. Historically (e.g., prior to 1992), the FAA terminal weather information capability was fairly rudimentary, and airlines had no access to the information. However, with deployment of the ITWS, the ASR-9 Weather Systems Processor (WSP) production systems, and CDMnet (and perhaps Internet) product servers for ITWS and WSP airlines will have access to the products. Thus, it is important now to consider how these products could be used operationally and what refinements should be made to the ITWS/WSP products to better meet the needs of airline users.

Automated air traffic decision support tools must compute the time it takes an aircraft to fly along a path. The estimation of Time-To-Fly (TTF) requires accurate knowledge of the wind. Two proposed sources of wind data for the Center-TRACON Automation System (CTAS) developed by NASA are the Rapid Update Cycle (RUC) and the Integrated Terminal Weather System (ITWS). The RUC is a mesoscale numerical weather prediction model run by the National Centers for Environmental Prediction. The ITWS was developed by MIT Lincoln Laboratory for the FAA. The ITWS winds product, Terminal Winds takes in RUC forecasts and refines them using recent local measurements of the wind from Doppler radars, aircraft, and ground stations. This report examines the question: does the use of RUC and ITWS wind fields lead to different Time-To-Fly estimates?

On June 1, 1999, American Airlines flight 1420 , arriving at Little Rock, AR from Dallas-Fort Worth, TX, was involved in a fatal accident upon landing, on runway 4R at Adams Field (LIT). There were eleven casualties, including the pilot, and numerous injuries among the 145 passengers and crew on board. At the time of the accident, 0451 UTC (11:51 PM CDT), severe thunderstorms existed in the vicinity of the airport. These storms were initiated by an approaching cold front and pre-frontal trough and were developmentally aided by veering low-level wind and warm air advection, which helped to further destabilize the atmosphere. This report will focus on the meteorological conditions preceding and immediately following the accident that could have played a contributing role in the crash. However, no theories on the actual cause will be put forth.

Major terminals and the surrounding en route airspace are critical elements of the US National Air System (NAS). A large fraction of the US population lives near these terminals, and the bulk of the hub connecting operations are at these airports as well. Adverse weather in these terminal areas and surrounding en route airspace is a major safety concern for the NAS as well as causing a large fraction of all US aviation delays. The principal weather decision support tool for these terminals is the Integrated Terminal Weather System (ITWS) which commenced full-scale development by the FAA in 1995, with first articles to be deployed shortly. In this paper, we discuss how the initial ITWS operational capability needs to be extended to address performance problems identified in operational use and to meet the many new user needs that have developed in the past five years. The paper proceeds as follows. In Section 2, we provide some necessary background on the ITWS operational capability, followed by a discussion of new capabilities to meet urgent user needs. Section 3 discusses refinements to the initial capability to address problems/issues that have been identified based on five years of operational use of ITWS products from ITWS demonstration systems at eight major airports. Next, we consider extending planned ITWS coverage to other major terminals. The final section summarizes the paper's results and suggests additional studies.

San Francisco International Airport (SFO) is unable to use independent parallel approaches to its closely-spaced parallel runways when marine stratus is present in the approach. Delay programs are imposed to regulate the flow of traffic to match the true arrival capacity of the airport. Failure to forecast accurately the times of onset and dissipation of stratus in the approach results in unnecessary delays, costly airborne holding and diversions, or in wasted capacity as the traffic management planners fail to match the arrival rate to the actual airport capacity. Previous studies have shown that accurate 1-2 hour forecasts of the times of clearing in the approach could provide substantial reductions in the delays and inefficiencies associated with the marine stratus impacts on air traffic at SFO. The San Francisco Marine Stratus Initiative has provided a four-year focus on this problem and has resulted in the development of several forecast algorithms that will aid, the operational forecasting of the dissipation of marine stratus in the approach to SFO (Clark and Wilson, 1997). These algorithms involve new techniques for the analysis of observational data and statistical and dynamical prognosis of the behavior of the marine stratus. This discussion of the design and the performance of these algorithms provides an overview of the status of this project.

The Integrated Terminal Weather System (ITWS) provides runway-orientated wind shear and microburst alerts to enhance the safety of flight operations at major U.S. airports. The alerts are reported as either losses or gains of airspeed, representing performance decreasing or performance increasing wind shears. The performance of ITWS as a stand-alone system has been thoroughly documented in previous research. During the 1994 ITWS Demonstration and Validation testing, the probability of detection (POD) and probability of false alarm (PFA) at Memphis (MEM) and Orlando (MCO) for all loss events were > 90 and < 5 percent, respectively, based on single-Doppler truth. The Low-Level Windshear Alert System-Network Expansion (LLWAS-NE) also generates runway alerts in the same format as ITWS. LLWAS-NE is not subject to viewing angle problems such as those experienced by single-Doppler radar. However, false alarms caused by LLWAS-NE sensor failures at some Terminal Doppler Weather Radar (TDWR) sites have reduced user confidence in the system. At those ITWS sites with an LLWAS-NE, the ITWS alerts derived from TDWR data will be integrated with LLWAS-NE alerts, hopefully to improve the performance. The ITWS integration algorithm is identical to the TDWR version, with the exception of a few adaptable parameter changes. The ITWS/LLWAS-NE parameters were modified slightly to account for ITWS and TDWR algorithm performance differences. In this paper, the performance of a stand-alone ITWS and the ITWS/LLWAS-NE integration algorithm at the MCO and Dallas-Ft. Worth (DFW) demonstration sites will be discussed. This assessment is considered unique since the radar and anemometer data were combined to create the runway truth. The focus of this research is to identify the shortcomings of both systems in order to recommend modifications that will improve the integration algorithm performance.