NTSB investigations: Piper PA-34-200T, ID
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
| 1981 | 1 |
|---|---|
| 1982 | 1 |
| 1990 | 1 |
| 1994 | 1 |
| 2007 | 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\" = 'ID' 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" = 'ID' 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 LAX07CA243Accident · No injuriesData collectionFinal reportPiper PA-34-200T · Big Creek, IDThe pilot's misjudgment of distance and speed, which led to a long landing, and his delayed application of brakes that resulted in long landing and a runway overrun.NTSB SEA94LA206Accident · Minor injuriesLimited investigationFinal reportPiper PA-34-200T · Salmon, IDThe pilot's failure to adequately judge the distance and altitude to the runway during the night VFR approach. Factors in the accident were: fatigue, lack of recent night flying experience, the dark night, and the operator's inadequate supervision of the…NTSB SEA91FA020Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Albion, IDThe pilot-in-command's failure to maintain control of the airplane in instrument meteorological conditions. Factors which contributed to the accident were the pilot's apprehension of flying in the forecasted weather, and the adverse weather conditions…NTSB SEA82FA122Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · 10 Nm E. Of Ken, IDThe plt declared an emergency & reported out of fuel. While approaching a field the plt observed a power/telephone line in his flt path & instinctively pulled the nose up. On-scene examination revealed no evidence of fuel.NTSB SEA81FA047Incident · No injuriesClosedPiper PA-34 · Boise, ID