NTSB investigations: Cessna 310Q
5 cases on aircraft the registry lists as Cessna 310Q, 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 |
|---|---|
| 1984 | 1 |
| 1988 | 1 |
| 1999 | 1 |
| 2001 | 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 ('2074242')
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 ('2074242')
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 ATL02FA010Accident · 1 fatalField investigationFinal reportCessna 310Q · Winston Salem, NCImproper installation of the elevator trim tab control rod by maintenance personnel which allowed the control rod to disconnect and jam in the full up position (elevator full down) while in-flight. This resulted in a loss of directional control and subsequent…NTSB CHI00LA038Accident · No injuriesLimited investigationFinal reportCessna 310Q · Moline, ILthe landing gear locking mechanism was not properly locked. Factors relating to this accident were the improper rigging of the gear and the runway marker.NTSB ATL88LA122Accident · No injuriesLimited investigationFinal reportCessna 310Q · Donalsonville, GAThe pilot stated that he had experienced prior brake problems and had repeated maintenance performed. He further stated that not all of the brake problems had been corrected. After landing the pilot noticed that the right brake seemed 'spongy'. He continued…NTSB FTW84LA360Accident · No injuriesLimited investigationFinal reportCessna 310Q · Amarillo, TXDuring gear retraction on post-maintenance check flight initial climb, gear unlocked light remained on and gear extend/retract motor circuit breaker popped. Plt reset cb and heard a 'loud pop' from the nose section of the acft. Plt then extended gear but nose…NTSB SEA83LA174Accident · No injuriesLimited investigationFinal reportCessna 310Q · Spokane, WAWhile landing with a slight left x-wind, the plt purposely touched down on the left main gear first. Momentarily after touching down on the other main wheel, the right gear collapsed. At first, the plt thought the right tire had blown out & corrective action…