Flight 664 · McDonnell Douglas MD-88
McDonnell Douglas MD-88 · Accident: airframe, component or system failure during initial climb
From Denver International Airport (DEN) to Hartsfield Jackson Atlanta International Airport (ATL)
Event
- NTSB case
- DEN05LA077
- 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
McDonnell Douglas MD-88
- Aircraft type
- McDonnell Douglas MD-88
- 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
- N949DL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Denver International Airport (DEN), Denver, COTo Hartsfield Jackson Atlanta International Airport (ATL), Atlanta, GA
- 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
- Initial climb
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Fuselage, pressure bulkhead › Penetrated
- Landing gear, nose gear assembly › Failure
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Shortly after takeoff, the pilots heard a loud bang and the cabin lost pressurization. The pilots observed an unsafe nose gear indication. They placed the gear handle in the down position and got three green lights. The control tower confirmed that the landing gear were down when the aircraft performed a low pass. The flight made an uneventful landing at Denver. Post-accident examination by maintenance personnel revealed a hole in the forward pressure bulkhead and broken nose gear actuator. The nose landing gear actuator piston rod had worn threads, and a key locking washer in the gear assembly was sheared. The airline said that this was original equipment.
Probable cause
the failure of the nose gear actuator resulted in penetration of the forward pressure bulkhead and a loss of pressurization.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN05LA077
- Event ID
- 20050526X00682
- Case number
- DEN05LA077
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-05-14.
- API snapshot SHA-256: c3dd332b9e2e1ca7f230e7aa80750e89409990eeb04dbf53830ed54e57cf1db3; retrieved 2026-09-18T15:02:35.777Z.