Casualties unknown

1997-05-11: Boeing 737-524 (N16618) — Continental Airlines, Inc. — Corpus Christi, TX

Corpus Christi, TX, US

On May 11, 1997, a Boeing 737-524 (registration N16618) operated by Continental Airlines, Inc. was involved in an aviation accident near Corpus Christi, TX. Investigators recorded the probable cause as: 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. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 8 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards
Boeing 737-524
Photo: San Diego Air & Space Museum Archives / Public domain, via Wikimedia Commons

A flight landed at Cabaniss Field instead of Corpus Christi International Airport after the ILS localizer for Runway 31 was not reselected and the crew failed to identify the frequency by morse code.

Approach Setup

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, and the In-Range and Approach checklists were completed, accompanied by an approach briefing.

ILS Frequency Change

A previous aircraft had requested the ILS Runway 13 approach, prompting the tower controller to switch the ILS localizer from Runway 31 to Runway 13. After that aircraft completed its approach, the tower controller did not reselect the localizer for Runway 31.

Crew Actions

The flightcrew tuned the localizer frequency for Runway 31 but 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 performed several full-scale deflections before locking on approximately 7 nautical miles southeast of the final approach fix. The aircraft was in and out of a broken cloud layer at 2,000 feet mean sea level, and visibility was about 5 to 6 miles.

Visual Identification

After verifying that all instruments were properly configured for the approach, the captain looked outside and saw a runway at the northern edge of the cloud layer. The runway had the number 31 painted on its approach end. The captain reported the field in sight to approach control and was instructed to contact tower control, which cleared the flight to land.

Actual Landing Site

The flight landed at Cabaniss Field, a Navy auxiliary field located 5 nautical miles southeast of Corpus Christi International Airport. Cabaniss Field lies on the final approach course for Runway 31 at Corpus Christi.

Crew Experience

The first officer had just completed ground and simulator differences training for the Boeing 737-300/500 series aircraft, and this flight was the first of his initial operating experience (IOE) for differences training in this aircraft type. The first officer had never been to Corpus Christi, and it had been three years since the captain had last visited.

Outcome

No injuries, fatalities, or aircraft damage were reported. The aircraft landed safely at the wrong airfield.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001208X07902. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.