NTSB investigations: Continental 0-300 series
14 cases on aircraft whose registry engine model is Continental 0-300 series, where the defining event was Collision during takeoff/land. 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
| 2008 | 1 |
|---|---|
| 2013 | 1 |
| 2016 | 2 |
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 2 |
| 2020 | 1 |
| 2021 | 3 |
| 2023 | 2 |
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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '490'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17022')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e."isDefiningEvent" AND e."tier2Number" = '490'))
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 CEN23LA108Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 172H · Crosby, TXThe pilot’s delayed soft-field takeoff procedure, which prevented the pilot from achieving adequate airspeed and a proper climb rate resulting in a collision with a moving train.NTSB WPR23LA082Accident · Serious injuriesClass 4 · LimitedFinal reportCessna 172 · Watsonville, CAThe pilot’s failure to maintain clearance from powerlines during a go around.NTSB WPR22LA037Accident · Minor injuriesClass 4 · LimitedFinal reportCessna 172 · Stanley, IDThe pilot's failure to attain sufficient airspeed for the airplane to climb with a tailwind.NTSB ERA21LA313Accident · Minor injuriesClass 3 · LimitedFinal reportCessna 172 · Waxhaw, NCThe pilot’s failure to abort the takeoff in sufficient time to stop the airplane on the runway remaining. Contributing to the accident was the lack of airplane takeoff performance due to the pilot’s failure to assure that the carburetor heat control was in…NTSB ANC21LA056Accident · Serious injuriesClass 3 · LimitedFinal reportCessna 170B · North Pole, AKThe pilot’s exceedance of the airplane’s takeoff performance limitations, which prevented the airplane from gaining sufficient altitude to clear the trees off the departure end of the runway.NTSB ERA21LA056Accident · No injuriesClass 3 · LimitedFinal reportCessna 172 · Atlanta, GAThe Cessna pilot’s failure to tune his radio to the common traffic advisory frequency, which resulted in a lack of awareness of the other aircraft operating at the airport. Contributing to the accident was the Cessna pilot’s lack of understanding of the…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 GAA19CA323Accident · No injuriesData collectionFinal reportCessna 172 · Yellow Pine, IDThe pilot's improper approach, which resulted in the airplane touching down with insufficient runway remaining to stop on the runway, a runway overrun, and subsequent collision with bushes and terrain.NTSB GAA18CA146Accident · Minor injuriesData collectionFinal reportCessna 172 · Gatesvile, TXThe pilot’s failure to maintain directional control during initial climb in a gusty condition.NTSB GAA17CA302Accident · No injuriesData collectionFinal reportCessna 175 · Prospect, ORThe flight instructor’s failure to attain an adequate climb rate during takeoff, which resulted in impact with trees.NTSB GAA16CA403Accident · No injuriesData collectionFinal reportCessna 172 · Rexburg, IDThe student pilot's failure to retract the flaps during a go-around in high density altitude conditions, resulting in the airplane's inability to climb and a subsequent collision with terrain and nose over.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 CEN13CA495Accident · No injuriesData collectionFinal reportCessna 172 · Kankakee, ILThe airplane struck a deer during takeoff. Contributing to the accident was the perimeter fence being less than FAA's recommended 10 feet high.NTSB WPR09LA056Accident · 1 fatalLimited investigationFinal reportCessna 172 · Lompoc, CAThe pilot's failure to maintain clearance from the power line. Contributing to the accident was the pilot's lack of recent experience.