NTSB investigations
6 cases where NTSB found Fire protection system.
Cases per year
| 2008 | 1 |
|---|---|
| 2010 | 1 |
| 2011 | 1 |
| 2013 | 1 |
| 2016 | 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.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '010226')) 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 f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '010226')) 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 ERA17CA295Accident · No injuriesData collectionFinal reportPiper PA 28-161 · Palatka, FLThe student pilot's overpriming of the engine and the flight instructor's delayed remedial action, which resulted in an engine fire.NTSB ERA16FA269Accident · 1 fatalField investigationFinal reportYakovlev YAK11 · West Mifflin, PAA malfunction of the electrical system, which resulted in an electrical fire in the right wing root of the airplane, which compromised the fuel system and resulted in ignition of fuel. Contributing to the accident was the routing of the electrical wiring near…NTSB WPR13FA294Accident · 1 fatalField investigationFinal reportCessna 172 · Birdseye, UT***This report was modified on August 18, 2015. Please see the docket for this accident to view the original report.*** The operator's improper installation of a supplemental electrical power supply, which caused a short circuit due to inadequate vibration…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…NTSB ENG10IA038Incident · No injuriesIncident investigationFinal reportBoeing 767 · Athens, GreeceA short circuit involving the light in position L3 on the squib test panel. The specific cause of the short circuit could not be determined.NTSB DCA08MA076Accident · No injuriesClass 1 · MajorFinal reportBoeing 767 · San Francisco, CAThe design of the supplemental oxygen system hoses and the lack of positive separation between electrical wiring and electrically conductive oxygen system components. The lack of positive separation allowed a short circuit to breach a combustible oxygen hose,…