Republic Airlines Embraer S A ERJ170-200LR accident
Embraer S A ERJ170-200LR · Accident: aircraft wake turbulence encounter en route
From Chicago O'Hare International Airport (ORD) to George Bush Intercontinental Airport (IAH)
Event
- NTSB case
- CEN14CA455
- 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 S A ERJ170-200LR
- Aircraft type
- Embraer ERJ170
- 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
- N421YX
- Operator
- Republic Airlines
- Onboard fatalities
- Unknown
- Route
- From Chicago O'Hare International Airport (ORD), Chicago, ILTo George Bush Intercontinental Airport (IAH), Houston, TX
- Aircraft age
- Built the same year (2014)
- 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
- Aircraft wake 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While cruising in smooth air conditions with no clouds in the area and with the autopilot on and the seat belt sign off the airplane had a brief encounter with what the flight crew described as wake turbulence. The momentary turbulence resulted in a sharp roll deviation of about 15 to 20 degrees. The turbulence lasted for less than five seconds then returned to smooth air conditions. One of the two flight attendants who had been standing in the rear galley was seriously injured and the other flight attendant sustained a minor injury. No significant turbulence had been forecast, and the flight crew had not overheard any airplanes in the area reporting turbulence. Immediately after the encounter, the airplane continued in smooth air conditions.
Probable cause
The airplane's inadvertent encounter with wake turbulence during cruise flight, which resulted in a serious injury to a flight attendant.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN14CA455
- Event ID
- 20140826X64917
- Case number
- CEN14CA455
- 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, 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: 3c7ad983f2c70bd1e0497f45c793ef1e6c29ffe08ecce64e91aa863f03b81b9f; retrieved 2026-09-16T01:41:08.623Z.