NTSB investigations: Piper PA-28-181, SD
6 cases on aircraft the registry lists as Piper PA-28-181. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1993 | 1 |
| 1999 | 1 |
| 2019 | 1 |
| 2024 | 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\" = 'SD' 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 ('7102807', '7102832'))
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" = 'SD' 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 ('7102807', '7102832'))
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 CEN24LA121Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-28-181 · Watertown, SDThe stuck No. 2 cylinder exhaust valve, which resulted in a partial loss of engine power and a forced landing due to an undersized exhaust valve guide. Contributing to the accident were the improper manufacture of the engine cylinders, and the operation of…NTSB CEN19LA053Accident · 1 fatalLimited investigationFinal reportPiper PA28 · Salem, SDThe incapacitating effects of an acute myocardial infarction (heart attack), which resulted in the pilot's loss of airplane control and impact with terrain.NTSB CHI99LA355Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Hermosa, SDthe pilot's improper fuel management, improper in-flight decision and the precautionary landing. Factors relating to this accident were the pilot's inadequate preflight planning and the fence post.NTSB CHI94LA024Accident · 1 fatalLimited investigationFinal reportPiper PA-28-181 · Woonsocket, SDthe pilot misjudging the airplane's clearance under the wires. Factors related to the accident were the performance of a low pass and the wires which were contacted.NTSB DEN83FTK04Accident · Serious injuriesFinal reportPiper PA-28-181 · Box Elder, SDBefore reaching his destination, the plt contacted apch control & reported that he was about 40 mi away & was low on fuel. About 10 min later, the acft ran out of fuel. The plt stated that he 'could possibly make ellsworth' but the controller told him that…NTSB DEN83FA001Accident · 1 fatalField investigationFinal reportPiper PA-28-181 · Wolsey, SDThe pilot had been issued an instrument rating on 8/6/82 and had logged 5.6 hrs since that time. The pilot's instructor believed this would have been his first low approach in actual instrument conditions since he completed his check flight. A witness stated…