Lufthansa Airbus Industrie A340-300 accident
Airbus Industrie A340-300 · Accident: in flight encounter with weather en route
From Frankfurt Main Airport (EDDF) to George Bush Intercontinental Airport (KIAH)
Event
- NTSB case
- FTW03LA195
- 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 Industrie A340-300
- Aircraft type
- Airbus A340
- 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
- D-AIGK
- Operator
- Lufthansa
- Onboard fatalities
- Unknown
- Route
- From Frankfurt Main Airport (EDDF), FrankfurtTo George Bush Intercontinental Airport (KIAH), Houston, TX
- 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 129: Foreign
- 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
- Flightcrew › Flight into adverse weather, continued
- Flightcrew › Weather evaluation, inadequate
- Weather condition › Turbulence
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The transport aircraft encountered severe turbulence at flight level 310 while in IMC during an international flight. Convective SIGMETs for an area of thunderstorms with tops to flight level 410 were in effect at the time and location of the accident. The FDR data showed aircraft disturbances in vertical acceleration, lateral acceleration, altitude, magnetic heading, and vertical speed. The autopilot and auto-throttle parameters remained engaged throughout the event. The captain side stick pitch, first officer side stick pitch, and first officer side stick roll parameters showed no movement during the disturbance. The captain side stick roll parameter moved -1 degree during 2057:07 and then returned to 0 degrees. The rudder pedal position and rudder parameters showed less than one degree of movement during the event sequence, and the pitch and elevator parameters registered excursions of less than 1.5 degrees. The altitude reached a minimum value of 30,884 feet msl, the aircraft stabilized at 31,000 feet. The aircraft landed at 2207 at the destination airport, approximately I hour and 10 minutes after the encounter with severe turbulence. Food service was in progress in the cabin, and the "fasten seat belt" light was on at the time of the turbulence encounter. The FA statements revealed that 7 FA's hit the cabin ceiling and then the floor, one FA hit the ceiling then an armrest, and 2 FA's were tossed through a galley. Three food serving carts were lifted from the floor, and numerous food service items were tossed about the cabin. Some of the passengers were out of their seats, and some, who were seated, did not have their seat belts secured per the "Fasten Seat Belt" light. The 18,593-hour captain/check airman with 4,093 hours in the accident aircraft, was the non-flying pilot (PNF) during the event, the 2,759-hour first officer was the pilot flying (PF). Reviews of the flight and duty time records disclosed no evidence of any activities that would have prevented the flight crewmembers from obtaining sufficient rest in the 72 hours before the accident flight. Company interviews revealed that the departure flight was delayed 4 hours and 7 minutes as a result of a change of airplanes. The Flight Crew Manual states in part: every cloud related to a severe thunderstorm represents a serious danger, and AVOID - AVOID - AVOID since weather can exceed the performance capabilities and/or structural limits of the airplane.
Probable cause
The flight crew's inadequate evaluation of the weather and their decision to continue the along the route of flight resulting in an encouter with severe turbulence. Contributing factors were the captain's instructions to continue food servicing in the cabin, and the passenger's failure to obey the lighted "FASTEN SEAT BELT" sign.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW03LA195
- Event ID
- 20030820X01371
- Case number
- FTW03LA195
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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. 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: 60883a46e43f8981d8353c1a814620cd7ddeb4899774abb481b32dd17814e8ef; retrieved 2026-09-18T15:42:55.677Z.
- The NTSB's operator name is blank for D-AIGK; the operator shown is the name the NTSB records it doing business as.