NTSB investigations: Piper PA-30
13 cases on aircraft the registry lists as Piper PA-30, 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
| 2011 | 3 |
|---|---|
| 2012 | 1 |
| 2013 | 1 |
| 2014 | 1 |
| 2015 | 1 |
| 2018 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 2 |
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 ('7103002')
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 ('7103002')
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 WPR23LA013Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-30 · Tucson, AZThe pilot’s loss of control during landing for reasons that could not be determined based on the available evidence.NTSB WPR22LA313Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-30 · St Ignatius, MTA partial loss of power during takeoff for undetermined reasons.NTSB ERA22LA049Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Newport Richie, FLA loss of directional control on landing for undetermined reasons.NTSB ERA20LA272Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 30 · Alabaster, ALA loss of control and lack of climb performance shortly after takeoff for reasons that could not be determined based on available evidence, resulting in a collision with terrain.NTSB CEN19FA035Accident · 1 fatalField investigationFinal reportPiper PA 30 · Marion, INThe pilot's exceedance of the airplane's critical angle of attack following a loss of the left engine power shortly after takeoff, which resulted in an aerodynamic stall at an altitude too low for recovery. Contributing to the accident was the loss of left…NTSB ERA18LA171Accident · No injuriesLimited investigationFinal reportPiper PA 30 · Vero Beach, FLThe collapse of all three landing gear for reasons that could not be determined because postaccident examination of the landing gear system revealed no evidence of any mechanical malfunctions or failures that would have precluded normal operation.NTSB CEN15LA357Accident · Minor injuriesLimited investigationFinal reportPiper PA 30 · Clifton, TXThe pilot's failure to maintain control during a precautionary landing following a total loss of power to one engine. The reason for the loss of engine power could not be determined based on available information.NTSB WPR14LA298Accident · No injuriesLimited investigationFinal reportPiper PA 30 · Othello, WAThe partial loss of engine power for reasons that could not be determined based on the available information.NTSB CEN13LA361Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Dayton, OHThe pilot’s loss of control of the airplane for reasons that could not be undetermined because a postaccident examination of the airplane did not reveal any anomalies that would have precluded normal operation.NTSB WPR12LA366Accident · No injuriesLimited investigationFinal reportPiper PA-30 B · Scappoose, ORThe failure of the landing gear to fully extend as a result of a failure of the landing gear transmission assembly for reasons that could not be determined based on the available evidence.NTSB CEN11LA364Accident · Minor injuriesLimited investigationFinal reportPiper PA30 · Phillipsburg, OHThe pilot’s failure to maintain directional control during takeoff following a loss of left engine power for undetermined reasons.NTSB CEN11LA262Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Ruidoso, NMThe left engine's intermittent loss of power during initial climb for undetermined reasons. Contributing to the accident was the high density altitude at the time of the accident.NTSB WPR11LA113Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Big Bear City, CAThe pilot’s failure to maintain the minimum single-engine control speed while on final approach for landing. Contributing to the accident was the pilot's decision to fly with a known deficiency in one engine and a loss of power in that engine for reasons that…