NTSB investigations: Piper PA-28R-201
5 cases on aircraft the registry lists as Piper PA-28R-201, 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
| 1991 | 1 |
|---|---|
| 1998 | 1 |
| 2001 | 1 |
| 2005 | 1 |
| 2006 | 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 ('7102816', '7102833')
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 ('7102816', '7102833')
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 DEN06FA111Accident · 1 fatalField investigationFinal reportPiper PA-28R-201 · Salida, COthe pilot's inadequate preflight planning/preparation. Contributing factors in this accident were the pilot's lack of familiarity with the geographical area, his becoming lost/disoriented, his improper decision, the high density altitude, and the reduction in…NTSB IAD05FA052Accident · 2 fatalField investigationFinal reportPiper PA-28R-201 · Green Creek, NJThe flight crew's failure to maintain terrain clearance while executing a practice published instrument approach in night visual meteorological conditions. A factor in the accident was the dark night.NTSB CHI01FA089Accident · 4 fatalField investigationFinal reportPiper PA-28R-201 · Webb Lake, WIthe pilot not maintaining altitude/clearance from the trees during takeoff. Factors were the trees, transmission wire, and the dark night.NTSB NYC99LA014Accident · No injuriesLimited investigationFinal reportPiper PA-28R-201 · Mattituck, NYThe pilot's failure to maintain the airplane's directional control during a go-around.NTSB LAX92LA049Accident · No injuriesLimited investigationFinal reportPiper PA28R-201 · Gila Bend, AZThe animal on the runway. Contributing to this accident was separation of the right main landing gear due to overload and the dark night.