NTSB investigations: Piper PA-30
6 cases on aircraft the registry lists as Piper PA-30, where the defining event was Loss of engine power (total). 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 | 1 |
|---|---|
| 2012 | 1 |
| 2015 | 1 |
| 2020 | 1 |
| 2021 | 1 |
| 2026 | 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 ('7103002')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e.\"isDefiningEvent\" AND e.\"tier2Number\" = '341'))
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_events.parquet' e WHERE e.case_mkey = x.case_mkey AND e.aircrafts_position = x.position AND e."isDefiningEvent" AND e."tier2Number" = '341'))
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 WPR26LA163Accident · Minor injuriesClass 3 · LimitedPreliminary reportPiper PA30 · Auburn, WAOn April 18, 2026, about 1330 Pacific daylight time, a Piper PA-30 Twin Comanche, N741TJ, was substantially damaged when it was involved in an accident near Auburn, Washington. The pilot and pilot-rated passenger sustained minor injuries. The airplane was…NTSB GAA21WA137Accident · No injuriesClass 4 · ForeignPiper PA-30 · Courcelles-sur-Viosnes, FranceNTSB WPR20LA223Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 30 · Vaughn, NMThe total loss of power in the right engine due to fuel starvation. Contributing to the accident was the pilot’s failure to follow the manufacturer-recommended procedure after the loss of power in the right engine.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 CEN12LA512Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Bragg City, MOThe pilot's failure to properly tighten the b-nut from the engine-driven fuel pump to the fuel-metering unit during maintenance, which resulted in a total loss of engine power due to fuel starvation.NTSB LAX08LA107Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Holbrook, AZA total loss of engine power due to fuel starvation as a result of the pilot's fuel system mismanagement and incorrect positioning of the fuel selector valves.