FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Airlines Flight 3646

27 May 2008 · Dallas, TX, United States Possible conflict

Embraer 140 LR · Accident: clear air turbulence encounter en route

From Springfield Branson National Airport (SGF) to Dallas Fort Worth International Airport (DFW)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
DCA08FA064
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

Embraer 140 LR

Aircraft type
Embraer 140
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
N816AE
Onboard fatalities
Unknown
Route
From Springfield Branson National Airport (SGF), Springfield, MOTo Dallas Fort Worth International Airport (DFW), Arlington, TX
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
Defining eventThe 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
Clear air turbulence encounter
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

  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

According to the flight crew the flight was carried out in smooth air for most of the way to Dallas. When the flight reached a point about 40 nm west of Bowie VOR, at 17,000 feet altitude, and as the airplane overflew a small cloud, the airplane was abruptly jolted by turbulence. The autopilot disconnected and was immediately reactivated by the flight crew. During the turbulence encounter, an elderly female passenger fell to the floor near the lavatory and suffered a broken ankle.

Probable cause

The flight's inadvertent encounter with turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA08FA064
Event ID
20081003X16303
Case number
DCA08FA064
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 3801ddb12d27737f7fdac51b6a02ca515f059db06d4be43bca788c82deeb45d2; retrieved 2026-09-15T10:16:27.458Z.