FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Wisconsin British Aerospace BAE 146-200A BAE 146-20 incident

11 Feb 1999 · Aspen, CO, United States

British Aerospace BAE 146-200A BAE 146-20 · Incident: total loss of engine power (mechanical failure) en route

From Aspen-Pitkin County Airport (Sardy Field) (ASE) to Denver International Airport (DEN)

Report a problem

Event

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

British Aerospace BAE 146-200A BAE 146-20

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
N608AW
Onboard fatalities
Unknown
Route
From Aspen-Pitkin County Airport (Sardy Field) (ASE)To 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 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
En route · climb to 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
Total loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Manufacturer › Maintenance, overhaul, inadequate

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

NTSB narrative

The airplane experienced an uncontained number 4 engine failure during climb to cruise altitude. Examination of the engine revealed that the number 4 turbine disc had all its blades separated just above the blade platform except 1, which separated just below the blade platform. According to maintenance records, the number 4 turbine disc assembly was installed 22.5 hours or 22 cycles prior to this event. The manufacturer of the turbine disc said that the wheel was new; however, all 60 of the blades had seen previous use. A high-cycle fatigue crack was found in the one blade which had separated below the blade platform. The metallurgist noted that the fatigue crack originated from a fretting damage mark located at the fir-tree portion. The manufacturer reported that 9 blade retention pins, which were used to prevent blade radial movement, did not meet the requirement of no more than 0.005 inch clearance between pen head and wheel. They further reported that blade stress concentration was induced by the wheel broach slots sharp edges.

Probable cause

The inadequate maintenance overhaul of the number four turbine disc by the manufacturer. A factor was the turbine blade's failure due to high cycle fatigue fracture.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN99IA038
Event ID
20001205X00147
Case number
DEN99IA038
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-02-12.
  • API snapshot SHA-256: 3f22a5fa03864e9f5f7b06a7d671d90e6f61cdcc70862d0706312884e5489a5a; retrieved 2026-09-18T16:59:28.233Z.
  • The NTSB's operator name is blank for N608AW; the operator shown is the name the NTSB records it doing business as.