NTSB investigations: Piper PA-32R-300, MS
6 cases on aircraft the registry lists as Piper PA-32R-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
| 1981 | 1 |
|---|---|
| 1982 | 1 |
| 1985 | 1 |
| 1988 | 1 |
| 1994 | 1 |
| 2012 | 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 ('7103213'))
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 ('7103213'))
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 ERA12FA433Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · New Site, MSThe pilot's decision to operate into a known area of adverse weather, which resulted in the inadvertent penetration of a severe thunderstorm, a subsequent loss of control, and in-flight breakup of the airplane.NTSB MIA94FA069Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Vicksburg, MSFailure of the pilot-in-command to maintain the proper glidepath while on a straight in approach resulting in the inflight collision with trees short of the runway. Contributing to the accident was the dark night condition.NTSB MIA89LA039Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-300 · Holly Springs, MSThe plt stated that after he began a descent from 12,000 ft to 4000 ft, the acft lost all electrical power due to failure of the alternator. While apchg to land at Holly Springs arpt, the acft enctrd unfavorable winds & turbulence. Subsequently, it lost…NTSB ATL85FA146Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Dundee, MSPlt obtained three preflight wx briefings then filed IFR using an assumed name. Routine communications until 2117 CST when pilot reported in a cell and said he wanted to make a 180 degree turn. Cleared for right turn. Radar and comm contact with aircraft lost…NTSB ATL82FLT04Accident · 3 fatalFinal reportPiper PA-32R-300 · Iuka, MSThe aircraft crashed during a pass across the airport. A witness was parked, facing east, in the runup area for runway 18. According to him, the the aircraft took off about 6 minutes earlier, made a traffic pattern, and crashed behind and to his right. The…NTSB ATL81FA087Accident · 4 fatalClosedPiper PA-32R · Vicksburg, MS