NTSB investigations: Piper PA-24-250
56 cases on aircraft the registry lists as Piper PA-24-250, where the sequence of events included Collision with terr/obj (non-CFIT). 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, newest first
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 ('7102404')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '470' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
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 ('7102404')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '470' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
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 WPR10FA239Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · Redmond, ORThe pilot's failure to maintain airspeed, which resulted in a stall and collision with terrain.NTSB CEN10LA216Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Madison, INThe pilot’s failure to maintain control of the airplane. Contributing to the accident was the pilot’s decision to conduct the flight with known physiological impairment and his use of unapproved sedating medication, both of which likely impaired his ability…NTSB CEN10CA221Accident · No injuriesData collectionFinal reportPiper PA-24-250 · West Chicago, ILThe pilot's failure to maintain directional control of the airplane during landing.NTSB WPR09FA192Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · San Diego, CAThe pilot's failure to maintain control during an en route cruise descent through multiple cloud layers, resulting in an in-flight breakup.NTSB DFW08FA212Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Yuma, COThe pilot's failure to maintain control of the airplane after an encounter with instrument meteorological conditions.NTSB SEA08CA152Accident · Minor injuriesData collectionFinal reportPiper PA-24-250 · Vernal, UTThe pilot's failure to verify the airplane's fuel quantity during his preflight, resulting in fuel exhaustion. Contributing to the accident was the presence of a vehicle on the road where the pilot executed his forced landing.