29 Apr 2014: BOEING 757

29 Apr 2014: BOEING 757 — Unknown operator

No fatalities • Powhatan, VA, United States

Probable cause

The air traffic controller’s failure to provide required advisories about significant radar-observed convective precipitation along both airplanes’ flight routes and the air route traffic control center’s lack of a program to ensure that air traffic controllers provide this required information to pilots, which led to both airplanes encountering severe turbulence. Contributing to the airplanes’ encounters with severe turbulence was the flight crews’ failure to detect the precipitation using on-board radar and request deviations, as necessary, to avoid the hazard.

— NTSB Determination

Accident narrative

AWE815 was en route from Orlando, Florida, to Philadelphia, Pennsylvania, and contacted ZDC sector 16 at 1930:42, reporting level at FL390. At 1935:04, the R16 controller instructed AWE815 to descend and maintain FL350. The pilot acknowledged. At 1939:02, the controller instructed AWE815 to cross SHONA intersection at FL310. The pilot began to acknowledge, transmitting, "SHONA at 310 Cactus 8 uh 15, we're in…we're in severe turbulence." At 1939:42, the pilot of AWE815 transmitted, "OK – say again for Cactus 815?" The controller reissued the crossing restriction at SHONA, the pilot acknowledged, and the controller then asked the pilot for further information about the reported turbulence. At 1939:56, the pilot responded, "Well, it lasted about, uh, wherever we just were, just about uh, ten south of Flat Rock, and it lasted about 30 seconds." The controller asked the pilot to confirm that the event occurred between FL370 and FL360, and the pilot did so. The controller then asked the pilot if he needed anything else, and the pilot replied, "We just need to catch our breath here." There were no further exchanges about the turbulence encounter with AWE815, and the pilot was instructed to contact the next sector at 1944:05. The crew did not report any damage or injuries before changing frequencies.

At 1938:34, JIA4678 checked in with the R16 controller, reporting climbing through FL270 to FL330. At 1941:14, after the severe turbulence report from AWE815, the R16 controller advised the crew of JIA4678 that they could deviate right or left as they deemed necessary, adding that a report of severe turbulence had occurred at their 12:00 position and 45 to 50 miles. The pilot responded, "Appreciate it – deviations approved." The controller continued, "…and uh yeah 50 miles straight ahead and he was out of 37 for 36." At 1944:22, the pilot of JIA4678 asked, "Any chance of direct COYLE?" At 1944:52, after talking to another aircraft, the controller responded, "I can't do direct COYLE – I can do direct AGARD." The crew accepted direct AGARD, and the controller continued, "If you need to deviate to the right that's approved, go direct AGARD when able, that's 15 degrees right about." The pilot accepted the clearance and approval of the deviation. At 1947:07, the controller asked the pilot of JIA4678, "How's the ride through the weather?, and the pilot responded, "Uh, pretty smooth." At 1948:06, JIA4678 called and the controller responded, "Go ahead." The pilot then stated, "Uh we're reporting severe turbulence, and we'd like to level off here at FL320." The controller acknowledged the report and told the crew to do what they needed to do, including deviate right "to get out of it," and to go direct AGARD when able. The pilot responded, "AGARD when able, right turn, and uh, does that look better?" The controller replied, "Yeah," and again told the crew to, "…do what they needed to do to get out of it."

At 1948:53, the controller instructed the pilot of AWE778 to fly heading 010 to go around the area where they turbulence reports had occurred. The pilot asked if a lower altitude would be better, and the R16 controller replied that he did not know because there were no other aircraft at lower altitude to provide a report. The pilot then requested FL270, and was assigned FL280. The controller then asked the crew of JIA4678 to advise when they were "out of it." The crew reported that they were out, and were climbing to FL330. They additionally recommended that aircraft stay away from the area 10 miles south of Flat Rock. JIA4678 was transferred to the next sector at 1951:11. The crew did not report any damage or injuries.

At 1950:17, the R16 controller coordinated with another sector to accommodate a northerly deviation for AWE778, stating, "I'm going to run north around that weather and then go to Nottingham, I've got severe turbulence in that cloud there."

During the approximately 1 3/4 hour session on the R16 position, no compliance with FAA order 7110.65, "Air Traffic Control", paragraph 2-6-4, "Weather and Chaff Services," was noted, although there were clearly areas of precipitation present in the sector as evidenced by review of recorded WARP/NEXRAD data, comments about weather made by the controller to several pilots, and numerous pilot requests for weather deviations. According to information provided by the facility support manager for quality control, ZDC had no program for live monitoring of weather services to ensure that displayed precipitation information was being provided to flight crews as required.

Two pilot reports about the severe turbulence encounters were submitted by the R16 controller following the incidents.

According to information supplied by American Airlines, all four flight attendants and several passengers aboard AWE815 requested medical examinations following the flight, although none of them reported injuries meeting the standard for an aircraft accident. Two of the flight attendants remained in a non-duty status for at least three weeks after the incident. The aircraft sustained hail damage and required replacement of the radome.

For further information, see the air traffic control group chairman's report in the docket for this case.

Contributing factors

  • cause ATC personnel
  • factor Flight crew
  • factor Flight crew
  • cause ATC
  • ATC

Conditions

Weather
IMC

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.