NTSB investigations: Piper PA-24
5 cases on aircraft the registry lists as Piper PA-24, where the first occurrence was “In flight collision with object”. 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
| 1983 | 1 |
|---|---|
| 1991 | 3 |
| 2002 | 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 ('7102402')
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\" = 220))
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 ('7102402')
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" = 220))
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 CHI03FA018Accident · 2 fatalField investigationFinal reportPiper PA-24 · Fond du Lac, WIThe pilot failed to maintain obstacle clearance from the power lines while on a night VFR approach. Factors to the accident included the dark night and the power lines.NTSB ATL92FA020Accident · 1 fatalField investigationFinal reportPiper PA-24 · Engelhard, NCThe spatial disorientation experienced by the pilot, and his inadvertent descent into the terrain. A factor was the dark, night lighting condition at the time of the accident.NTSB NYC91FA097Accident · 1 fatalField investigationFinal reportPiper PA-24-180 · Muncie Valley, PAThe pilot's attempt to maintain visual flight into known instrument meteorological conditions, resulting in a collision with trees. Factors related to the accident were: the pilot's failure to obtain a pre-flight weather briefing and his failure to maintain…NTSB CHI91LA074Accident · Serious injuriesLimited investigationFinal reportPiper PA-24 · Cabool, MOFailure of the pilot to maintain proper runway alignment during a go-around. Factors related to the accident were: darkness and the pilot's lack of understanding of the landing gear electrical system.NTSB ATL84LA048Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Clemson, SCThe pilot failed to lower the landing gear stating that he was distracted by an acft on the ground & diverted his attention from the landing checklist.