Republic Airline Flight 3143
Embraer-Empresa Brasileira de ERJ 170-20 · Accident: turbulence encounter on approach
From Ronald Reagan Washington National Airport (DCA) to Indianapolis International Airport (IND)
Event
- NTSB case
- CEN09LA461
- 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-Empresa Brasileira de ERJ 170-20
- Aircraft type
- Embraer ERJ-170
- 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
- N120HQ
- Operator
- Republic Airline
- Onboard fatalities
- Unknown
- Route
- From Ronald Reagan Washington National Airport (DCA), Washington, DCTo Indianapolis International Airport (IND), Indianapolis, IN
- 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
- Approach
- 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
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While on final approach to the destination airport, the airplane was in light turbulence with occasional moderate turbulence. Flight and cabin crew reports of the event indicated that several announcements had been made instructing passengers to remain seated with their seat belts fastened for the remainder of the flight and that the fasten seat belt signs were illuminated. After these instructions were given, a passenger elected to leave his seat to use the lavatory. While returning to his seat after using the lavatory, the airplane encountered moderate turbulence and the passenger fell. He suffered a broken ankle.
Probable cause
The passenger's failure to comply with crewmember instructions to remain seated while the airplane was in turbulent weather conditions, resulting in an injury to the passenger.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN09LA461
- Event ID
- 20090724X34459
- Case number
- CEN09LA461
- 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: f654f23ed104bbced92924642e3659a0fe5bf170f3338e70b820762a6dadc7a6; retrieved 2026-09-15T12:01:12.498Z.