NTSB investigations: Continental 0-200 series, MN
4 cases on aircraft whose registry engine model is Continental 0-200 series, where the first occurrence was “In flight collision with object”. 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
| 1984 | 1 |
|---|---|
| 1986 | 1 |
| 1989 | 1 |
| 1990 | 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\" = 'MN' 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 ('17020')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220))
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" = 'MN' 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 ('17020')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 MKC90LA052Accident · No injuriesLimited investigationFinal reportCessna 150 · Clear Lake, MNFailure of the pilot to maintain proper alignment with the runway, his delay in initiating a go-around, and his premature raising of the flaps. Factors related to the accident were the adverse wind conditions and the tree.NTSB MKC89FA060Accident · 1 fatalField investigationFinal reportCessna 150K · Pemberton, MNPoor judgement on the part of the pilot in that he attempted a down wind take off without adequate distance to clear obstacles in his flight path.NTSB CHI86LA162Accident · Minor injuriesLimited investigationFinal reportCessna 150L · Int'L Falls, MNAcft struck power lines on approach to private airstrip. The plt stated that an air pocket pulled the plane down. Weather at international Falls, six miles from the accident site, reported winds at 7 KTS with no gusts. The plts flt time was not reported.NTSB CHI85LA041Accident · No injuriesLimited investigationFinal reportCessna 150M · Pillager, MNThe plt took off uphill on a grass rwy that was dew covered. The field was aprx 1600 ft long bordered by 50-75 ft trees. The plt stated that during takeoff roll the acft lights were flickering. He said that the acft was airborne aprx 300 ft before reaching…