NTSB investigations: Piper PA-23-250, MS
6 cases on aircraft the registry lists as Piper PA-23-250. 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 |
|---|---|
| 1976 | 1 |
| 1982 | 1 |
| 1988 | 1 |
| 1995 | 1 |
| 2006 | 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\" = 'MS' 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 ('7102308'))
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" = 'MS' 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 ('7102308'))
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 DFW06LA207Accident · Minor injuriesLimited investigationFinal reportPiper PA-23-250 · Newton, MSThe total loss of engine power due to fuel contamination. A factor was the pilot's inadequate preflight inspection.NTSB MIA95LA170Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Winstonville, MSPoor preflight planning/preparation and clearance not maintained by the pilot in command.NTSB MIA89LA013Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Tupelo, MSThe operator had applied for an on-demand/air taxi cert, but had not obtained approval. After lvl-off on a flt to carry canceled checks, the plt elected to use the remaining fuel fm the inbd tanks. He stated that soon thereafter, the left eng bgn running…NTSB ATL82FKQ10Accident · 1 fatalFinal reportPiper PA-23-250 · Mccomb, MSBefore taking off from jackson, MS, the pilot received a weather briefing by radio and filed an IFR flight plan to Mccomb, MS. During arrival at Mccomb, the weather was IFR with an indefinitely obscured ceiling at zero ft, visibility 1/2 mile in fog, wind 160…NTSB MIA76AM105Accident · 1 fatalClosedPiper PA-23 · Clarksdale, MSNTSB MIA71AM048Accident · 3 fatalClosedPiper PA-23 · Belzoni, MS