NTSB investigations, IN
14 cases where the sequence of events included Sys/Comp malf/fail (non-power).
Cases per year
| 2008 | 2 |
|---|---|
| 2009 | 1 |
| 2011 | 2 |
| 2013 | 1 |
| 2015 | 1 |
| 2017 | 1 |
| 2018 | 1 |
| 2020 | 1 |
| 2022 | 1 |
| 2024 | 1 |
| 2025 | 2 |
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.\"eventStateOrRegion\" = 'IN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.\"tier2Number\" = '330' 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 c."eventStateOrRegion" = 'IN' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT s.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s."tier2Number" = '330' 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 CEN25LA392Accident · No injuriesClass 4 · LimitedFinal reportDiamond DA20-C1 · Terre Haute, INThe failure of the nose landing gear strut and associated nosewheel separation during takeoff.NTSB CEN25LA382Accident · No injuriesClass 4 · LimitedFinal reportBeech C23 · South Bend, INThe pilot’s failure to maintain control of the airplane during a go around which resulted in an aerodynamic stall. Contributing to the accident was the loss of directional control during the landing roll.NTSB CEN25LA013Accident · Minor injuriesClass 3 · LimitedFinal reportRotorway Exec · Plymouth, INA loss of control due to the failed forward tail rotor belt as a result of the owner’s failure to follow the helicopter manufacturer’s tail rotor belt replacement recommendations.NTSB CEN22LA186Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32R · Loogootee, INThe inadequate maintenance and subsequent failure of an internal component in the fuel servo that prevented adequate fuel flow to the engine, which resulted in a partial loss of engine power.NTSB CEN20CA416Accident · No injuriesClass 4 · Data collectionFinal reportCessna 172RG · Lafayette, INThe separation failure of a landing gear system hydraulic line and its compression fitting during cruise flight, which resulted in a partial gear up landing.NTSB CEN18FA107Accident · 3 fatalField investigationFinal reportCessna 441 · Rossville, INAn in-flight loss of control for reasons that could not be determined based on the available evidence.NTSB CEN17LA365Accident · No injuriesLimited investigationFinal reportGaddis Michael Exec 162 F · Plymouth, INA failure of the drive belt for reasons that could not be determined based on the available information.NTSB CEN16LA047Accident · No injuriesLimited investigationFinal reportEurocopter EC120B · Goshen, INThe failure of the Thomas coupling at the interface with the main gear box tail rotor output shaft, which resulted in the helicopter's loss of tail rotor control.NTSB CEN13LA231Accident · No injuriesLimited investigationFinal reportNeedham Stoddard-Hamilton TD · Bloomington, INThe improper installation of a rudder control cable connector and its subsequent separation from the bellcrank, which resulted in the loss of directional control during takeoff.NTSB CEN11LA315Accident · No injuriesLimited investigationFinal reportHughes 269B · Edgerton, INA loss of clearance between the tail rotor drive shaft and the tailboom bulkhead for undetermined reasons, which resulted in the overstress failure of the drive shaft.NTSB CEN11IA180Incident · No injuriesIncident investigationFinal reportHawker Beechcraft C90 · Evansville, INThe peel chip-type failure of the co-pilot's window during initial climb.NTSB CEN09CA232Accident · No injuriesData collectionFinal reportCessna 150D · Madison, INThe loss of engine power due to the failure of the engine's muffler which melted and grounded the ignition P-lead wire.NTSB CHI08FA269Accident · 3 fatalField investigationFinal reportBell 206L-1 · Greensburg, INThe in-flight separation of a main rotor blade due to a fatigue failure of the blade spar, rendering the helicopter uncontrollable, and the manufacturer's production of main rotor blades with latent manufacturing defects, which precipitated the fatigue…NTSB CHI08CA117Accident · No injuriesData collectionFinal reportCessna 182D · Madison, INThe inadequate preflight inspection of the landing gear tires by the pilot, which did not identify a worn tire and resulted in a flat tire during landing touchdown. An additional cause was the directional control not possible during the landing rollout, and…