Fatal NTSB investigations: Continental 0-300 series, OR
8 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
| 1967 | 1 |
|---|---|
| 1982 | 1 |
| 1991 | 1 |
| 2005 | 1 |
| 2012 | 1 |
| 2016 | 1 |
| 2019 | 1 |
| 2023 | 1 |
Where
Latest 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 c.\"eventStateOrRegion\" = 'OR' AND c.\"eventCountry\" = 'USA'
AND c.\"highestInjuryLevel\" = 'Fatal'
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 c."eventStateOrRegion" = 'OR' AND c."eventCountry" = 'USA'
AND c."highestInjuryLevel" = 'Fatal'
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 WPR24FA057Accident · 3 fatalClass 3 · FieldFinal reportCessna 172G · Independence, ORThe pilot’s decision to continue flight under visual flight rules into instrument meteorological conditions, which resulted in collision with an obstacle while landing.NTSB WPR19FA244Accident · 2 fatalClass 3 · FieldFinal reportCessna 172 · McKenzie Bridge, ORThe pilot's delayed climb and misjudgment of the airplane’s performance and the runway distance needed to clear obstacles at the end of the runway, which resulted in a collision with trees and subsequent impact with terrain. Contributing to the accident was…NTSB WPR16LA138Accident · 3 fatalLimited investigationFinal reportCessna 172 · Brookings, ORThe pilot's spatial disorientation and loss of situational awareness during the departure turn in dark night conditions, which resulted in an in-flight collision with water.NTSB WPR12FA274Accident · 4 fatalField investigationFinal reportCessna 172 · Veneta, ORThe pilot’s failure to maintain adequate airspeed and altitude to clear trees during the initial climb after takeoff.NTSB SEA05FA180Accident · 1 fatalField investigationFinal reportMaule Bee Dee M-4 · Ritter, ORThe loss of control for an undetermined reason which resulted in a ground collision.NTSB SEA92FA002Accident · 4 fatalField investigationFinal reportCessna 172G · Miltonfreewater, ORInadequate in-flight planning. Factors to the accident were: mountainous terrain, clearance not maintained, lack of total flight experience, and lack of familiarity with geographical area.NTSB SEA82FYK07Accident · 1 fatalFinal reportCessna 172 · Lapine, ORWhen the pilot landed at lakeview,OR,he checked the weather but reported to his passenger that although the weather was bad he did not want to stay in lakeview. The aircraft departed lakeview, following a highway, when the weather conditions continued to…NTSB SEA68A0027Accident · 1 fatalClosedCessna 172 · Portland, OR