Continental Airlines Flight 134
McDonnell Douglas MD-82 · Incident: airframe, component or system failure during landing
From DIA · Denver, CO to Newark Liberty International Airport (EWR)
Event
- NTSB case
- IAD97IA048
- 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
- Instrument Meteorological Cond
McDonnell Douglas MD-82
- Aircraft type
- McDonnell Douglas MD-82
- 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
- N34838
- Operator
- Continental Airlines
- Onboard fatalities
- Unknown
- Route
- From DIA · Denver, COTo Newark Liberty International Airport (EWR), NJ
- 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 · landing roll
- 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
- Minor
Cause areas
- Landing gear, nose gear assembly › Fatigue
Approximate · Estimated position: the centre of Newark, NJ, the place the record names. Not the accident site.
NTSB narrative
The crew experienced an unsafe nose gear light on approach to landing. After recycling the gear, all indications were that the gear was down and locked. The airplane landed on runway 4R during which the nose gear collapsed; the airplane skidded to a stop. Examination of the airplane revealed the nose landing gear upper lock link had fractured. The lock link had accumulated 28,978 service hours and 24,511 cycles since original manufacture. The lock link was overhauled 13,515 and 6,317 hours prior to the failure. A metallurgical examination revealed the upper lock link was fractured through the 'I' beam section near its lower end about 3 inches from the overcenter pivot with the lower lock link. The fracture features were typical of fatigue which progressed over a large portion of the fracture. No mechanical, corrosion, or manufacturing discontinuities were visible at the fatigue origin. At the time of the failure, there was an Airworthiness Directive AD-97-02-10 about the upper lock link. It required inspections of assemblies prior to 10,000 total cycles or within 90 days of its issue, February 11, 1997, whichever came later. Continental Airlines was in the process of inspecting its entire fleet of affected aircraft when this incident occurred.
Probable cause
fatigue fracture of the upper lock link, which led to the collapse of the nose gear during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD97IA048
- Event ID
- 20001208X07410
- Case number
- IAD97IA048
- 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. 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: 59c8dd233c05a4689e2667aec2e59f414cd7ed0008f81ddbb3b8e9cb52f93382; retrieved 2026-09-18T17:42:15.300Z.
- The NTSB's operator name is blank for N34838; the operator shown is the name the NTSB's other records give its FAA operator code, CALA.