NTSB investigations: Piper PA-32R-300
11 cases on aircraft the registry lists as Piper PA-32R-300, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 1 |
|---|---|
| 1985 | 2 |
| 1987 | 1 |
| 1988 | 1 |
| 1992 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 2 |
| 2005 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 130))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103213')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 130))
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 MIA05LA116Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fort Myers, FLInadequate maintenance and repair of the engine top cowling by company maintenance personnel, resulting in failure and separation of the cowling in flight.NTSB IAD97LA092Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Defiance, OHThe failure of a wheel rim due to overstress separation with no clear evidence initiating event.NTSB LAX97LA181Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Burbank, CAimproperly secured upper cowl fasteners by unknown person(s).NTSB CHI96FA314Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Medford, MNfailure of the pilot to maintain control of the airplane, due to spatial disorientation. Factors relating to the accident were: failure of the (primary) vacuum system and a restriction in the (standby) vacuum system.NTSB FTW95LA355Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Fayetteville, ARThe pilot's inability to extend the landing gear due to the failure of an emergency gear extension valve.NTSB CHI92LA160Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Round Lake, ILThe pilot-in-command's failure to follow emergency procedures, and the fire in the electrical system for reasons undetermined.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 LAX87LA245Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Tucson, AZAt the end of a business flt, the plt extended the landing gear and noted that the left main landing gear indicated that it was not down and locked. The plt activated the emergency landing gear extension which still indicated it was not down. While on final…NTSB CHI85LA286Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Appleton, WIAs the plt applied brakes during a full stop landing, the right brake failed. The plt then maneuvered the acft off the paved landing surface in an attempt to get it to roll to a stop. The right landing gear strut collapsed. The acft then slid into a fence and…NTSB ATL85IA132Incident · No injuriesIncident investigationFinal reportPiper PA-32R-300 · Marion, ALCruising at 4000 ft MSL when engine vibration occurred and became severe. Reduced throtte but roughness persisted. Unable to mntn altitude with 2000 RPM and 25 inches map. Made forced ldg in corn field. Nose ldg gr collapsed. Engine checked out okay. One…NTSB ATL84LA041Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Columbia, SCWhile en route, the acft's ammeter went to a zero reading, and subsequently, a complete electrical failure occurred. Prior to landing, the plt attempted to lower the landing gear by letting it freefall, in accordance with recommended procedures. The gear…