NTSB investigations: Piper PA-24-250
13 cases on aircraft the registry lists as Piper PA-24-250, where NTSB found Not determined, general. 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 | 2 |
|---|---|
| 2013 | 1 |
| 2014 | 4 |
| 2015 | 2 |
| 2016 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 2022 | 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 ('7102404')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '05000000')))
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_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '05000000')))
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 CEN22LA102Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-24-250 · Grand Forks, NDFailure of the landing gear to properly extend before landing for reasons that could not be determined.NTSB ERA21FA333Accident · 2 fatalClass 3 · FieldFinal reportPiper PA24 · Wadesboro, NCA partial loss of engine power during takeoff for reasons that could not be determined. Contributing was the pilot’s loss of airplane control, resulting in an aerodynamic stall and impact with trees and terrain.NTSB WPR19LA239Accident · No injuriesClass 3 · LimitedFinal reportPiper PA24 · Wendover, UTFailure of the landing gear solenoid, which resulted in failure of the landing gear position switch, and the pilot's subsequent inability to extend the gear using the manual emergency extension system for undetermined reasons.NTSB CEN16LA132Accident · Minor injuriesLimited investigationFinal reportPiper PA24 · Kentland, INThe loss of engine power for reasons that could not be determined because postaccident examination of the airframe and engine did not reveal any mechanical anomalies that would have precluded normal operation. Contributing to the accident was the flight…NTSB ERA16LA061Accident · Minor injuriesLimited investigationFinal reportPiper PA-24 · Millville, NJThe total loss of engine power during initial climb for reasons that could not be determined because postaccident examination of the engine revealed no anomalies that would have precluded normal operation.NTSB CEN15LA444Accident · No injuriesLimited investigationFinal reportPiper PA 24-250 · New Orleans, LAThe collapse of the landing gear for reasons that could not be determined based on the available information.NTSB WPR15FA045Accident · 1 fatalField investigationFinal reportPiper PA 24-250 · Garberville, CAA loss of engine power for reasons that could not be determined due to extensive damage sustained during the collision and postaccident water immersion.NTSB ERA14LA325Accident · Minor injuriesLimited investigationFinal reportPiper PA 24-250 · Monroeville, ALA loss of engine power for reasons that could not be determined because postaccident examination of the engine and fuel system revealed no anomalies.NTSB WPR14LA099Accident · No injuriesLimited investigationFinal reportPiper PA 24-250 · San Jose, CAThe pilot’s failure to sump the fuel tanks, which resulted in water contamination, a partial loss of engine power during takeoff, and collision with a taxiing airplane during the subsequent forced landing.NTSB CEN14LA107Accident · No injuriesLimited investigationFinal reportPiper PA 24-250 · Silver City, NMThe collapse of the landing gear during landing for reasons that could not be determined during postaccident examinations.NTSB WPR14LA061Accident · Minor injuriesLimited investigationFinal reportPiper PA 24-250 · Fair Oaks, CAThe loss of engine power during cruise flight for reasons that could not be determined because postaccident examinations of the airplane and engine did not reveal any anomalies that would have precluded normal operation.NTSB DEN08CA144Accident · No injuriesData collectionFinal reportPiper PA-24-250 · Pine Bluff, ARLanding gear collapse for reasons undetermined.NTSB SEA08LA064Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Placerville, CAThe collapse of the right main landing gear during landing for undetermined reasons.