NTSB investigations: Continental 0-300 series, 2018
22 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\") = 2018
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") = 2018
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 GAA19CA123Accident · Minor injuriesData collectionFinal reportCessna 172 · Center, TXThe pilot's exceedance of the airplane's critical angle of attack during landing in gusting crosswind conditions, which resulted in an aerodynamic stall.NTSB ANC19LA008Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Whittier, AKA total loss of engine power for reasons that could not be determined based on the available evidence.NTSB GAA19CA068Accident · No injuriesData collectionFinal reportSilveira Jonathan A Sonex · Corona, CAThe pilot’s failure to see and avoid the airplane on the runway while landing and the pilot receiving instruction’s and flight instructor's failure to properly scan the approach before pulling onto the runway during the takeoff.NTSB ANC19LA006Accident · No injuriesLimited investigationFinal reportCessna 172 · Anchorage, AKThe pilot's failure to maintain airplane control during the landing flare, which resulted in the wing striking the runway. Contributing to the accident was a partial loss of engine power, which resulted from fuel contamination.NTSB GAA19CA048Accident · Minor injuriesData collectionFinal reportCessna 172 · Cleburne, TXThe pilot's improper preflight fuel planning and in-flight fuel management, which resulted in fuel exhaustion and the subsequent total loss of engine power.NTSB ERA18TA266Accident · No injuriesFinal reportCessna 172 · Somerset, PAThe pilot's decision to land with insufficient runway remaining to stop, which resulted in a runway overrun.NTSB ERA18LA257Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Winter Haven, FLThe student pilot’s improper pitch attitude control during the initial climb, which resulted in a loss of airspeed, and his subsequent decision to conduct a 180° turn following the perceived anomaly, which resulted in a runway overrun.NTSB GAA18CA526Accident · No injuriesData collectionFinal reportCessna 172 · Karluk, AKThe pilot’s failure to maintain proper pitch for a soft-field landing, which resulted in a loss of airplane control.NTSB CEN18LA352Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Rushville, INLoss of engine power due to carburetor icing and the pilot's failure to use carburetor heat in weather conditions conducive to carburetor icing.NTSB GAA18CA493Accident · Minor injuriesData collectionFinal reportCessna 172 · Silver City, NMThe pilot’s failure to maintain directional control while landing with a quartering tailwind.NTSB GAA18CA485Accident · No injuriesData collectionFinal reportCessna 172 · Sallisaw, OKThe student pilot's loss of directional control during the landing roll.NTSB CEN18LA298Accident · Minor injuriesLimited investigationFinal reportExtra EA300 · North Fox Island, MIThe Extra pilot’s failure to see and avoid the Cessna, which resulted in an in-flight collision. Contributing to the accident was the failure of the Extra pilot to tune his radio to the correct frequency, which resulted in no common traffic advisories being…NTSB GAA18CA431Accident · Minor injuriesData collectionFinal reportCessna 172 · King and Queen, VAThe pilot’s improper preflight fuel planning, which resulted in fuel exhaustion and a subsequent total loss of engine power.NTSB GAA18CA369Accident · No injuriesData collectionFinal reportCessna 172 · Bruington, VAThe pilot’s improper decision to abort the takeoff with insufficient runway remaining to safely stop the airplane.NTSB ERA18LA169Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172D · Quinton, VAA loss of engine power for reasons that could not be determined based on the available evidence.NTSB GAA18CA280Accident · Minor injuriesData collectionFinal reportCessna 172 · Nooksack, WAThe pilot’s improper approach in tailwind conditions, which resulted in long landing and subsequent runway overrun.NTSB GAA18CA267Accident · No injuriesData collectionFinal reportCessna 172 · Fulton, NYThe student pilot’s improper landing flare, which resulted in a hard, bounced landing.NTSB GAA18CA183Accident · No injuriesData collectionFinal reportGlobe GC 1B · Fullerton, CAThe pilot’s failure to maintain directional control during the takeoff roll resulting impact with PAPI lighting.NTSB GAA18CA170Accident · No injuriesData collectionFinal reportCessna 172 · Vernon, TXThe pilot's failure to maintain directional control while landing in gusty crosswind conditions.NTSB GAA18CA160Accident · No injuriesData collectionFinal reportCessna 172 · England, ARThe pilot’s failure to detect water in the fuel system during the preflight inspection, which resulted in a loss of engine power during departure and a subsequent impact with terrain.NTSB GAA18CA146Accident · Minor injuriesData collectionFinal reportCessna 172 · Gatesvile, TXThe pilot’s failure to maintain directional control during initial climb in a gusty condition.NTSB CEN18FA088Accident · 1 fatalField investigationFinal reportCessna 172F · Williamsport, INThe pilot's mismanagement of fuel, which resulted in fuel exhaustion and descent and collision with trees.