FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Great Lakes Aviation Beech 1900D accident

19 Aug 1998 · Denver, CO, United States

Beech 1900D · Accident: airframe, component or system failure during initial climb

From Denver International Airport (DEN) to Southwest Wyoming Regional Airport (RKS)

Report a problem

Event

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

Beech 1900D

Aircraft type
Beechcraft 1900
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
N251GL
Onboard fatalities
Unknown
Route
From Denver International Airport (DEN)To Southwest Wyoming Regional Airport (RKS), Rock Springs, WY
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
Initial climb
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
Substantial

Cause areas

  • Other maintenance personnel › Maintenance, major repair, improper
  • Propeller system/accessories, leading edge cap › Debonded

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

NTSB narrative

Shortly after the airplane took off, the crew heard a loud noise and felt a slight vibration from the left propeller. They returned and landed. It was discovered that the propeller erosion shield had debonded and a portion had penetrated the passenger cabin just aft of the airstair door, knocked ajar Seat 1A Passenger Service Unit, ricocheted off the ceiling, and penetrated the inner window pane at Seat 2C. Laboratory examination of the propeller blade revealed an area 'consistent with adhesive disbonding (debond) on about 80% of the total bond area...' Three hundred hours before the accident, the blade had been overhauled and repaired. The repaired area contained numerous voids, air bubbles, dirt and debris. Evidence of chaffing (rubbing) was found at several locations in the debonded area, indicative of movement between the debonded erosion shield and the propeller blade body. Samples of the erosion shield adhesive were tested and found to have been mixed in improper proportions, reducing bond strength.

Probable cause

Debonding of the propeller erosion shield due to an improper overhaul and repair by other maintenance personnel.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record FTW98FA364
Event ID
20001211X10832
Case number
FTW98FA364
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: 881be4b430dee4a07f01439405ec19c00e1d477e308b65da8e71f4d2bd0a77e6; retrieved 2026-09-18T17:05:43.226Z.