FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Horizon Air Bombardier DHC-8-402 incident

5 Mar 2013 · Danville, CA, United States

Bombardier DHC-8-402 · Incident: fire/smoke (non-impact) en route

From Mineta San Jose International Airport (SJC) to Boise Air Terminal/Gowen Field (BOI)

Report a problem

Event

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

Bombardier 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
N417QX
Operator
Horizon Air
Onboard fatalities
Unknown
Route
From Mineta San Jose International Airport (SJC), San Jose, CATo Boise Air Terminal/Gowen Field (BOI), Boise, ID
Aircraft age
About 9 years (built 2004)
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
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
Fire/smoke (non-impact)
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

  • Aircraft › Aircraft power plant

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

NTSB narrative

The flight was climbing through flight level 200 when the flight crew received a No. 2 engine audible fire warning, which was accompanied by a bang sound. The crew subsequently shut the No. 2 engine down and discharged both of the engine's fire extinguishing bottles. The cabin crew reported no visible fire, but the flight crew continued to receive a fire indication. The captain then declared an emergency, began a descent to the departure airport, and landed about 9 minutes after the event. After the airplane was stopped on the runway and the No. 1 (left) engine was shut down, an emergency evacuation was conducted using the main cabin door. An initial assessment by company personnel indicated that the fire damage to the airplane was limited to what was visible on the aircraft's exterior.

A visual postincident examination of the engine revealed that sooting was present on external case surfaces, which were concentrated on the aft half of the No. 2 engine. A disassembly of the engine confirmed that about half of the SED outer dome within the combustion section had separated and was subsequently ingested into the gas path. To determine the reason for the separation, three locations on the outer dome were sectioned and examined. All three locations exhibited insufficient weld penetration so that the welds remained totally contained within the SED outer dome and did not penetrate through to the inner duct as required by the manufacturing specifications.

Probable cause

The failure and separation of a section of the No. 2 engine's combustion chamber's small exit duct (SED), which created an airflow disruption that led to an engine surge and subsequent fire. Contributing to the accident was the insufficient weld penetration that remained totally contained within the SED outer dome and did not penetrate through to the inner duct as required by the manufacturing specifications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR13IA144
Event ID
20130312X23544
Case number
WPR13IA144
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, coordinates. 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: 4fd74c2212ac39807b790d1861efd8284b8595c9557c87f81124fcac7801c097; retrieved 2026-09-15T21:04:00.090Z.