No fatalities

29 Apr 2014: BOEING 757 — Powhatan, VA

Powhatan, VA, United States

On 29 Apr 2014, a BOEING 757 was involved in an aviation accident near Powhatan, VA. No fatalities were reported. Investigators recorded the probable cause as: 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… This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 1778583330Data APIEditorial standards
BOEING 757
Photo: Ryanmac06 at English Wikipedia / Public domain, via Wikimedia Commons

Two severe turbulence encounters near Flat Rock, Virginia, led to medical exams for AWE815 crew and passengers, and hail damage. ATC did not provide required weather services despite precipitation.

Overview

On an unspecified date, multiple aircraft experienced severe turbulence while under the control of Washington Air Route Traffic Control Center (ZDC) sector 16. The incidents involved flights AWE815, JIA4678, and AWE778. The controller did not comply with FAA Order 7110.65, paragraph 2-6-4, regarding weather and chaff services, despite clear indications of precipitation.

AWE815 Turbulence Encounter

AWE815, en route from Orlando, Florida, to Philadelphia, Pennsylvania, contacted ZDC sector 16 at 1930:42, reporting level at flight level (FL) 390. At 1935:04, the R16 controller instructed a descent to FL350, which the pilot acknowledged. At 1939:02, the controller directed 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." After a request for repetition, the controller reissued the crossing restriction and inquired about the turbulence. At 1939:56, the pilot reported that the turbulence lasted about 30 seconds, occurring approximately ten nautical miles south of Flat Rock, between FL370 and FL360. The pilot added, "We just need to catch our breath here." No further exchanges occurred, and at 1944:05, the pilot was instructed to contact the next sector. The crew did not report any damage or injuries before changing frequencies.

Responses from JIA4678 and AWE778

JIA4678 checked in at 1938:34, climbing from FL270 to FL330. At 1941:14, after AWE815's report, the controller advised JIA4678 of severe turbulence 45 to 50 miles ahead at their 12 o'clock position, approving deviations. At 1944:22, the crew requested direct COYLE but were cleared direct AGARD. The crew later reported smooth ride at 1947:07. However, at 1948:06, JIA4678 reported severe turbulence and requested to level at FL320. The controller approved a right deviation and direct AGARD when able. At 1948:53, the controller instructed AWE778 to fly heading 010 to avoid the turbulence area. The pilot requested lower altitude; assigned FL280. JIA4678 reported exiting turbulence at 1951:11, climbing to FL330, and recommended other aircraft avoid the area 10 miles south of Flat Rock. Neither JIA4678 nor AWE778 reported damage or injuries.

Air Traffic Control Compliance Issues

During the approximately 1 hour and 45 minutes the R16 controller worked the position, no compliance with FAA Order 7110.65, paragraph 2-6-4, "Weather and Chaff Services," was noted. Recorded WARP/NEXRAD data showed areas of precipitation, and the controller made weather-related comments to pilots, while numerous pilot requests for deviations were received. The ZDC facility had no live monitoring program for weather services, according to the facility support manager for quality control.

Aftermath

The R16 controller submitted two pilot reports about the severe turbulence encounters. American Airlines reported that all four flight attendants and several passengers aboard AWE815 requested medical examinations after the flight, though none reported injuries meeting the standard for an aircraft accident. Two flight attendants remained in a non-duty status for at least three weeks. The aircraft sustained hail damage and required replacement of the radome.

Contributing factors

Causes

ATC personnelATC

Other contributing factors

Flight crew