Fatal NTSB investigations: Piper PA-28R-200
12 cases on aircraft the registry lists as Piper PA-28R-200, 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
| 1986 | 1 |
|---|---|
| 1989 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 1998 | 2 |
| 2002 | 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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811')
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811')
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 FTW02FA262Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Chromo, COThe flight instructor's failure to maintain clearance with the mountainous terrain during the cross-country flight. A contributing factor was the dark night light conditions.NTSB LAX02FA255Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Echo Summit, CAThe pilot's decision to continue the flight into the rising mountainous terrain, and subsequent failure to maintain clearance with the trees. Contributing factors were the rising mountainous terrain, and the high density altitude,NTSB LAX99FA028Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Bishop, CAThe failure of the pilot-in-command, after encountering a downdraft, to maneuver and maintain clearance from mountainous terrain. Physical impairment due to hypoxia was a factor in the accident.NTSB LAX98FA189Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · Lytle Creek, CAthe pilot's intentional VFR descent into instrument meteorological conditions, resulting in a collision with mountainous terrain.NTSB FTW97FA100Accident · 3 fatalField investigationFinal reportPiper PA-28-200 · Lone Wolf, OKthe pilot's impairment of judgment and performance due to drugs, his resultant improper planning/decision, and his failure to maintain sufficient altitude (clearance above a lake), while performing aerobatic flight. Factors relating to the accident were: the…NTSB SEA96FA170Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Libby, MTcollision with rising mountainous terrain for unknown reason(s).NTSB ATL95FA128Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Raleigh, NCThe pilot's failure to follow proper IFR procedures by descending below the decision height. Factors relating to the accident were the weather conditions and the dark night.NTSB BFO95FA020Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Nesquehoning, PAthe non-instrument-rated pilot's poor in-flight decision to continue VFR flight into instrument meteorological conditions, at night, and his failure to maintain sufficient altitude to ensure clearance from obstructions/terrain. Related factors were the…NTSB SEA93FA025Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Cedar City, UTClearance from mountainous terrain was not maintained. Factors to the accident were: dark night condition, snow showers, and intentional flight into known adverse weather.NTSB FTW91FA010Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Kingsland, TXThe pilot's failure to avoid flying into the mountain.NTSB LAX90FA031Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Camarillo, CAImproper IFR procedure by the pilot, and his failure to maintain the minimum descent altitude (mda) for that segment of the VOR approach. Factors related to the accident were: darkness, low ceiling, fog, haze, the pilot's lack of recent instrument experience,…NTSB BFO87FA004Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Mount Pleasant, MDThe acft was on the second apch attempt for ILS rwy 23 when the accident occurred- on the first attempt the pilot flew outbound instead of inbound on the localizer course. For the second attempt the pilot was cleared for a full apch for ILS rwy 23; which…