NTSB investigations: Piper PA-31-350, VA
8 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
| 1975 | 1 |
|---|---|
| 1976 | 1 |
| 1983 | 2 |
| 1985 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 2011 | 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.\"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 ('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" = '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 ('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 ERA11LA240Accident · Serious injuriesLimited investigationFinal reportPiper PA-31-350 · Richmond, VAThe pilot’s failure to maintain adequate airspeed during the initial climb, which resulted in an aerodynamic stall and subsequent impact with the ground.NTSB BFO92LA033Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Qioquinton, VAEngine failure due to fuel exhaustion because of an open crossfeed fuel line drain valve.NTSB BFO89FA075Accident · 5 fatalField investigationFinal reportPiper PA-31-350 · Lynchburg, VAPilot's failure to maintain clearance from obstructions because of improper IFR operation. Contributing to the accident was descent below decision height, delay in initiating the missed approach, and fog conditions.NTSB BFO85FA073Accident · No injuriesField investigationFinal reportPiper PA-31-350 · Norfolk, VAThe acft experienced a complete gear collapse after contacting a rwy light and a taxiway sign during a landing roll. Theflt departed la guardia arpt 230 lbs over the 7000 pld max gross weight of the acft and at least 1 inch aft of the center of gravity limit.…NTSB ATL83FA293Accident · Minor injuriesField investigationFinal reportPiper PA-31-350 · Richmond, VAThe plt made a forced landing following a power loss on an approach to Richmond, Virginia. The flt had been operating 4 hours, including 7 takeoffs, since refueling. After the accident both propellers were found in the feathered position. The right wing fuel…NTSB DCA83AA019Accident · Serious injuriesFinal reportPiper PA-31-350-T1020 · Fort Belvoir, VAOn a flt from newark, NJ to richmond, VA, the departure time was delayed, and subsequently, the acft did not arrive at richmond until after the refueling facilities were closed. The plt decided there was sufficient fuel aboard to complete the next flt to the…NTSB IAD77FA008Accident · 4 fatalClosedPiper PA-31 · Hampton, VANTSB IAD76II040Incident · No injuriesClosedPiper PA-31 · Chantilly, VA