NTSB investigations: Piper PA-34-200T, CT
4 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
| 1988 | 1 |
|---|---|
| 1990 | 1 |
| 1993 | 1 |
| 2002 | 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\" = 'CT' 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" = 'CT' 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 IAD02FA043Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Oxford, CTThe pilot's failure to follow the published instrument approach procedure. Factors were the night and low ceiling conditions.NTSB BFO93LA072Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Simsbury, CTLack of braking action from the right brake. The pilot's failure to attain the proper touchdown point was a related factor.NTSB NYC90LA089Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Bridgeport, CTThe pilot failed to maintain directional control during a crosswind landing.NTSB NYC88FA093Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Stratford, CTThe pilot and pilot-rated pax received vectors for multiple ILS approaches in deteriorating conditions. On the first attempt the aircraft passed over witnesses but was off course and not in a position to land. The second attempt was aborted before reaching…