NTSB investigations: Piper PA-31-310, TX
8 cases on aircraft the registry lists as Piper PA-31-310. 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
| 1970 | 1 |
|---|---|
| 1974 | 2 |
| 1977 | 1 |
| 1982 | 1 |
| 1984 | 1 |
| 1988 | 1 |
| 2011 | 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\" = 'TX' 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 ('7103102'))
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" = 'TX' 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 ('7103102'))
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 CEN11LA574Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-310 · Perryton, TXThe explosion and subsequent fire in the airplane for undetermined reasons because an examination of the burned airplane could not identify any preaccident anomolies.NTSB FTW89FA007Accident · No injuriesField investigationFinal reportPiper PA-31-350 · Edinburg, TXAcft experienced a double eng failure. Plt stated that immediately after the left eng failed, in climb to cruise, the acft rolled left, the stall warning activated, and the acft entered a left spiral. The rt eng failed during the two-turn spiral. Plt's…NTSB FTW84LA138Accident · Minor injuriesLimited investigationFinal reportPiper PA-31 · Brownsville, TXThe plt was maneuvering for an ILS approach when he collided with the ground. He said he was distracted by the swinging CDI and was below the glide slope. He said he started to add power for a missed approach and the acft impacted the ground. A passenger said…NTSB FTW82FRG21Accident · 1 fatalFinal reportPiper PA-31 · Port Mansfield, TXThe aircraft crashed and burned about 1/2 mile from the approach end of runway 12. A witness reported that "the plane just fell" while the pilot was making a sharp turn. An estimated 1500 lbs of marijuana was on board.NTSB FTW77DA032Accident · No injuriesClosedCessna 172 · Dallas, TXNTSB FTW74FRG94Accident · No injuriesClosedPiper PA-31 · D'Hanis, TXNTSB FTW74FPA20Accident · No injuriesClosedPiper PA-31 · Dallas, TXNTSB FTW71DQG41Accident · No injuriesClosedPiper PA-31 · Midland, TX