NTSB investigations: Piper PA-34-220T
5 cases on aircraft the registry lists as Piper PA-34-220T, where the first occurrence was “Loss of engine power”. 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
| 1992 | 1 |
|---|---|
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 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 ('7103420', '7103223')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 350))
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 ('7103420', '7103223')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 350))
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 LAX03LA302Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Show Low, AZThe pilot-in-command's (CFI) selection of the wrong runway (downwind) for the approach and landing. The failure of the left engine to respond to throttle application for undetermined reasons during the go-around was also causal. The high density altitude was…NTSB IAD03LA064Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Burnet, TXThe pilot's failure to properly manage the airplane's fuel supply which led to the total loss of engine power, due to fuel starvation. A factor contributing to the accident was the presence of trees in the landing area used by the pilot to perform the…NTSB FTW03FA051Accident · 5 fatalField investigationFinal reportPiper PA-34-220T · McAlester, OKThe pilot's failure to maintain the airplane's minimum controllable airspeed during a single-engine go-around which resulted in his loss of control. Contributing factors to the accident included the loss of power from the left engine as a result of…NTSB CHI02LA052Accident · Minor injuriesLimited investigationFinal reportPiper PA-34 · Clinton, MOthe pilot's inadequate prefight, his failure to feather the propellers, and the fuel exhaustion.NTSB BFO92LA024Accident · No injuriesLimited investigationFinal reportPiper PA-34-200T · Columbus, OHFuel starvation in both engines, due to the pilot's improper positioning of the engine or fuel controls.