# NTSB investigations: GE CF34 series, AZ

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB DCA15CA118](https://openairdocs.org/ntsb/DCA15CA118.md): Bombardier CL600 2D24 · Phoenix, AZ · Accident · No injuries · Data collection · Final report · May 4, 2015 · N932LR · Substantial damage
  > the CRJ900 captain's misjudgment of the clearance between their horizontal stabilizer and the B757 winglet.
- [NTSB DCA11FA072](https://openairdocs.org/ntsb/DCA11FA072.md): Bombardier CL600 2B19 · Phoenix, AZ · Accident · No injuries · Field investigation · Final report · Apr 2, 2011 · N7264V · Substantial damage
  > 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.
- [NTSB WPR11IA019](https://openairdocs.org/ntsb/WPR11IA019.md): Bombardier CL-600-2B19 · Phoenix, AZ · Incident · No injuries · Incident investigation · Final report · Oct 18, 2010 · N938SW · Minor damage
  > The overextension of the main cabin door due to difficulty opening the door because the power-assist motor cable was lodged within the main cabin door assembly.
- [NTSB LAX07IA191](https://openairdocs.org/ntsb/LAX07IA191.md): Bombardier CL-600-2B19 · Phoenix, AZ · Incident · No injuries · Incident investigation · Final report · Jun 13, 2007 · N7264V · No damage
  > An out of rig/jammed door. Contributing to the incident was the operator's inadequate maintenance program and the airframe manufacturer's inadequate response to the issue.
- [NTSB LAX03IA199](https://openairdocs.org/ntsb/LAX03IA199.md): Bombardier CL-600-2B19 · Phoenix, AZ · Incident · No injuries · Incident investigation · Final report · Jun 14, 2003 · N97325 · No damage
  > the simultaneous failure of both horizontal stabilizer trim channels on two separate occasions for undetermined reasons.

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."eventStateOrRegion" = 'AZ' AND c."eventCountry" = 'USA'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30015'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?engine=30015&state=AZ

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.