FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN04IA059 · Beech 1900D

9 Apr 2004 · Denver, CO, United States

Great Lakes Aviation Beech 1900D · Incident: airframe, component or system failure en route

From Pueblo Memorial Airport (PUB) to Denver International Airport (DEN)

Report a problem

Event

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

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
N210GL
Onboard fatalities
Unknown
Route
From Pueblo Memorial Airport (PUB), Pueblo, COTo Denver International Airport (DEN), Denver, CO
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
En route · cruise
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
None

Cause areas

  • Anti-ice/deice system, windshield › Arcing

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The captain reported that he had placed the windshield heat to the "normal" position and then called for the climb checklist. The captain said they were operating in and out of IMC conditions. As they were leveling off at 11,000 feet mean sea level (msl), the captain said, " ... we experienced a popping sound as the result of the first officer's windshield beginning to crack. There were 4 or 5 cracks that started from the bottom left hand corner of the windshield and reached the halfway point of the windshield. At that time and almost instantly we heard another pop and those same cracks continued up the entire length of the windshield." The captain said that after the window had cracked completely, he heard the first officer say, "it's burning." The captain said he asked him what was burning and he replied, "the windshield." The captain said he turned off the heat on his side of the windshield and removed his approach plates from the glare shield. He said he looked over to see what was going on, but did not see any smoke or fire. The captain said he called for the "cracked or shattered windshield checklist." They completed the checklist and landed the airplane uneventfully. The first officer said he noticed a constant spark at the bottom left corner of his windshield and brought it to the captain's attention. The first officer said they turned off the windshield anti-ice switch for his side and the spark stopped. "A few seconds later, my side of the windshield cracked in different places." An examination of the windshield showed six cracks in the outer pane originating at a location 6 inches inboard of the center post along the anti-ice terminal strip. Further examination of the windshield showed that the glass exhibited thermal damage and sooting between the glass layers at the origination point of the cracks, along the lower edge of the heating element. An examination of the hub seal, around the outer edge of the glass and aluminum frame showed evidence of deterioration. There was evidence of water intrusion between the glass plies. The intrusion damage extended along much of the lower edge of the windshield. The windshield heating element was corroded in the areas where water intrusion was observed. The airplane maintenance manual states that the primary cause of moisture ingress is a deteriorated seal. Moisture ingress eventually leads to one or all of the following: delamination between the glass and interlayer, corrosion of the buss bar-heating wire junctions, failure of the electric heating system, and fracture of the outer glass ply. Inspection of the seal is called for during each of six 200-hour Detail Inspections.

Probable cause

arcing of the windshield deicing system. Factors contributing to the incident were the improper inspection of the windshield's exterior seal, deterioration of the windshield seal, and water penetration through the deteriorated seal.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN04IA059
Event ID
20040413X00453
Case number
DEN04IA059
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, coordinates, 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: 142268f27530881a552633f38684f97722e91bd87f69859cb7eedeb0416f2e78; retrieved 2026-09-22T07:45:46.624Z.