NTSB investigations: Continental 0-300 series, 2013
21 cases on aircraft whose registry engine model is Continental 0-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 | 183 |
|---|---|
| 1965 | 197 |
| 1966 | 237 |
| 1967 | 250 |
| 1968 | 163 |
| 1969 | 112 |
| 1970 | 114 |
| 1971 | 113 |
| 1972 | 96 |
| 1973 | 87 |
| 1974 | 53 |
| 1975 | 51 |
| 1976 | 61 |
| 1977 | 68 |
| 1978 | 65 |
| 1979 | 49 |
| 1980 | 37 |
| 1981 | 48 |
| 1982 | 31 |
| 1983 | 31 |
| 1984 | 34 |
| 1985 | 31 |
| 1986 | 38 |
| 1987 | 39 |
| 1988 | 35 |
| 1989 | 27 |
| 1990 | 28 |
| 1991 | 23 |
| 1992 | 29 |
| 1993 | 30 |
| 1994 | 22 |
| 1995 | 32 |
| 1996 | 29 |
| 1997 | 18 |
| 1998 | 31 |
| 1999 | 28 |
| 2000 | 27 |
| 2001 | 28 |
| 2002 | 30 |
| 2003 | 37 |
| 2004 | 28 |
| 2005 | 32 |
| 2006 | 27 |
| 2007 | 28 |
| 2008 | 23 |
| 2009 | 18 |
| 2010 | 22 |
| 2011 | 17 |
| 2012 | 20 |
| 2013 | 21 |
| 2014 | 12 |
| 2015 | 22 |
| 2016 | 17 |
| 2017 | 20 |
| 2018 | 22 |
| 2019 | 23 |
| 2020 | 13 |
| 2021 | 30 |
| 2022 | 17 |
| 2023 | 19 |
| 2024 | 17 |
| 2025 | 25 |
| 2026 | 10 |
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\") = 2013
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022'))
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") = 2013
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022'))
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 ANC14CA005Accident · No injuriesData collectionFinal reportCessna 172 · Juneau, AKThe pilot's decision to land on an unsuitable surface, which resulted in a nose over.NTSB ANC14FA002Accident · 1 fatalField investigationFinal reportCessna 172C · Fairbanks, AKThe pilot’s failure to ensure that adequate fuel was on board the airplane, which resulted in fuel exhaustion and a subsequent collision with terrain.NTSB ERA14LA008Accident · Minor injuriesLimited investigationFinal reportCessna 172 - F · Gainesville, FLA total loss of engine power for reasons that could not be determined because a postaccident engine examination and test run revealed no anomalies.NTSB CEN13LA581Accident · No injuriesLimited investigationFinal reportCessna 172 · Rio Vista, TXThe student pilot’s failure to maintain adequate airspeed during the initial climb after an excessive takeoff run from a grass airstrip, which resulted in the exceedance of the airplane's critical angle-of-attack and a subsequent aerodynamic stall and loss of…NTSB ERA13CA414Accident · No injuriesData collectionFinal reportCessna 172B · Shellman Bluff, GAAn inadvertent collision with a deer during landing.NTSB ERA13FA388Accident · 1 fatalField investigationFinal reportCessna 172 · Limington, MEAn impairing medical event of undetermined origin that led to a loss of control during takeoff.NTSB ERA13CA393Accident · No injuriesData collectionFinal reportCessna 172E · Apex, NCThe pilot's failure to attain the proper touchdown point on the runway, which resulted in a runway overrun and subsequent aircraft noseover.NTSB WPR13LA378Accident · No injuriesLimited investigationFinal reportCessna 172B · Sisters, ORA loss of engine power during cruise flight for reasons that could not be determined because the engine was not properly preserved to prevent corrosion after the wreckage was recovered from the lake.NTSB CEN13CA495Accident · No injuriesData collectionFinal reportCessna 172 · Kankakee, ILThe airplane struck a deer during takeoff. Contributing to the accident was the perimeter fence being less than FAA's recommended 10 feet high.NTSB WPR13CA371Accident · No injuriesData collectionFinal reportCessna 172H · Metaline Falls, WAThe pilot's failure to maintain clearance from a windsock pole while taxiing.NTSB WPR13CA252Accident · Minor injuriesData collectionFinal reportCessna 172A · Eatonville, WAA partial loss of engine power due to carburetor icing and the pilot's failure to maintain adequate airspeed during a go-around, which resulted in a stall.NTSB WPR13CA240Accident · No injuriesData collectionFinal reportGlobe GC-1B · Tucson, AZThe pilot's failure to lower the landing gear prior to touchdown.NTSB CEN13LA232Accident · No injuriesLimited investigationFinal reportCessna 172G · Reading, MIThe partial loss of engine power due to the improper securing of the throttle linkage by maintenance personnel.NTSB CEN13LA216Accident · No injuriesLimited investigationFinal reportCessna 172 · Wonewoc, WIThe restricted vented fuel cap and obstructed fuel vent lines, which resulted in a total loss of engine power due to fuel starvation.NTSB WPR13CA163Accident · Minor injuriesData collectionFinal reportCessna 172G · Temecula, CAThe pilot's inadequate fuel planning, which resulted in a total loss of engine power due to fuel exhaustion.NTSB WPR13CA168Accident · Serious injuriesData collectionFinal reportCessna 170 · Livermore, CAThe pilot's failure to maintain directional control during the landing roll.NTSB CEN13CA200Accident · No injuriesData collectionFinal reportCessna 172 · Kremmling, COThe student pilot’s failure to maintain directional control while landing.NTSB WPR13CA139Accident · No injuriesData collectionFinal reportCessna 172F · Nampa, IDThe failure of the pilot of another airplane, who was taxiing with no intent for flight, to maintain proper visual lookout.NTSB CEN13CA176Accident · No injuriesData collectionFinal reportCessna 172A · Vineland, MNThe pilot’s decision to attempt a touch-and-go landing on a narrow, ice-covered road with snow banks on each side.NTSB CEN13LA166Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Akron, COThe pilot’s physical impairment due to alcohol intoxication, which resulted in an aerodynamic stall during landing.NTSB WPR13LA098Accident · Minor injuriesLimited investigationFinal reportCessna 172F · Marysville, CAA total loss of engine power during initial climb due to fuel starvation, which resulted from maintenance personnel’s improper installation of the fuel selector handle. Contributing to the accident was an incorrectly modified fuel selector handle assembly.