NTSB investigations: Continental GO-300 series, 1992
3 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
| 1964 | 27 |
|---|---|
| 1965 | 31 |
| 1966 | 26 |
| 1967 | 25 |
| 1968 | 12 |
| 1969 | 17 |
| 1970 | 11 |
| 1971 | 10 |
| 1972 | 8 |
| 1973 | 11 |
| 1974 | 9 |
| 1975 | 11 |
| 1976 | 8 |
| 1977 | 9 |
| 1978 | 9 |
| 1979 | 5 |
| 1980 | 9 |
| 1981 | 3 |
| 1982 | 3 |
| 1983 | 4 |
| 1984 | 6 |
| 1985 | 3 |
| 1986 | 4 |
| 1987 | 5 |
| 1988 | 6 |
| 1989 | 8 |
| 1990 | 2 |
| 1991 | 1 |
| 1992 | 3 |
| 1993 | 3 |
| 1994 | 6 |
| 1995 | 5 |
| 1996 | 3 |
| 1997 | 5 |
| 1998 | 5 |
| 1999 | 4 |
| 2000 | 1 |
| 2001 | 6 |
| 2002 | 5 |
| 2003 | 11 |
| 2004 | 3 |
| 2005 | 3 |
| 2006 | 2 |
| 2007 | 1 |
| 2008 | 3 |
| 2009 | 2 |
| 2010 | 5 |
| 2011 | 1 |
| 2012 | 3 |
| 2013 | 5 |
| 2014 | 2 |
| 2016 | 5 |
| 2017 | 1 |
| 2019 | 4 |
| 2020 | 1 |
| 2021 | 4 |
| 2022 | 3 |
| 2023 | 4 |
| 2024 | 1 |
| 2025 | 1 |
| 2026 | 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 year(c.\"eventDate\") = 1992
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 year(c."eventDate") = 1992
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 LAX92FA305Accident · 4 fatalField investigationFinal reportCessna 175A · Overgaard, AZThe pilot's improper preflight performance planning and decision to operate the airplane over the maximum certified gross weight at a high density altitude airport which resulted in an inadvertent stall. Contributing to the accident was inadequate maintenance…NTSB MIA92LA125Accident · Serious injuriesLimited investigationFinal reportCessna 175 · Yulee, FLLoss of engine power due to undetermined reasons shortly after takeoff.NTSB CHI92LA074Accident · No injuriesLimited investigationFinal reportCessna 175 · Warren, MIA loss of engine power as a result of a connecting rod failure. Factors related to the accident were the power lines and trees in the path of the selected emergency landing site.