NTSB investigations: Continental 0-300 series, VT
6 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
| 1975 | 1 |
|---|---|
| 1985 | 1 |
| 2000 | 1 |
| 2001 | 2 |
| 2017 | 1 |
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 c.\"eventStateOrRegion\" = 'VT' AND c.\"eventCountry\" = 'USA'
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" = 'VT' AND c."eventCountry" = 'USA'
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 CEN18FA037Accident · 1 fatalField investigationFinal reportCessna 172G · Pittsford, VTThe pilot's decision to continue visual flight into instrument meteorological conditions, which resulted in a loss of control due to spatial disorientation.NTSB NYC02FA012Accident · 3 fatalField investigationFinal reportCessna 172 · South Hero, VTThe pilot's failure to maintain aircraft control during the takeoff. Factors in this accident were wind gusts and the airplane's high gross weight condition.NTSB NYC01FA147Accident · 1 fatalField investigationFinal reportCessna 172 · Newfane, VTThe pilot's failure to maintain aircraft control during takeoff. A factor was the pilot's impairment due to a narcotic painkiller and antihistamine.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 NYC85LA220Accident · No injuriesLimited investigationFinal reportCessna 170B · Morrisville, VTAccording to the plt, a post maintenance test flt was performed about 45 mins before the landing occurred. The plt stated that he allowed the right seat passenger a student plt and owner of the Cessna 170, to fly and land the acft. Upon landing the plt…NTSB NYC75DNC31Accident · No injuriesClosedCessna 172H · Montpelier, VT