NTSB investigations: Piper PA-32-300, VA
11 cases on aircraft the registry lists as Piper PA-32-300. 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
| 1971 | 1 |
|---|---|
| 1975 | 1 |
| 1977 | 1 |
| 1978 | 2 |
| 1985 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 2007 | 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.\"eventStateOrRegion\" = 'VA' 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 ('7103212'))
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" = 'VA' 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 ('7103212'))
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 ERA22FA418Accident · 1 fatalClass 3 · FieldFinal reportPiper PA32 · Afton, VAA catastrophic engine failure due to oil starvation, which resulted in a total loss of engine power at night over mountainous terrain.NTSB NYC07LA104Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Richmond, VAThe improper installation of the right brake assembly by maintenance personnel.NTSB NYC92LA064Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Fredericksburg, VAThe failure of the pilot to maintain the proper glide path. Factors related to the accident were delayed remedial action by the pilot and night conditions.NTSB BFO89LA066Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Williamsburg, VAThe pilot's failure to maintain aircraft control by improperly flaring the airplane during the landing approach.NTSB BFO89FA012Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Meadows Of Dan, VAThe pilot conducted VFR flight into IMC because of inadequate inflight planning/decision. The aircraft experienced inflight brakup when the pilot was unable to maintain flight within the design stress limits of the aircraft.NTSB BFO85LA075Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Williamsburg, VAThe plt contacted the field on UNICOM frequency of 122.8 and was informed that the active rwy was 31, with wind from 040 degrees at 13 knots. The final approach was made with crab and power, but just prior to touchdown, the right wing lifted and the acft…NTSB IAD79FA010Accident · 4 fatalClosedPiper PA-32 · Melfa, VANTSB IAD78FA093Accident · No injuriesClosedPiper PA-32 · Norfolk, VANTSB IAD78FID02Accident · Serious injuriesClosedPiper PA-32 · Prospect, VANTSB IAD75FIA16Accident · No injuriesClosedPiper PA-32 · Warrenton, VANTSB NYC72FID16Accident · No injuriesClosedPiper PA-32 · Lynchburg, VA