NTSB investigations: Piper PA-23-250, OR
7 cases on aircraft the registry lists as Piper PA-23-250. 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
| 1966 | 1 |
|---|---|
| 1977 | 1 |
| 1978 | 1 |
| 1984 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 2013 | 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.\"eventStateOrRegion\" = 'OR' 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 ('7102308'))
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" = 'OR' 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 ('7102308'))
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 WPR13LA154Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Hillsboro, ORA runway overrun due to an insufficient stopping distance due to the downsloping runway during a rejected takeoff. Contributing to the accident was a cabin door that inadvertently opened during the takeoff roll.NTSB SEA93FA084Accident · 4 fatalField investigationFinal reportPiper PA-23-250 · Estacada, ORFailure of the pilot to maintain proper clearance (and/or altitude) from moutainous terrain. Factors related to the accident were: darkness, clouds, low ceilings, and the high (mountainous) terrain in the area of the accident site.NTSB SEA90LA153Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Burns, ORLoss of engine power due to a blocked fuel line and the operation of the aircraft in an non-airworthy condition by the PIC.NTSB SEA85LA018Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Aurora, ORThe acft caught fire during start. The FAA inspectors said that AD 72-11-01 had not been followed in compliance.NTSB SEA78FA018Accident · 6 fatalClosedPiper PA-23 · Medford, ORNTSB SEA77FA017Accident · 1 fatalClosedPiper PA-23 · Moro, ORNTSB SEA66F0267Accident · No injuriesClosedPiper PA-23 · Portland, OR