NTSB investigations: Piper PA-34-220T
4 cases on aircraft the registry lists as Piper PA-34-220T, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1985 | 1 |
|---|---|
| 1987 | 1 |
| 2001 | 1 |
| 2005 | 1 |
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\" = 130))
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" = 130))
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 MIA05IA132Incident · No injuriesIncident investigationFinal reportPiper PA-34-220T · Titusville, FLThe pilot's continued operation of the airplane with known intermittent deficiencies of the electric pitch trim switch, resulting in a mis-trim condition of the airplane (nose-up), and subsequent hard landing on the nose landing gear causing it to collapse. A…NTSB DEN01LA062Accident · No injuriesLimited investigationFinal reportPiper PA-34-220T · Durango, COthe pilot's failure to maintain directional control. A contributing factor was the blown tire.NTSB NYC87LA185Accident · No injuriesLimited investigationFinal reportPiper PA-34 · Southbridge, MADuring landing roll, a failure of a tire tube caused a flat tire and control of the aircraft was lost. When the tire was dismantled, the inner tube was found to be defective at the joint seam. Total time on the acft and tire WAS407 hrs. The acft had a 100 hr…NTSB FTW85FA131Accident · 4 fatalField investigationFinal reportPiper PA-34-220T · Stigler, OKThe plt filed a VFR flt plan after the wx improved from IFR to VFR with a chance of thunderstorms en route. Ocnl mod turbulence below 5000 ft was forcast due to strong/gusty low lvl wnds. While the acft was en route, a gnd witness heard the engs rev up more…