The U.S. aircraft register, updated daily
Accidents · NTSB ENG11IA021 · Final report

Bombardier INC DHC 8 402 incident near Pittsburgh, Pennsylvania, March 17, 2011

On March 17, 2011 at about 4:40 pm local time, a 2010 Bombardier INC DHC 8 402, registered N339NG, suffered minor damage in an incident during enroute (cruise) near Pittsburgh, Pennsylvania. It was flown under scheduled airline rules (Part 121). No one was hurt; 40 people were on board or involved. The weather was conditions the NTSB did not record.

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 17, 2011 · about 4:40 pm local time · cases in 2011
Place
Pittsburgh, Pennsylvania · map
Type
Incident
Injuries
No one was hurt; 40 people were on board or involved.
Weather
conditions the NTSB did not record
Aircraft
Bombardier INC DHC 8 402 402, built 2010
Registration
N339NG · not in the FAA's current or past register files · serial 4339
Damage
Minor damage
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Powerplant sys/comp malf/fail during enroute (cruise) defining event
  2. Fire/smoke (non-impact) during enroute (cruise)
  3. Loss of engine power (total) during enroute (cruise)
  4. Engine shutdown during enroute (cruise)
  5. Sys/Comp malf/fail (non-power) during enroute (cruise)

The NTSB's findings

The aircraft

  • Maximum gross weight: 64,501 lb
  • Landing gear: fixed
  • Engine 1: P&W Canada PW150A (turboprop); 0 hours total
  • Engine 2: P&W Canada PW150A (turboprop); 0 hours total
  • Operator: Colgan Air, Inc.

The flight

  • Departed from: CLE Cleveland OH
  • Destination: BMI Baltimore MD
  • Flight plan: VFR then IFR
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Cabi2
Flight crew2
Passengers36

Documents from the investigation the NTSB's docket: the evidence folder behind the report

5 documents, released by the NTSB on May 28, 2015. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ENG11IA021.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.