Fatal NTSB investigations: Cessna T310Q
9 cases on aircraft the registry lists as Cessna T310Q. 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
| 1972 | 1 |
|---|---|
| 1973 | 1 |
| 1976 | 1 |
| 1980 | 1 |
| 1987 | 1 |
| 1992 | 1 |
| 2006 | 1 |
| 2015 | 1 |
| 2017 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074244'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('2074244'))
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 WPR17FA066Accident · 4 fatalField investigationFinal reportCessna T310Q · Riverside, CAThe pilot's failure to maintain airplane control upon entering instrument meteorological conditions, which resulted in the airplane exceeding its critical angle of attack and an aerodynamic stall. Contributing to the accident was the pilot's personal pressure…NTSB CEN15FA425Accident · 1 fatalField investigationFinal reportCessna T310Q · Wichita, KSThe separation of the attachment hardware connecting the elevator trim tab pushrod to the elevator trim actuator, which resulted in the elevator trim tab jamming in a position outside the limits of normal travel and a subsequent loss of airplane control.NTSB DFW07FA036Accident · 3 fatalField investigationFinal reportCessna 310Q · Waco, TXThe pilot's failure to maintain sufficient airspeed to avoid a stall during the instrument landing approach, which resulted in an inadvertent stall and collision with terrain. Also causal was the pilot's impairment due to prohibited drugs. Factors associated…NTSB MIA92FA121Accident · 3 fatalField investigationFinal reportCessna 310Q · Odessa, FLLoss of engine power on initial takeoff climb on all engines for undetermined reasons. This resulted in a forced landing, in flight collision with trees, terrain, and postcrash fire.NTSB LAX87FA156Accident · 2 fatalField investigationFinal reportCessna 310Q · Half Moon Bay, CAWhile flying northwest over water along the pacific coast on an IFR clnc, the plt rprtd to the sector controller (ctlr) 'we've got a problem.' The ctlr inquired about the nature of the problem. The plt then stated, 'going down fast, out of control.' The ctlr…NTSB CHI80FA059Accident · 2 fatalClosedCessna T310 · Cahokia, ILNTSB IAP76AI064Accident · 2 fatalClosedCessna 310Q · Ranelle, WVNTSB SEA73AS034Accident · 6 fatalClosedCessna T310Q · Cottage Grve, ORNTSB DEN72AD029Accident · 2 fatalClosedCessna 310Q · Lehi, UT