NTSB investigations, MI
7 cases where the first occurrence was “Gear collapsed”.
Cases per year
| 1989 | 2 |
|---|---|
| 1997 | 1 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 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.\"eventStateOrRegion\" = 'MI' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 190)
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" = 'MI' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 190) 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 CHI03LA177Accident · No injuriesLimited investigationFinal reportWaco ARE · Battle Creek, MIThe inadequate material used in the landing gear cross supports leading to its collapse during the landing roll.NTSB CHI02LA144Accident · No injuriesLimited investigationFinal reportMitsubishi MU2B-20 · Belleville, MIThe pilot's failure to verify the extension of the landing gear prior to landing, and his failure to perform the emergency landing gear extension procedure. The popped circuit breaker was a factor.NTSB CHI02LA127Accident · No injuriesLimited investigationFinal reportCessna 310L · Detroit, MIThe total failure of the electrical system, the landing gear indicating system not operating, and the unsuccessful emergency landing gear extension.NTSB CHI01LA279Accident · No injuriesLimited investigationFinal reportGlobe GC-1B · Traverse City, MIThe pilot not following the emergency landing gear extension procedures. Factors were the failure of the hydraulic motor, and the landing gear locks not engaged.NTSB CHI97LA186Accident · Minor injuriesLimited investigationFinal reportHulliberger Starduster II · Berrien Springs, MIthe failure of the landing gear axle due to fatigue.NTSB CHI89LA080Accident · No injuriesLimited investigationFinal reportCessna 411 · Detroit, MIFailure of a bolt in the left main landing gear assembly.NTSB CHI89LA043Accident · No injuriesLimited investigationFinal reportCessna T303 · Romeo, MIThe failure of the left main landing gear assembly due to stress corrosion.