NTSB investigations: Cessna 310K
4 cases on aircraft the registry lists as Cessna 310K, 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
| 1994 | 1 |
|---|---|
| 1995 | 2 |
| 1998 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074228')
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 ('2074228')
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 LAX98LA229Accident · No injuriesLimited investigationFinal reportCessna 310K · Calexico, CAThe pilot's continued operation of the aircraft with known deficiencies in the landing gear indicating system. A contributing factor to the accident was the pilot's expectation that the gear would be extended and locked irrespective of the indicator lights…NTSB BFO95LA094Accident · Minor injuriesLimited investigationFinal reportCessna 310K · Columbiana, OHThe improper maintenance installation and the subsequent separation of the torque links on the left main landing gear during the landing roll.NTSB SEA95LA099Accident · Minor injuriesLimited investigationFinal reportCessna 310K · Sequim, WAFailure of an undetermined aircraft component, which resulted in a severe vibration, and subsequent ditching at sea. A factor relating to the accident was: the pilot's low cruising altitude (over water) of less than 1,000 feet, which limited his ability to…NTSB FTW94FA091Accident · 4 fatalField investigationFinal reportCessna 310K · Wichita Falls, TXWas the loss of control due to the pilot's spatial disorientation following a complete electrical system failure. Factors were the dark night and the electrical failure as result of burned out wiring terminal.