NTSB investigations: Continental GO-300 series, MT
8 cases on aircraft whose registry engine model is Continental GO-300 series. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 1969 | 3 |
|---|---|
| 1981 | 1 |
| 1988 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2016 | 1 |
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 c.\"eventStateOrRegion\" = 'MT' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17024'))
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" = 'MT' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17024'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun 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 GAA16CA097Accident · No injuriesData collectionFinal reportCessna 175 · Seeley Lake, MTThe pilot' failure to identify the plowed runway width in dusk and flat light conditions, which resulted in a touchdown left of the runway center, an impact with a snow berm, and a ground loop.NTSB SEA02FA009Accident · 1 fatalField investigationFinal reportCessna 175C · Miles City, MTThe separation of the number four cylinder exhaust valve guide from the cylinder head, leading to the failure of the exhaust valve stem and the catastrophic failure of the engine while in cruise flight. Factors include the necessity of attempting a forced…NTSB SEA98LA166Accident · No injuriesLimited investigationFinal reportCessna 175 · Missoula, MTA complete loss of crankcase oil due to a missing oil filler tube followed by the failure of a connecting rod. Factors include encountering a small pine tree during the landing roll.NTSB DEN89LA021Accident · Serious injuriesLimited investigationFinal reportCessna 175 · Fort Peck, MTThe plt enctrd hvy snow at night & turned back to find a nearby landing strip that he was familiar with. He recognized a ranch house associated with the strip, but was unable to find the landing area. He began to circle in hopes that someone would turn on the…NTSB DEN81DTI04Accident · Minor injuriesClosedCessna 175 · Belgrade, MTNTSB SEA70D0141Accident · No injuriesClosedCessna 175 · Ryegate, MTNTSB DEN70A0024Accident · 1 fatalClosedCessna 175 · Eureka, MTNTSB SEA69A0049Accident · 3 fatalClosedCessna 175 · Four Buttes, MT