NTSB investigations: Continental GO-300 series, UT
9 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
| 1965 | 1 |
|---|---|
| 1977 | 1 |
| 1984 | 1 |
| 2000 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2010 | 1 |
| 2013 | 1 |
| 2023 | 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\" = 'UT' 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" = 'UT' 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 WPR23LA204Accident · No injuriesClass 4 · LimitedFinal reportCessna 175A · Enterprise, UTThe pilot’s inability to maintain altitude during an initial climbout in mountainous terrain after encountering a suspected downdraft.NTSB WPR13LA108Accident · No injuriesLimited investigationFinal reportCessna 175B · Wellsville, UTA loss of engine power during cruise flight due to carburetor ice.NTSB WPR10CA320Accident · No injuriesData collectionFinal reportCessna 175 · Huntsville, UTThe pilot's failure to maintain adequate clearance from terrain during climb.NTSB DEN03LA088Accident · Minor injuriesLimited investigationFinal reportCessna 175B · Cedar City, UTthe pilot's inadvertently switching the fuel selector to the right tank, resulting in fuel starvation, and his failure to maintain direction control during the forced landing. Contributing factors were the crosswind and the tree.NTSB DEN02LA055Accident · Minor injuriesLimited investigationFinal reportCessna 175 · Salt Lake City, UTtotal mechanical loss of engine power for reasons undetermined. Contributing factors were the lack of an annual inspection and the (forced landing in) salt water.NTSB DEN01FA013Accident · 1 fatalField investigationFinal reportCessna 175 · Hanksville, UTthe pilot's failure to maintain control of the airplane while maneuvering at low altitude, and his physical impairment due to alcohol and drugs. A contributing factor was the downdraft.NTSB DEN84LA112Accident · No injuriesLimited investigationFinal reportCessna 175 · Ogden, UTAfter takeoff, the eng began to smoke & lose power. During a forced landing in a muddy plowed field, the acft nosed over. A compression check was accomplished & the #5 cylinder was found to have zero compression. The cylinder was removed & found to be cracked…NTSB DEN77FTM30Accident · No injuriesClosedCessna 175 · Hite, UTNTSB DEN66F0048Accident · No injuriesClosedCessna 175 · Salt Lake City, UT