NTSB investigations, 2016
8 cases where the sequence of events included Evacuation.
Cases per year
| 2009 | 3 |
|---|---|
| 2010 | 1 |
| 2011 | 4 |
| 2012 | 3 |
| 2013 | 2 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 8 |
| 2017 | 1 |
| 2018 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 4 |
| 2023 | 12 |
| 2024 | 18 |
| 2025 | 23 |
| 2026 | 14 |
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 year(c.\"eventDate\") = 2016
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '460' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\"))
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 s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '460' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")) 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 GAA17CA087Accident · No injuriesData collectionFinal reportJack Fehling Celebrity · North Hampton, NHThe pilot’s unstabilized approach, which resulted in the biplane being low and striking trees.NTSB DCA17FA021Accident · Serious injuriesClass 1 · FieldFinal reportBoeing 767 · Chicago, ILThe failure of the high-pressure turbine (HPT) stage 2 disk, which severed the main engine fuel feed line and breached the right main wing fuel tank, releasing fuel that resulted in a fire on the right side of the airplane during the takeoff roll. The HPT…NTSB DCA16CA226Accident · No injuriesData collectionFinal reportBombardier DHC 8 202 · Dulles, VAincorrect installation of the frangible towing fuse that prevented the nose landing gear from extending.NTSB GAA16CA406Accident · No injuriesData collectionFinal reportCessna 177 · Kalispell, MTThe airplane's hard landing during an aborted takeoff, following an encounter with a downdraft during takeoff initial climb from a remote mountain airstrip, resulting in an uncontrolled descent, attempt to land on the runway remaining, and subsequent nose…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 GAA16CA395Accident · No injuriesData collectionFinal reportEngineering & Research 415 · Collinsville, OKThe pilot's failure to maintain directional control during takeoff in a high density altitude condition, which resulted in a runway excursion and impact with a tree.NTSB GAA16CA358Accident · No injuriesData collectionFinal reportCessna 172 · Bountiful, UTThe pilot's decision to fly into a canyon without sufficient room to reverse course if necessary, which resulted in an emergency landing, loss of directional control, collision with terrain, and a post-crash fire.NTSB DCA16WA097Accident · Serious injuriesForeign investigationBoeing 737 · Chitose, JapanThe government of Japan has notified the NTSB of an incident involving a Boeing 737 airplane that occurred on February 23, 2016. The NTSB has appointed a U.S. Accredited Representative to assist the government of Japan's investigation under the provisions of…