NTSB investigations: Continental 0-300 series, 2000
27 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\") = 2000
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") = 2000
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 DEN01FA028Accident · 2 fatalField investigationFinal reportCessna 172 · Lusk, WYthe pilot's VFR flight into instrument meteorological conditions, and his subsequent failure to maintain terrain clearance, which resulted in an in-flight collision with terrain. Contributing factors were the pilot's failure to obtain a weather briefing, low…NTSB ATL01LA018Accident · No injuriesLimited investigationFinal reportCessna 172 · Mobile, ALThe pilot's improper flare during landing that resulted in a hard landing and the subsequent overload failure of the nose gear assembly.NTSB CHI01LA036Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Kalkaska, MIThe student pilot's failure to maintain aircraft control on the ground. Factors relating to this accident were the student pilot's improper abort procedures, the sign, and the ditch.NTSB CHI01LA031Accident · No injuriesLimited investigationFinal reportCessna 172 · Carrollton, MOthe misjudged touchdown point by the pilot. Factors were the runway lights not on, the dark night, and the plowed field.NTSB NYC01LA014Accident · Serious injuriesLimited investigationFinal reportCessna 172G · Steubenville, OHThe pilot's failure to maintain directional control while landing with a crosswind. Factors in the accident were the pilot's lack of familiarity in the make and model airplane, and the crosswind conditions.NTSB ATL01LA007Accident · Minor injuriesLimited investigationFinal reportCessna 172-B · Palatka, FLThe CFI's inadequate preflight planning which resulted in fuel exhaustion and the subsequent loss of engine power.NTSB LAX01LA008Accident · No injuriesLimited investigationFinal reportCessna 172H · Hilo, HIAn inadvertent pilot-induced porpoise resulting from the pilot's improper landing flare and inadequate power management.NTSB CHI01LA004Accident · Minor injuriesLimited investigationFinal reportCessna 172M · Sparta, WIthe pilot's inaccurate fuel consumption calculations, improper fuel management, inadequate in-flight planning/decision, flight to destination alternate not performed, and the discontinued planned approach to the initially selected runway. Contributing factors…NTSB CHI00LA305Accident · No injuriesLimited investigationFinal reportCessna 172 · Buffalo, MOThe inadvertent stall during a go-around. Factors relating to this accident were the student pilot's improper in-flight decisions and his failure to raise the flaps during the go around.NTSB IAD00LA080Accident · Minor injuriesLimited investigationFinal reportCessna 172B · Halfmoon, NYThe pilot's inadequate preflight planning, and his continued flight into, and attempted landing during a thunderstorm. A factor was the thunderstorm.NTSB SEA00LA168Accident · No injuriesLimited investigationFinal reportCessna 172B · Sunriver, ORThe pilot's improper decision to continue the takeoff after the aircraft failed to climb or accelerate immediately after the initial liftoff. Factors were inadequate preflight planning, to include the pilot's failure to calculate takeoff performance data,…NTSB NYC00FA226Accident · 1 fatalField investigationFinal reportCessna 172 · Davis, WVThe pilot-in-command's inadequate weather evaluation, which resulted in a takeoff with a tailwind, and a subsequent inadvertent stall. Factors were a high gross weight, a high density altitude, and a tailwind.NTSB FTW00LA217Accident · Serious injuriesLimited investigationFinal reportCessna 172B · Olney, TXThe pilot's inadequate compensation for wind conditions. A factor was the gusty crosswind.NTSB NYC00LA202Accident · No injuriesLimited investigationFinal reportCessna 172H · Rainelle, WVThe pilot's failure to maintain a proper decent rate. A factor was the up-sloping runway.NTSB IAD00LA057Accident · Serious injuriesLimited investigationFinal reportCessna 172G · North Elba, NYthe pilot's inaccurate fuel consumption calculations and exhaustion of his fuel supply.NTSB IAD00LA055Accident · No injuriesLimited investigationFinal reportCessna 172H · Kutztown, PAThe pilot's improper recovery from a bounced landing, and his delay in remedial action.NTSB IAD00LA061Accident · No injuriesLimited investigationFinal reportCessna 172H · Friendly, MDthe student pilot's inadequate compensation for winds that resulted in his failure to maintain runway alignment and a hard landing.NTSB ATL00LA060Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Foley, ALThe pilot exceeding the performance capability of the airplane during takeoff. A factor was the trees.NTSB SEA00LA093Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Johnson Creek, IDThe pilot's failure to maintain clearance from the rising terrain. Factors include his poor decision to depart without assurance that he could clear the surrounding terrain under the ambient conditions, his failure to adhere to the accepted procedure of…NTSB FTW00LA148Accident · No injuriesLimited investigationFinal reportCessna 172H · Mesquite, TXThe flight instructor's inadequate supervision of the student pilot during the landing.NTSB FTW00LA119Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Lubbock, TXThe pilot's incorrect positioning of the fuel selector which resulted in fuel starvation. Factors were the pilot's lack of familiarity with the fuel system due to an inadequate checkout by a flight instructor, and the lack of suitable terrain for the forced…NTSB SEA00LA058Accident · No injuriesLimited investigationFinal reportCessna 170B · Lopez Island, WAThe pilot's failure to maintain aircraft control during landing. Contributing factors were the crosswind condition, gusts, and the pilot's overall lack of total (flight and tail wheel) experience.NTSB NYC00LA099Accident · No injuriesLimited investigationFinal reportCessna 172 · Sissonville, WVThe pilot's failure to maintain runway alignment during takeoff. A factor in the accident was wind gusts.NTSB NYC00LA095Accident · No injuriesLimited investigationFinal reportCessna 172 · New Brighton, PAThe pilot's inadequate compensation for the gusty wind conditions. A factor was the windshear encountered on final approach.NTSB IAD00LA019Accident · No injuriesLimited investigationFinal reportCessna 172 · Lyndonville, VTthe student pilot's failure to maintain directional control during landing. A factor in the accident was the ditch that ran parallel to the runway.NTSB LAX00LA063Accident · No injuriesLimited investigationFinal reportCessna 172G · Victorville, CAThe failure of the pilot to maintain positional awareness, which resulted in his becoming lost and disoriented. Contributing factors were the pilot's delay requesting assistance from air traffic control and the failure of the airplane's electrical generator.NTSB LAX00LA062Accident · Minor injuriesLimited investigationFinal reportCessna 172A · Dos Palos, CAA partial loss of engine power due to the failure of maintenance personnel to properly install and safety the throttle arm to the carburetor throttle shaft.