NTSB investigations: Piper PA-31-350, NV
6 cases on aircraft the registry lists as Piper PA-31-350. 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
| 1978 | 1 |
|---|---|
| 1985 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2008 | 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.\"eventStateOrRegion\" = 'NV' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103110', '7103125'))
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."eventStateOrRegion" = 'NV' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103110', '7103125'))
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 LAX08FA286Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Las Vegas, NVA loss of power in the right engine due to an in-flight fuel-fed fire in the right engine compartment that, while the exact origin could not be determined, was likely related to the right engine-driven fuel pump, its fuel supply line, or fitting. Contributing…NTSB LAX01FA201Accident · No injuriesField investigationFinal reportPiper PA-31-350 · North Las Vegas, NVfatigue failure of the right main landing gear retraction arm.NTSB LAX00LA277Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Boulder City, NVThe fatigue fracture and separation of the No. 6 cylinder fuel injector line due to the company maintenance personnel's failure to comply with an Airworthiness Directive. A factor in the accident was the company's decision to operate the aircraft in…NTSB LAX00FA014Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · North Las Vegas, NVThe failure of the pilot-in-command to maintain separation from terrain while operating under visual flight rules. Contributing factors were the improper issuance of a suggested heading by air traffic control personnel, inadequate flight progress monitoring…NTSB SEA86LA008Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Panaca, NVA forced landing onto rough terrain was made due to fuel exhaustion.NTSB UNK78X0134Accident · 10 fatalClosedPiper PA-31 · Las Vegas, NV