NTSB investigations: GE CF34 series
5 cases on aircraft whose registry engine model is GE CF34 series, where the defining event was Fire/smoke (non-impact). Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 2009 | 1 |
|---|---|
| 2011 | 2 |
| 2019 | 1 |
| 2021 | 1 |
Where
Latest cases
Query with SQL
duckdb -csv -c "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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30015')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '150'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30015')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e."isDefiningEvent" AND e."tier2Number" = '150'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ENG21LA023IncidentClass 3 · LimitedFinal reportBombardier CL-600-2C10 · North Canton, OHMoisture ingression thru the window humpseal coming into contact with the terminal block braid wires.NTSB GAA20WA123Incident · No injuriesForeign investigationBombardier CL600 2B19 · Madrid, SpainThe government of Spain has notified the NTSB of an accident involving a BOMBARDIER CL600 2B19 airplane that occurred on November 10, 2019. The NTSB has appointed a U.S. Accredited Representative to assist the government of Spain's investigation under the…NTSB ENG12IA004Incident · No injuriesIncident investigationFinal reportBombardier CL600 2C10 · Atlanta, GAThe 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…NTSB DCA11FA072Accident · No injuriesField investigationFinal reportBombardier CL600 2B19 · Phoenix, AZinadequate 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 DCA09FA033Accident · No injuriesField investigationFinal reportBombardier CRJ · Tallahassee, FLAn electrical anomaly in the top portion of the JB-1 junction box resulting in ignition of adjacent combustible materials, including insulation blankets, and a flexible oxygen line.