NTSB investigations, 2016
7 cases where NTSB found Powerplant parameters.
Cases per year
| 2008 | 1 |
|---|---|
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 2 |
| 2012 | 1 |
| 2013 | 5 |
| 2014 | 6 |
| 2015 | 2 |
| 2016 | 7 |
| 2017 | 4 |
| 2018 | 1 |
| 2019 | 3 |
| 2020 | 4 |
| 2021 | 2 |
| 2022 | 5 |
| 2023 | 11 |
| 2024 | 13 |
| 2025 | 5 |
| 2026 | 2 |
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\") = 2016
AND c.\"mKey\" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f.\"findingCode\", '01062050'))
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") = 2016 AND c."mKey" IN (SELECT f.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE starts_with(f."findingCode", '01062050')) 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 ERA17LA042Accident · 1 fatalLimited investigationFinal reportNorth American Navion · Blairstown, NJThe pilot's improper engine start procedure, which resulted in a loss of control on the ground and collision with a tree.NTSB CEN16CA317Accident · No injuriesData collectionFinal reportErcoupe 415 · Eminence, INThe pilot's failure to maintain a proper glide path during the landing approach and his failure to use available engine power to arrest the descent, resulting in an undershoot and collision with terrain.NTSB CEN16LA270Accident · Serious injuriesLimited investigationFinal reportCessna 182J · Weatherford, TXAn electrical system malfunction for reasons that could not be determined, and the subsequent loss of engine power due to the loss of the electrical boost pumps. Also causal was the pilot's improper emergency action following the loss of engine power due to…NTSB CEN16LA213Accident · Minor injuriesLimited investigationFinal reportBell 47G 5 · Laureles, TXThe pilot's failure to apply additional engine power when he applied collective input, which led to a loss of rotor speed and the exceedance of the helicopter’s performance capability.NTSB GAA16CA278Accident · No injuriesData collectionFinal reportPiper PA24 · Wadsworth, OHThe pilot's inadvertent power reduction during landing, which resulted in a runway undershoot, collision with the runway threshold, nose and right main landing gear collapse, and runway excursion.NTSB WPR16FA095Accident · 1 fatalField investigationFinal reportMooney M20K · Woodland, WAThe pilot's delay in recognizing that the airplane was not performing as expected and aborting the takeoff, which resulted in collision with a berm beyond the end of the runway. Contributing to the accident were the pilot's exceedance of the airplane's gross…NTSB GAA16CA143Accident · Minor injuriesData collectionFinal reportBell 47 · Agua Dulce, CAThe pilot's failure to set the appropriate collective friction prior to releasing the collective in flight, which resulted in decreased main rotor pitch, settling with power, and an impact with terrain.