NTSB investigations: Cessna 310Q, IN
12 cases on aircraft the registry lists as Cessna 310Q. 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
| 1974 | 1 |
|---|---|
| 1977 | 2 |
| 1978 | 2 |
| 1979 | 1 |
| 1980 | 1 |
| 1988 | 2 |
| 2004 | 1 |
| 2006 | 1 |
| 2007 | 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.\"eventStateOrRegion\" = 'IN' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074242'))
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" = 'IN' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074242'))
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 CHI07LA289Accident · No injuriesLimited investigationFinal reportCessna 310Q · Brownsburg, INThe pilot's poor in-flight planning to make an off airport precautionary landing and his failure to maintain clearance from the construction equipment during the landing roll. Contributing to the accident was the construction equipment.NTSB CHI06CA068Accident · No injuriesData collectionFinal reportCessna 310Q · Griffith, INThe overload failure of the right main landing gear locking mechanism due to undetermined reasons.NTSB CHI04CA221Accident · No injuriesData collectionFinal reportCessna 310Q · Nappanee, INThe delay in the pilot's performance of an aborted takeoff. A factor was the reported restricted movement of the elevator. Additional factors were the rising easement and roadway the airplane went over before coming to rest in the farmers field.NTSB CHI89LA001Accident · Serious injuriesLimited investigationFinal reportCessna 310Q · Tell City, INThe pilot flew a VOR approach to the airport, but was too high to land on the approach runway. He executed a circling VFR pattern to land on the reciprocal runway, then flew into the ground fog in the descending base turn. The left wing struck a tree while in…NTSB CHI88FA080Accident · 1 fatalField investigationFinal reportCessna 310Q · Servia, INThe pilot induced overload to the airplane structure causing material failure of the airplane. Attempted flight into adverse weather, and spatial disorientation of the pilot, are contributing factors in this accident.NTSB CHI80FET09Accident · No injuriesClosedCessna 310Q · Kendallville, INNTSB CHI79FA079Accident · 2 fatalClosedCessna 310 · Blue Ridge, INNTSB CHI79FEX06Accident · No injuriesClosedCessna 310Q · Marion, INNTSB CHI78DET19Accident · No injuriesClosedCessna 310Q · Fort Wayne, INNTSB CHI77FEX34Accident · No injuriesClosedCessna 310Q · W.Lafayette, INNTSB CHI77FEX07Accident · No injuriesClosedCessna 310Q · Columbus, INNTSB CHI75FEA02Accident · Serious injuriesClosedCessna 310Q · Bedford, IN