NTSB investigations: Piper PA-28R-200, CA
6 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
| 1983 | 1 |
|---|---|
| 1989 | 1 |
| 1992 | 1 |
| 1998 | 2 |
| 2002 | 1 |
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.\"eventStateOrRegion\" = 'CA' 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 ('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."eventStateOrRegion" = 'CA' 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 ('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 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 LAX92LA398Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Avalon, CAThe pilot's intentional flight at an altitude which provided insufficient clearance from the water.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 LAX84LA027Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-200 · San Diego, CAAfter departing north island nas (naval air station), the plt attempted to change frequencies, but the megahertz (mhz) tuning knob came off at a setting of 122.1 mhz. He could still use the knob for tuning tenths of a mhz, so he contacted San Diego fss on…