Colgan Air Bombardier Inc DHC 8 402 incident
Bombardier Inc DHC 8 402 · Incident: powerplant system/component malfunction/failure en route
From Cleveland Hopkins International Airport (CLE) to BMI · Baltimore, MD
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- ENG11IA021
- 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
- Unknown
Bombardier Inc DHC 8 402
- Aircraft type
- Bombardier DHC-8
- 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
- N339NG
- Operator
- Colgan Air
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Cleveland Hopkins International Airport (CLE), Cleveland, OHTo BMI · Baltimore, MD
- Aircraft age
- About 1 year (built 2010)
- 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 · cruise
- Defining eventThe 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
- Powerplant system/component malfunction/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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
A left engine aft thrust rotor bearing incipient spalling condition progressed to failure during cruise flight. The loss of rotor thrust support caused the rotor to displace aft and contact adjacent stationary structures, including structures in the No. 2 bearing area. The resulting machining-type contact damage generated metal debris that contaminated the engine oil. Metal particles in the oil scavenged from the No. 2/2.5 bearing oil cavity damaged the engine oil pump and arrested its rotation, which caused torsional separation of the oil pump driveshaft, cutting off oil supply to the engine. The left engine oil pressure master warning activated. The flight crew did not shut down the engine. The engine operated 84 seconds without oil flow, until combustor and turbine component fire damage disrupted combustor flame stability and the engine flamed out. The continued operation without oil flow elevated engine operating temperatures, and the No. 5 engine bearing cavity temperature increased beyond the material properties of the No. 5 bearing seal runner. The seal runner expanded radially and caused a hard rub against the (titanium-alloy) No. 5 bearing flexible support. The local temperature at the contact point rapidly reach its ignition temperature. The resulting titanium fire consumed the No. 5 bearing flexible support and progressed to adjacent thin-walled titanium components, including the diffuser diaphragm. Molten titanium droplets falling onto diffuser exit ducts located directly beneath the No. 5 bearing area melted through three of the exit ducts and penetrated the gas generator case. The titanium fire self-extinguished when the conditions required for sustained titanium combustion were altered by the flameout and the case burn-through. The lack of circumferential titanium droplet distribution, the undamaged condition of the diffuser ring bore internal surfaces, and the gravity-driven nature of the case penetration indicate that the titanium fire originated external to the diffuser/engine gas path. The cockpit engine fire warning remained active when no fire was present because one of the nacelle fire/overheat detector elements was unable to reset due to a permanently deformed switch diaphragm.
Probable cause
the flight crew's delay in shutting down the left engine following an engine oil pressure master warning, which led to a hard rub inside the engine that served as an ignition point for a titanium fire. Contributing to the event was a PW150 No. 5 seal design vulnerability to titanium ignition that can occur with continued engine operation following an engine oil pressure loss event.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ENG11IA021
- Event ID
- 20110317X14552
- Case number
- ENG11IA021
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 187ef26bde97cc3bff75cedfda4b99869c5ddff9e77bb7de7ef211b4aaad55ea; retrieved 2026-09-15T15:55:15.222Z.