- Eastern Airlines B727 Flight 66 near JFK Int'l Airport
- Accident Overview
- Accident Board Findings
- Accident Board Recommendations
- Relevant Regulations
- Prevailing Cultural / Organizational Factors
- Key Safety Issue(s)
- Safety Assumptions
- Resulting Safety Initiatives
- Airworthiness Directives (ADs) Issued
- Common Themes
- Related Accidents / Incidents
- Lessons Learned
- Eastern Airlines B727 Flight 66 near JFK Int'l Airport
Photo of 727-225 in Eastern livery similar to accident airplane
Photo copyright Kenny Ganz - used with permission
History of Flight
Eastern Airlines Flight 66 was a regularly scheduled passenger flight between New Orleans, Louisiana and New York's John F. Kennedy International Airport (JFK), Jamaica, New York. The flight, a Boeing 727 with 116 passengers and a crew of 8 aboard fdeparted New Orleans at 1319 Eastern Daylight Time (EDT) with a planned arrival around 1600. The National Weather Service (NWS) forecast for JFK called for thunderstorms and rain showers after 1800. The forecast was amended at 1430 to include thunderstorms and moderate rain showers after 1515. At 1545, the forecast was further amended to call for thunderstorms, heavy rain showers with visibilities as low as ½ mile, and winds from 270 degrees at 30 knots with gusts to 50 knots after 1615. However, there is no evidence that the flightcrew of Eastern 66 received any of these forecasts.
The Eastern Air Lines weather forecast, which was issued at 1208, and was valid from 1215 to 2000, predicted widely scattered thunderstorms with tops from 30,000 to 40,000 feet in New York and eastern New Jersey. The terminal forecast for New York City predicted scattered clouds until 2000; thereafter, thunderstorms were possible with light rain showers. The flightcrew of Eastern 66 received this forecast before departing New Orleans. LaGuardia airport, near to JFK was filed as the flight's alternate destination.
A significant feature of the weather at JFK on the day of the accident was the presence of a stationary sea-breeze front which held for over an hour near the approach end of runway 22L. This front did not effect the growth of the thunderstorms that were in the area, which were already violent, but was significant in that the airport wind sensor used by air traffic control was located near the opposite end of the runway (almost 15,000 feet away from the thunderstorm) and was influenced by the onshore sea-breeze. It therefore gave information that called for landings to the southwest on runway 22L. However, just to the north, at the approach end of runway 22L, high winds were beginning to occur as a result of the rapidly deteriorating weather. Due to the localized nature of the downbursts that were occurring, the airport wind sensor did not detect the high winds associated with the weather that caused the accident.
Photo of 727-225 in Eastern livery similar to accident airplane
Photo copyright Bob Garrard - used with permission
Photo of JFK looking east, showing runway 22L near top of photo – approach would be from left to right
Photo copyright Kavin Kowsari - Air Team Images - used with permission
The flight was uneventful until arriving in the New York City terminal area. Beginning at 1535 EDT, Kennedy approach control (Southgate arrival controller) provided radar vectors to sequence the flight with other traffic, and to position the aircraft for an ILS approach to runway 22L. The flight had received the Automated Terminal Information Service (ATIS) which stated: "Kennedy weather, VFR, sky partially obscured, estimated ceiling 4,000 broken. 5 miles with haze… …wind 210 degrees at 10, altimeter 30.15. Expect vectors to an ILS runway 22L, landing runway 22L, departures are off 22R..." Traffic concentration into JFK was high, with aircraft landing on runway 22L every 1-2 minutes.
As Eastern 66 approached the Long Island area from the south, a violent thunderstorm was starting to affect landing traffic at JFK. For 4 minutes, between 1544 and 1548, a strong downdraft, which is now understood to be the first downburst cell at the approach end of the arrival runway, caused three aircraft to experience slight difficulties in landing related to wind shear, heavy rain and deviations below the glideslope. Departures were unaffected and no mention of the severe weather was broadcast to arriving traffic. Subsequent landings were accomplished with no difficulty.
At 1552, the Southgate arrival controller broadcast that the field was VFR with a 5-mile visibility, light, very light rain shower and haze. Within a minute this broadcast was updated with the information that the field had just gone IFR with 2 miles visibility, very light rain showers and haze. Control transmitted; "…the runway visual range is---not available, and Eastern 66 descend and maintain four thousand, Kennedy radar one three two four." Eastern 66 acknowledged the transmission.
Eastern 66 was one of a number of aircraft that were being vectored to intercept the ILS localizer course for runway 22L. At 1553, the flight contacted the Kennedy final vector controller who continued to provide radar vectors around thunderstorms in the area, sequencing the flight with other traffic, and positioning the flight on the localizer course.
Between 1552 and 1600 a second, more severe, downburst affected arriving traffic. A 747, which landed at 1552, experienced some wind shear, but, according to the accident report, did not warrant reporting. This aircraft was followed by a 707, which landed at 1554, and experienced a drift to the left at 200 feet which required ~8 degrees of heading change to correct. After this, two aircraft experienced major difficulties.
Photo of Flying Tiger Flight DC-8 landing at JFK airport
Photo copyright Ken Rose - used with permission
Flying Tiger Flight 161, a DC-8, flew into heavy rain at 1000 feet and then experienced a strong downdraft, severe changes of wind direction, turbulence, airspeed fluctuations of 15 to 30 knots, and a strong crosswind which pushed the airplane to the left. The captain had to apply 25 to 30 degrees of heading change to correct this deviation. At 300 feet, this pilot applied almost maximum thrust to arrest the descent and to maintain approach speed. The aircraft touched down at approximately 1556. Flight 161 reported problems to the local controller after clearing the runway landing at 1557:30; "I just highly recommend that you change the runways and land northwest, you have such a tremendous wind shear down near the ground on final." To which the local controller responded; "Okay, we're indicating wind right down the runway at 15 knots when you landed." The captain of Flight 161 retorted; "I don't care what you're indicating; I'm just telling you that there's such a wind shear on the final on that runway you should change it to the northwest." In post-accident interviews, the Flying Tiger captain stated he believed that the conditions were so severe that he would not have been able to abandon the approach after he had applied maximum thrust and therefore he landed. Post-accident analysis of the DC-8's drift to the left indicated that, in addition to the downdraft, the aircraft experienced a 60-70 knot crosswind close to the ground.
Eastern 902, an L-1011, abandoned its approach at 1558 after experiencing major difficulties. This flight flew into heavy rain at 400 feet, experienced a rapid drop in airspeed from 150 knots indicated to 120 knots, and the rate of descent increased significantly. Unlike the preceding Flying Tiger flight, this aircraft moved to the right of the localizer course and the captain elected to abandon the approach. He was unable to arrest the aircraft's descent until he had established a high nose up attitude and had applied near maximum thrust. He thought the aircraft had descended to about 100 feet before it began to climb. Post-accident analysis showed that Eastern 902, despite applying power at 250 feet, did not start recovering altitude until it was just 60 feet above the ground.
At 1557:55, the local controller transmitted missed approach directions to Eastern 902 and asked "…was wind a problem?" Eastern 902 answered, "Affirmative."
Finnair 105, a DC-8 then landed normally without difficulties at 1559.
Photo of a microburst with light winds nearby
Around 1557, while Eastern 902 was on approach, the Eastern 66 flightcrew discussed problems associated with carrying minimum fuel loads when confronted with delays in terminal areas. One of the crewmembers stated that he was going to check weather at the alternate airport, which was essentially "next door" at LaGuardia airport, and affected by the same weather patterns. Less than a minute later one of the crewmembers remarked, "…one more hour and we'd come down whether we wanted to or not."
At 1559, the final vector controller transmitted a message to all aircraft on his frequency that "a severe wind shift" had been reported on the final approach to runway 22L, and that he would report more information shortly.
At 1559:40, Eastern 902 re-established radio communications with the JFK final vector controller and reported; "…we had… a pretty good shear pulling us to the right and… down and visibility was nil, nil out over the marker.. .correction.. at 200 feet it was.. .nothing.". The final vector controller responded; "Okay, the shear you say pulled you right and down?". Eastern 902 replied; "Yeah, we were on course and down to about 250 feet. The airspeed dropped to about 10 knots below the bug and our rate of descent was up to 1,500 feet a minute, so we put takeoff power on and we went around at a hundred feet."
When queried by control if Eastern 66 had heard Eastern 902's report. Eastern 66 replied, "…affirmative,"…
At this point the controller established Flight 66's position as being 5 miles from the outer marker and cleared the flight for an ILS approach to runway 22L. Eastern acknowledged the clearance just prior to 1601 with the statement; "Okay, we'll let you know about the conditions?"
The first officer, who was flying the aircraft, called for completion of the final checklist and while completing this checklist the captain stated that the radar was, "Up and off… .standby."
At 1602:20 the captain said, "…I have the radar on standby in case I need it, I can get it off later." indicating that the flightcrew anticipated a go-around as a possibility.
Photo of a “wet” microburst
At 1602:42, the final vector controller asked Eastern 902; "..would you classify that as a severe wind shift, correction, shear?" The flight responded; "Affirmative."
At 1602:50, the first officer of Eastern 66 said; "Gonna keep a pretty healthy margin on this one." An unidentified crewmember said; "I… would suggest that you do." The first officer responded; "In case he's right."
Eastern reported over the outer marker and the flight was cleared to contact Kennedy tower. The Kennedy tower controller cleared Eastern 66 to land. The captain acknowledged the clearance and asked; "Got any reports on braking action…?" The local controller did not respond until the query was repeated. At 1604:14, the local controller replied; "No, none, approach end of runway is wet.. .but I'd say about the first half is wet – we've had no adverse reports."
His query and the comment to "…keep a pretty healthy margin…" by the Eastern flightcrew appears to be in line with the, then current, Eastern Airlines Administrative Bulletins on low-level wind shear associated with both thunderstorms and frontal-zone weather. The bulletins implied that higher approach speeds should be used when shear is anticipated, but cautioned that when runways are wet excessive landing speeds should be avoided because of hydroplaning.
Photo of wreckage of Flight 66 on Rockaway Boulevard, just north of runway 22L.
Google Earth view of JFK, Showing Crash Site
Eastern 66 continued the approach into what is now known to be a classic downburst/microburst encounter. The flight initially experienced this downburst as light rain while centered on the glideslope with airspeed oscillating between 140 and 145 knots. At approximately 500 feet, Flight 66 experienced heavy rain and an increasing headwind "shear" with gusts of 10-20 knots, which resulted in a deviation above glideslope. The resultant pilot reaction was to retard throttles to re-stabilize the approach speed and a relaxation of pitch to re-acquire glideslope. Around this time, the aircraft transited the initial outflow front and then experienced the center of the microburst which yielded a severe downdraft with vertical winds of 1000-1500 feet per minute and a cessation of the previous headwind, leaving the aircraft in a low energy state and with a large downward inertia. Flight 66 descended rapidly below the glideslope with a descent rate of approximately 1500 fpm, and the airspeed decreased from 138 knots to 123 knots in 2.5 seconds. When the aircraft was at 150 feet, the captain called "runway in sight." The first officer, who was flying the aircraft, acknowledged the runway about a second later. Three seconds later, the first officer called for takeoff thrust, but the aircraft impacted the "non-frangible" approach lights approximately 2300 feet short of the runway threshold, caught fire and disintegrated. The wreckage ultimately came to rest on Rockaway Boulevard located north of runway 22L.
In the course of the investigation, airline crews were interviewed on their decision-making process with regard to ascertaining whether an approach was hazardous. Crews reported that when they conducted instrument approaches to airports affected by weather hazards, they relied substantially on the experience of preceding flights as to whether to make the approach themselves or to choose a different course of action. Eastern 66 would not have heard the conversation between the tower controller and the Flying Tiger flight crew about their experience on landing. Approach control had only reported the Flying Tiger experience as a "severe wind shift" on final. Eastern 66 did hear the detailed report of Eastern 902's missed approach but then would have been aware that two more aircraft had landed with no reported problems.
The aircraft transited a severe downpour with high winds, lightning, and thunder (classic wet microburst). Witnesses located at the outer marker reported heavy rain and very high winds. Witnesses at the airport, who were just over ½ mile south of Rockaway Boulevard stated that no rain was falling at their location when they saw the crash. They further stated that the visibility to the northeast was good, but that visibility to the north was reduced. Witnesses who were located approximately 1½ miles north of Rockaway Boulevard described the weather conditions when Eastern 66 passed overhead as; Heavy rain, lightning and thunder, and the wind blowing hard from directions ranging from north through east.
An animation of the accident sequence, and the associated weather phenomena is available at the following link: (Eastern Flight 66 Accident Animation.)
Weather in the Vicinity of JFK Airport
The weather at JFK on the day of the Flight 66 accident was influenced by a slow moving cold front that ran from the southwest to the northeast. This front was moving into the area and was spurring the development of scattered thunderstorms in Northern Pennsylvania, New Jersey and the New York City area. In addition, for over an hour prior to the accident, a stationary "sea-breeze front" had formed near the approach end of the active runway, 22L. While this front did not influence the growth of the thunderstorms, which were already violent by the time they arrived north of JFK, it did affect the wind direction that was being reported to the tower controller. The airport wind sensor was located near the opposite end of the runway, and therefore was measuring the gentle sea breeze, which continued to show gentle winds straight down the runway, effectively masking the severity of the weather through which approaches were being flown. Based on this information, air traffic controllers continued to direct approaches from the north, through stormy weather.
Illustration of a cross section of microburst. Microburst is defined as a downburst affecting an area 4 km (2.5 miles) in diameter or less.
Photo of a microburst, showing outflow
Evident in the post accident analysis of the weather patterns on the day of the accident was the dramatic changes in the weather that occurred in the hour before the accident. The JFK thunderstorm, which ultimately created the family of downbursts that crossed the approach end of runway 22L, moved rapidly toward the western tip of Long Island. The cold sea-breeze front would hold back the southern outflow of the forerunner storms. In addition, the squall-line activity in eastern Pennsylvania and northern New Jersey was intensifying rapidly, resulting in a surge of northwesterly winds that fed warm air into the area north of JFK airport, creating tremendous instability just north of the approach end of the runway. This sequence of events, along with the convergence of the JFK thunderstorm with the forerunner storms, focused the energy of the storms leading to the development of the JFK downbursts.
At the time of the accident, there was no SIGMET in effect for the New York City terminal area. Investigators determined that Eastern 66 had only been supplied with their company weather forecast, predicting widely scattered thunderstorms in New York and eastern New Jersey, and the terminal forecast predicting scattered clouds until 2000, with thunderstorms possible with light rain showers thereafter.
The National Weather Service Forecast Office located in midtown Manhattan did issue a strong wind warning at 1526 which was valid from 1600 to 2000, calling for gusty surface winds to 50 knots from the west in thunderstorms in the New York City terminal area. This warning was distributed to the JFK airport but there was no evidence Eastern 66 received this warning.
Investigators determined that the primary weather indicators to Eastern 66 were the preceding aircraft on the approach path. The controller was only able to report a "severe wind shift" which had been reported on final approach by a previous aircraft (the Flying Tigers DC-8), and then Eastern 66 overheard the report of Eastern 902 after flight 902 had accomplished a go-around.
Investigators concluded that there was a deficiency in the ability to discern hazardous weather conditions, and the Eastern 66 accident investigation correctly acknowledged the need for reliable windshear detection equipment at commercial airports, along with the dissemination of severe weather information to the air traffic control system.
Conceptual models of environmental opposite extremes associated with micrbursts
Figure from “Microbursts-A Handbook for Visual Identification” (Caracena et al, NOAA, 1989)
The investigators identified a contributing factor as the fact that prior to Flight 66, Eastern Airlines flight crews had received advisory information on how to "cope" with windshear hazards on final approach. The technique taught was to increase the approach speed in order to provide an additional airspeed margin above the aircraft's stall speed, thereby allowing a performance capability for safe transit of the expected windshear by sacrificing airspeed for altitude if severe downdrafts or tailwinds were experienced. The main caution to the crews who were taught this technique was to check for braking conditions to ensure that this added speed did not significantly degrade the landing performance. Having obtained a report that there were no braking difficulties, the Eastern 66 flightcrew decided to continue the approach, planning to execute a go-around if necessary.
Although the accident report discerned that Eastern 66 had, in fact, added 10-15 knots airspeed to the normal approach speed, the NTSB, as a result of piloted simulations accomplished using assumptions about the wind conditions on the day of the accident, was uncertain as to whether the accident could have been avoided by quicker recognition and correction of the high descent rate caused by the "adverse winds" from the thunderstorm. Transition from instruments to visual indications would likely have been difficult due to the heavy rain that the flight was penetrating on short final. It was unclear whether the downdraft that Eastern 66 encountered was too severe for a successful approach and landing even if they had relied upon, and responded rapidly to, the indications of the flight instruments.
Cold front schematic
This accident, became the catalyst for extensive meteorological investigation that would lead to the discovery of the downburst/microburst phenomenon.
Photo of an anvil cloud with overshooting top
Photo of rainshaft just beyond approach end of runway
Photo copyright George Hamlin - used with permission
The Windshear hazard
Low Level Windshear associated with both thunderstorms and frontal-zone weather had been identified as a flight hazard prior to Flight 66. Thunderstorms were generally understood to contain severe vertical currents, downdrafts, and outflows which could create "gust fronts.” These storms were often accompanied by heavy rain. In a generic sense, the wind conditions that are typically present with thunderstorms and convective weather fit the Windshear definition (e.g., a change in wind direction and/or speed in a very short distance in the atmosphere). At the time of this accident, the presence of thunderstorms in the vicinity of an airport, while cause for concern, did not constitute a level of hazard that would prompt air traffic control personnel to take an action to change the active runway or traffic flow unless the weather was affecting landing visibility or surface conditions at the airport itself. Air traffic control was primarily concerned with the separation of aircraft from other aircraft, as opposed to separation of aircraft from adverse weather. The National Weather Service could give general reporting and forecasting of significant weather, but at the time was not equipped with the tools that could give a reliable prediction of storm movements or hazardous winds in the terminal area.
The characteristics of downbursts and microbursts are such that they are highly dynamic, localized, and relatively transient in nature. One or more aircraft can transit an area safely, while a following aircraft, such as Eastern 66, can encounter the severe effects of the downburst while passing through the same airspace. A following aircraft could subsequently transit the same area, and also experience no adverse effects.
Early stages of a multiple microburst formation
Fully developed multiple microbursts
A video acquired from KSHB (NBC) TV in Kansas City illustrates the rapid and transient nature of downbursts and microbursts how rapidly they can occur: (KSHB video). As noted in the video, the rapidly descending air mass associated with a microburst can be referred to as an “atmospheric bomb,” in that it can descend suddenly through a larger air mass, and if atmospheric conditions are conducive, will descend until impacting the ground.
Photo of a thunderstorm in Montana
A downburst is a negatively buoyant parcel of air specified as having a downward speed of at least 12 feet per second (~20 knots) when measured at an altitude of 300 feet above the ground (which is comparable to the speed of a jet transport following the usual 3 degree glideslope on final approach). The downburst has a spatial extent of 0.8 kilometers (0.5 miles) or larger, which makes it large enough to have a noticeable effect on an aircraft (a smaller spatial extent is experienced by the aircraft as turbulence).
Negatively buoyant parcel of air = Downburst
Although the term "microburst" and "downburst" are sometimes used interchangeably, the term "microburst" was actually created to specifically distinguish a hazard to aviation where the energy of the downburst is focused within a spatial extent less than 4 kilometers (2.5 miles), which is on the order of a typical jet transport runway length. Although falling precipitation can contribute to a downdraft, the primary forcing mechanism of the microburst is evaporation. There is no correlation between rain rate and microburst intensity. In a microburst, evaporation cools the air. The rain-cooled air can be significantly colder, and more dense, than its environment, creating negative buoyancy. The rate of sinking depends on the temperature difference. Several degrees of temperature differential can cause downward speeds of 35-50 knots. If there is a temperature differential between the cold parcel of air and its environment all the way to the ground, the microburst will accelerate until it hits the ground causing strong horizontal wind gusts. Microbursts can occur with and without precipitation reaching the ground, and can cause damage at and around the impact point. A Video of an experiment illustrating the formation of a downburst is available at the following link: (Educational ice simulation of microburst phenomena)
In the decade after Eastern 66, downburst diameters would be observed to range from as little as 0.5 mile to 10's of miles in diameter. The specific hazard to aviation continued to be extensively researched and analyzed to be related to the scale of the downburst. The smaller spatial scale of a small, intense downburst was found to result in tighter windshear gradients that are experienced by penetrating aircraft as more rapid changes in wind vectors, perhaps well in excess of the performance capabilities of the airplane. In order to identify and differentiate the various downdraft phenomena and to draw attention to the serious hazard posed to aircraft, the term microburst was later defined by Dr. Theodore Fujita of the University of Chicago describing a downburst with a diameter less than four km (2.2 nautical miles), roughly equivalent to a typical transport airplane runway length.
Time History of Windshear Event Following Landing of Air Force One at Andrews Air Force Base (Source: National Oceanic and Atmospheric Adminstration)
Photo of a microburst
In August, 1983, the strongest microburst recorded at an airport was observed at Andrews Air Force Base in Washington DC. The peak horizontal winds speeds were recorded at greater thaýn 130 knots in this microburst. The peak gust was recorded 7 minutes after Air Force One, with U.S. President Ronald Reagan on board, landed on the same runway as the microburst was recorded.
Meteorology course lecture material can be accessed at the following links. The lecture material discuss both downburst and microburst phenomena, courtesy of Dr. Matthew Eastin of the University of North Carolina at Charlotte (Downbursts), and Dr. Haiyan Jiang of Florida International University, (Microbursts). Many of Dr. Jiang's lecture slides are extracted from the textbook Severe & Hazardous Weather-- An introduction to high impact meteorology" by Rauber et al,. and published by Kendall Hunt. Both presentations provide separate overviews of downburst and Microburst phenomena.
Advances in Windshear Detection Technology
As a result of the Flight 66 accident investigation, a study was conducted to better understand the weather phenomena associated with this accident. The resulting report, "Spearhead Echo and Downburst in the Crash of an Airliner", authored by T. Theodore Fujita and Horace R. Byers would use a detailed meteorological study to discover the presence of a severe downdraft phenomenon that was not previously understood. This downdraft phenomenon would be designated as a "downburst." In this report, the downburst was described as a localized, intense downdraft with vertical currents exceeding a downward speed of 12 feet per second (approximately 720 feet per minute) at 300 feet above the surface. This value corresponded with the approximate downward speed of a typical transport aircraft flying a stabilized 3 degree glideslope, thus capable of doubling the descent rate of the affected aircraft.
Photo of LLWAS anemometer pole
Terminal Doppler Weather Radar
Ground based Doppler LIDAR system installed at Tokyo's Haneda airport
Fujita theorized that since an aircraft may fly into a downburst cell abruptly and unexpectedly, immediate recognition and quick action by the pilot would be necessary to overcome its effects. Of equal importance in this report, was the realization that the atmospheric conditions that spurred development of this phenomenon could result in a "family" of downburst cells that could affect some aircraft approaching a runway while others would remain relatively unaffected. It would be several years before the Joint Airport Weather Study (JAWS, 1982) measurements, and high profile windshear crashes in New Orleans (Pan American Flight 759, 1982) and Dallas-Fort Worth (Delta Flight 191, 1985) would lead to the acceptance of Fujita’s theories within the aviation meteorology community.
Around the same time that Dr. Fujita was completing this research, and in direct response to the Eastern 66 accident, the Federal Aviation Administration (FAA) in 1976 developed and began deployment of the Low Level Windshear Alert System (LLWAS). The initial implementation, LLWAS Phase I, was in response to the belief that the Eastern 66 accident was a result of a gust front encounter. This early form of LLWAS had only six anemometers and was designed to detect a gust front. It had no downburst/microburst detection capabilities and, due to the early alert logic, it had the potential to provide misleading information or false alerts. It was not until the analysis of anemometer data obtained from studies subsequent to the Eastern 66 accident, and several high-profile accidents, notably Delta Flight 191 in 1985, that LLWAS Phase 2 was developed and fielded which utilized an improved algorithm that provided some microburst detection capability and reduced the number of false windshear alerts.
Phase 2 LLWAS was a stand-alone system which had drawbacks in that the time required to recognize and then transmit the information to interested airplanes reduced it’s capabilities to provide timely warnings. Today the Phase 2 LLWAS is obsolete, having been replaced by high-quality microburst detection algorithms, so-called Phase 3 LLWAS. This latest LLWAS provides detailed windshear alerts to air traffic controllers, and is effective for wet- and dry- climate microbursts. Windshear is also detected with Terminal Doppler Weather Radar (TDWR) which were designed specifically for the detection of microbursts in the terminal areas of high density airports. TDWR is highly effective when windshear is accompanied by precipitation, but is not as effective in dry climates.
Photo of a microburst with outflow
Light Detection and Ranging (LIDAR) Doppler systems, which "see" aerosols to detect windshear, are now finding their way into use. LIDAR Doppler systems are capable of detecting microbursts in dry climates. In conjunction with all these ground-based windshear detection sensors has been an effort to meld these weather systems, and others into the Integrated Terminal Weather System (ITWS) which now yields one display with consistent terminology for Air Traffic Control to report weather information including windshear alerts to arriving or departing traffic. Similarly, the information from each of these systems is used in the Windshear and Turbulence Warning System (WTWS), which makes the source of the information and alerts transparent to Air Traffic Control personnel. Windshear alerts now use a standard phraseology, providing the flightcrew with Runway, Alert type (wind shift, microburst, etc.), Loss or Gain, and Location of first windshear encounter with relation to the Runway. Operators typically have specific operating procedures when certain alerts are received.
In 1982, the FAA, The National Center for Atmospheric Research (NCAR), and the University of Chicago collaborated to better understand the microburst threat to aviation. Research involved Doppler Radar, anemometers, and sounding systems located in eastern Colorado. During the summer of 1982, approximately 99 microburst events were detected within 10 nautical miles of Denver's Stapleton Airport. This research was identified as “Joint Airport Weather Studies Project (JAWS)” An overview of the JAWS Program can be found in a paper titled “Windshear Hazards to Aviation Operations”, prepared by NCAR, dated July 2012 is available at the following link: (JAWS Overview)
Two high profile accidents, Flight 759, a Boeing 727 attempting to take off from New Orleans in 1982, and Flight 191, a Lockheed L-1011 attempting to land at Dallas-Fort Worth (DFW) in 1985 would punctuate the fact that there was a need to detect and "escape" low level windshear, not just "cope" with the hazard. These accidents would lead to the development and widespread deployment of ground-based and airborne windshear detection equipment.