Trans World Airlines Douglas DC-9-31 incident
Douglas DC-9-31 · Incident: hard landing
From St. Louis Lambert International Airport (STL) to Nashville International Airport (BNA)
Event
- NTSB case
- MIA99IA249
- 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
- Incident
- 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
Douglas DC-9-31
- Aircraft type
- Douglas DC-9
- 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
- N993Z
- Operator
- Trans World Airlines
- Onboard fatalities
- Unknown
- Route
- From St. Louis Lambert International Airport (STL), St. Louis, MOTo Nashville International Airport (BNA)
- 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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
- Landing gear › Fractured
- Other crewmember › Proper descent rate, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The first officer failed to maintain the proper rate of descent (sink rate) resulting in a hard landing on touch down, and separation of the left main landing gear during landing rollout. The pilot-in-command stated he knew the first officer was not going to make a good landing. He did not take any corrective action other than informing the first officer initially to increase power. Examination of the left main landing gear assembly revealed a preexisting crack in the outer cylinder housing.
Probable cause
A preexisting crack on the left main landing gear outer cylinder housing and the first officer's failure to maintain the proper rate of descent resulting in a hard landing on touchdown, and subsequent total failure and separation of the left main landing gear on landing rollout. Contributing to the accident was the pilot-in-commands improper supervision of the first officer during the approach phase of the landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99IA249
- Event ID
- 20001212X19826
- Case number
- MIA99IA249
- 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: ff158cd4e7264edb41ea27609dfa38c11a8e6583fd29b4f5b749cbfb61a06024; retrieved 2026-09-18T16:53:20.873Z.