NTSB investigations: Piper PA-30
13 cases on aircraft the registry lists as Piper PA-30, where NTSB found Use of equip/system. 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 |
| 2014 | 2 |
| 2016 | 2 |
| 2020 | 1 |
| 2021 | 1 |
| 2022 | 1 |
| 2023 | 2 |
| 2024 | 1 |
| 2025 | 1 |
Where
Latest 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\", '02063015')))
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", '02063015')))
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 WPR26LA007Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Gila Bend, AZThe pilot’s improper throttle input and failure to maintain aircraft control during landing.NTSB CEN25LA016Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Springfield, MOThe flight instructor’s inability to confirm landing gear position before landing due to the sun glare which resulted in gear up landing. Contributing to the accident was an undetected tripped circuit breaker for the landing gear and the inoperative gear…NTSB CEN23FA284Accident · 1 fatalClass 3 · FieldFinal reportPiper PA-30 · Sherman, TXThe pilot’s failure to maintain control during a forced landing following a loss of engine power. Contributing was the pilot’s failure to feather the left propeller following the loss of engine power.NTSB ERA23FA274Accident · 3 fatalClass 3 · FieldFinal reportPiper PA-30 · Claxton, GAThe flight crew’s improper fuel management, which resulted in the airplane’s right engine being starved of fuel and its subsequent total loss of power.NTSB ERA23FA067Accident · 2 fatalClass 3 · FieldFinal reportPiper PA-30 · Winston-Salem, NCContamination and/or misalignment of the regulator section of the right engine’s fuel servo, which resulted in excessive idle fuel flow and a total loss of engine power. Also causal was the pilot's failure to land immediately on the nearest runway at the…NTSB CEN22LA083Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-30 · Houston, TXThe instructed pilot and the flight instructor’s failure to extend the landing gear before landing resulting in a wheels up landing.NTSB 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 CEN16LA380Accident · Serious injuriesLimited investigationFinal reportPiper PA 30 · Mineral Wells, TXThe pilot's fuel mismanagement, which resulted in fuel starvation to both engines and their subsequent loss of engine power.NTSB ERA16LA092Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 30 · Dublin, GAThe pilot’s inadvertent retraction of the landing gear during the landing roll following a landing approach in gusting wind conditions.NTSB WPR14LA269Accident · Minor injuriesLimited investigationFinal reportPiper PA 30 · Kalispell, MTThe pilot’s inadequate preflight planning and checks, during which he failed to determine the quantity and distribution of the fuel, which resulted in the loss of right engine power during takeoff due to fuel starvation.NTSB WPR14LA169Accident · Minor injuriesLimited investigationFinal reportPiper PA30 - NO Series · Bullhead City, AZThe pilot's mismanagement of the throttle and propeller controls during the attempted go-around after encountering turbulence, which resulted in his failure to maintain adequate airspeed and climb rate and a subsequent forced landing and impact with terrain.…NTSB CEN12LA204Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Roanoke, TXThe pilot’s failure to follow the published emergency procedures to lower the landing gear following a loss of electrical power.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.