FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight 2651 · Bombardier CL600 2B19 200

2 Apr 2011 · Phoenix, AZ, United States

Bombardier CL600 2B19 200 · Accident: fire/smoke (non-impact) on approach

From Des Moines International Airport (DSM) to Phoenix Sky Harbor International Airport (PHX)

Report a problem

Event

NTSB case
DCA11FA072
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
Visual Meteorological Cond

Bombardier CL600 2B19 200

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
N7264V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Des Moines International Airport (DSM), Des Moines, IATo Phoenix Sky Harbor International Airport (PHX), Phoenix, AZ
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
Approach
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 systems

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 crew stated that while on final approach, they noted a right engine 10th stage bleed air indication, a right jet pipe over-heat indication, and a right pack over pressure indication. They also noted, after landing, that there was a burning smell. Postaccident examination of the airplane revealed fire damage to the aft equipment bay in the area of the right pylon directly above the auxiliary power unit (APU) exhaust duct. There was evidence of chaffing on the right integrated drive generator (IDG) power feeder cable as well as damage to an adjacent hydraulic line. Additionally, two support brackets, designed to secure the hydraulic line to the aft fuselage, near the area of the fire had fractured, with one bracket no longer attached to the fuselage. Consistent with the chafing, there was a pin-sized hole near the end of the hydraulic line where it connected to a fitting that was mounted on a bracket attaching the line to the airplane's structure. The pin-sized hole was near the chafed IDG cable strand, and about 0.0625 inches from the hydraulic line, instead of the required minimum distance of 2.0 inches specified in Bombardier wiring installation specifications. NTSB Metallurgical examinations of the IDG power feeder cable revealed that the damage to the insulation around the pin-sized hole was consistent with chafing. The examination also found material splatter consistent with electrical arcing of the conductors. The damaged area of the hydraulic line revealed evidence of splattering and material expulsion consistent with electrical arcing against the hydraulic line's external surface. Additionally, the chaffed wire and hydraulic line were examined using energy dispersive x-ray spectroscopy (EDS) to determine if any material transfer consistent with an electrical arcing event, had occurred and the wire and the hydraulic line both had chemical elements not normally found in each. The bracket had fractured into two pieces, and one of the tabs matched the fracture on the main body of the bracket. There was fretting wear damage on the surface of the tab where it was attached to another surface indicative of the tab possibly having rubbed against a bolt or pin used to mount the bracket, and the fracture surface exhibited dimpled ductile fracture that is indicative of overstress bending. As a result of the findings from this accident, both Transport Canada and the FAA released Airworthiness Directives.

Probable cause

inadequate clearance between the Integrated Drive Generator (IDG) power cables and hydraulic lines in the aft equipment bay that resulted in chaffing of the IDG power cables and hydraulic lines, arcing, and fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA11FA072
Event ID
20110407X95823
Case number
DCA11FA072
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: 7e392c9e7e1575851ba57347f65eadfb04c23bcb203eb981a7538306fd88c438; retrieved 2026-09-15T16:01:35.832Z.