Flight 2009 · Airbus Industrie A-300B4-605R A300B4-605
Airbus Industrie A-300B4-605R A300B4-605 · Accident: in flight encounter with weather en route
From Philadelphia International Airport (PHL) to Luis Munoz Marin International Airport (SJU)
Event
- NTSB case
- NYC97LA040
- 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
- 0
- 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 Industrie A-300B4-605R A300B4-605
- Aircraft type
- Airbus A-300
- 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
- N50051
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Philadelphia International Airport (PHL), Philadelphia, PATo Luis Munoz Marin International Airport (SJU), San Juan, PR
- 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
- En route · cruise
- 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
- In flight encounter with weather
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Flight attendant › Seat belt, not used
- Weather condition › Turbulence, clear air
Not plotted · Location withheld: coordinates are missing, conflicting, invalid, or have no accepted acquisition method. No substitute location has been invented.
NTSB narrative
The flight was cruising at FL330 in visual meteorological conditions. There were no SIGMETS for turbulence in effect. Flight attendants were working in the forward and aft galleys in preparation for meal service when the flight encountered turbulence. According to the flight data recorder, the turbulence consisted of two pulses which were separated by 8 seconds. Each pulse had a maximum value of +1.6 g's as measured on the vertical axis of the airplane. The seatbelt sign was illuminated. Three flight attendants received minor injuries and a fourth was seriously injured with a fractured ankle. Two passengers in the rear of the airplane whose seat belts were unfastened received minor injuries.
Probable cause
an encounter with unforecast clear air turbulence and the flight attendant's failure to use the seat belt.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC97LA040
- Event ID
- 20001208X07347
- Case number
- NYC97LA040
- 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. 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: fd422fb93c71ebaf9c07c1d80b6e3e8d39cca526cf4e47de5ce91c47b78d3977; retrieved 2026-09-18T17:43:27.937Z.