Continental Airlines Boeing 737-524 incident
Boeing 737-524 · Incident: system/component malfunction/failure (non-power) during landing
From OKC Will Rogers World Airport (OKC) to George Bush Intercontinental Airport (IAH)
Event
- NTSB case
- DFW08IA087
- 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
- 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
Boeing 737-524
- Aircraft type
- Boeing 737
- 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
- N23661
- Operator
- Continental Airlines
- Onboard fatalities
- Unknown
- Route
- From OKC Will Rogers World Airport (OKC), Oklahoma City, OKTo George Bush Intercontinental Airport (IAH), 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 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
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight crew departed for the destination airport knowing that the anti-skid system was inoperative. While in flight the flight crew briefed the operational procedures for landing with an inpoerative anti-skid system, including manual deployment of the speed brakes and thrust reversers before using minimal braking during the landing to avoid tire blowout. During the landing the flight crew encountered four blown main landing gear tires, resulting in minor damage to the airplane. An examination of the wheels, tires, and brakes revealed no anomalies. Further examination of the airplane and its systems revealed no anomalies aside from the inoperative anti-skid system. The flight data recorder data depicted no deployment of the speed brakes, no use of the thrust reversers, and an increase in brake pressure at the same time weight was transferred to the nose gear, consistent with brake application upon landing.
Probable cause
The flight crew's improper landing technique for an inoperative anti-skid system resulting in locked brakes and four blown main landing gear tires.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW08IA087
- Event ID
- 20080404X00426
- Case number
- DFW08IA087
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, 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: f5522d2737df0d99d1304c9522f7790254ada13f6f546d1fa2db07370fecbdde; retrieved 2026-09-15T09:29:24.850Z.