NTSB investigations: Piper PA-32-300, CT
9 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
| 1977 | 1 |
|---|---|
| 1978 | 1 |
| 1979 | 1 |
| 1984 | 1 |
| 1989 | 2 |
| 1996 | 1 |
| 2011 | 1 |
| 2025 | 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\" = 'CT' 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" = 'CT' 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 ERA25LA215Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA32-300 · Branford, CTMaintenance personnel's improper installation and inspection of the crankshaft gear bolt during major overhaul, which resulted in the crankshaft gear disengaging from the accessory gears which led to a total loss of engine power.NTSB ERA11CA365Accident · Serious injuriesData collectionFinal reportPiper PA-32-300 · Bridgeport, CTThe pilot's failure to maintain clearance from a blast fence on final approach to land.NTSB NYC96LA064Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Stratford, CTinadequate visual lookout by the pilot and the vehicle operator, resulting in their failure to see and avoid each other.NTSB NYC90FA011Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Glastonbury, CTThe pilot-in-command's failure to maintain adequate altitude control during maneuvering flight. Contributing to the accident was the failure of the airplane's electrical system and the pilot's operation at night, without emergency lighting (flashlight).NTSB NYC89LA169Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Danbury, CTThe pilot's misjudgement of (excessive) airspeed, his failure to attain the proper touchdown point, and failure to make a go-around, while there was sufficient runway remaining. The fence was a related factor.NTSB NYC85LA021Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Oxford, CTAfter entering the traffic pattern for the selected runway, plt was informed of surface wind conditions and elected to continue and execute a downwind landing. Upon touchdown, plt raised flaps to assist braking action. During roll-out the plt decided…NTSB NYC79FNE10Accident · Minor injuriesClosedPiper PA-32 · Danielson, CTNTSB NYC78FNE09Accident · No injuriesClosedPiper PA-32 · Meriden, CTNTSB NYC77FNE09Accident · No injuriesClosedPiper PA-32 · Plainville, CT