Final NTSB investigations: GE CF34-3B1
4 cases on aircraft whose registry engine model is GE CF34-3B1. 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
| 2005 | 1 |
|---|---|
| 2006 | 1 |
| 2008 | 1 |
| 2017 | 1 |
Where
Open the mapLatest 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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30070'))
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."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30070'))
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 ENG17IA008Incident · No injuriesIncident investigationFinal reportBombardier CL 600 2B19 · Baltimore, MDA Bombardier CRJ200 No. 2 engine failure due to the separation of a fan blade airfoil at a low cycle fatigue crack that originated at the forward fan blade pin hole attachment. The separated fan blade had previously undergone a hot form repair and both…NTSB DCA09FA011Accident · Minor injuriesField investigationFinal reportBombardier CL-600-2B19 · Detroit, MIThe lack of vigilance on the part of the ramp agent driving the baggage tug. Contributing factors include the night conditions, and low visibility due to fog and rain.NTSB ATL06IA054Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B19 · Asheville, NCThe improper installation of the pilot's windshield by company maintenance personnel, which resulted in flame and smoke in the cockpit, and subsequent emergency landing.NTSB CHI05FA077Accident · No injuriesField investigationFinal reportBombardier CL-600-2B19 · Milwaukee, WIthe captain's failure to adequately compensate for the crosswind conditions, and his failure to maintain directional control during landing. Contributing factors include the captain's failure to land at the nearest suitable airport after an in-flight…