FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Shuttle America Embraer-Empresa Brasileira de ERJ 170 200 LR accident

27 Aug 2014 · Columbus, OH, United States

Embraer-Empresa Brasileira de ERJ 170 200 LR · Accident: cabin safety event en route

From Ronald Reagan Washington National Airport (KDCA) to Eppley Airfield (KOMA)

Report a problem

Event

NTSB case
DCA14CA155
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-Empresa Brasileira de ERJ 170 200 LR

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
N204JQ
Onboard fatalities
Unknown
Route
From Ronald Reagan Washington National Airport (KDCA), Washington, DCTo Eppley Airfield (KOMA), Omaha, NE
Aircraft age
About 6 years (built 2008)
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 · climb to 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
Cabin safety event
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

  • Aircraft › Aircraft systems

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 flight attendant (FA) statements, the airplane was climbing to cruise altitude in smooth air. While preparing for meal service, a FA pulled out a beverage cart from its stowed position in the aft galley and it immediately toppled over onto the foot of another FA that was in area. The injured FA was unable to continue her duties and the flight diverted to a closer airport without further incident. The flight attendant was transported to the hospital and diagnosed with an open fracture of her right foot. There were no reported malfunctions or failures with the beverage cart.

Probable cause

the capabilities of the beverage cart were exceeded which resulted in the cart toppling over and fracturing the flight attendant's foot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA14CA155
Event ID
20140828X43935
Case number
DCA14CA155
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: 4b26877c7e418c10d93f120204b50fd6f53f903e24c494d700d2022af92d332c; retrieved 2026-09-16T01:41:40.675Z.