FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Continental Airlines Boeing 737-524 incident

11 May 1997 · Corpus Christi, TX, United States

Boeing 737-524 · Incident during landing

From George Bush Intercontinental Airport (IAH) to Corpus Christi International Airport (CRP)

Report a problem

Event

NTSB case
FTW97IA187
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

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
N16618
Onboard fatalities
Unknown
Route
From George Bush Intercontinental Airport (IAH), Houston, TXTo Corpus Christi International Airport (CRP)
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
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
Miscellaneous/other
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

  • Flightcrew › IFR procedure, not followed
  • Flightcrew › In-flight planning/decision, inadequate

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight was issued vectors to intercept the final approach course of Runway 31 at Corpus Christi International Airport, and was cleared for the localizer 31 approach. The first officer was manipulating the controls, the In-Range and Approach checklists were completed, and the approach was briefed. A previous aircraft had requested the ILS RWY 13 approach and the tower controller had switched the ILS localizer from 31 to 13. After the completion of the approach, the tower controller did not reselect the localizer 31 approach. The flightcrew tuned in the localizer for Runway 31; however, they did not identify it by morse code. The captain reported that the localizer for Runway 31 was intercepted, 'although at the very beginning the course deviation bar did a couple of full scale deflections, but locked on 7 miles southeast' of the final approach fix. The aircraft was in and out of a broken cloud layer at 2,000 feet msl and the visibility was about 5 to 6 miles. After verifying all instruments were properly configured for the approach, the captain looked outside and 'saw a runway at the northern edge of the cloud they were in and out of.' The runway also had the number 31 painted on its approach end. The captain reported the field in sight to approach control and he was instructed to contact tower control. Tower cleared the flight to land. The flight landed at Cabaniss Field which is a Navy auxiliary field located 5 nautical miles southeast of Corpus Christi International Airport. Cabaniss is located on the final approach course for Runway 31 to Corpus Christi. The first officer had just completed ground and simulator differences training for the Boeing 737-300/500 series aircraft, and this was the first flight of his initial operating experience (IOE) for differences training in the aircraft. The first officer had never been to Corpus Christi, and it had been three years since the captain had been there.

Probable cause

The flightcrew's inadequate in-flight planning and decision, and their failure to refer to the navaids needed for the instrument approach procedure. A factor was the lack of a minimum safe altitude warning from approach control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW97IA187
Event ID
20001208X07902
Case number
FTW97IA187
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: cbddc1cb1d49924bef85da149ccd7025aa0951e1e03bb64ba3a0e15b86e6559d; retrieved 2026-09-18T17:34:38.880Z.