NTSB investigations: Piper PA-28R-200
5 cases on aircraft the registry lists as Piper PA-28R-200, where the defining event was Powerplant sys/comp malf/fail. 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
| 2008 | 1 |
|---|---|
| 2011 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2023 | 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 ('7102811')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '340'))
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 ('7102811')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e."isDefiningEvent" AND e."tier2Number" = '340'))
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 ERA23LA144Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-28R-200 · Slaughters, KYMaintenance personnel’s failure to secure the fuel strainer bowl with safety wire, which resulted in the fuel strainer bowl leaking and starving the engine of fuel. Also causal was the obstruction of two fuel injector nozzles.NTSB CEN16LA227Accident · No injuriesLimited investigationFinal reportPiper PA 28R-200 · Bowie, TXThe inadequate maintenance and inspection of the throttle control arm, which resulted in its in-flight separation and the subsequent loss of engine power.NTSB CEN15LA270Accident · No injuriesLimited investigationFinal reportPiper PA28-200 · Jonesboro, ARMaintenance personnel's improper engine oil drain valve installation, which led to engine oil exhaustion and the subsequent loss of engine power after takeoff at an altitude too low for the pilot to execute a forced landing in a suitable area.NTSB CEN12FA025Accident · No injuriesField investigationFinal reportPiper PA-28R-200 · Watertown, WIThe separation of the number 2 connecting rod from the crankshaft for reasons that could not be determined during postaccident metallurgical examination, which ultimately resulted in a total loss of engine power.NTSB NYC08LA086Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-R200 · York, SCLoss of engine power due to improper welding of the crankcase, which resulted in fatigue failure of the through-studs and a subsequent separation of the number two cylinder. Contributing to the accident was the unsuitable terrain for a forced landing.