NTSB investigations: Piper PA-31-310, OH
8 cases on aircraft the registry lists as Piper PA-31-310. 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
| 1977 | 2 |
|---|---|
| 1978 | 1 |
| 1979 | 2 |
| 1983 | 1 |
| 1989 | 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.\"eventStateOrRegion\" = 'OH' 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 ('7103102'))
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" = 'OH' 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 ('7103102'))
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 IAD01LA059Accident · Serious injuriesLimited investigationFinal reportPiper PA-31-310 · Uniontown, OHFuel exhaustion due to the pilot's failure to perform fuel calculations. A factor was the inboard fuel tank probes not being within the manufacturer's resistance limits, which resulted in inaccurate fuel gauges.NTSB ATL89FA066Accident · 1 fatalField investigationFinal reportPiper PA-31 · Springfield, OHFuel exhaustion precipatated by the inadequate fuel consumption calculations performed by the pilot, pressure from the company president to not carry excess fuel and improper in-flight planning/decisions by the pilot by not refueling enroute before fuel was…NTSB CHI83IA360Incident · No injuriesIncident investigationFinal reportPiper PA31-310 · Mount Vernon, OHOn final approach both engines failed. The pilot elected to land intentional gear up short of therunway. Less than 1 pint of fuel was found on board.NTSB CHI79FEI44Accident · No injuriesClosedPiper PA-31 · Sandusky, OHNTSB IAD79IA030Incident · No injuriesClosedPiper PA-31 · Cincinnati, OHNTSB CHI78FEK08Accident · No injuriesClosedPiper PA-31 · Bluffton, OHNTSB CHI78FEK03Accident · No injuriesClosedPiper PA-31 · Delaware, OHNTSB CHI77FA031Accident · Serious injuriesClosedPiper PA-31 · Worthington, OH