FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 3967 · Embraer 145LR

13 May 2006 · Winchester, VA, United States

Embraer 145LR · Accident while maneuvering

From Chicago O'Hare International Airport (ORD) to Washington Dulles International Airport (IAD)

Report a problem

Event

NTSB case
NYC06LA115
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
Instrument Meteorological Cond

Embraer 145LR

Aircraft type
Embraer 145
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
N653AE
Operator
Unknown
Onboard fatalities
Unknown
Route
From Chicago O'Hare International Airport (ORD), Chicago, ILTo Washington Dulles International Airport (IAD), Dulles, VA
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
Maneuvering
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
Miscellaneous/other
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

  • Passenger › Unsafe/hazardous condition warning, not followed

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

NTSB narrative

The airplane was approaching its destination, at 10,000 feet, and the seat belt sign had been illuminated for 10-15 minutes, when the crew noticed that clouds ahead "appeared bumpy." The flight attendant was notified, and she advised the passengers of possible turbulence via the public address system. A passenger subsequently got out of her seat to use the lavatory, and upon leaving the lavatory, while the airplane was in a cloud and experiencing turbulence, she fell and broke her ankle.

Probable cause

The passenger's failure to heed the flight attendant warning and the seat belt sign. A factor was the turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06LA115
Event ID
20060721X00983
Case number
NYC06LA115
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: badc5f32e538e33de27d7338ec18623212b9d510ce4cefe6e3a1f41840852ae4; retrieved 2026-09-18T14:53:23.339Z.