NTSB investigations: Piper PA-34-200T
5 cases on aircraft the registry lists as Piper PA-34-200T, where NTSB found Performance/control parameters, general. 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
| 2008 | 1 |
|---|---|
| 2013 | 1 |
| 2014 | 1 |
| 2018 | 2 |
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 ('7103406')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '01062000')))
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 ('7103406')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '01062000')))
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 ERA19LA012Accident · 3 fatalLimited investigationFinal reportPiper PA34 · Westhampton Beach, NYThe instructor's decision to conduct and continue a visual flight rules flight into instrument meteorological conditions with a known flight instrument anomaly, which resulted in spatial disorientation, causing a loss of airplane control and subsequent…NTSB ERA18FA148Accident · 1 fatalField investigationFinal reportPiper PA34 · Bennington, VTThe pilot's improper decision to attempt a visual flight rules flight in instrument meteorological conditions, which resulted in a loss of control during a turn.NTSB CEN15FA087Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Port Huron, MIThe pilot’s decision to continue flight below the minimum descent altitude without visually acquiring the runway and his delayed and improperly executed missed approach procedure in instrument meteorological conditions.NTSB ERA13FA253Accident · 3 fatalField investigationFinal reportPiper PA-34-200T · Johnstown, NYThe pilot's loss of control due to spatial disorientation in instrument meteorological conditions, which resulted in an exceedance of the airplane's design stress limitations, and a subsequent in-flight breakup.NTSB ERA09CA104Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Tallahasee, FLThe pilot's failure to maintain aircraft control after touchdown. Contributing to the accident were the gusting winds.