NTSB investigations: Piper PA-30
10 cases on aircraft the registry lists as Piper PA-30, where the first occurrence was “In flight collision with object”. 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
| 1985 | 1 |
|---|---|
| 1990 | 1 |
| 1993 | 3 |
| 1994 | 1 |
| 1998 | 1 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 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 ('7103002')
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\" = 220))
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 ('7103002')
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" = 220))
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 ATL04FA027Accident · 1 fatalField investigationFinal reportPiper PA-30 · Spartanburg, SCThe pilot's failure to follow IFR procedures and descent below the glide path, which resulted in an inflight collision with trees during an instrument approach. A factor was the pilot's impairment due to the sedating effects of medication.NTSB CHI02LA219Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Abilene, KSThe pilot failed to achieve clearance over the trees and wires. Factors associated with the accident were the pilot failed to use all available runway, a downwind takeoff was performed, the tailwind, trees, and wires.NTSB CHI01LA221Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Bowman, NDAltitude/clearance not obtained by the pilot during the initial climb. Factors relating to the accident were attaining the proper climb rate not being possible, the microburst, the dark night, and the tree.NTSB ATL98LA074Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Hendersonville, NCThe pilot's failure to attain the proper touchdown point and improper go-around procedures resulting in collision with wires, trees, and the ground. Factors were the pilot's lack of familiarity with the airplane and the short runway.NTSB BFO94LA153Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Wolfeboro, NHThe pilot's failure to maintain directional control during landing which resulted in inflight collission with trees.NTSB LAX94FA047Accident · 1 fatalField investigationFinal reportPiper PA-30 · Brea, CAThe pilot's choice of an inadequate cruise altitude over rolling hill terrain which resulted in an in-flight collision with helium balloons and an in-flight loss of control for undetermined reasons. A factor in the accident was the pilot's inadequate visual…NTSB NYC93LA132Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Mitchellville, MDThe failure of the pilot to maintain a proper glide path during the final approach, which resulted in the airplane striking a moving vehicle.NTSB DEN93LA037Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Eckert, COThe pilot-in-command's failure to maintain adequate clearance from the truck during the landing. Factors which contributed to the accident were: the pilot's poor judgement in attempting the operation, and the driver's poor judgement in not vacating all…NTSB MIA90IA072Incident · No injuriesIncident investigationFinal reportPiper PA-30 · Tallahassee, FLProper glidepath not maintained.NTSB ATL85LA257Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Portland, TNThe plt made a visual aprch to the wrong airport & attempted to go-around. During the go-around the acft coll ided with trees on the departure end of the rwy.