NTSB investigations: Cessna 210
6 cases on aircraft the registry lists as Cessna 210, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 1 |
|---|---|
| 1989 | 1 |
| 1992 | 1 |
| 1996 | 1 |
| 2005 | 1 |
| 2006 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2073402')
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\" = 130))
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.aircraft_model_code IN ('2073402')
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" = 130))
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 DFW07CA031Accident · No injuriesData collectionFinal reportCessna 210 · Baytown, TXThe failure of the main landing gear to fully extend for an undetermined reason during takeoff-initial climb, which resulted in a gear-up landing.NTSB CHI05LA225Accident · No injuriesLimited investigationFinal reportCessna 210 · Rapid City, SDThe landing gear extension not possible and inoperative flap system due to fatigue failure of a hydraulic system tube during approach. An additional cause was the improper rebuild/remanufacture of the hydraulic tube. Contributing factors were the dependency…NTSB FTW96LA334Accident · No injuriesLimited investigationFinal reportCessna 210 · Pueblo, COimproper routing of the nose landing gear hydraulic line by unknown maintenance personnel, allowing it to chafe on the nose wheel and develop a leak, which resulted in an inability to obtain a down-and-locked condition of the landing gear.NTSB LAX92LA081Accident · No injuriesLimited investigationFinal reportCessna 210 · Bakersfield, CAThe pilot's attempt to restart the engine when there was evidence of a fuel leak. A factor in the accident was the fractured fuel line due to the improper installation and overtorque of the line by company maintenance.NTSB LAX89LA250Accident · No injuriesLimited investigationFinal reportCessna 210 · Thermal, CAA twisted nose gear uplock due to an elongated bolt hole which prevented the nose gear from extending.NTSB ATL83LA119Accident · No injuriesLimited investigationFinal reportCessna 210 · Folkston, GAShortly after departure, the pilot observed fuel coming from the fuel tank vent and elected to make a precautionary landing. He touched down in the first 1/3 of runway 17 at a speed of about 80 mph. The pilot stated that the brakes failed during the roll-out…