FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Atlantic Southeast Airlines Bombardier CL600 2C10 701 incident

23 Oct 2011 · Atlanta, GA, United States

Bombardier CL600 2C10 701 · Incident: fire/smoke (non-impact) during landing

Report a problem

Event

NTSB case
ENG12IA004
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
Not recorded

Bombardier CL600 2C10 701

Aircraft type
Bombardier CL600
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
N751EV
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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
Landing · landing roll
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
None

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

An Atlantic Southeast Airways (ASA) Bombardier Canadair Regional Jet (CRJ)-700 experienced an undercowl engine fire after landing at Hartsfield-Jackson Atlanta International Airport (ATL), Atlanta, Georgia. The pilot shut down the affected engine and the fire warning quickly ceased. No fire bottles were discharged. The airplane taxied to the gate and the passengers deplaned normally. The airplane was undamaged and no injuries were reported. The incident flight was a 14 CFR Part 121 regularly scheduled passenger flight from a Des Moines Airport, Iowa, to ATL.

Examination of the engine revealed that the Start Operability Bleed Valve (OBV) fuel return adapter-fitting had fractured and the electrical harness in the vicinity of the OBV was sooted and thermally damaged. No cowling damage was noted. Metallurgical examination of the fractured fuel return adapter-fitting revealed that it had failed in fatigue due to cyclic loading. The return adapter-fitting tube end ball-nose area had a dent. Material deposits were found outboard of the sealing area and axial scrape marks were found beneath and adjacent to the deposited material. The valve flow body flange of the OBV also exhibited a dent and material deposit. An analysis of the deposited material revealed elemental peaks of silicon and oxygen, elements present in sand and not in the return adapter-fitting alloy composition. The presence of silicone and the dent is consistent with the OBV most likely having been dropped and impacted a hard surface that damaged the fuel return adapter-fitting before it was reinstalled on the engine. The impact damage to the return adapter-fitting reduced its loading-carrying and fatigue capability. The OBV fuel return adapter-fitting eventually fractured and separated, which allowed fuel to spill onto a hot engine case that ignited the undercowl fire.

Although not related to the incident, testing and analytical modeling of the OBV adapter-fitting joint revealed that, as designed, the joint is directly affected by variations in the applied preload caused by differences in installation torque, coefficient of friction, application of a primer on the serrations, and use of the combination installation tool and that static applied loads were sufficient to create loose contact between the adapter-fitting and the OBV piston housing threads. Vibratory loads during normal engine operation can create relative motion between the adapter-fitting and the piston housing threads generating a wear mechanism that can eventually lead to a fatigue separation of the piston housing threads and the pull-out of the adapter-fitting and subsequent fuel leaks that could lead to a fire. To address this design deficiency, service bulletins were issued to replace the affected OBV with an OBV from alternate manufacturer, and the removal schedule was based on the amount of flight time each OBV had accumulated. The FAA issued an Airworthiness Directive mandating the service bulletins.

Probable cause

The Start Operability Bleed Valve (OBV) fuel return adapter-fitting fractured and separated in cyclic fatigue, which allowed fuel to spill onto a hot engine case that ignited the undercowl fire. The OBV fuel adapter-fitting was dropped and the damage reduced its load carrying and fatigue capability, eventually leading to its failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG12IA004
Event ID
20111027X01810
Case number
ENG12IA004
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, damage. 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: 194233b5f16e1c1672228d3d9c4d201239b785aa513b6729b2adf557bfbb6422; retrieved 2026-09-15T16:53:23.043Z.