NTSB investigations: Cessna 310R
5 cases on aircraft the registry lists as Cessna 310R, where the first occurrence was “In flight encounter with weather”. 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 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 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 ('2074245')
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\" = 240))
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 ('2074245')
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" = 240))
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 CHI93LA077Accident · Minor injuriesLimited investigationFinal reportCessna 310R · Minocqua, WIThe pilot's failure to properly align the aircraft with the landing area.NTSB ATL92FA091Accident · 1 fatalField investigationFinal reportCessna 310R · Gatlinburg, TNThe pilot's continued VFR flight into IMC, and his failure to attain a proper altitude over high, mountainous terrain. Factors were the high terrain, and the fog, clouds, and obscuration at the accident site.NTSB NYC90LA159Accident · No injuriesLimited investigationFinal reportCessna 310R · Hyannis, MAA hard landing due to the pilot stalling the airplane during the landing flare. Contributing to this accident was gusty wind conditions.NTSB MIA84FA090Accident · 1 fatalField investigationFinal reportCessna 310R · St. Petersburg, FLPrior to departure the plt noticed thunderstorms & lightning to the north of the arpt. He stated that immediately after takeoff he remembered a flash of light & a noise. His next recollection is impact & being in the water. The area around St. Petersburg at…NTSB ATL83FA128Accident · 3 fatalField investigationFinal reportCessna 310 · Hopkinsville, KYThe plt obtained a wx briefing & filed a flt plan from lexington to paducah,KY with a 15 min en route stop at bowling green, KY. While inbound to bowling green, he reported that the cloud base was at aprx 6000 ft & that there was lightning to the west. After…