NTSB investigations: Piper PA-28R-200, CA
5 cases on aircraft the registry lists as Piper PA-28R-200, where the first occurrence was “Loss of engine power(total) - mech failure/malf”. 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 |
|---|---|
| 1991 | 2 |
| 1993 | 1 |
| 1994 | 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\" = 'CA' 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 ('7102811')
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\" = 351))
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" = 'CA' 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 ('7102811')
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" = 351))
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 LAX94FA308Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · San Luis Obispo, CAthe failure of the No. 4 cylinder connecting rod for undetermined reasons. The dark night lighting conditions, which hampered the ability of the pilots to detect the power lines, was a factor in this accident.NTSB LAX93LA229Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Hesperia, CAFatigue failure of the exhaust valve due to inadequate maintenance and inspection.NTSB LAX91LA382Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Redwood City, CAThe fatigue failure of the number two connecting rod and rod cap due to an engine overspeed condition which the rods and rod caps were exposed at some undetermined historical point.NTSB LAX91LA314Accident · No injuriesLimited investigationFinal reportPiper PA28R-200 · So. Lake Tahoe, CAEngine failue due to the failure of the crankshaft resulting from failure induced by a non-metallic inclusion in the shaft.NTSB LAX89FA032Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Anaheim, CAFive minutes after departure and during normal cruise flight, the certified flight instructor noticed a prop overspeed. He immediately pulled back on the prop control to reduce engine r.p.m. and instructed the student, a private pilot, to divert to the…