NTSB investigations: Piper PA-32-300, MO
18 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
| 1972 | 1 |
|---|---|
| 1974 | 2 |
| 1975 | 1 |
| 1976 | 1 |
| 1979 | 1 |
| 1980 | 1 |
| 1985 | 1 |
| 1989 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 2 |
| 2004 | 1 |
| 2015 | 1 |
| 2023 | 2 |
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\" = 'MO' 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" = 'MO' 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 CEN24LA039Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA32 · Ozark, MOA reported total loss of engine power for undetermined reasons.NTSB CEN23LA415Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Moberly, MOThe flight instructor’s inadequate fuel management that resulted in fuel starvation and a total loss of engine power during an approach for landing.NTSB CEN15FA268Accident · 1 fatalField investigationFinal reportPiper PA 32 · Cuba, MOThe pilot's continued flight into thunderstorm activity, which resulted in his loss of airplane control, the exceedance of the airplane's design limits, and its subsequent in-flight breakup. Contributing to the accident was the pilot's reliance on onboard…NTSB CHI04FA205Accident · 5 fatalField investigationFinal reportPiper PA-32-300 · Point Lookout, MOThe pilot's failure attain adequate flying speed and his delay in aborting the takeoff which resulted in premature liftoff and an overrun of the runway. Contributing factors were the descending embankment, trees and ravine.NTSB CHI95LA300Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Osage Beach, MOthe student pilot's misjudgement of distance and speed during the landing and failure to attain the proper touchdown point.NTSB CHI95FA226Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Festus, MOan improper annual inspection, the fouled spark plugs, the arcing magneto distributor, and the pilot's attempt to take off with known deficiencies.NTSB CHI94LA265Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Richmond, MOa loss of engine power due to fuel starvation, reason undetermined.NTSB CHI93LA048Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Shell Knob, MOThe pilot's misjudging of the landing flare.NTSB CHI91LA164Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · St. Charles, MOThe pilot's failure to maintain directional control of the airplane during the takeoff ground run. Factors related to the accident were the gusty crosswind conditions, the pilot's lack of total experience and the vehicles which the airplane contacted.NTSB MKC89LA152Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Excelsor Sprgs, MOThe catastrophic failure of the aircraft engine and the pilots failure to maintain directional control of the aircraft during the landing roll. Improper maintenance, the dark night conditions, and restricted visibility due to oil on the windscreen were…NTSB MKC85LA147Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Point Lookout, MOWhile landing at dusk, the acft touched down hard & both main gear collapsed rearward. A wing fuel tank was punctured, but no fire erupted.NTSB MKC80DCA06Accident · No injuriesClosedPiper PA-32 · Festus, MONTSB MKC79DCG40Accident · Minor injuriesClosedPiper PA-32 · Excelsior Spgs, MONTSB MKC76FCA18Accident · Minor injuriesClosedPiper PA-32 · Fenton, MONTSB MKC75FCG39Accident · No injuriesClosedPiper PA-32 · Macon, MONTSB MKC75DCG18Accident · No injuriesClosedPiper PA-32 · Boonville, MONTSB MKC74FGA18Accident · No injuriesClosedPiper PA-32 · Jefferson City, MONTSB MKC72AK063Accident · No injuriesClosedPiper PA-32 · Poplar Bluff, MO