NTSB investigations: Piper PA-34-200T, OH
5 cases on aircraft the registry lists as Piper PA-34-200T. 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
| 1979 | 1 |
|---|---|
| 1984 | 1 |
| 1995 | 1 |
| 2003 | 1 |
| 2008 | 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 ('7103406'))
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 ('7103406'))
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 CHI08CA140Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Sandusky, OHThe pilot misjudging the flare and not maintaining airspeed during the landing.NTSB IAD03FA069Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Galion, OHThe pilot's improper in-flight decision making and flight into known adverse weather conditions while maneuvering to land. Also causal was the pilot's failure to regard the pre-flight weather briefing. Factors were the thunderstorm, rain, wind gusts and hail.NTSB BFO95LA029Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · London, OHthe loss of engine power (both engines, cause undetermined) shortly after lift off. Related factors are the foggy, dark night conditions, and the unsuitable terrain encountered during the subsequent forced landing.NTSB CHI84LA325Accident · No injuriesLimited investigationFinal reportCessna 182-C · Akron, OHA Cessna 182 on takeoff on rwy 19 collided with a Piper PA34 landing on rwy 25. Each plts view of the other was obstructed by airport parking at one point during the mishap. The airport tower was closed. The pilot of the Cessna left the UNICOM frequency for…NTSB CHI80FEI09Accident · No injuriesClosedPiper PA-34 · Youngstown, OH