SkyWest Airlines Bombardier Inc CL 600 2C10 700C accident
Bombardier Inc CL 600 2C10 700C · Accident: fire/smoke (non-impact) while taxiing
From Aspen-Pitkin County Airport (Sardy Field) (KASE) to Denver International Airport (KDEN)
Event
- NTSB case
- DCA17LA182
- 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
- Accident
- 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 CL 600 2C10 700C
- Aircraft type
- Bombardier CL-600
- 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
- N796SK
- Operator
- SkyWest Airlines
- Onboard fatalities
- Unknown
- Route
- From Aspen-Pitkin County Airport (Sardy Field) (KASE), Aspen, COTo Denver International Airport (KDEN), Denver, CO
- Aircraft age
- About 7 years (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
- Taxi · from runway
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After the scheduled air carrier flight touched down on the runway, a left engine undercowl fire occurred. The fire occurred after leaked fuel accumulating inside the engine core compartment (a fire zone) ignited from contact with a hot engine surface. The fuel accumulated inside the core compartment because the nacelle drainage system was overwhelmed by the release of about 34 gallons of fuel during the landing roll, at which time the high rates of ventilation through the nacelle were reduced. The leak occurred during landing when the removal of fuel leakage depends in part on gravity drainage. A nacelle drainage capability assessment found that the core compartment contained about 20 gallons of fuel at the time of ignition. After engine shutdown, fuel draining from the core compartment was no longer carried overboard by the fan exhaust, and the fuel pooled in the fan duct. Some of this fuel drained to the ground through the transcowl drain holes. The fire became uncontrolled when it escaped the fire zone and spread to areas where expelled/drained fuel had accumulated in the nacelle and on the ground. The draining fuel led to a fire on the ground and on the underside of the left pylon. The fire was extinguished by airport rescue and firefighting personnel. On-site investigation found that a rosan -05 to -06 expander fitting had pulled out from the fuel supply port of the operability bleed valve (OBV), which is part of the left engine’s environmental control system (ECS). Also, two ECS support links (which attach and support the ECS hardware, including the OBV, to the engine) were found severely worn. Metallurgical examination of the OBV upper housing fuel supply port found evidence of advanced thread wear and fatigue damage, consistent with side-to-side fitting cyclic movement and insufficient remaining threads to prevent the fitting in the upper housing from pulling out. Modal testing demonstrated that ECS link wear can shift the OBV natural operating frequency into the engine operating frequency range, significantly increasing the fuel tube loads into the fitting. OBV design evaluation testing found that fitting joint preload loss permits relative motion to occur between the fitting and upper housing port threads, initiating upper housing thread wear and leading to upper housing thread failure and fitting pullout. The rosan -05 to 06 expander fitting with the cast aluminum housing lacked the design margin to maintain sufficient preload against engine vibration loads and fitting pullout. A review of CF34-8 maintenance engineering sheets and field maintenance documents found that rod end alignment instructions critical to preventing ECS support link wear were not provided in the base engine assembly drawing and that the ECS support links were not part of any scheduled airplane- or engine-level maintenance. As a result, maintenance personnel did not inspect for wear caused by poor rod end alignment. Worn or misaligned ECS support links increase fuel tube fitting loads and can result in fitting pullouts.
Probable cause
The fuel supply tube fitting pulling out of the left engine’s operability bleed valve (OBV) during the landing rollout, allowing fuel to leak and contact hot engine cases, which ignited a fire that caused thermal damage to the engine pylon. Contributing to the fitting pullout from the OBV was an undetected progressive environmental control system (ECS) support link wear condition that allowed excessive OBV movement relative to the engine, and the lack of alignment instructions in the base engine assembly drawing and the lack of maintenance tasks to assess the operational condition of the ECS links.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DCA17LA182
- Event ID
- 20170712X12448
- Case number
- DCA17LA182
- 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, cause areas. 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: 4859b80da94796ff1f9bba7a6211f7a53f235a38096921a115d7d127ba88a13a; retrieved 2026-09-16T05:32:04.917Z.