NTSB investigations: Piper PA-32-300, MD
6 cases on aircraft the registry lists as Piper PA-32-300. 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
| 1982 | 1 |
|---|---|
| 1987 | 1 |
| 1989 | 2 |
| 1996 | 1 |
| 2012 | 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\" = 'MD' 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 ('7103212'))
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" = 'MD' 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 ('7103212'))
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 ERA13CA079Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Easton, MDThe pilot's failure to maintain directional control while landing.NTSB IAD97FA001Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Brandywine, MDThe pilots failure to maintain his assigned altitude in IFR conditions. A related factor was the failure of the radar controller to prevent the descent of N2881W to an altitude below the minimum vectoring altitude. Additionally, the controller's failure to…NTSB BFO89FA058Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Libertytown, MDContinued VFR flight by the non-instrument rated pilot into instrument meteorological conditions (IMC), which resulted in the pilot's loss of aircraft control due to disorientation, and overload failure of the wings and stabilator due to the pilot exceeding…NTSB BFO89FA043Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Myersville, MDContinued flight by the pilot into instrument meteorological conditions (IMC) and his inability to maintain control of the aircraft after becoming spatially disoriented. Contributing factors were hilly/mountainous terrain, weather conditions, the pilot's lack…NTSB BFO88LA018Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Churchton, MDThe plt rprtd that after searching unsuccessfully for a wind sock & getting no reply on UNICOM freq, he made an apch to rwy 16. Later, he saw the wind sock about half way down the rwy near a building. Drg the apch, he noticed he was high & put the acft in a…NTSB ATL82DA193Accident · Minor injuriesFinal reportPiper PA-32-300 · Westminster, MDWhile on a cross-country flight, the pilot elected to make an unscheduled stop at a unfamiliar airport to check the en route weather. He circled the airport and thought the wind indicated favored runway 31, but later, he found that the wind was calm. No…