FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Air Lines Airbus A330 323 accident

17 Mar 2014 · Seattle, PO, United States Possible conflict

Airbus A330 323 · Accident: cabin safety event en route

From Seattle–Tacoma International Airport (SEA) to Narita International Airport (RJAA)

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
DCA14CA083
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

Airbus A330 323

Aircraft type
Airbus A330
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
N803NW
Onboard fatalities
Unknown
Route
From Seattle–Tacoma International Airport (SEA), Seattle, WATo Narita International Airport (RJAA), Narita
Aircraft age
About 11 years (built 2003)
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
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

  • Environmental issues › Physical environment

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

About four hours after departure on an international flight, and while over the Pacific Ocean, a flight attendant tripped and fell over a passenger's extended foot while walking down the aisle. The flight attendant was unable to continue her duties due to a swollen and painful foot. During a follow up examination, the flight attendant was diagnosed with a fractured foot.

Probable cause

the flight attendant inadvertently tripping over a passenger's foot that was protruding into the aisle, which resulted in the flight attendant fracturing her foot.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA14CA083
Event ID
20140320X53321
Case number
DCA14CA083
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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
  • API snapshot SHA-256: 22dba35d6ed5124d003976b00f0829fce7caa2a0340a6d08ff4e3ce890eb7ff3; retrieved 2026-09-15T23:25:32.302Z.