Publications
A 9PAC system and application programmer's guide
February 16, 1999
Project Report
Published in:
MIT Lincoln Laboratory Report ATC-267
Topic:
R&D area:
Summary
The ASR-9 Processor Augmentation Card (9PAC) is a custom processing card that provides the ASR-9 system with increased beacon and radar processing performance. This paper describes the system and application software that executes on the prototype board, with an emphasis on the interaction between software modules. The application software on the 9PAC determines the position of radar and beacon target reports, replacing software that previously ran on the ASR-9 Array Signal Processor (ASP). The software is organized as a set of cooperating tasks executing under the control of a real-time operating system, PAC/OS, which provides all the services typical of an embedded kernel such as interrupt handling, pre-emptive multitasking, queues, signals, semaphores, mailboxes, and memory management. The deployment of 9PAC will occur in two phases. The Phase I application replaces only the beacon target detector (BTD) and radar/beacon target merge (MRG) functions of the ASP. The Phase I application consists of two executable programs since Phase I uses only two of the C44 processors on the 9PAC. One program, the housekeeping processor, is responsible for all I/O functions and performs the radar/beacon merge operation. The second progam, the beacon processor, is dedicated to processing the raw beacon replies and generating beacon targets which are then returned to the first processor for the merge operation. The Phase II application consists of three executable programs, one for each of the C44 processors on the 9PAC and performs much of the Phase I functionality and adds primary radar processing. The intent of this paper is to provide the 9PAC software support personnel with sufficient information to implement future enhancements without unintentionally compromising some aspect of the overall system.
Summary
The ASR-9 Processor Augmentation Card (9PAC) is a custom processing card that provides the ASR-9 system with increased beacon and radar processing performance. This paper describes the system and application software that executes on the prototype board, with an emphasis on the interaction between software modules. The application software on...
READ MORE
Evaluating intrusion detection systems without attacking your friends: The 1998 DARPA intrusion detection evaluation
February 9, 1999
Conference Paper
Published in:
Third Conf. and Workshop on Intrusion Detection and Response, 9-13 February 1999.
R&D area:
Summary
Intrusion detection systems monitor the use of computers and the network over which they communicate, searching for unauthorized use, anomalous behavior, and attempts to deny users, machines or portions of the network access to services. Potential users of such systems need information that is rarely found in marketing literature, including how well a given system finds intruders and how much work is required to use and maintain that system in a fully functioning network with significant daily traffic. Researchers and developers can specify which prototypical attacks can be found by their systems, but without access to the normal traffic generated by day-to-day work, they can not describe how well their systems detect real attacks while passing background traffic and avoiding false alarms. This information is critical: every declared intrusion requires time to review, regardless of whether it is a correct detection for which a real intrusion occurred, or whether it is merely a false alarm. To meet the needs of researchers, developers and ultimately system administrators we have developed the first objective, repeatable, and realistic measurement of intrusion detection system performance. Network traffic on an Air Force base was measured, characterized and subsequently simulated on an isolated network on which a few computers were used to simulate thousands of different Unix systems and hundreds of different users during periods of normal network traffic. Simulated attackers mapped the network, issued denial of service attacks, illegally gained access to systems, and obtained super-user privileges. Attack types ranged from old, well-known attacks, to new, stealthy attacks. Seven weeks of training data and two weeks of testing data were generated, filling more than 30 CD-ROMs. Methods and results from the 1998 DARPA intrusion detection evaluation will be highlighted, and preliminary plans for the 1999 evaluation will be presented.
Summary
Intrusion detection systems monitor the use of computers and the network over which they communicate, searching for unauthorized use, anomalous behavior, and attempts to deny users, machines or portions of the network access to services. Potential users of such systems need information that is rarely found in marketing literature, including...
READ MORE
A case study of mid-level turbulence outside regions of active convection
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range, and Aerospace Meteorology (ARAM), 10-15 January 1999.
Topic:
R&D area:
R&D group:
Summary
Historically, the principal focus of research on clear-air turbulence of concern to aircraft has been on jet stream and mountain (orographic) induced turbulence. Relatively little research has focused on the turbulence hazard outside of, but in the vicinity of, convective storms, known as Convective Induced Turbulence (CIN). In this paper, we present our analysis requested by the National Transportation Safety Board (NTSB) of the meteorological conditions leading to severe turbulence and near loss of flight control of a commercial passenger jet and find that they fall into the CIN category. On 12 May 1997, at approximately 1929 UT, an American Airlines Airbus A300 en route from Boston, MA to Miami, FL encountered severe turbulence off the coast of West Palm Beach, FL. Near the time of the incident the crew had been directed to hold at 16,000 ft because of weather and traffic near Miami International. While approaching the holding position, the aircraft experienced severe turbulence and dropped over 3000 vertical feet in 30 seconds. A detailed postevent analysis by the NTSB failed to find any causal evidence for the turbulence and no single sensor, data set, or pilot report examined by the NTSB provided justification for the magnitude of the event. Our independent analysis of the incident was conducted primarily using recorded Miami WSR-88D base data. The analysis revealed a small-scale vertical shear zone may have emanated from a thunderstorm upstream of the Airbus. Animated cross-sectional images also suggested that a rotor may have propagated with the mean wind and intersected the flight path at the time the severe turbulence was reported. This paper will focus on meteorological conditions that led to the upset and provide evidence for several possible causes of the turbulence.
Summary
Historically, the principal focus of research on clear-air turbulence of concern to aircraft has been on jet stream and mountain (orographic) induced turbulence. Relatively little research has focused on the turbulence hazard outside of, but in the vicinity of, convective storms, known as Convective Induced Turbulence (CIN). In this paper...
READ MORE
The thunderstorm penetration/deviation decision in the terminal area
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range and Aerospace Meteorology, ARAM, 10-15 January 1999.
Topic:
R&D area:
R&D group:
Summary
During thunderstorm periods, terminal air traffic planners make a number of key decisions. They decide when to close and re-open arrival fixes, departure fixes, and runways; they anticipate and execute changes in runway configuration; they negotiate routing and flow rate decisions with Air Route Traffic Control Center (ART CC) traffic managers; and they set the airport acceptance rate. In making each of these decisions, the traffic planner looks at a weather radar display and makes an educated guess at answering the two following questions: - What will the weather be like in the airspace and time period in question? - Will the pilots be able and willing to fly through that airspace during that time? The same two questions will be important for advanced terminal automation systems. One key element of air traffic automation systems such as the Center-TRACON Automation System (CTAS) is the calculation of candidate trajectories for each aircraft for the time period of automation control. To make this calculation, the automation software must know which routes will be usable during the control period. The first of the two fundamental questions is being addressed by the convective weather Product Development Team (PDT) of the FAA's Aviation Weather Research program. (Wolfson, 1997; Wolfson, 1999; Hallowell, 1999; Forman, 1999; Evans, 1997) The second fundamental question is the subject of the work reported here. The state of the art answer to the second question is a widely quoted air traffic control rule-of-thumb which says that pilots generally do not penetrate precipitation that is NWS VIP level 3 (i.e. 41 dBZ) or higher. That is not to say that air traffic controllers always vector aircraft around level 3+ cells but rather that they begin to anticipate pilot requests for deviations when the weather approaches level 3. A suite of new weather sensors have become available that provide much more comprehensive information on convective weather features than was available in the past. Additionally, flight-related data such as preceding pilot behavior and whether a flight is running late are easier to obtain than in the past. In this study we develop an objective quantitative assessment of which weather and flight-related variables best explain pilot deviation decision-making.
Summary
During thunderstorm periods, terminal air traffic planners make a number of key decisions. They decide when to close and re-open arrival fixes, departure fixes, and runways; they anticipate and execute changes in runway configuration; they negotiate routing and flow rate decisions with Air Route Traffic Control Center (ART CC) traffic...
READ MORE
Addressing the weather delay problems of the New York City airports with the Integrated Terminal Weather System
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range, and Aerospace Meteorology, 10-15 1999.
Topic:
R&D area:
R&D group:
Summary
The three major New York City (NYC) air carrier airports (Kennedy, LaGuardia, Newark) currently experience high delays due to adverse terminal weather, both in an absolute sense and relative to other major airport complexes. Significantly expanding the NYC airports (e.g., by adding new runways) to reduce delays is not feasible. One alternative is to provide aviation weather decision support systems to air traffic, airline, and airport operations personnel to help them operate more safely and effectively with the existing runway/taxiway complexes. Under an innovative partnership between the Port Authority of New York and New Jersey and the Federal Aviation Administration (FAA), Massachusetts Institute of Technology, Lincoln Laboratory has installed and is currently operating a functional prototype Integrated Terminal Weather System (ITWS) to conduct research on improving the safety and efficiency of operations at the NYC airports during adverse weather. The New York terminal area provides a stringent test of the ITWS ability to safely reduce delays due to both the meteorology and the operational usage challenges not found at the earlier ITWS test locations of Orlando, Memphis, and Dallas. In this paper, we describe key features of the New York terminal environment and the ITWS prototype, the initial experience in addressing the meteorological and operational usage challenges of the New York terminal area, and describe plans for the coming years.
Summary
The three major New York City (NYC) air carrier airports (Kennedy, LaGuardia, Newark) currently experience high delays due to adverse terminal weather, both in an absolute sense and relative to other major airport complexes. Significantly expanding the NYC airports (e.g., by adding new runways) to reduce delays is not feasible...
READ MORE
Aviation user needs for convective weather forecasts
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range, and Aerospace Meteorology (ARAM), 10-15 January 1999.
Topic:
R&D area:
R&D group:
Summary
The prediction of convective weather is very important to aviation, since almost half of the serious delay at major airports in the warm season is caused by thunderstorms. The need for accurate 0-6 hr forecasts for NAS users has been the subject of extensive publications, forums, and advisory committees in the aviation weather community over the last several years (Wolfson, et al; 1997). The Convective Weather Product Development Team (PDT), a core team of scientists and engineers from NCAR, NSSL, and MIT LL, was formed in 1996 as part of the reorganization of the FAA Aviation Weather Research Program. The team is developing convective weather forecast algorithms that produce operationally useful products for both the terminal area and enroute airspace. The products are designed to meet specific users' air traffic planning and safety needs. Before major algorithm development began, PDT members visited terminal and enroute Air Traffic (AT) personnel and airline dispatchers to understand the forecast products that were currently available to them and their needs for a near future product. Also, in order to reach the pilot community, a pilot survey about existing convective weather information and how to improve it, was created and distributed at the OshKosh Fly-In in August of 1997. This needs assessment took advantage of interviewees that had extensively used state-of-the-art weather information products (ITWS) in an operational setting for years. Their requirements, based on personal experiences with operational products during convective weather events, were less stringent than those reported in the recent requirements document pertaining to ARTCC TMUs (Browne, et al; 1999). The results of these investigations were used in the creation of the DFW Terminal Convective Weather Forecast (TCWF) product and the National Convective Weather Forecast (NCWF) products that were demonstrated throughout the summer of 1998 (Hallowell, et al; 1999; Mueller, et al; 1999). These demonstrations also provided additional insight into user needs. In this paper we describe Air Traffic users and their specific responsibilities. We then summarize AT and airline needs based on interviews conducted in 1997 and 1998. Information on pilots' needs for convective weather information is presented at the end.
Summary
The prediction of convective weather is very important to aviation, since almost half of the serious delay at major airports in the warm season is caused by thunderstorms. The need for accurate 0-6 hr forecasts for NAS users has been the subject of extensive publications, forums, and advisory committees in...
READ MORE
Nowcasting requirements for the aircraft vortex spacing system (AVOSS)
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range, and Aerospace Meteorology, 10-15 Jan. 1999, pp. 340-344.
Topic:
R&D area:
R&D group:
Summary
Aircraft wake vortices are counter-rotating tubes of air that are generated from aircraft as a consequence of the lift on the aircraft. The safety concern of wake vortices, particularly when lighter aircraft are following heavy planes, has caused the Federal Aviation Administration (FAA) to enact minimum separation requirements during the arrival phase of flight. These separation standards are imposed at the arrival threshold during Instrument Flight Rules (IFR) and are a significant constraint on arrival capacity at the largest U.S. airports. Any movement toward increasing air traffic efficiency, such as concepts toward free-flight, must address increasing runway capacity if they are to be fully effective. Decades of past wake vortex measurements clearly show that current wake vortex separations are overconservative in many weather conditions, and that adapting the separations to the current weather state could safely reduce these separations...This paper describes the known meteorological influences on vortex behavior and gives an overview of AVOSS. Airport climatology is studied to discuss the prevalence of conditions that are conducive to capacity increases with AVOSS technology. Finally, additional constraints on AVOSS nowcasts are discussed.
Summary
Aircraft wake vortices are counter-rotating tubes of air that are generated from aircraft as a consequence of the lift on the aircraft. The safety concern of wake vortices, particularly when lighter aircraft are following heavy planes, has caused the Federal Aviation Administration (FAA) to enact minimum separation requirements during the...
READ MORE
Optimizing the ITWS algorithm designed to remove anomalous propagation ground clutter from the ASR-9 precipitation product
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range and Aerospace Meteorology, ARAM, 10-15 January 1999.
Topic:
R&D area:
R&D group:
Summary
A key product within the Integrated Terminal Weather System (ITWS) Initial Operating Capability (IOC) product suite removes anomalous propagation (AP) ground clutter from the ASR-9 precipitation product. This has been identified as a critical component of ITWS due to the frequent occurrence of AP when storms or outflows move over an ASR-9. Editing is accomplished by comparing the raw ASR-9 weather data to composite maps generated by the Next Generation Weather Radar (NEXRAD) and the Terminal Doppler Weather Radar (TDWR). An editing template, containing regions of AP, is created based on the ASR-9 data collected at the middle of the composite volume scan to minimize the difference in update rates. The template is used to edit the ASR-9 scan immediately after the composite map and all subsequent scans until a new composite map is received. This algorithm has been shown to perform quite well, especially if the weather and AP returns are not co-located. During the 1994 Demonstration and Validation Operational Test and Evaluation in Memphis (MEM) and Orlando (MCO), the probability of editing AP (PEAP) in the absence of weather was 0.97 for level 2 and greater returns (Klingle-Wilson, 1995). The probability of editing weather (PEW) for those cases with weather only was quite low, i.e., 0.01. In order to minimize the removal of weather returns in those cases where the AP and weather are located in close proximity, the editing thresholds are quite conservative. This is reflected by the 1994 results which show a PEAP of 0.81 and a PEW of 0.02 for this class of event. Besides the conservative thresholds, another area of concern is the fact that the AP regions can expand or increase in intensity after the AP editing template is created. This rapid variation frequently occurs with convectively generated AP and can cause the performance of the algorithm to decrease with time until a new template is created. In this study, we will examine the algorithm failure mechanisms in detail to identify possible site-adaptable parameter changes that can be used to improve the performance for the mixed weather/AP events. This is especially germane since the parameter set was not re-evaluated after the TDWR composite map was incorporated in 1995. In the critical region over the airport during hazardous weather conditions, this radar updates more frequently than the NEXRAD. Since the parameters were designed to account for the NEXRAD volume update rate, they are probably too conservative for the current algorithm (which uses both composite maps).
Summary
A key product within the Integrated Terminal Weather System (ITWS) Initial Operating Capability (IOC) product suite removes anomalous propagation (AP) ground clutter from the ASR-9 precipitation product. This has been identified as a critical component of ITWS due to the frequent occurrence of AP when storms or outflows move over...
READ MORE
The growth and decay storm tracker
January 10, 1999
Conference Paper
Published in:
Proc. Eighth Conf. on Aviation, Range, and Aerospace Meteorology, 10-15 Jan. 1999, pp. 58-62.
Topic:
R&D area:
R&D group:
Summary
An elliptical filter/tracker capable of accounting for systematic growth and delay, designated the Growth and Decay Storm Tracker, has been developed and tested. Its performance depends on the size and shape of the filter, the performance of the cross-correlation tracker, the time interval between successive scans, the forecast lead time, and the type of storm being tracked.
Summary
An elliptical filter/tracker capable of accounting for systematic growth and delay, designated the Growth and Decay Storm Tracker, has been developed and tested. Its performance depends on the size and shape of the filter, the performance of the cross-correlation tracker, the time interval between successive scans, the forecast lead time...
READ MORE
Study of Network Expansion LLWAS (LLWAS-NE) fault identification and system warning optimization through joint use of LLWAS-NE and TDWR data
January 10, 1999
Conference Paper
Published in:
8th Conf. on Aviation, Range, and Aerospace Meteorology (ARAM), 10-15 January 1999.
Topic:
R&D area:
R&D group:
Summary
Low level wind shear has been identified as an aviation hazard which has caused or contributed to a significant number of aircraft accidents (Soffer, 1990). To protect aircraft from hazardous wind shear, the Federal Aviation Administration (FAA) developed a system called the Low Level Wind Shear Alert System (LLWAS), containing a collection of anemometers as well as data processing logic (Wilson and Gramzow, 1991). The LLWAS has undergone several advancements in both design and algorithmic computation. The latest deployment, known as the Network Expansion Low Level Wind Shear Alert System (LLWAS-NE), consists of additional sensors to the original LLWAS network, providing better coverage of the airfield. In addition, the LLWAS-NE is capable of providing runway-oriented wind shear and microburst alerts with loss and gain values. The alerts from LLWAS-NE will be integrated with those from the Terminal Doppler Weather Radar (TDWR) and the Integrated Terminal Weather System (ITWS) at locations where all systems are available (Cole, 1992; Cole and Todd, 1994). An analysis was undertaken at Orlando (MCO) and Dallas/Ft. Worth (DFW) International Airports to assess the accuracy of wind shear alerts produced by LLWAS-NE and the TDWR/LLWASNE integration algorithm. Identifying improvements that can be made to either system is important, as LLWAS-NE alert information is anticipated to be integrated with ITWS in an ITWS/LLWAS-NE integration algorithm. As currently specified, the ITWS/LLWAS-NE integration algorithm will work the same as the TDWR/LLWAS-NE version. The ITWS/LLWAS-NE algorithm is an area where additional work is necessary to ascertain if the integration parameters should be modified to account for performance differences between the ITWS and TDWR algorithms. We suggest that ongoing assessment of the LLWAS-NE should use both LLWAS-NE data and TDWR base data, when possible. Comparing both data sets also will facilitate optimization of LLWAS-NE parameters used in the computation of the alerts.
Summary
Low level wind shear has been identified as an aviation hazard which has caused or contributed to a significant number of aircraft accidents (Soffer, 1990). To protect aircraft from hazardous wind shear, the Federal Aviation Administration (FAA) developed a system called the Low Level Wind Shear Alert System (LLWAS), containing...
READ MORE