NTSB investigations: Piper PA-28RT-201, CA
7 cases on aircraft the registry lists as Piper PA-28RT-201. 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
| 1981 | 1 |
|---|---|
| 1982 | 1 |
| 1990 | 2 |
| 1997 | 1 |
| 2005 | 1 |
| 2011 | 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.\"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 ('7102818'))
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 ('7102818'))
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 WPR11FA182Accident · 1 fatalField investigationFinal reportPiper PA-28RT · Cherry Valley, CAThe pilot’s continued flight in an area of low ceiling and visibility, which resulted in a collision with mountainous/hilly terrain.NTSB LAX06CA038Accident · No injuriesData collectionFinal reportPiper PA-28RT-201 · Bakersfield, CAthe pilot's failure to maintain adequate airspeed, which resulted in an accelerated stall and hard landing.NTSB LAX97FA272Accident · 3 fatalField investigationFinal reportPiper PA-28RT-201 · Hesperia, CAfailure of the pilot to see-and-avoid high voltage power lines, while coping with a lack of engine power during a go-around in a high density altitude condition. Factors relating to the accident were: high density altitude that resulted in a normal reduction…NTSB LAX90FA292Accident · 4 fatalField investigationFinal reportPiper PA-28RT-201 · Long Beach, CAThe inadequate visual outlook of the pilots of the Cessna 172P and their failure to see and avoid the Piper pa- 28RT-201. Contributing to the accident was the azimuth and angle of the sun which was in a position at the time of the accident to impair the scan…NTSB LAX90LA089Accident · No injuriesLimited investigationFinal reportPiper PA-28RT-201 · Napa, CAThe student pilot's failure to maintain directional control after landing.NTSB LAX82FYM18Accident · No injuriesFinal reportPiper PA-28RT-201 · San Carlos, CAAfter landing at the airport, the pilot taxied to the transient parking area, parked and got a cup of coffee. He stated that he then made a quick preflight check, but did not visually inspect the fuel tanks. During the takeoff, the engine began to surge at…NTSB LAX81FUG19Accident · No injuriesClosedPiper PA-28R · Rancho, CA