Continental Airlines Flight 75
McDonnell Douglas DC-10-10 · Accident: uncontrolled altitude deviation en route
From Los Angeles International Airport (LAX) to HON · Honolulu, HI
Event
- NTSB case
- LAX98FA169
- 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
McDonnell Douglas DC-10-10
- Aircraft type
- McDonnell Douglas DC-10
- 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
- N68043
- Operator
- Continental Airlines
- Onboard fatalities
- Unknown
- Route
- From Los Angeles International Airport (LAX)To HON · Honolulu, HI
- 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 · climb to 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
- Uncontrolled altitude deviation
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Autopilot/flight director, transmitter(autopilot) › Contamination, other than water
- Company maintenance personnel › Maintenance, inadequate
- Manufacturer › Inadequate quality control
- Manufacturer › Material inadequate, improper
- Pilot in command › Elevator, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The aircraft was climbing in smooth air about 500 feet per minute with the No. 1 autopilot engaged. The captain reported that the aircraft began a sudden and hard uncommanded 2g pull-up, with the control yoke moving rapidly aft. He immediately grabbed the control yoke, disengaged the autopilot, and leveled the aircraft. Three flight attendants in the aft galley and one passenger in an aft lavatory sustained serious injuries. The aft galley flight attendants described the onset of the event as 'being pulled to the floor by what felt like a strong pull of gravity.' The force suddenly reversed and the three were 'thrown up into the ceiling.' Another force reversal followed and the three were 'slammed down against the floor.' The flight attendants said that a 'roller coaster' type movement then occurred, which quickly damped into a steady state. Review of the aircraft's maintenance records for the year preceding the accident revealed over 50 discrepancies for autopilot system uncommanded disconnects, uncommanded pitch-ups, and failures to engage. Review of the DFDR data revealed that as the aircraft passed through 29,200 feet, four pitch cycles were recorded over a 15-second time period and were accompanied by vertical accelerations, the most severe of which was between 1.84 and -0.12 g's. The initial uncommanded nose pitch-up was preceded by an autopilot controlled movement of the left inboard elevator. The subsequent elevator movements and resultant pitch excursions were due to the pilot's control inputs. With the exception of the captain's and first officer's control wheel sensor units, all autopilot systems passed functional checks. Postaccident test of the first officer's control wheel sensor unit showed an out of tolerance and drifting null signal for the strain gage which provides pitch signal input to the No. 1 autopilot. After about 3 minutes, the signal became noisy and jumped to values of up to 4 volts several times. Many spikes were also observed at values under 3.5 volts (signals over 3.5 volts trigger an automatic disengagement of the autopilot). Subsequent examination of the pitch strain gages by optical magnification found a foreign black-gray metallic-like substance bridging the terminal lug ends. Analysis showed the material was a silver based conductive substance, lying below a factory applied sealing layer, which was introduced during manufacture. The solder on the lugs and the wire used between the lugs and terminals was found not to be consistent with the manufacturer's specifications.
Probable cause
The contaminated strain gage, which resulted in shorting of the strain gage's terminal lugs which lead to excessive autopilot initiated elevator movement, and excessive elevator actuation during recovery by the captain. Contributing factors were the failure of the airline maintenance department to diagnose and correct a historical problem with the autopilot system and the manufacturer's inadequate quality assurance program.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX98FA169
- Event ID
- 20001211X10120
- Case number
- LAX98FA169
- 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, damage. 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: 7fae8b88a9433c5704da6ca38e91bc9576ebfac8547f6f71da99d28fa9ef388f; retrieved 2026-09-18T17:09:04.474Z.