FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 952 · Boeing 767-232

11 Jul 2005 · Raleigh-Durham, NC, United States

Boeing 767-232 · Accident: in flight encounter with weather en route

From Hartsfield Jackson Atlanta International Airport (ATL) to LaGuardia Airport (LGA)

Report a problem

Event

NTSB case
DCA05MA083
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Boeing 767-232

Aircraft type
Boeing 767
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N113DA
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GATo LaGuardia Airport (LGA), New York, NY
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Weather condition › Turbulence, clear air

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The captain stated that after takeoff he waited until FL370, and well past the line of weather, to turn off the seat belt light. The flight was smooth for about 10 to 15 minutes, and they transited in and out of cirrus clouds, with the weather radar being used to scan from the 160 to 40 mile range, and with no weather being noted. As the flight progressed he said they encountered moderate turbulence for about 10 to 15 seconds, and he immediately made an announcement for the flight attendants and passengers to sit. Shortly thereafter the captain said he was informed that a flight attendant had been injured. The first officer stated that as the flight climbed they easily transited between two cells, entered clear skies, and was in smooth air. The seat belt sign had been turned off, and the captain continued searching the area with the weather radar. The first officer said that although there were some intermittent high cirrus clouds, there was no weather that would pose problems along the route of flight. About 10 to15 minutes after level-off, the first officer said the airplane hit what he would call severe turbulence, and both he and the captain were tossed about in their seats. They were initially unable to either grab the flight controls, or turn on the seat belt sign, and after the initial big bump, the first officer said "he grabbed the controls (it was my leg), and followed through with the thrust levers and yoke." According to the first officer, as soon as able the captain turned on the seat belt sign, made the announcement for everyone to sit down, and they soon heard a flight attendant make an announcement asking for a doctor. All flight attendants provided statements that were consistent, affirming that there had been turbulence, and that the seat belt sign was not lit during the turbulence prior to the accident. The NTSB conducted studies of airplane's DFDR, as well a study of the weather around the time of the accident. Examination of the DFDR revealed information affirming that the autopilot had been engaged, and consistent with there having been an encounter with turbulence. The weather study examined many weather products and provided data consistent with there being convectively induced turbulence in the vicinity of strong to severe thunderstorms.

Probable cause

An inadvertent in-flight encounter with clear air turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA05MA083
Event ID
20051028X01749
Case number
DCA05MA083
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, damage. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 4b57c427ba79db0e388ec3fcdfd3872411f14df346ddacddaba79d6b3c1fda1f; retrieved 2026-09-18T15:00:19.114Z.