NTSB investigations: Continental 0-300 series, 1999
28 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\") = 1999
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") = 1999
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 FTW00LA049Accident · No injuriesLimited investigationFinal reportCessna 172 · Fort Worth, TXThe student pilot's improper flare and improper recovery from a bounced landing, which resulted in a porpoise.NTSB FTW00LA023Accident · No injuriesLimited investigationFinal reportCessna 172B · Beaumont, TXFuel exhaustion as a result of the flight instructor's failure to refuel the airplane. A factor was the lack of suitable terrain for the forced landing.NTSB MIA00LA015Accident · No injuriesLimited investigationFinal reportCessna 172G · Itta Bena, MSa loss of engine power for undetermined reasons resulting in a forced landing that was short of the intended touchdown point, and the subsequent impact with the ground.NTSB DEN00LA011Accident · No injuriesLimited investigationFinal reportCessna 172B · Englewood, COThe pilot-in-command's failure to maintain directional control of the aircraft during landing roll. Factors were the gusty crosswind and the runway light.NTSB CHI00LA010Accident · No injuriesLimited investigationFinal reportCessna 172G · Cambridge, MNthe fractured main landing gear due to the improper maintenance by an unknown person(s) and the inadequate annual inspection by an unqualified person.NTSB NYC00LA002Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Wolfeboro, NHA total loss of engine power for undetermined reasons.NTSB ANC99LA152Accident · Minor injuriesLimited investigationFinal reportMaule ML-4 · Anchorage, AKThe improper (reversed) connection of the elevator control cables by the owner/pilot-mechanic, and the failure to have the installation inspected by another mechanic.NTSB ANC99LA151Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Galena, AKThe pilot's failure to refuel, and the resulting fuel exhaustion. A factor was the dark night which hampered location of a nearby closed, and unlit, airstrip.NTSB IAD99LA067Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Honeoye Falls, NYthe pilot's loss of directional control after landing. A factor in the accident were ruts in the turf runway that were hidden from view.NTSB SEA99LA158Accident · No injuriesLimited investigationFinal reportCessna 170B · Auburn, WALoss of directional control due to deficient brakes and tailwheel. Factors include leaking brake cylinder, loose tailwheel casting, and obstructions (VASI lights) in the path of the airplane as it left the runway.NTSB ATL99LA125Accident · No injuriesLimited investigationFinal reportCessna 172P · Buchanan, GAThe loss of engine power for undetermined reasons. Factors were conditions favorable for the formation of carburetor ice during glide and cruise, and rough and uneven terrain.NTSB ATL99LA123Accident · No injuriesLimited investigationFinal reportCessna 172 · Houston, MSThe pilot's failure to switch the magneto switch to the both position before attempting a takeoff that resulted in the loss of engine power and resulted in the subsequent collision with trees.NTSB ANC99FA128Accident · 2 fatalField investigationFinal reportCessna 170B · Cooper Landing, AKThe pilot's inadvertent stall.NTSB CHI99LA288Accident · No injuriesLimited investigationFinal reportCessna 172G · Glenarm, ILthe pilot's selection of the wrong runway for the prevailing winds. Factors were the pilot's misunderstanding of the wind information and the tailwind.NTSB DEN99LA134Accident · No injuriesLimited investigationFinal reportCessna 170B · Casper, WYThe pilot's selection of a wrong runway for landing and his failure to maintain directional control.NTSB LAX99LA256Accident · No injuriesLimited investigationFinal reportCessna 172E · Emeryville, CAThe pilot's inadequate in-flight planning and inadequate fuel consumption calculations, resulting in a total loss of engine power due to fuel exhaustion. Factors were the pilot's failure to have all appropriate flight manuals aboard the airplane and the low…NTSB CHI99LA201Accident · No injuriesLimited investigationFinal reportCessna 172G · Union, INThe pilot's failure to maintain clearance with the sign. Factors associated with the accident were the low ceilings and the sign which was contacted.NTSB LAX99LA217Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Needles, CAThe pilot's inadequate compensation for the gusty crosswind condition and subsequent failure to maintain alignment with the road used for takeoff, which resulted in a collision with a construction sign during the initial climb.NTSB ATL99LA094Accident · Minor injuriesLimited investigationFinal reportCessna 172E · Millington, TNLoss of engine power due to undetermined reasons. Factors were weather conditions favorable to carburetor ice and the terrain condition at the forced landing site.NTSB LAX99FA162Accident · 2 fatalField investigationFinal reportGlobe GC-1B · Trona, CAThe pilot's failure to maintain an adequate terrain clearance altitude while performing intentional low altitude passes over a campground.NTSB SEA99LA059Accident · No injuriesLimited investigationFinal reportCessna 172D · Glenns Ferry, IDThe failure of both pilots to see-and-avoid wires crossing the river. Factors included: transmission wires; inattention of both pilots to the aircraft's flight path; and the pilots' low-altitude flight.NTSB LAX99LA145Accident · No injuriesLimited investigationFinal reportCessna 172H · North Las Vegas, NVThe pilot's failure to maintain directional control during takeoff roll resulting in a collision with taxiway sign. A factor was the sign.NTSB LAX99LA132Accident · No injuriesLimited investigationFinal reportCessna 172B · Winslow, AZThe pilot's decision to continue flight into known adverse wind conditions which exceeded the ground handling capability of the aircraft.NTSB ATL99LA064Accident · No injuriesLimited investigationFinal reportCessna 172B · Mt. Airy, NCThe pilot's failure to maintain proper airspeed during landing and his failure to attain a proper touchdown point on the runway.NTSB ATL99LA059Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Florala, ALThe pilot's inadequate preflight inspection, which resulted in a loss of engine power due to fuel system contamination with water.NTSB ANC99LA032Accident · No injuriesLimited investigationFinal reportCessna 170B · Palmer, AKThe pilot's inadequate preflight inspection, and his failure to refuel the airplane that resulted in fuel exhaustion.NTSB FTW99LA071Accident · No injuriesLimited investigationFinal reportCessna 172E · Guymon, OKThe pilot's failure to maintain aircraft control. A factor was the gusty crosswind.NTSB ATL99LA041Accident · No injuriesLimited investigationFinal reportCessna 172 · Centre, ALThe pilot's inadequate in-flight planning and his failure to attain the proper touchdown point on the runway. Factors were the tailwind weather condition, and the wet sod runway.