NTSB investigations: Piper PA-32R-300
16 cases on aircraft the registry lists as Piper PA-32R-300, where the first occurrence was “In flight collision with terrain/water”. 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
| 1982 | 1 |
|---|---|
| 1983 | 1 |
| 1985 | 1 |
| 1987 | 1 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 3 |
| 1995 | 2 |
| 1997 | 1 |
| 1999 | 1 |
| 2004 | 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\" = 230))
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" = 230))
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 LAX04FA102Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Big Pine, CAfailure of the pilot to maintain clearance with mountainous terrain for undetermined reasons.NTSB ANC99FA130Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Bettles, AKThe pilot's continued flight into known adverse weather conditions. Factors in the accident were low ceilings and snow.NTSB NYC97LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Lumberton, NJThe pilot's delay in initiating remedial action to arrest an excessive descent rate during a go-around. A crosswind condition was a contributing factor.NTSB ANC95FA101Accident · 6 fatalField investigationFinal reportPiper PA-32R-300 · Haines, AKThe pilot's failure to maintain an adequate altitude above and clearance from the surrounding terrain. A factor related to the accident was the pilot's improper decision to conduct the maneuver in such close proximity to the rising terrain.NTSB FTW95FA112Accident · 5 fatalField investigationFinal reportPiper PA-32R-300 · Conroe, TXThe pilot's failure to follow published IFR procedures. Factors were the weather conditions, the dark night, and the pilot's failure to activate the approach lighting system.NTSB SEA94FA040Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Spokane, WAThe pilot's failure to maintain proper alignment with the instrument landing system approach course. The pilot's failure to perform a missed approach was a factor.NTSB CHI94FA048Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Antigo, WIthe failure of the pilot in command to maintain proper altitude.NTSB ANC93FA134Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Atigun Pass, AKThe pilot-in-command's intentional VFR flight into instrument meteorological conditions and his unfamiliarity with the geographical area. Factors were the rain and fog.NTSB SEA92LA173Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Farmington, UTThe pilot's poor inflight decision. Factors include downdrafts and a box canyon.NTSB NYC91LA167Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Rhinebeck, NYThe pilot did not calculated the airplane's performance data to insure that he had enough runway to clear an obstacle at the end of the field, which resulted in the airplane's landing gear striking high hedges, subsequently the pilot elected to land in a…NTSB LAX91FA124Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Palm Springs, CAIncapacitation of the pilot due to inadequate sleep.NTSB CHI90FA236Accident · 7 fatalField investigationFinal reportPiper PA-32R-300 · Watertown, WIInitiation of VFR flight into adverse weather and instrument meteorologial conditions. Factors which contributed to the accident were the adverse weather conditions and the pilot's self-induced pressure to maintain currency.NTSB NYC87FA188Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Tannersville, NYWhile on a VFR air taxi cargo flight, the aircraft collided with trees on the east side of high peak mountain, elevation 3,655 feet. The accident site elevation was 3080 feet. A witness said it was heavy overcast, not raining and the clouds were not below the…NTSB DEN85FA153Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Melstone, MTThe acft was observed in a left turn in a steep dive until it passed out of view behind a hill. The investigation revealed no evidence of airframe or engine malfunction or failure piror to the crash. Medical findings revealed the plt, sole occupant, had 90…NTSB MIA83IA239Incident · No injuriesIncident investigationFinal reportPiper PA-32R-300 · Orlando, FLAcft made an intentional gear up landing after both normal & emergency procedures failed to lower the gear. It was determined that the hydraulic pump motor had failed. Normal & emergency systems were interdependent. The emergency gear diaphragm was blocked by…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…