FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FTW98MA096 · Gates Learjet 25B

13 Jan 1998 · Houston, TX, United States

American Corporate Aviation Gates Learjet 25B · Accident: airframe, component or system failure on approach

From William P. Hobby Airport (HOU) to George Bush Intercontinental Airport (IAH)

Report a problem

Event

NTSB case
FTW98MA096
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
2 · 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
General aviation
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

Gates Learjet 25B

Aircraft type
Learjet 25
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
N627WS
Onboard fatalities
Unknown
Route
From William P. Hobby Airport (HOU)To George Bush Intercontinental Airport (IAH)
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 91: General Aviation
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
Approach · IFR final approach
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
Destroyed

Cause areas

  • Flightcrew › Decision height, not complied with
  • Flightcrew › Proper glidepath, not maintained

Approximate · Estimated position: the centre of Houston, TX, the place the record names. Not the accident site.

NTSB narrative

The flight crew was positioning the airplane in preparation for a revenue flight when it crashed 2 nautical miles (nm) short of the runway during a second instrument landing system approach in instrument meteorological conditions. Except for the final 48 seconds of the 25-minute flight, the captain was the flying pilot, and the first officer was the nonflying pilot. When the airplane was about 0.5 nm inside the outer marker on the first approach, the compass warning flag on the captain's course deviation indicator appeared, indicating that the heading display was unreliable. The airplane deviated from the localizer centerline to the left but continued to descend. After about 1 minute, during which time the airplane's track continued to diverge from the localizer centerline, the flight crew executed a missed approach. The flight crew then unsuccessfully attempted to clear the compass flag by resetting circuit breakers. The captain directed the first officer to request a second approach. Contrary to company crew coordination procedures, the flight crew did not conduct an approach briefing or make altitude callouts for either approach. Although accurate heading information was available to the captain on his radio magnetic indicator, he experienced difficulty tracking the localizer course as the airplane proceeded past the outer marker on the second approach. The captain transferred control to the first officer when the airplane was 1.9 nm inside the outer marker. The airplane then began to deviate below the glideslope. The descent continued through the published decision height of 200 feet above ground level, and the airplane struck 80-foot-tall trees. Postaccident testing revealed that the first officer's instruments were displaying a false full fly-down glideslope indication because of a failed amplifier in the navigation receiver. The glideslope deficiency was discovered 2 months before the accident by another flight crew. An FAA repair station attempted to resolve the problem and misdiagnosed it as "sticking" needles in the cockpit instruments. The operator was immediately advised of the problem. The operator's minimum equipment list for the airplane required that the problem be repaired within 10 days, but the operator improperly deferred maintenance on it for 60 days and allowed the unairworthy airplane to be flown by the accident flight crew. The airplane was not equipped with, nor was it required to be equipped with, a ground proximity warning system, which would have sounded 40 seconds before impact.

Probable cause

The flight crew's continued descent of the airplane below the glideslope and through the published decision height without visual contact with the runway environment. Also, when the captain encountered difficulty tracking the localizer course, his improper decision to continue the approach by transferring control to the first officer instead of executing a missed approach contributed to the cause. In addition, the following were factors to the accident: (1) American Corporate Aviation's failure to provide an airworthy airplane to the flight crew following maintenance, resulting in a false glideslope indication to the first officer; (2) the flight crew's failure to follow company crew coordination procedures, which called for approach briefings and altitude callouts; and (3) the lack of an FAA requirement for a ground proximity warning system on the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW98MA096
Event ID
20001211X09446
Case number
FTW98MA096
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. 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: 7731bf208e1ebff43d15778dc2e2602972fce62d70d3c833ab94c8c4797d4017; retrieved 2026-09-20T22:42:17.623Z.