NTSB investigations, 2011
7 cases where NTSB found Compressor section.
Cases per year
| 2008 | 5 |
|---|---|
| 2009 | 3 |
| 2010 | 2 |
| 2011 | 7 |
| 2012 | 1 |
| 2013 | 4 |
| 2014 | 3 |
| 2015 | 2 |
| 2016 | 1 |
| 2017 | 3 |
| 2018 | 1 |
| 2019 | 7 |
| 2020 | 4 |
| 2021 | 5 |
| 2023 | 3 |
| 2024 | 1 |
| 2025 | 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 year(c.\"eventDate\") = 2011
AND c.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '01057230'))
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 year(c."eventDate") = 2011 AND c."mKey" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '01057230')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
Run 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 CEN12IA096Incident · No injuriesIncident investigationFinal reportBell Helicopter Textron Canada 407 · Gulf Of MexicoThe failure of the compressor section No. 2 bearing due to false brinnelling and fatigue.NTSB ENG11IA051Incident · No injuriesIncident investigationFinal reportBoeing 757-222 · Denver, CO**This probable cause was modified on 4/5/2012. Please see the public docket for this accident to view the original probable cause.** The initial damage to the fan blades was caused by the ingestion of a Red-Tailed Hawk that caused one or more fan blades to…NTSB WPR11LA379Accident · No injuriesLimited investigationFinal reportBell 47G-3B-2 · Los Banos, CAThe pilot’s inadequate preflight, and contamination of both the engine compressor section and the main rotor blades, which resulted in reduced performance of the engine and rotor system.NTSB ENG11IA043Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-51 · Atlanta, GAThe probable cause of the No. 2 engine failure and subsequent aborted takeoff was the high cycle fatigue failure of a fan blade near the blade root that resulted in extensive low pressure compressor damage and compressor case breach.NTSB WPR11LA320Accident · No injuriesLimited investigationFinal reportSchweizer G-164B · Yuba City, CAHigh-cycle fatigue on the 1st-stage compressor blade retaining ring, which resulted in the ring’s fracture and a subsequent loss of engine power.NTSB CEN11LA252Accident · Minor injuriesLimited investigationFinal reportBell 206L-3 · (Gulf of Mexico)The loss of engine power due to an engine compressor stall as a result of ingesting methane gas during takeoff.NTSB ENG11IA021Incident · No injuriesIncident investigationFinal reportBombardier DHC 8 402 · Pittsburgh, PAthe flight crew's delay in shutting down the left engine following an engine oil pressure master warning, which led to a hard rub inside the engine that served as an ignition point for a titanium fire. Contributing to the event was a PW150 No. 5 seal design…