NTSB investigations: Continental 0-300 series, 1998
31 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\") = 1998
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") = 1998
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 MIA99LA036Accident · No injuriesLimited investigationFinal reportCessna 172C · Tallahassee, FLan on ground collision with a horse.NTSB IAD99LA018Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Essex, MDA loss of engine power for undetermined reasons. Factors were the lack of suitable terrain for a forced landing and dark night conditions.NTSB CHI99LA030Accident · No injuriesLimited investigationFinal reportCessna 172C · Falls City, NEthe flight instructor (on the ground)'s conducting inadequate initial training of the student pilot. Factors were the student pilot's misjudging the flare and his lack of total experience in the type of operation.NTSB FTW99LA009Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Conroe, TXThe pilot's failure to maintain clearance with trees. Factors were the fogged front windshield and side windows.NTSB ATL99LA001Accident · No injuriesLimited investigationFinal reportCessna C-172F · Ball Ground, GAThe pilots failure to maintain directional control of the airplane on take-off, during gusty conditions, resulting in a collision with a tree.NTSB SEA98LA189Accident · No injuriesLimited investigationFinal reportCessna 172D · Ronan, MTThe pilot's failure to attain adequate airspeed during liftoff from a soft field takeoff. Factors include high density alttiude.NTSB ANC98LA163Accident · No injuriesLimited investigationFinal reportCessna 170B · Igiugig, AKThe pilot's failure to maintain directional control of the aircraft. Contributing factors were the crosswind condition, the pilot's lack of total experience in make/model of the aircraft, and the pilot not achieving a climb on takeoff.NTSB LAX98LA301Accident · No injuriesLimited investigationFinal reportCessna 172F · Long Beach, CAThe pilot's misjudging the flare point and failure to maintain an adequate airspeed margin, which resulted in a stall/mush and hard landing. A contributing factor was the dark night conditions.NTSB LAX98LA287Accident · No injuriesLimited investigationFinal reportCessna 170B · San Jose, CAThe pilot's inadequate compensation for the existing crosswind condition and failure to maintain directional controlNTSB MIA98LA234Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Leesburg, FLThe pilot's decision to leave the engine running with no one at the controls as he exited the aircraft to check for wheel chocks in place. This resulted in the aircraft moving uncontrolled and eventually colliding with a fence.NTSB MIA98LA233Accident · No injuriesLimited investigationFinal reportCessna 172F · Spring Hill, FLThe pilot's misjudgment of distance and his delay in initiating a go around. Contributing was the pilot's improper landing flare.NTSB ATL98LA120Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Sewanee, TNThe inadequate visual lookout by the ground pedestrian. A factor was dark night conditions.NTSB IAD98LA096Accident · No injuriesLimited investigationFinal reportCessna 172G · Williamson, NYDirectional control not maintained by one of the pilot's on board the airplane.NTSB ANC98LA131Accident · No injuriesLimited investigationFinal reportCessna 172 · Palmer, AKFatigue of the forward end of the engine crankshaft resulting in separation of the propeller assembly, and the operator's failure to comply with a required maintenance procedure. A factor was uneven terrain.NTSB FTW98LA318Accident · No injuriesLimited investigationFinal reportCessna 172H · Commerce, TXThe pilot's inadequate compensation for the crosswind resulting in a loss of control. A factor was the crosswind.NTSB IAD98LA081Accident · Minor injuriesLimited investigationFinal reportCessna 172G · Dover, DEThe pilot's failure to attain the proper touchdown point.NTSB CHI98LA195Accident · No injuriesLimited investigationFinal reportCessna 172E · Demotte, INThe pilot's inadequate preflight planning that failed to ensure takeoff could be attained. Other related factors were the aborted takeoff, grass, and a dirt bank.NTSB ANC98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Naknek, AKThe pilot's inadequate compensation for wind conditions. A factor associated with this accident was a crosswind.NTSB LAX98LA183Accident · Serious injuriesLimited investigationFinal reportCessna 172H · Mariposa, CAFuel exhaustion due to the pilot's inadequate preflight planning, and improper in-flight decision not to make a precautionary landing for additional fuel.NTSB IAD98LA064Accident · No injuriesLimited investigationFinal reportCessna 172D · Beverly, MAfailure of the pilot to maintain control of the airplane during the landing and attempted go-around. A related factor was the crosswind.NTSB FTW98LA254Accident · No injuriesLimited investigationFinal reportCessna 172A · Ten Sleep, WYThe student pilot's failure to select a proper touchdown point. A factor was his lack of recent experience conducting solo flight operations.NTSB LAX98LA163Accident · No injuriesLimited investigationFinal reportCessna 172A · Van Nuys, CAThe pilot's failure to maintain obstacle clearance due to his inadequate visual lookout and selection of the wrong taxi route. Contributing factors were the pilot's diverted attention while taxiing in the vicinity of a construction area.NTSB CHI98LA122Accident · Serious injuriesLimited investigationFinal reportCessna 172 · Barrington Hill, ILThe pilot's failure to maintain adequate airspeed which resulted in a stall/mush and subsequent in-flight collision with trees.NTSB FTW98LA166Accident · No injuriesLimited investigationFinal reportCessna 172F · Fort Collins, COthe pilot's improper in flight planning/decision in electing to land with a known 30 knot tailwind. Factors were high winds and a tailwind.NTSB ANC98LA031Accident · No injuriesLimited investigationFinal reportCessna 172A · Paxson, AKThe pilots failure to maintain terrain clearance while flying into a box canyon, and an inadvertent stall during his attempt to reverse direction.NTSB FTW98LA155Accident · Minor injuriesLimited investigationFinal reportZito ZMI-A · Ogden, UTthe improper placement of lead ballast by the pilot, resulting in an improper balance of the airplane; and the pilot's excessive control input to correct a nose high attitude, resulting in ground impact.NTSB FTW98LA133Accident · No injuriesLimited investigationFinal reportCessna 172D · El Paso, TXThe pilots improper compensation for the wind conditions and his failure to maintain control of the aircraft. A factor was the high wind condition.NTSB MIA98LA080Accident · No injuriesLimited investigationFinal reportCessna 172H · St. Petersburg, FLa sudden encounter with wind gusts associated with a quickly passing rain shower which resulted in a nose-over, and subsequent collision with the runway.NTSB MIA98LA065Accident · No injuriesLimited investigationFinal reportCessna 172 · Valkaria, FLthe pilot's inadequate preflight, and subsequent loss of engine power, due to fuel exhaustion, which resulted in a forced landing and impact with trees.NTSB FTW98LA116Accident · No injuriesLimited investigationFinal reportCessna 172 · Laramie, WYThe pilot's improper flare and subsequent improper go-around in that he failed to use compensating elevator control, and his loss of directional control.NTSB MIA98LA057Accident · No injuriesLimited investigationFinal reportCessna 170 · Orlando, FLfailure of the the left brake to operate, due to a bad o-ring; and subsequent failure of the pilot to maintain directional control of the airplane during landing rollout, resulting in a ground loop and subsequent on-ground encounter with terrain.